Careers
We do not hire to grow headcount. We hire when the work demands someone whose name goes on the outcome. Here is what we look for, and what it actually looks like to be on the team.
Accountability by design. Your name on the file.
We run small and senior. Every engagement has one contact: one person who scoped it, ships it, and answers for it when it drifts. When you join a project here, you are that person.
One contact per engagement. The person who scoped it ships it. You work directly with clients who have real decisions to make, and you have the latitude to make calls on scope and trade-offs.
Engagements run short and specific. You will move across strategy, build, and support depending on the project shape. We work best with people who like varied, client-facing delivery.
Three snapshots, same bar for quality
No slide decks about culture. This is what the week tends to look like when you own delivery end to end.
Quiet blocks, real depth
Long stretches without standing meetings. You protect focus because the client expects judgment on the outcome.
Async first, sync when it earns
Decisions land in writing. Calls exist when ambiguity would cost a day. Whiteboards are for alignment on the next decision.
Paid reads, no free work
Assessments mirror the job. Short loops. When the fit is wrong, we say so early so neither side burns runway.
Async-first, one contact, clear overlap.
Core overlap is agreed before the work starts. Written updates beat status calls. When we need sync, it is short and decision-shaped.
Comp and contract: We hire into scoped roles with clear ownership. Engagements start with contracts so both sides can exit cleanly if reality does not match the conversation. Technical hiring uses one paid assessment, reviewed by the person you would ship beside.
Three things we will not compromise on
Own the outcome, end to end
The brief ends at shipped and working. The gap between "done" and "actually done" is yours to close before handover.
Write your thinking clearly
Async-first team. If you cannot write a tight paragraph that explains a trade-off, the quality of your code does not compensate. We make decisions in writing before we make them in calls.
One owner. Full context.
The person who scopes the work ships the work. You will talk directly to clients when it matters. That direct line is how you know whether the work actually solved the problem.
Probably not us if this is you
If the role shape does not match how you like to work, we would rather say so in the first call than find out three months in.
- You want one steady focus. Here you would move between planning, building, and client support.
- You like clear direction from a manager before deciding. Here you decide and explain your thinking in writing.
- Your work ends when the deliverable ships. Here you stay on it until the client problem is actually fixed.
- You want to grow into a lead role over time. Here we need someone who already runs projects end to end.
What we are hiring for now
Senior Full-Stack Engineer
India · Remote
Next.js, React, TypeScript, and Supabase. You own features from the architecture call to the production deploy. We read the codebase before kickoff; you should too.
WordPress Engineer
India · Remote
Performance-first builds, ACF, Gutenberg blocks, WooCommerce. You understand why WordPress has a reputation and how to make it undeserved. Strong opinion on what ships versus what waits.
Short, specific, zero surprises
We do not run multi-stage panels or ask you to work for free. If the application looks like a fit, the first call is 30 minutes: us explaining the project shape, you explaining how you work.
For technical roles there is one scoped assessment: paid, relevant to the actual work, and reviewed by the person you would work alongside. A paid assessment, relevant to the actual work. Zero whiteboard sessions.
If it is a fit, we move to a short engagement. Contracts first, always, so both sides have a clean exit if the reality does not match the conversation.
Ready to talk.Send us the brief.
Not sure where to start? Send the page, workflow, or backlog causing the problem. We will tell you whether it needs a scope call, a short diagnostic, or a different first step.