Careers
We are not hiring many people, and that is the point
Our whole proposition to a client is that the person who designs their system builds it, and that nobody learns their process at their expense. That constrains hiring more than growth would like.
The work
What you would actually do
Not a lane. You would sit with a finance or operations team, understand why the process is shaped the way it is, design the control, then build the thing that enforces it and watch it run.
The uncomfortable part is that you will sometimes conclude the honest answer is not to build. We expect you to say so, in front of the client, before the budget is committed.
Data model first
You will design schemas, state machines and operation functions before anyone opens a design tool. An interface can be redrawn in a week. A data model cannot.
In front of the client
No account layer to hide behind. You present your own work, take the hard question in the room, and answer it without a follow up email.
Own it in production
You will load test it, break it, and fix the defect you shipped. Nobody hands your work to a support tier and walks away.
Write it down
Documentation, handover packs and the open list of what is not built. If a client cannot run it without you, the design was wrong.
Who fits
Three things that matter more than a stack
We do not screen on years, framework names or a degree. These are the three we do screen on, and we say so at the first conversation.
You have carried something
A service level, a close, a queue, a release. People who have only advised tend to design controls that nobody can actually operate at six on the last working day.
You state the gap
You are comfortable writing down what your work does not do yet. Confidence that survives scrutiny is worth more than confidence that avoids it.
You finish
Prototypes are easy and cheap. We are looking for people who take something all the way into production, including the boring last ten per cent.
How to apply
Show us something you finished
Send one thing you took all the way, and two paragraphs: what it does, and what it does not do yet. That second paragraph tells us more than a resume does.
Write to info@anviratech.com with Careers in the subject line. Every application from a real person gets a reply, including the ones that are a no.
We are early. There is no ladder to climb yet and no benefits brochure.
Hiring is occasional and role specific. There may be nothing open when you write.
What you do get is senior client exposure from week one, and your name on the work.
Based in Nagpur, India, working across several time zones. Remote is discussed per role.
Nothing open, but worth a conversation?
If the work above is the work you want to do, write anyway. We keep a short list and we do go back to it.