zevOS

01Careers

Build the software that makes charging networks work

Small team, physical consequences, and a market that is being built now rather than optimised later.

Why here

What is genuinely different about this job

01

The problem is real and physical

Your code controls hardware in car parks and on highways. A bug is not a misaligned button — it is a driver who cannot charge, or a session billed wrongly. That constraint makes the work better.

02

You will talk to operators

Engineers here speak to the people running the chargers. Requirements arrive as specific reproductions from the field, not as tickets translated through three layers.

03

India-first, not India-adapted

GST, UPI, DisCom tariffs and monsoon failure modes are the design centre. You are building for the market you live in.

04

Small enough that it matters

Nobody here owns a feature nobody uses. What you ship goes into production and gets used by an operator within weeks.

Process

How hiring works here

  1. 01

    A conversation

    Thirty minutes about what you have built and what you want to build. No take-home yet.

  2. 02

    A technical discussion

    We go deep on something you have actually shipped, and on a problem from our domain. No algorithm puzzles unrelated to the work.

  3. 03

    A practical exercise

    Paid, time-boxed and drawn from a real problem — not a fictional one. You keep the work.

  4. 04

    Meet the team

    The people you would work with, asking their own questions and answering yours honestly.

  5. 05

    Offer

    With the reasoning behind the number, and room to discuss it.

Write to us anyway

If you are good at something we clearly need and have not listed, tell us what it is and what you would do here.