You're in the room
Engineers join client calls. You hear the problem in the client's own words, before anyone has summarised it for you.
Career
The work, without the noise.
No status meetings about status meetings. Here is what a fortnight looks like.
The rhythm
Two-week loops, each one ending in something real.
01
You start on something real
First ticket in week one, on a product with live users. Onboarding is a person and a codebase.
02
Two-week sprints, shipped to staging
Every sprint ends in software the client can click. Nothing waits six months for a reveal.
03
Review is a conversation
Every change is read by someone senior. Not a rubber stamp, and not a gauntlet — the point is the code gets better and so do you.
04
You see it land
You watch your work go to production and hear what it did for the people who paid for it. That loop is the whole job.
What makes it different
Small teams, whole problems
Three to five people own a delivery end to end — architecture, build, release, and the tuning after. Nobody is handed a slice of a spec.
Senior by default
There is no junior tier doing the unglamorous half. If you are here, you are trusted with the decision — and supported when it is hard.
Remote first, rooms when they help
Remote-first, genuinely
The default is wherever you work best. Remote is not a concession here — the company was built this way, so nobody dialling in is second-class in a meeting.
Studios when a room helps
Kolkata and Dallas are there for the work that is better in person — kickoffs, hard architecture calls, and the occasional Friday that runs long.
Client time, on purpose
Some sessions belong face to face. We travel for kickoffs and hard conversations, and stay remote for everything a call handles better.
How we run the day
01
Async is the default
Write it down. A decision in a document survives the person who made it and reaches whoever was asleep.
02
Meetings earn their place
No agenda, no meeting. Anything that is a status update becomes a message instead.
03
Deep work is protected
Mornings stay clear of internal calls. Interrupting an engineer mid-problem is an expensive way to save five minutes.
04
One timezone rule
Overlap hours are agreed per team and honoured. Nobody is quietly expected to live on another continent's clock.
How you get better
01
A mentor who is not your manager
Someone senior is accountable for your progress, meets you regularly, and has read your code.
02
Feedback every four days
Short cycles mean nothing about your standing is ever a surprise, and course corrections are cheap.
03
Budget that gets used
Conferences and certifications every year. We check it is spent, because an unclaimed budget is just a line in a job ad.
04
Range on purpose
Across a couple of years you will touch AI, platform and product work. When you specialise, it is your call to make.