Skip to content

Open nowPosted 8 days ago

Senior Software Engineer I/II - Backend (Python)

UrbanPiper1 open role

Where
Bengaluru
Get the CV for this job

From $25 per CV, paid once. No subscription.

Your applicationOpen nowSenior Software Engineer I/II - Backend (Python)UrbanPiper · Bengaluru
  1. YouYes, apply to this one.

  2. CV RocketCV written for this posting.

  3. 25 readersRecruiter, hiring manager, skeptic. Round after round.

  4. CV RocketApplied on UrbanPiper's own form.

The reply lands in your private mailbox

3×more interviews than doing it yourself with ChatGPT.

The clock on this job

Early applications get read.

11.5% of postings close within 7 days. Measured by our own scanner across the market.

Share of postings closed within
  1. 2.0%1 day
  2. 4.3%3 days
  3. 11.5%7 days
  4. 18.1%14 days
  5. 35.6%30 days
  6. 44.6%60 days
This job: posted 8 days ago

The posting

About UrbanPiper

Close to 30 million restaurant orders a month run through UrbanPiper. We sit between thousands of restaurant kitchens and everywhere they sell: Swiggy, Zomato, their own storefronts, the POS at the counter. When we get it wrong, a restaurant stops selling. When we get it right, nobody notices. That's the job.

About the Team

A restaurant's menu is its storefront, and it lives in a dozen places at once. Change one price, one add-on, one opening hour, and it has to land correctly on every aggregator, each with its own schema, its own rate limits and its own ways of failing silently. Now do that for thousands of brands, hundreds of times a day at peak.

The Menu team owns that pipeline: ingestion, publishing, and knowing exactly what went where when something breaks. The hard parts are : data modelling, idempotent sync, async processing at scale, and partners who change their APIs without telling you.

How we work

Small team, large surface area. We use AI as a force multiplier & not just to speed up coding. We expect you to work effectively with AI agents, exercise sound engineering judgment, and take ownership of what ships. Not every problem comes with a clear spec or an obvious solution; we expect you to iterate, challenge your assumptions, and find the best solution to the problem.

What you'll do

  • Ship to production in your first week. Then keep shipping.
  • Take a merchant's "my prices are wrong on Zomato" from Support, find the cause in the logs and the data, and make sure it can't happen again.
  • Design async pipelines that survive retries, partial failures and rate limits (Kafka, RabbitMQ, SQS, Temporal).
  • Model messy catalogue data so that each new aggregator's quirks stay out of the core.
  • Build the validation loops that make AI-written code safe to ship: tests, replays against real production payloads, staging checks.
  • Instrument your services well enough that you find the bug before the merchant does.
  • Review code, write design docs, and go on call for what you built.

You'll fit if

  • You're AI-native. You run AI coding agents (Claude Code, Codex, Cursor or similar) every day, and not as ask-and-hope. You think before you prompt, give the agent the right context, and close every loop with a check. You have opinions on models, tools, plugins and skills, and you can defend them.
  • You take responsibility for what ships, regardless of who wrote it. AI makes mistakes; you know where, and you catch them before production does. You own the code whether you typed it or not.
  • You've built Python backends that run in production at meaningful scale. Django or FastAPI (we run both), REST and GraphQL APIs with versioning, pagination and error contracts.
  • You know your fundamentals. Data structures, testing, SQL you can index and read a query plan, and the ways async systems fail.
  • You write clearly. A PR description or incident note from you explains the trade-off.
  • You've owned something. A service in production, a design across teams, engineers who got better working with you.

Good to have

  • You have built your own AI tooling: agent skills, MCP servers, hooks, eval sets, or automations that run without you.
  • Hands-on experience with Kubernetes, Helm, and GitOps with ArgoCD.
  • Catalogue, e-commerce, or third-party marketplace integrations.
  • Durable workflow engines such as Temporal.
  • Experience at a fast-paced startup.

Your first 6 months

  • Week 1: ship your first PR to Prod! You set up your environment and AI tooling yourself, from the code and the docs.
  • Month 1: you take a real customer escalation, root-cause it from logs and data, and ship the permanent fix. You're on the on-call rotation.
  • Month 3: a part of the menu pipeline is yours, end to end. Something you shipped is used daily by partners or Support, with alerts and dashboards you built.
  • Month 6: you own a number, such as publish failure rate or ingestion time, and you've moved it. You've led a design across services, contributed to next quarter's roadmap for your area, and built tooling that makes the rest of the team faster.
From $25, paid onceGet the CV for this job

What happens when you press

One press. We do the rest.

  1. A CV for this posting

    Written against UrbanPiper's own wording, from every piece of relevant proof in your profile.

  2. 25 readers review it

    Recruiter, hiring manager, skeptic and more read every draft, round after round. You get the best round.

    The review screen in CV Rocket: how each CV was read, round by round.
  3. We apply on UrbanPiper's form

    Our application engine gets through the hardest forms there are. Where a question needs you, AI suggests the best answer. Don't want us applying from our IP addresses? Use our Chrome extension: we apply straight from your own browser.

    An application in CV Rocket: every answer filled in on the employer's form.
  4. Every reply, sorted

    UrbanPiper's answer lands in your private mailbox, and we classify it on arrival: interview, question, rejection.

    The CV Rocket inbox: each employer reply classified as an interview, an action or a rejection.
  5. Reply with AI

    AI helps you write the email, checks it and sends it. We show you whether the recruiter read it.

  6. The interview in your calendar

    Full integration with your calendar. The invitation goes straight in.

    An interview invitation in the CV Rocket inbox, added to the candidate's calendar.
Get the CV for this job

From $25 per CV, paid once. No subscription.

Why it works

3×

more interviews than doing it yourself with ChatGPT.

ChatGPT writes a CV and never learns what happened to it. We see every reply. For each CV we know:

  • How it was written, and how the review scored it
  • When we applied, and how long after the posting went up
  • Which posting, which company, which city
  • Who got the interview, and who heard nothing

That is how we know which CVs get called.

Get the CV for this job

From $25 per CV, paid once. No subscription.

The numbers game

More applications. More interviews.

Every application goes out with its own CV, written for that posting and paid once. Send enough of them and the law of large numbers finds you the job.

By hand5–10
With CV Rocket100
applications a day

Before you press

Straight answers

Get the CV for this job

From $25 per CV, paid once. No subscription.

What if my background isn't good enough?

We make the most of the background you have. The CV uses every piece of relevant proof your profile holds, and one of the 25 readers reads your whole profile and flags what the CV left out.

Do you really apply for me?

Yes, on the employer's own form, the hardest ones included. Where a question needs you, you answer it right there and AI suggests the best answer. Don't want us applying from our IP addresses? Use our Chrome extension: we apply straight from your own browser.

Is it a subscription?

No. You pay once per CV, from $25. Every application goes out with its own CV, written for that posting.

One job. One CV.
Paid once.

Pick the posting you want. We write for it, apply for you and catch the reply.

Get the CV for this job

From $25 per CV, paid once. No subscription.