Seven People, Naraina, New Delhi
Careers
We are not always hiring, and we would rather say so than collect applications.
What is permanently true is the bar and the process. Both are below, so you can decide whether this is somewhere you would want to work before writing anything.
Quick Answer
Updated August 22, 2026
What is it like to work at SoftwareCrafting?
It is a seven-person senior engineering team in Naraina, New Delhi, founded in 2022. Engineers join client calls rather than working through an account manager, own a product area end to end rather than a ticket queue, and have every change reviewed by a second engineer. Roughly half of engagements start with a codebase somebody else wrote, so reading unfamiliar code well matters more here than it does at a product company. The stack is TypeScript across the board — Next.js, React, React Native, Flutter, Node.js, Python, PostgreSQL, MongoDB, AWS. We hire roughly one engineer at a time when sustained work justifies it, not continuously.
Team size
7 engineers
Office
Naraina, New Delhi
Hiring
Occasional, not continuous
Best for
- Engineers who want breadth across many products in a year
- People comfortable talking directly to the client
- Anyone who prefers reading code to being handed a spec
Not best for
- Engineers who want depth on one product over several years
- People who would rather not speak to clients at all
- Anyone looking for an equity story or a large-company ladder
The Work
What the job actually involves
You talk to the client
Engineers join scoping calls and sprint reviews. There is no account manager translating between you and the person whose product it is, which is better for the work and uncomfortable if you would rather only write code.
You own something end to end
On a seven-person team you take a product area — its data model, its API, its screens — rather than a queue of tickets somebody else decomposed.
Half the work is inherited code
Roughly half our engagements start with a codebase somebody else wrote. Reading unfamiliar code well is a core skill here, not an occasional inconvenience.
You publish under your own name
Technical articles carry the author’s byline and a public profile, not a company one. It is optional, and the people who do it own that work permanently.
Review is not negotiable
Every change is read by a second engineer before it merges. That applies in both directions and from the first week.
You will be told when you are wrong
Directly and early, about your code and your estimates. We would rather that than a polite team that ships something nobody believed in.
The Bar
What we are actually looking for
Not a list of frameworks. These are the things that separate the people who work out here from the ones who do not, and they are the same things we tell clients we screen for when they hire through us.
- You can design a schema and write the migration without being asked twice
- You can read a codebase you did not write and describe what it does before changing it
- You write clearly enough that a written explanation beats a call
- You estimate with the assumptions attached, not as a single confident number
- You can name something that went wrong on a recent project and what you changed afterwards
- You push back on a brief when it is wrong, including ours
The Process
Four steps, no whiteboard algorithms
Step 1
A written note from you
Not a template cover letter. Something you built, something you fixed, or something you disagree with on this site. We read all of them.
Step 2
A conversation with an engineer
Not a recruiter and not an automated coding test. A senior engineer talks to you about work you have actually done.
Step 3
A paid practical exercise
A task close to real work, reviewed the way we would review a pull request. Paid, because asking for unpaid work is a bad way to start.
Step 4
A conversation about fit
What you want next, what we can and cannot offer, and whether a seven-person agency is the right place for it. Both sides answer honestly.
FAQ
Questions candidates ask
Are you hiring right now?
Not continuously. We are seven people and we add roughly one engineer at a time, when there is sustained work to justify it rather than in anticipation. We keep good applications on file and come back to them — a note that arrives in a quiet month is not wasted, it is just slower.
What roles do you hire for?
Full-stack, backend, and mobile engineering, mostly senior. We work in TypeScript across the stack — Next.js and React on the web, React Native and Flutter on mobile, Node.js and Python on the backend, PostgreSQL and MongoDB for data, AWS for infrastructure. We do not staff Angular, Vue, .NET, Java, or PHP.
Do you hire juniors?
Rarely, and honestly. A seven-person team has limited capacity to train, and clients are paying senior rates for senior work. When we do take someone earlier in their career it is because they were unusually strong in the exercise, and we say up front how much mentoring we can realistically provide.
Is the work remote or in the office?
Our office is in Naraina, New Delhi. We are not a fully remote company and will not describe ourselves as one — but the day is not measured in hours at a desk, and the team works from home regularly.
What is the interview process?
A written note, a conversation with a senior engineer about work you have actually done, a paid practical exercise reviewed like a pull request, and a fit conversation. No whiteboard algorithms, no unpaid take-homes, and no recruiter screen.
Why work at a seven-person agency rather than a product company?
You see more products in a year than you would in five at one company, you talk to the people whose business depends on the work, and nothing is far from you. The trade-off is real: less depth on any single product, more context switching, and no equity story. If depth on one product is what you want, a product company is genuinely the better choice.
Applying
There is no listings page. Write to us anyway.
Tell us something you built, something you fixed that was genuinely hard, or something on this site you think is wrong. A senior engineer reads every note. If we are not hiring, we will say so and keep it on file rather than leave you guessing.
Worth reading first: how we build for the delivery process you would be joining, and the team page for an honest account of what a seven-person team cannot do.
Quick Brief
Start the conversation here
Tell us what you have built and what you want to work on next. A senior engineer reads every note.
Your Name
Work Email
What do you need help with?
More about us
Before you write
The team, the process, and the facts — the same pages our clients read.