Skip to content
CV Rocket
Get started
How it worksThe enginePricingBlogContactSign in

Open nowPosted 218 days ago

Software Engineer

Practice By Numbers18 open roles

Where
Gurugram, Haryana, India
Work mode
On site
Get the CV for this job

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

Your applicationOpen nowSoftware EngineerPractice By Numbers · Gurugram, Haryana, India

  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 Practice By Numbers'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.9% of postings close within 7 days. Measured by our own scanner across the market.

Share of postings closed within
  1. 2.1%1 day
  2. 4.4%3 days
  3. 11.9%7 days
  4. 18.6%14 days
  5. 35.6%30 days
  6. 45.1%60 days
This job: posted 218 days ago

The posting

Software Engineer Practice by Numbers · Gurugram, India · In-office (5 days) · Full-time

About us Practice by Numbers builds the software dental practices run their day on — scheduling, patient communications, analytics, VOIP and payments, in one platform. Around 1,500 practices across the US and Canada use us to run their front desk.

Payments is one of our fastest-growing areas, and one of the few where the software is directly responsible for whether a practice gets paid. We're investing heavily in it: new payment methods, new products built on the payments platform, and a lot of work making the core more reliable as volume grows.

We operate like a startup, because we are one. Scope is wide, decisions are fast, and there isn't a layer of people between you and the problem.

About the role We're hiring a software engineer for our Payments team in Gurugram. You'll report to our Payments engineering lead and work alongside senior engineers who've built this platform.

This is a good role for someone a few years into their career who wants to go deep rather than wide. Payments is an unusually good domain to grow in — correctness matters, edge cases are real, and the habits you build here (thinking about failure modes, retries, reconciliation, data integrity) transfer everywhere. It's hard to pick that up on a CRUD product, and it compounds fast once you have it.

You'll start with well-scoped work and a lot of review, and take on larger and more ambiguous pieces as you get your footing. We'd expect you to be owning a meaningful surface of the product within your first year.

What you'll work on Backend features and APIs in Python/Django — shipping real functionality that practices use the same week. Payment flows. Card transactions through in-office terminals, hosted payment pages, and patient-facing payment links. You'll learn how each one fails, which is most of the education. Recurring billing. Scheduled charges, retry behaviour, and the handling around payments that don't go through the first time. Integrations. Working against our payment processor's APIs and syncing data into third-party practice management systems. Queries and data. Writing and tuning PostgreSQL queries, designing tables, writing migrations that are safe to run against production data. Bugs and production issues. A real share of them, because debugging someone else's payment edge case is how you learn a payments system properly. Tests and tooling. Contributing to our test coverage and CI pipelines rather than treating them as someone else's job.

What we're looking for 3–5 years building backend software professionally, with solid Python experience. Django specifically is a strong plus, but we'll take a good engineer from another framework who wants to learn it. Comfortable with SQL and relational databases — you can write a join, read a query plan, and reason about what an index is doing. Experience building or consuming REST APIs. Familiarity with Git-based workflows — branching, code review, CI. Care about correctness. In payments, "mostly working" is a bug. We're looking for someone who tests their own work and thinks about what happens when things fail, not just when they succeed. Clear written communication. Our team spans the US, India and Bangladesh, so a lot of thinking happens in writing.

We care more about how you think than about your exact checklist of technologies. If you're strong on fundamentals and missing a couple of items above, apply anyway and tell us what you'd need to pick up.

Bonus, not required Any exposure to payments, fintech, billing or subscription systems. Redis, Celery, or background job processing. Docker. Experience working with an external API that was unreliable, and having to design around it.

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 Practice By Numbers'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 Practice By Numbers'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

    Practice By Numbers'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.

Get the CV for this job
By hand5–10
With CV Rocket100
applications a day

Nearby

Live postings like this one

Same employer first, then the same role elsewhere.

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.