CareersAhmedabad, IndiaRemote-first
How we
hire.
The process has four steps and takes about three weeks. We read your work, we pay for the practical exercise, and the last conversation is with the engineer whose reviews you would read every week. You get a clear answer either way.
Open roles
Roles we are
hiring for.
A role appears here when the work exists and the budget is approved. Applications go to careers@cognimit.com and are read by an engineer.
The process
Four steps,
three weeks.
There are no puzzle rounds, no unpaid take-home projects and no panels. The exercise is paid, and the last conversation is with the engineer you would work beside.
You write, we read
Send your work: a repository, a system you shipped, or a fix nobody noticed. An engineer reads it, and you get a reply either way.
Within 3 working days
One technical conversation
Forty-five minutes on something you have actually built. Why the architecture went that way, what you would change now, and what broke. No whiteboard puzzles and no algorithm trivia.
Week 1
A scoped practical exercise
A small, real problem in our stack, scoped to a few hours and paid at your rate. You keep the work. If the budget does not cover it, we make the exercise smaller.
Week 2
A conversation with the person you would work with
You meet the engineer whose reviews you will read, and they answer your questions about the work. Then you get an offer with the number stated, or a clear no.
Week 2–3
What we look for
How you decide
matters most.
Four things, taken from the principles we apply to client work. We care more about how you make decisions, and what you do when the answer is inconvenient, than about the frameworks on your CV.
You read before you change
Our first principle is also a hiring filter. We look for people who read the code, the data and the workflow before proposing anything, and who can say what they do not yet understand.
You finish the whole thing
Error states, empty states, slow networks, permissions, migrations. We look for engineers whose definition of done includes the third-most-likely failure.
You write things down
Decision records, runbooks and the reasoning behind the option you rejected. Clear writing is how architecture survives someone leaving.
You state the numbers early
Estimates, confidence and bad news, given clearly and early. We would rather hear a slip three weeks out than the day before a deadline, and we hold ourselves to the same rule.
Understand the system before changing it
We read the code, the data and the workflow before we propose anything. Changes made without that understanding are paid for later, in production.
Working here
Every engagement has a named owner.
Every engagement has a named engagement lead accountable for scope, schedule, and quality, working to a documented governance model: weekly written reporting, a defined escalation path, formal change control, and senior technical review on every change before it reaches production.
Clear ownership, senior review
You own systems by name, and every change you write is read by a second engineer before it ships. Accountability is assigned in writing, in both directions.
Named accountability
Your name sits against the systems you build, in the decision records and in the runbooks. When the work succeeds, the credit is visible.
You own what you ship
End to end, from the data model to the last state on screen. You carry it into production, you watch it under load, and you fix it when it bends. Reviewed by a second engineer, always.
Products we own, as well as client work
Aurelia, Voyazio and AxleOne are ours. Aurelia is in beta on Android, and Voyazio and AxleOne are in development. Engineers here work on them alongside client projects and live with the consequences of every shortcut.
At a glance
- Base
- Ahmedabad, Gujarat, India
Remote-first, with the office available when collaboration needs a room.
- Hours
- Monday to Friday, 10:00–18:00 IST
- Products
- Aurelia · Voyazio · AxleOne
Products the company owns and runs.
- Applications
- careers@cognimit.com
Read by an engineer. Reply within three working days.
Read before you write
The clearest picture of the work is on this site. The services page sets out the 12 services you would work across, the products are the ones we own, engagements explains how client work is bought, and trust publishes the statutory details of the company you would be joining.