Software Engineer

Somewhere in Bengaluru, one brake pad has four names. Tally calls it F00X H23 42613. The warehouse calls it F00XH2342613. The supplier’s catalogue has a third code, and the counter staff have a nickname for it.

To a person, that’s one part. To a computer, it’s four. We’re hiring someone who finds that problem fun.

WHAT WE DO:

Autoryx builds the software that runs a distributor: parts catalogue and vehicle fitment, orders, godown, field sales, a dealer ordering app, and the Tally connection underneath all of it.

We didn’t build it in a conference room. We built it inside Vikas Trade Links, an auto parts distributor in Bengaluru, and it runs there and at Potauto every day. The people who use what you ship are salesmen, godown pickers, billing clerks and dealers, often in the same week you ship it.

PROBLEMS WAITING FRO YOU:

•      A Tally server that answers one question at a time, and keeps working on a question you gave up on until someone restarts it. Sync hundreds of bills a day without jamming it.

•      A dealer statement that has to match Tally to the rupee. Not roughly. We say “wrong data is worse than no data”, and we mean it.

•      Catalogues that arrive as scanned PDFs, 800 MB design files and phone photos. Turn them into parts, vehicles and what fits what.

•      An order with 30 lines where 24 are in stock. Supply those, keep the rest open, and tell the dealer and the salesman.

•      A salesman in a shop with one bar of signal and a budget phone. Your API has to work for him.

WHAT YOU’LL DO:

•      Build and own backend services and APIs for catalogue, fitment, inventory, orders and field sales.

•      Keep the Tally sync fast, safe and correct, in both directions.

•      Write the checks that prove a number is right before anyone sees it.

•      Design data models and migrations in PostgreSQL that survive real, messy data.

•      Build and own backend services and APIs for catalogue, fitment, inventory, orders and field sales.

•      Keep the Tally sync fast, safe and correct, in both directions.

•      Write the checks that prove a number is right before anyone sees it.

•      Design data models and migrations in PostgreSQL that survive real, messy data.

YOU’LL NEED:

•      Experience building and shipping backend APIs in at least one of Node.js, Python, Go or Java. Jobs, internships and serious personal projects all count.

•      SQL beyond SELECT *: joins, indexes, and at least one migration you’ve run on real data.

•      Solid CS basics: data structures, algorithms, and how a database stores and finds things.

•      Git and tests as habits, not chores.

•      A degree in computer science or engineering, or equivalent practical experience.