The Role
You’ll join as a backend generalist with Go as the core language and architecture ownership as the real brief. This isn’t a maintenance role — the platform is scaling fast off the back of recent Series A funding, and the backend layer needs engineers who can design systems, not just extend them. Long-term, there’s a path to team lead and a hand in growing the engineering org.
About the Product
The platform is a multi-CDN intelligence layer — a routing and orchestration system that sits between online services and their CDN vendors (think Cloudflare, Akamai and similar), selecting the fastest and most cost-efficient delivery path in real time based on geolocation, traffic type, and time of day. It targets five-nines availability for clients in gaming, streaming, e-commerce, and financial SaaS — environments where CDN failure or degradation costs real money. The system also consolidates WAF, DDoS protection, rate limiting, and serverless compute into a single control plane, so clients stop managing a stack of disparate tools. High-volume, latency-sensitive, multi-cloud by design.
The Stack: The platform is built on Go as the primary language, with some legacy Java surface. Infrastructure spans AWS and GCP. The data layer is a mix of MongoDB, MySQL, and PostgreSQL. Python and Django are also in the picture. It’s a real microservices architecture on cloud-native infrastructure — not a monolith in disguise.
What You’ll Be Doing
Design and build backend services for high-throughput, latency-sensitive data delivery flows
Take end-to-end ownership of features — from architecture decisions through to production
Work directly with the CEO, backend team, and DevOps on system design and cross-cutting concerns
Optimize existing systems for performance, scalability, and reliability under real production load
Make database design and query optimization decisions across a mixed persistence layer
Evaluate and adopt tooling and approaches — you’ll have real input on how the stack evolves
What We Expect
Must-have
7+ years of backend engineering experience, with Go as the primary production language
Solid experience with microservices architecture — not just familiarity, but real design-level understanding
Cloud platform experience: AWS or GCP
Strong grasp of multithreading and concurrency fundamentals
Comfort with relational and non-relational databases, including performance tuning
Experience working on SaaS products
Readiness to eventually transition to an in-office model
Nice to have
Prior experience in a tech lead, principal, or general engineer capacity
Commercial background in Java, C++, PHP, or .NET — useful given legacy surface area
Track record of participating in team building or hiring
Why This Role Is Worth Your Time
The company just closed $20M in funding and is moving fast — the architecture decisions you make now will define the platform for the next several years
Real ownership: you’re expected to build from scratch and make decisions, not implement tickets
A direct line to leadership — you’ll collaborate with the CEO and core team, not sit three layers below the tech lead
A defined growth path toward team lead and, eventually, a role in shaping the engineering org
Відгукнутись на вакансію
