Some roles are about shipping features. This isn’t one of them.
This is for engineers who want to take something from zero to something real. Not optimising what already exists, but shaping what it becomes.
You’ll be working in an early-stage, high-calibre environment where the problems aren’t neatly defined yet. The kind where you’re expected to think in systems, not tickets, and make calls without perfect information.
The work sits across:
- Product-led engineering with real user impact
- Backend / infrastructure problems that actually matter
- Systems that need to scale, perform, and be right first time
- Data and distributed architecture challenges
It’s not a role where you inherit a roadmap and crack on. More likely: a rough idea, a hard problem, and the expectation you figure out the best way forward.
What they’re looking for:
- Engineers who’ve operated in startup or scale-up environments
- Strong backend or full stack foundations (with a backend bias)
- People who care how things are built, not just that they work
- Comfortable in ambiguity, making decisions and owning outcomes
- Naturally curious builders, the kind who have side projects or have broken and rebuilt systems before
Tech isn’t the focus, but you’ll likely be working across modern backend systems, APIs, and performance-sensitive environments. There’s also room to pick up newer languages and tools as part of the journey.
Why it’s interesting:
- High-impact product work, not just infrastructure for the sake of it
- Small, sharp teams where quality matters
- Real scope to influence architecture and direction
- The messy, interesting part of building
If you’re someone who gets energy from a blank page rather than a backlog, it’s probably worth a conversation.
#J-18808-Ljbffr…