You own a surface end to end — architecture, calls with the client, the release. Squads are four to six people, never twenty.
Weekly demos to real users, not internal decks. The feedback loop is days, so your judgement compounds fast.
Fintech one quarter, industrial IoT the next. Four years here looks like ten years of surface area on your CV.
No perk theatre. Six things, funded properly.
These aren't wall posters. They're the tiebreakers we use in code review, in pitches and in performance conversations. Hover any value to see how it shows up.
One considered release is worth five rushed ones. We would rather cut scope than ship something we would not use ourselves.
The job is the client’s result, not the ticket. If the spec is wrong, say so before you build it.
Bad news travels fastest here. Slipping dates, shaky architecture, a decision you disagree with — day one, not week six.
Knowledge that lives in one head is a risk. Write it down, present it, pair on it.
Sustained pace, not heroics. Crunch is a planning failure and we treat it as one.
Every stage is scheduled within 48 hours of the last, and you get a decision either way — with reasons.
One short form. No login, no 12-page profile, no re-typing your CV.
25 minutes with the team lead you would work with. Your questions get equal time.
Real work from a real project, paired with two engineers. Paid if we ask for prep.
Two people outside your discipline. How you decide, disagree and hand off.
Written offer with the band, the level and the ladder. Reasons either way.
A public ladder, a budget with your name on it, and a mentor whose review includes how well you grew someone else.
Promotion reviews run twice a year against these written expectations — no calibration theatre, no waiting for a seat to open.
Courses, certifications, conferences, hardware for a side experiment. One-line approval, no business case.
Six guilds — AI, mobile, security, cloud, design, delivery. Every engineer presents at least twice a year.
Weekly 1:1s for your first six months, then monthly for as long as you want them. Mentors are reviewed on it.
Yes, for most engineering and AI roles within IST ±3 hours. Design and delivery roles are hybrid — two days a month in a studio, travel covered. We are async-first by default: decisions live in writing so timezone is never a tax.
Intro call, a 90-minute paired craft session on real project work, then a values conversation. Three conversations, twelve days median, no take-home marathon and no whiteboard algorithm trivia. If we ask you to prepare anything longer than an hour, we pay for it.
Apply. We hire for trajectory and judgement, and roughly a third of our current team applied to a role they were not a literal match for. Tell us which parts you have done and which you want to grow into — that answer matters more than the checklist.
Always. We open headcount for the right person about twice a quarter, and several of our senior hires arrived through a general application. Use the general form and be specific about what you would want to own.
We run a six-month paid apprenticeship twice a year — March and September — with four to six places across engineering and design. It is structured, mentored, and about 70% of apprentices convert to full-time roles.
Bands are set per level and per studio location, reviewed annually against market data, and the band is shown to you in the written offer. We do not negotiate against your previous salary and we do not ask for it.
One form, five minutes, a real reply within four days — whichever way it goes.
Start Your Application →