Technology & Intelligence Ref XE-TEC-207 Open

Graduate Software Engineer

Start your engineering career on real client builds, with a mentor, a rotation across three teams and a clear path to mid-level.

Illustrative opening — hiring confirms the details before it opens.

Share Email it
Two engineers at a desk discussing code on a monitor, one leaning over the other's shoulder.
The practiceTechnology & Intelligence
Practice
Technology & Intelligence
Location
Ludhiana · New Delhi
Work pattern
On-site
Level
Entry
Type
Full-time
Experience
0–1 years
Salary band
₹7–10 lakh a year Indicative
Openings
4
Posted
Closes
72 days left

About the role

Our early-careers track for engineers. You will spend your first year rotating through three teams — web, data and AI — with a named mentor and a written plan for each rotation.

You will write production code from the first month, learn how we test and review, and learn how to use coding assistants without handing them your judgement. The track is designed to take you to mid-level in about two years.

What you will do

  1. Write, test and ship production code under review
  2. Rotate through web, data and AI teams across your first year
  3. Learn our review, testing and release practices
  4. Keep a short weekly log of what you learned and what you are stuck on

A typical week

Where the hours go in an ordinary week, and which parts agents carry. Whatever an agent drafts or checks, a person decides what happens next.

Graduate Software Engineer 40 hours in a typical week
  • You22 h · 55%
  • You, with an agent drafting14 h · 35%
  • An agent runs it, you review4 h · 10%
  1. Writing and testing code

    You write it; a coding assistant may suggest — you check every suggestion and say so in review.

    You, with an agent drafting14 h

  2. Pairing with your mentor

    Daily at first, then as you need it.

    You10 h

  3. Code review, both ways

    Your changes reviewed, and your first reviews of others’.

    You6 h

  4. Rotation learning sessions

    Web, data or AI — whichever team you are with.

    You6 h

  5. Reading CI results

    Tests and checks run on every change; you learn to read and fix what fails.

    An agent runs it, you review4 h

An illustrative split, not a timesheet. The hiring lead walks you through the real one in your first conversation.

What you bring

  • A degree in computer science or related field, or equivalent evidence of skill
  • Projects you built yourself — a repository link matters more than grades
  • Comfort with one programming language
  • Curiosity about how things work under the hood

Nice to have

  • Contributions to open source
  • An internship at a product or services company

Never a reason to rule anyone out. If you have most of the list above and none of this, apply.

Tools you will use

Grouped by what they are for. Nobody knows all of them on day one.

Languages & runtimes
  • TypeScript
  • Python
Web & frontend
  • React
Data, analytics & streaming
  • PostgreSQL
Containers, IaC & CI/CD
  • GitHub
Testing & quality
  • Jest
  • Playwright

Technologies we work with and license — not partnerships.

Your first 90 days

  1. Days 1–30

    Set up, pair daily with your mentor and merge your first small change

  2. Days 31–60

    Build a feature with its tests, reviewed by two engineers

  3. Days 61–90

    Your first rotation review, and the plan for the next team

A hand-drawn goal review on dot-grid paper: tallies for weeks one to eleven beside an assess-and-plan column, two pens resting on the page.
The plan is written down before your first day, and you review it with your lead as the weeks go by.

Where you would work

The places this role can be based. Each team agrees its own studio days; remote roles meet in a studio for a team week each quarter.

  • Traffic at a busy junction in Dugri, Ludhiana, seen from a rooftop among trees.

    Studio

    Ludhiana

    Two floors on Ferozepur Road, opposite Hotel Park Plaza.

    Pictured: Ludhiana (Dugri)

  • Auto rickshaws on a wide avenue in New Delhi, the dome of Rashtrapati Bhavan at the end of the road in evening haze.

    Studio

    New Delhi

    Studio at Aerocity, ten minutes from the airport — handy for client travel.

    Pictured: New Delhi

How and where we work

What we offer

With this role

  • A named mentor and a written rotation plan
  • A learning budget from month one

With every role

  • Health and family

    Medical insurance · Parental leave · Mental health

  • Time

    Paid leave · Winter break · Flexible days

  • Growth

    Learning budget · Growth reviews · Internal moves

  • Setup

    Your own machine · Home office · Team weeks

The full benefits schedule

The team you would join

Technology & Intelligence, the practice behind this role.

Engineers who build websites, platforms, data systems and AI products, with tests, evals and security in the pipeline on every change.

Open roles in this practice
4 on the board
Based in
Remote (India) · New Delhi · Ludhiana

Where this role sits

L2 of 6 · Associate

Owns a deliverable. Ships reliably with review.

Each level is defined by the scope you own, not years served. Growth reviews twice a year measure you against the six standards at your level.

Ways in, and ways up
  1. L1 Intern A task
  2. This role L2 Associate A deliverable
  3. L3 Mid A feature
  4. L4 Senior A workstream
  5. L5 Lead An engagement
  6. L6 Principal A practice

The rung below

L1 · Intern — A task. Learns the craft on real work, with a mentor.

Next rung

L3 · Mid — A feature. Owns a piece of work end to end.

How we hire for this role

5 steps, and a reply after every one.

The same five stages we use for every role. Timings are targets; when one slips, we tell you.

  1. Within 5 working days

    Step 1: Read

    A practitioner in the practice reads your application — your links first, your CV second. No keyword filter, no agency.

  2. Week 1 · 45 min

    Step 2: Conversation

    The hiring lead: the role, your work, and the level and salary band — before you invest more time in us.

  3. Week 2 · 2–3 h, paid

    Step 3: Work sample

    A short exercise close to the job, or a deep review of work you have already done. Paid, and never unpaid spec work.

    Work sample · the brief
  4. Week 3 · half a day

    Step 4: Team day

    Meet the people you would work with, in a studio or on video. Ask them anything; they will answer honestly.

  5. Week 3–4

    Step 5: Offer

    In writing, with the level, the salary, the full benefits and a start date that suits you. No exploding deadlines.

What helps an application

  • A link to work you made, with your own part in it named.
  • One project you could talk through for half an hour.
  • If you used AI, a line on how you checked what it produced.
  • Plain words. We read for substance, not polish.

Adjustments. Extra time, questions in advance, captions, a different format — tell us on the form or by email. Asking never counts against you.

Start the application

Graduate Software EngineerLudhiana or New Delhi · On-site · Closes 15 Dec

Apply for this role

Your move

Not the right role yet? Tell us what you would build here.

A speculative application gets the same read as any other: a practitioner in the practice you choose, and a reply either way.