ALGOBAIN
A team of engineers working together at laptops around one table
[Photo placeholder] Engineering team, Indore

Careers

Build it. Run it. Own it.

We are looking for engineers who want to see their work hold in production, and who would rather be on call for a system than hand it over.

Indore, remote and hybridFull-time and contract roles across AI, engineering and mobile.

01Why work here

Work that ships, and stays yours.

i

Ownership, end to end.

Every engineer owns their work from the first diagram to the on-call rota. The person who designs a system is trusted to run it.

ii

Current tools, applied with judgement.

We work with the latest models and agent frameworks, and use them where they earn their place. Proven engineering everywhere else.

iii

Learning is part of the job.

Continuous learning and development is built into how we work: reviews, pairing and the decision record of every engagement are open to the team.

iv

Production, not pilots.

What you build goes live and is held to a number. Our clients run systems with 99.7% uptime because the people who wrote them are the people who keep them up.

02How the team works

Senior judgement, with agents doing the volume.

You will direct fleets of AI agents that explore codebases, draft options, write tests and review changes, while you set the architecture and make the decisions that matter.

An engineer working at a laptop in a bright office
[Photo placeholder] Reviewing a change against the request
01

Test first, always

A failing test before the code, a passing run after, and a review against the original request. Nothing ships past a failed gate.

02

A record as you go

Every decision, test result and approval is logged as the work happens, so nobody inherits a mystery.

03

Close to the client

Engineers attend the assessment, the reviews and the incident calls. There is no account layer between you and the people using the system.

04

Human in command

The systems we build put a named person at every consequential decision. We hold our own work to the same rule.

04Hiring process

Four steps, each with a reply.

Every applicant hears back. Durations below are placeholders until the team confirms them.

From application to offer

Send your work

Day 1

A short note, the role, and something you built: a repository, a write-up or a system you ran.

Engineer conversation

[Within X days]

A call with a senior engineer about your work and how you make decisions, not a quiz.

Working session

[Format and length to confirm]

A problem close to the real work, reviewed the way we review every change.

Offer

[Within X days]

A written offer, or a written reason why not.

Engineers working side by side at laptops on a shared desk
[Photo placeholder] Pairing session
An engineer working on a laptop inside a hardware lab
[Photo placeholder] On site, integration
Who you work with

Senior engineers who write the assessment, build the system and stay on call for it afterwards.

A quiet open office with desks and large windows in daylight
[Photo placeholder] Head office

Show us something you built.

Use the short form, name the role in the message, and link your work. A senior engineer reads every one.

  1. 1
    The work you would joinCase studies
  2. 2
    What we buildFive practices
  3. 3
    How we thinkInsights