Go APIs & backend services
Build or extend REST, GraphQL and gRPC services, with clear interfaces, error handling and automated tests.
Typical scope: a backend capability with tests and handover notes.
Independent Go & platform consulting
Freelance Go developer for APIs and Kubernetes platforms
I help engineering teams build Go services, automate Kubernetes workflows and improve backend reliability. Available for focused consulting alongside my full-time role.
Engineering support for a defined problem
Bring a backend feature, a platform workflow or a service that needs attention. We can define a focused scope around your existing codebase, delivery constraints and the people who will maintain it.
My experience spans Go APIs, Kubernetes controllers, GraphQL, automated testing and delivery pipelines. The work starts with understanding your system and agreeing on what a useful outcome looks like.
What we can work on
Kubernetes platform automation
Develop Go controllers and CRDs for repeatable provisioning workflows, with reconciliation, status reporting and least-privilege access.
Typical scope: a controller or platform workflow integrated with your delivery process.
Reliability & maintainability
Review concurrency, service boundaries and test isolation. Identify bottlenecks and agree on the changes worth making before refactoring.
Typical scope: prioritized findings and agreed improvements verified against a baseline.
Relevant engineering experience
Examples from my existing portfolio. These describe previous employment, not independent client engagements.
Gorilla Logic
Kubernetes-native provisioning in Go
- Context
- Teams needed a repeatable way to provision platform resources across GKE workload clusters.
- My contribution
- Built a platform that creates namespaces, RBAC and Argo CD Applications from one YAML definition, using custom CRDs and controller reconciliation. Supported releases with Helm, GitHub Actions, Kind and automated end-to-end tests.
Wind River
Go service boundaries and concurrent processing
- Context
- Backend work involved tightly coupled services, sequential processing and tests that needed stronger isolation.
- My contribution
- Restructured two services into six focused microservices, introduced concurrent Go workflows and refactored more than 400 unit tests for independent, concurrent execution.
How a focused engagement works
Share the problem
Describe the system, current symptoms, desired outcome and any timeline or access constraints.
Agree on scope
We confirm fit, availability, deliverables and acceptance criteria before committing to implementation.
Build and hand over
Review changes with your team, verify the agreed behavior and document the decisions needed to maintain the work.
Before we work together
Are you available full-time?
No. I work full-time, so consulting availability is limited. I am open to discussing focused Go backend and platform engineering engagements.
Can you work with an existing Go codebase?
Yes. We can start with a defined feature, a review or an isolated improvement. Scope depends on the codebase, access and your team’s constraints.
What does an engagement cost?
Scope and availability need to be agreed first. Send the problem, expected outcome and timeline so we can discuss whether the engagement is a fit.
Can you collaborate in English and Spanish?
Yes. I speak native Spanish and English at B2+ level, and work with technical documentation, architecture reviews and knowledge sharing.
How I approach the engineering
Technical articles on the systems and quality practices behind this work.
Have a Go or platform problem to solve?
Share the context, the outcome you need and your timeline. I will confirm whether the scope fits my consulting availability.
Discuss your Go project