How we
hire.
Four steps, three weeks, no whiteboard puzzles. We read work rather than keywords, 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.
Every listing
is real.
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.
Four steps,
three weeks.
No puzzle rounds, no unpaid take-home projects, and no panel of people you would never see again. The exercise is paid or scoped small, and the last conversation is with the engineer you would work beside.
- 01
You write, we read
Send work rather than a keyword-optimised CV — a repository, a system you shipped, a thing you fixed that nobody noticed. An engineer reads it, not a parser. You get a reply either way.
Within 3 working days
- 02
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
- 03
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 we cannot pay for it, we scope it smaller rather than asking for free labour.
Week 2
- 04
A conversation with the person you would work with
Not a panel and not a culture-fit screen. The engineer whose reviews you will read, answering your questions about the work. Then an offer with the number stated, or a clear no.
Week 2–3
Judgement over
vocabulary.
Four things, taken straight from the doctrine we hold engagements to. We care less about the frameworks on your CV than about how you decide, and what you do when the honest answer is inconvenient.
You read before you change
The first clause of our doctrine is a hiring filter. We look for people who open the codebase, the ledger, 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, not just the happy path.
You write things down
Decision records, runbooks, and the reasoning behind the option you rejected. Clear writing is not a soft skill here. It is how architecture survives someone leaving.
You say the number
Estimates, confidence, and bad news stated plainly 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
Cognition comes first in the name for a reason. We read the codebase, the ledger, and the workflow before proposing anything. Speed bought by skipping comprehension is borrowed, and the interest is paid in production.
Accountability is assigned, not implied.
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 rather than assumed, in both directions.
Named accountability
Your name sits against the systems you build, in the decision records and in the runbooks. That is the point. It also means the credit is legible when the thing works.
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.
Ventures we own, not just client tickets
Aurelia, Voyazio, and AxleOne are ours. Engineers here work on products the company funds and operates, which means real users, real churn, and the consequences of every shortcut.
The record
- Base
- Ahmedabad, Gujarat, India
Remote-first, with the office available when collaboration needs a room.
- Hours
- Monday to Friday, 10:00–18:00 IST
- Ventures
- Aurelia · Voyazio · AxleOne
Products the company funds and operates itself.
- Applications
- careers@cognimit.com
Read by an engineer. Reply within three working days.
Read before you write
The clearest picture of the work is in the record itself. Our capabilities set out the nine practices you would work across, the ventures are the products we own, engagements explains how client work is bought, and trust publishes the statutory record of the company you would be joining.