Skip to content
Brihat InfotechBrihat Infotech

Careers

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.

Open roles
4Open roles
Delhi NCR based
HybridDelhi NCR based
Engagements, not projects
LongEngagements, not projects

What it is like

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.

01

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.

02

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.

03

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.

04

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

4 open roles

Every role reports to someone who writes code. Interview loops are three conversations, and we tell you where you stand after each one.

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.

The offer

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.

Hiring process

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.

01

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.

02

Technical discussion

90 minutes

Your code or ours, discussed rather than performed. No whiteboard algorithms and no take-home that eats a weekend.

03

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.

04

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.

Before you apply

Occasionally, and never more than one or two at a time — a small team can only mentor properly at that rate. Most of our openings are for engineers with three or more years, because engagements put you in front of clients early.

Not a candidate

Here for the engineering, not the job?

If you found this page because you are evaluating us as a partner rather than an employer, the work itself is a better read.