Skip to content
MicrosystemsPrecision engineeringP9e Microsystems
Careers

Build things that leave the building.

Our work ends up in plants, data halls, farms, vehicles and airframes. If you would rather ship a system that has to survive a decade than a demo that has to survive a sprint review, we should talk.

Open roles

Currently hiring

Do not see your discipline? Send us your work anyway — we hire ahead of the requisition when someone is right.

Send an open application

Or email careers@p9e.in. Attach a CV and, if you have one, something you built.

What you would join

A practice, not a project.

You are hired into a discipline and you stay in it. Work rotates across the group's companies and divisions, which is how an embedded engineer here ends up with a flight controller, a battery pack and an irrigation RTU on the same CV.

One bench, six practices, six places the work lands

Engineers are hired into a practice, not into a project — and the practice keeps its standards, its review gates and its platforms wherever the work goes. That is why a fix made for a flight controller shows up in an irrigation controller without anyone arranging a transfer.

PRACTICESWHERE IT LANDSEnterprise applicationsData centre & infrastructureSCADA & industrial automationEmbedded & electronicsCloud & DevOpsIoT & connected systemsVyovrinda — aerospaceSasyaveda — agricultureSavithru — energyEnterprise SoftwareSmart InfrastructureIndustrial AutomationOne engineering benchShared review gatesShared platformsShared standardsShared evidence trailThe shaded destinations are separately branded companies; the rest are divisions of P9eDifferent names on the door, the same bench behind it. That is the whole argument for the group being structured this way.
Working here

What we offer, plainly.

Real hardware, real deployments

Work reaches plants, farms, vehicles and airframes. Nothing here stops at a prototype video.

Cross-discipline teams

Firmware engineers sit with control engineers and platform engineers. The seams between disciplines are where the interesting problems are.

Structured mentoring

Every engineer has a named mentor and a review cadence. We have trained over 10,000 engineers — internally and through our institutional programmes.

Certification support

Sponsored vendor and safety certifications, plus dedicated time to prepare for them.

Health cover

Medical insurance for you and your immediate family, and cover for site-deployed engineers.

Hybrid where the work allows

Software and platform teams work hybrid. Lab, plant and field work is on site, and we are honest about which is which.

Hiring process

Four steps, roughly two weeks.

No unpaid take-homes that run to a weekend, and no surprise rounds.

  1. 01

    Screening call

    Thirty minutes with an engineer — what you have built and what you want to build next.

  2. 02

    Technical conversation

    A working session on a problem from your discipline. Bring your own code or design if you would rather discuss that.

  3. 03

    Team and practice fit

    Meet the people you would sit with, and the practice lead.

  4. 04

    Offer

    Written offer with the role scope, mentor and review cadence stated up front.

Nothing above fits, but you still want in?

Send us what you have built. We read everything that arrives.

Send an applicationGet in touch