Go & TypeScript API Engineer
Budget: £20 – £250 GBP
I’m looking for a hands-on developer who can take the lead on API development in Go while also handling the TypeScript side of the stack. The back-end is the priority: I need clean, well-structured endpoints, solid error handling, and test coverage.
Although I already have some documentation, it’s limited, so part of your job will be to expand it as you code—clear comments, concise README updates, and endpoint reference pages are all expected.
Key responsibilities
• Design and implement new API endpoints in Go (gin, echo, or your preferred framework)
• Wire the services to a relational database (PostgreSQL or MySQL) with migrations and seeding scripts
• Create a lightweight TypeScript layer—this could be SDK wrappers, simple admin panels, or integration tests—so that front-end teammates can consume the APIs immediately
• Write unit and integration tests for both Go and TypeScript portions
• Document every endpoint, payload, and error code so onboarding remains painless
To fit well, you should be comfortable with Git workflows, containers (Docker), and continuous integration tools. If you’ve previously shipped production-grade RESTful APIs and enjoy refining documentation as you go, I’d like to hear how you would approach this build and what best practices you bring.
Although I already have some documentation, it’s limited, so part of your job will be to expand it as you code—clear comments, concise README updates, and endpoint reference pages are all expected.
Key responsibilities
• Design and implement new API endpoints in Go (gin, echo, or your preferred framework)
• Wire the services to a relational database (PostgreSQL or MySQL) with migrations and seeding scripts
• Create a lightweight TypeScript layer—this could be SDK wrappers, simple admin panels, or integration tests—so that front-end teammates can consume the APIs immediately
• Write unit and integration tests for both Go and TypeScript portions
• Document every endpoint, payload, and error code so onboarding remains painless
To fit well, you should be comfortable with Git workflows, containers (Docker), and continuous integration tools. If you’ve previously shipped production-grade RESTful APIs and enjoy refining documentation as you go, I’d like to hear how you would approach this build and what best practices you bring.
Related categories:
Golang
MySQL
PostgreSQL
RESTful
Git
Docker
Documentation
Continuous Integration
API Development