Careers
Difficult work, with people worth learning from.
Enterprise engineering on systems that matter, in a firm that publishes its pay bands and pays for on-call.
20%
Time on research
4.6/5
Internal engagement
92%
Two-year retention
5 days
Learning budget
Open roles
Where we are hiring
If none of these fit but you think you should be here, apply anyway and say why.
- Apply
Senior Software Engineer
Build enterprise platforms in TypeScript, .NET, or Go. You will own architecture decisions on your slice and be in front of the client regularly.
- Product Engineering
- Kathmandu / Hybrid
- Full-time
- Apply
Cloud Platform Engineer
Landing zones, Kubernetes platforms, and infrastructure as code across AWS and Azure, with real ownership of the platform's reliability.
- Cloud Practice
- Kathmandu / Remote
- Full-time
- Apply
Data Engineer
Warehouse modelling, ELT pipelines, and semantic layers. Heavy SQL, dbt, and a lot of conversations with people about what a number means.
- Data & AI Practice
- Kathmandu / Hybrid
- Full-time
- Apply
Security Consultant
Posture assessment, identity architecture, and detection engineering for regulated clients. Validation by hand, not by scanner output.
- Cyber Security Practice
- Kathmandu / Hybrid
- Full-time
- Apply
Delivery Lead
Run multi-workstream engagements end to end. Accountable for the outcome, with the authority to change the plan when it is wrong.
- Delivery
- Kathmandu
- Full-time
- Apply
Graduate Engineer
An eighteen-month structured programme across two practices, with a named mentor and real production work from month two.
- Engineering
- Kathmandu
- Graduate programme
What we offer
The things people actually asked for
This list changes when the internal survey says it should.
Transparent pay bands
Published internally with the criteria for each level. Reviewed annually against market, not against how well you negotiated on entry.
Twenty per cent research time
One day a fortnight on Innovation Lab tracks or your own investigation, provided the findings get written up either way.
Hybrid, with intent
Two anchor days a week for the teams that benefit from being together. Fully remote for roles where it genuinely does not matter.
Health and family cover
Medical cover for you and dependants, plus parental leave that applies equally regardless of which parent you are.
Certification funded
Cloud, security, and platform certifications paid for including exam retakes, with study time inside working hours.
On-call that is compensated
Rotations are paid, capped, and staffed properly. If a rotation is consistently disturbed we fix the system, not the roster.
Hiring process
Five steps, roughly three weeks
No unpaid take-home projects, and no more than five conversations in total.
- 01
Step 1
Application review
Read by an engineer from the relevant practice, not filtered by keyword. You will hear back within five business days either way.
- 02
Step 2
Conversation, not a screen
Forty-five minutes with the hiring manager about what you have built and what you want to do next. No trick questions.
- 03
Step 3
Technical session
A paired session on a realistic problem, using your own environment. No whiteboard algorithms and no unpaid take-home project.
- 04
Step 4
Team and client conversation
Meet the people you would work with, and ask them anything. We also cover what client-facing work actually involves.
- 05
Step 5
Offer
Within two business days of the final conversation, at the band the criteria put you in — with the reasoning explained.
Working here
What you should know before applying
The honest version, including the parts that will not suit everyone.
You will face clients
Engineers here attend client sessions from early on. If you would rather never speak to a stakeholder, this is not the right firm.
Estimates are taken seriously
We commit to dates publicly, which means estimating carefully and raising problems early is part of the engineering job.
Writing is part of the work
Decisions, post-mortems, and research findings get written down. Engineers who write well have an advantage here.
Progression
What each level owns, and how you move
Published rather than discussed only at review time, so you can see what the next step asks for before deciding whether you want it.
| Level | What you own | What we look for to progress | Typical time at level |
|---|---|---|---|
| Engineer | Well-scoped tasks within a feature | Consistent delivery and reviewable work | 18–30 months |
| Senior engineerMost of the team | A feature end to end, including its operations | Judgement under ambiguity, mentoring others | 2–4 years |
| Lead engineer | A workstream and the people on it | Technical direction others can follow and challenge | 3+ years |
| Principal | Architecture across engagements | Decisions that hold up two years later | Open-ended |
| Practice lead | A practice: standards, hiring and client outcomes | Building a team that outperforms its headcount | Open-ended |
Engineer
- What you own
- Well-scoped tasks within a feature
- What we look for to progress
- Consistent delivery and reviewable work
- Typical time at level
- 18–30 months
Senior engineer
Most of the team- What you own
- A feature end to end, including its operations
- What we look for to progress
- Judgement under ambiguity, mentoring others
- Typical time at level
- 2–4 years
Lead engineer
- What you own
- A workstream and the people on it
- What we look for to progress
- Technical direction others can follow and challenge
- Typical time at level
- 3+ years
Principal
- What you own
- Architecture across engagements
- What we look for to progress
- Decisions that hold up two years later
- Typical time at level
- Open-ended
Practice lead
- What you own
- A practice: standards, hiring and client outcomes
- What we look for to progress
- Building a team that outperforms its headcount
- Typical time at level
- Open-ended
The honest version
Three things about working here, including a caveat
The work
Client work, product work, and the ability to move between them
Running a product platform alongside a consulting practice means engineers are not stuck on one client for three years or buried in an internal roadmap. Most people here do both across a year, and the rotation is planned rather than accidental.
- Rotation between client engagements and platform work
- Domain exposure across eight regulated sectors
- You will meet the people who use what you build
- No pyramid model — seniors deliver, they do not just sell
The bar
Reviewed work, and the right to argue
Everything goes through review, including work by the people who set the standards. Disagreeing with an architectural decision is expected, and the decision record exists so the argument is about the trade-off rather than about who said it.
- Every change reviewed, no exceptions by seniority
- Architecture decisions written down with alternatives
- Post-incident reviews are blameless and change the system
- Saying 'I do not know' is a normal thing to say here
The hours
Sustainable pace, with the honest caveat
We run cutovers, peak trading events and incident response, so there are nights that are genuinely hard. What we commit to is that those are planned, compensated and rare — not a permanent operating state disguised as commitment.
- On-call is rota'd, compensated and voluntary to join
- Cutover weekends are planned months out, with time back
- No expectation of evening or weekend availability by default
- Workload raised in one-to-ones is treated as a real problem
Questions
What candidates ask us
If yours is not here, ask it in the first conversation — we would rather answer it early.
Hiring
What does the interview process actually involve?
A conversation about your experience, a practical exercise close to work we really do, and a session with the people you would work alongside. There is no algorithmic whiteboard round. The practical exercise is time-boxed and we do not ask for unpaid work on anything we would ship.
Do you hire people without a computer science degree?
Routinely, and several of the strongest engineers here came through other routes. What we assess is whether you can reason about a system, communicate the reasoning, and take feedback on it. How you learned that is not something we score.
Is there a take-home exercise?
Yes, time-boxed to around three hours, and we mean the time box — we would rather see a partial solution with clear reasoning than evidence that you spent a weekend on it. If a take-home is not workable for your circumstances, tell us and we will run a paired session instead.
Working here
Is the role remote, hybrid or on-site?
Hybrid by default from Bangalore, with the specifics varying by engagement — some regulated clients require on-site presence for parts of a programme, and we tell you that at offer stage rather than after you join. Fully remote is possible for some roles and we will say which in the listing.
How much travel is involved?
For most engineers, very little. For practice leads and on engagements with an on-site requirement it can be a few days a month. We plan it rather than sprung it, and it is discussed at offer stage.
What happens if an engagement I am on ends early?
You move to platform work or another engagement. Utilisation pressure is carried by the business rather than pushed onto individuals — nobody here is asked to find their own next project, and a gap between engagements is not treated as a performance issue.
Apply, or just ask a question.
If you want to know what a week actually looks like before applying, we will put you in touch with someone doing the job.