No open roles right now — and here is how we hire anyway
We would rather say that plainly than list an evergreen “Software Engineer” vacancy that has been open for two years. If the way we work sounds like something you want, write to us and we will keep it on file properly.
Send a speculative applicationFour things we do differently
Most of these exist because we have been on the other side of a bad hiring process and remember what it was like.
We read the code, not the keyword list
A CV listing fourteen technologies tells us nothing. Something you built and can explain the trade-offs of tells us most of what we need — including work that is unfinished or that went wrong, if you can say why.
No unpaid take-home marathons
A short exercise, or a conversation about code you already have. We are not asking for a weekend of unpaid work to be considered, and we do not run algorithm puzzles that have nothing to do with the job.
Depth over breadth, at this size
On a small team, someone who genuinely understands one stack and how databases behave under load is worth more than someone who has touched eight. Breadth comes later and follows from depth.
You will talk to the people you would work with
Including the CTO, who reviews the code here. Not a screening panel who cannot answer your questions about the actual work.
Less about your stack than you would expect
We can teach a good engineer a framework in a fortnight. The things below take considerably longer, so we hire for them instead.
- You can explain why you chose an approach, and what you gave up by choosing it
- You write things down — commit messages, decision records, replies that answer the question
- You are comfortable saying "I do not know" and then finding out
- You have opinions about your tools and can be argued out of them with evidence
- You care what happens to the software after it ships
What we build with
- React & Next.js
- Node.js
- .NET
- Laravel & PHP
- React Native
- Flutter
- PostgreSQL
- AWS & Cloud
You are not expected to know all of these. Depth in one, and curiosity about the rest, is the actual requirement.
The honest version
Small company, real ownership, and a set of trade-offs worth knowing before you write.
What is good about it
You will own things outright, early. There is no layer of people between you and the decision, and your code will be reviewed by someone who reads it properly rather than approving it in forty seconds.
What is harder about it
A four-person company has no bench. If something breaks and it is your area, it is yours. There is no dedicated DevOps team, no design department to hand things to, and less structure than a larger firm would give you. Some people find that energising and some find it exhausting — both are reasonable, and it is worth knowing which you are before applying.
- Location
- Ahmedabad, Gujarat — in person, with flexibility
- Team size
- Small. You will own things directly, from early on
- Review
- Every change is reviewed. That includes ours
- Clients
- India, the US, the UK and Australia — written communication matters
- Stack
- TypeScript, React, Node, PostgreSQL, React Native, AWS
What to send
Short is fine. We would rather read three specific paragraphs than a two-page CV of keyword lists.
Something you built
A repository, a live thing, a screenshot of an internal tool — whatever you are allowed to share. Unfinished is fine. Something that went wrong is better than fine, if you can explain what you learned.
A decision you would make differently now
One paragraph. This tells us more about how you think than any list of technologies, and it is the answer we actually read first.
What you want to be doing in two years
So we can be honest about whether this is a place that gets you there. Sometimes the honest answer is no, and it is better for both of us to know that in week one than in year one.
Use the contact form and mention Careers, or call +91 81601 58313. We reply to every application, including the ones we decline.
No vacancy, still interested?
Write anyway. Small teams hire when the right person appears rather than when a requisition opens, and a good speculative application has started more than one of our conversations.