Digiaeon Services Pvt Ltd logo

Careers

Own what you ship, including the parts that break.

Digiaeon is small on purpose. The work is production software other companies depend on, and the engineer who designs a system is the engineer who carries its pager.

Open roles
4 — engineering
Where
Chandigarh, and remote across India
Applications
careers@digiaeon.com

The shape of the team

Digiaeon hires senior engineers who want to own systems end to end rather than tickets. Small team, real production responsibility, and an explicit expectation that you write down what you learn. Based in Chandigarh with remote working across India; we hire against the roles below as the work requires, and we would rather leave a seat unfilled for a quarter than fill it badly.

Why join

  1. You operate what you build

    No throwing work over a wall to an operations team. You design it, ship it, watch it under load, and carry the pager for it during the engagement. That feedback loop is the fastest way to become a better engineer, and it is uncomfortable exactly often enough to be useful.

  2. Depth over breadth of logos

    Fewer clients, longer engagements, and the expectation that you understand the domain well enough to argue with the requirement. You will not be rotated across six accounts in a year to fill a utilisation target — there is no utilisation target.

  3. Time to do it properly is in the plan

    Instrumentation, eval suites, runbooks and decision records are scoped and sold as part of the work, not squeezed in after hours. When we take a shortcut it is deliberate, written into the debt register, and given an owner.

  4. Direct access to the decisions

    Flat structure, no account-management layer between you and the client’s engineers, and architecture arguments settled on merit with the tradeoff written down. If you are right, it ships — including when it contradicts what was proposed.

Open roles

Hired against the work, not a headcount plan.

Expand a role for the detail, then write to us directly. Every application is read by an engineer.

  1. Senior Applied AI Engineer

    Full-timeChandigarh or remote (India)

    Design agent loops, retrieval pipelines and the eval harnesses that keep them honest. You have shipped an LLM system that survived real traffic and can explain precisely why its retrieval failed before you fixed it. Strong Python or TypeScript, comfortable with vector and lexical search internals, and unromantic about model choice.

    Apply for Senior Applied AI Engineer

  2. Platform & Reliability Engineer

    Full-timeChandigarh or remote (India)

    Own infrastructure as code, deployment pipelines and the SLOs that keep them honest across several client environments. Deep AWS, Terraform and container orchestration, plus the judgement to know when a workload does not need Kubernetes. You have run a real incident and written the postmortem afterwards.

    Apply for Platform & Reliability Engineer

  3. Senior Product Engineer (Full-stack)

    Full-timeChandigarh, hybrid

    Build the interfaces and services clients use every day — Next.js and TypeScript on the front, Postgres-backed services behind. You care about p75 latency on a mid-range Android handset, about accessibility as a correctness property, and about schemas as the contract between layers.

    Apply for Senior Product Engineer (Full-stack)

  4. Data Engineer

    Full-timeRemote (India), occasional travel to client sites

    Build the warehouses, contracts and pipelines that every AI system quietly depends on. Comfortable with Postgres internals, columnar stores, change data capture and dbt, and able to explain to a client why their nightly batch cannot support the dashboard they have asked for.

    Apply for Data Engineer

Hiring process

What actually happens after you write.

  1. Step 01

    Written application and a short technical exchange

    No cover letter theatre. Send code we can read — a repository, a pull request, a piece of writing about something you built — and we reply with two or three specific questions about the decisions in it. Expect an answer either way within a week.

  2. Step 02

    Technical conversation, 90 minutes

    A real system you have operated, walked through in depth: the architecture, what failed, what you would do differently. No whiteboard algorithm puzzles and no trivia about syntax you would look up anyway.

  3. Step 03

    Paid working session

    A scoped piece of realistic work — roughly one day, paid at your day rate, done on your own schedule against a problem shaped like our actual engagements. You keep the code and we discuss it together afterwards, which is where most of the signal is.

  4. Step 04

    Founder conversation and offer

    How you want to grow, what you refuse to work on, and what you need from us to do your best work. References are checked with your permission, the offer comes in writing within three days, and the compensation band is stated before the call rather than negotiated out of you.

None of the above

Speculative applications are genuinely read.

If no role above fits but the way we work does, write anyway. Tell us what you have built and operated, what broke, and what you did about it. We keep a short list and go to it first when an engagement opens a seat — and we will say plainly if nothing is coming.

Write to careers@digiaeon.com