Hire a senior Golang developer on contract
Hire a Golang developer through me when you need a service designed and built properly the first time: an API other teams depend on, a worker that has to run for months without attention, or a slow part of a larger system rewritten in Go. I work in your repository and ship the code myself.
I run Go in production on my own product. Craaft is a kanban board for people and AI agents, and the whole platform ships as a single Go binary on PostgreSQL.
Go work I take on
- APIs and services. REST and gRPC services on PostgreSQL, with authentication, rate limiting and versioning thought through up front.
- Real-time features. WebSocket and server-sent event systems where every connected client sees a change as it happens.
- Workers and pipelines. Queue consumers, schedulers and data movers with retries, idempotency and backpressure.
- MCP servers and agent tooling. Go services that expose your product to AI agents with scoped permissions. More in MCP server development.
- CLIs and internal tools. Single-binary tools that are easy to distribute and hard to misconfigure.
Go I’ve shipped
Craaft is the clearest example. The platform is one Go binary backed by PostgreSQL. A card moved by one person, or by an AI agent, appears live for everyone on the board. The same binary serves the REST API, and the official MCP server is written in Go and public on GitHub.
On client work I ran the cloud migration and CI/CD for a retail platform whose stack included Go services alongside Java, Python and PHP.
How I write Go
- Standard library first. net/http, database/sql and context cover most of what a service needs. Dependencies are added when they earn their place.
- One binary, simple deploys. Static builds, configuration from the environment, migrations that run on start or as a separate command.
- Explicit errors. Errors wrapped with context and handled where a decision can be made about them.
- Concurrency with limits. Goroutines with bounded worker pools, contexts for cancellation, and the race detector running in CI.
- Observable by default. Structured logs, metrics and pprof endpoints from the first deploy.
How a contract works
It starts with a two-week sprint with a concrete deliverable. After that I work a fixed number of days a week, agreed up front. I invoice monthly from my own company, in your currency, on 30-day terms.
I work remotely from Cape Town (GMT+2), with a full working day of overlap with Europe and the Gulf and mornings with the US East Coast.
Questions
Where can I see your Go code?
The Craaft MCP server is public on GitHub under the craaft organisation. The Craaft platform itself is a Go product you can sign up for and use.
Should we rewrite our service in Go?
Usually only part of it. Go pays off for network services, workers and anything with a lot of concurrent connections. A working Rails or Django application rarely needs replacing; the slow or expensive piece can move to Go behind the same API. I cover the trade-off in rewrite vs refactor.
Do you work with our existing Go team?
Yes. I join as a senior engineer or as the tech lead, review pull requests, and pair with your engineers so the design decisions are understood after I leave.
Do you only write Go?
No. I also work in Python, TypeScript, Rust, Ruby and PHP, which helps when a Go service has to sit beside an older system.
Need a senior Go developer?
Tell me what the service has to do and what it has to survive. We scope a two-week sprint, I ship something real, then you decide.
GMT+2 · Full EU and Gulf overlap · US East mornings · Singapore afternoons