You will get a senior code review of your Go codebase with concrete improvements
Project details
You will get a thorough, senior-level review of your Go (Golang) codebase with concrete, prioritized improvements your team can act on. I am a Staff Backend Engineer with 20+ years building distributed systems and high-traffic Go services, and I review code the way I'd review a junior engineer's PR before it ships to production: directly and constructively.
This is the right fit if your team is shipping fast but worried about quality drift, you're about to scale a service and want a sanity check first, you're hiring more Go engineers and want a baseline of what good looks like, or you suspect there are bugs/perf issues you haven't found yet.
What you receive:
• File-by-file review covering concurrency, error handling, performance, security, testability, idiomatic Go style
• Findings tagged Critical / High / Medium / Low with concrete file references
• Prioritized recommendations with effort estimates
• Sample refactor PR or pseudocode for top issues (Advanced tier)
• 30 or 60 minute walkthrough call covering every finding
• One round of follow-up clarifications by message
I communicate clearly in English, Portuguese, and Spanish.
This is the right fit if your team is shipping fast but worried about quality drift, you're about to scale a service and want a sanity check first, you're hiring more Go engineers and want a baseline of what good looks like, or you suspect there are bugs/perf issues you haven't found yet.
What you receive:
• File-by-file review covering concurrency, error handling, performance, security, testability, idiomatic Go style
• Findings tagged Critical / High / Medium / Low with concrete file references
• Prioritized recommendations with effort estimates
• Sample refactor PR or pseudocode for top issues (Advanced tier)
• 30 or 60 minute walkthrough call covering every finding
• One round of follow-up clarifications by message
I communicate clearly in English, Portuguese, and Spanish.
Programming Languages
Python, Java, GoCoding Expertise
Performance Optimization, SecurityWhat's included
| Service Tiers |
Starter
$75
|
Standard
$200
|
Advanced
$450
|
|---|---|---|---|
| Delivery Time | 2 days | 4 days | 7 days |
Number of Revisions | 1 | 2 | 3 |
Source Code | - | - | - |
Optional add-ons
You can add these on the next page.
Fast Delivery
+$50 - $150
Additional Revision
+$50
Extra 5k LoC reviewed
(+ 2 Days)
+$150
Pair-programming session (60 min)
(+ 1 Day)
+$120
Written architecture recommendations
(+ 2 Days)
+$200Frequently asked questions
About Alessander
Staff Backend Engineer - Go, Microservices, Distributed Systems
Florianopolis, Brazil - 7:18 pm local time
I operate through a US-based LLC, making B2B engagement seamless for North American and European organizations.
What I architect:
- Event-Driven Microservices and Serverless (Golang, AWS Lambda, GCP)
- Internal Developer Platforms (IDP) that cut provisioning from days to minutes
- Observability stacks (Datadog, SOC2) that slash MTTR by 40%
- Cloud Cost Optimization - 30% API latency gains on high-volume ERP systems
- Legacy Modernization - monolith-to-microservices with zero downtime
Core stack: Golang, Java, Python, AWS, GCP, Terraform, Kubernetes, Kafka, PostgreSQL, Redis, Datadog
Google Professional Cloud Architect certification in progress. Postgraduate specializations in Software Architecture and Database Administration.
Open to Staff / Principal / Tech Lead engagements - remote, contract or full-time.
Steps for completing your project
After purchasing the project, send requirements so Alessander can start the project.
Delivery time starts when Alessander receives requirements from you.
Alessander works on your project following the steps below.
Revisions may occur after the delivery date.
Scope alignment
I confirm which files/packages are in scope and your top concerns (correctness, performance, security, style, testability). I confirm timeline and review depth before starting.
Deep code review
I review each file: concurrency, error handling, interfaces, performance hot spots, test coverage, security issues, idiomatic patterns. Findings tagged Critical/High/Medium/Low with file references.