Build the systems that do not get switched off.
Bond registries, plant ERPs, hospital records, national fleets. If you want your work used by thousands of people every day for the next decade, that is what we do.
The trade, stated plainly.
No ping-pong tables in this list. These are the things that are actually different about working here, including the ones that will not suit everyone.
You own it after it ships
The team that builds a platform runs it. That changes how you design — you are the one carrying the pager for the shortcut you took in month two.
Discovery is real work here
We do not start coding until we can describe the client's problem back to them better than the brief did. Engineers sit in those workshops, not just delivery managers.
Small teams, long engagements
No bench, no rotation between accounts every quarter. You go deep on a domain — rail finance, plant operations, hospital records — until you genuinely understand it.
Boring is a compliment
The highest praise for a system here is that nobody thinks about it. We optimise for the thing still working in year ten, not for the thing demoing well in week three.
Open roles
No open roles right now.
We hire in bursts around new engagements. Send a note anyway — we keep good CVs and come back to them.
We hire in bursts, and this is a quiet one.
Roles open when an engagement starts, which means the gap between postings can be months and then three appear in a fortnight.
Thank you for your interest in joining our team. At this time, we have paused active hiring across our open roles. We encourage you to keep an eye on our careers page, as positions will reopen in the future. We truly appreciate your patience and continued interest in being part of our team.
Send us something anyway. Speculative notes go to the engineering leads rather than to a queue, and when a role does open the people already in that pile are the ones we call first.
Tell us what you buildWhat is worth sending
- Something you built that you can talk about for twenty minutes.
- A problem you solved where the interesting part was not the code.
- What you want to be doing in two years.
- Where you are based and whether you can reach Noida when it matters.
A CV is fine. A link to something you built is better. Both is best.
Nothing fits, but you think you should be here? careers@brihatinfotech.com — tell us what you have built and what you want to build next.
What you actually get.
Not a perks list. The things that change what a working week feels like.
You own a system, not a ticket
Engagements run for years. You will know one domain — rail finance, plant operations, hospital records — properly enough to argue with the client about it.
Hybrid, with a real reason to come in
Noida-based teams come together for discovery weeks and release weeks. The rest is yours to arrange. We do not count days.
On-call that is actually rostered
Paid, rotated, and never one person permanently. If a system pages often, fixing that is the work — not a heroism competition.
Time for the unglamorous half
Test coverage, documentation and refactoring are scoped into the plan. You will not have to sneak them past a delivery manager.
Health cover and the usual
Medical insurance for you and immediate family, statutory benefits, and leave that people are expected to take.
Learning that is not a portal
Conference and certification budget, and time inside the week for it. Architecture reviews are open to anyone who wants to sit in.
Three conversations, and we tell you where you stand after each.
No take-home that eats your weekend, no panel of eight, and no going quiet on you.
A conversation
45 minutes
With the person you would report to, who writes code. What you have built, what you want next, and whether this is that.
Technical discussion
90 minutes
Your code or ours, discussed rather than performed. No whiteboard algorithms and no take-home that eats a weekend.
Meet the team
45 minutes
Two people you would work beside, with time set aside for you to interrogate us. This one goes both ways.
Offer
Within 3 days
Numbers, level and scope in writing, set against the role rather than negotiated up from there.
Start to finish is usually two to three weeks.
If nothing open matches what you do but the work above sounds like yours, send a speculative application.