BILLFREE

Growth Engineer

Noida, Sector 63 • On-site • 2-5 years • Full-time

WHY THIS ROLE EXISTS

Every day, lakhs of retail transactions flow through Billfree across apparel, footwear, QSR, electronics, jewellery and more.

Each transaction is a signal. Who the customer is. What they bought. When they’re likely to come back. What would bring them back sooner.

Most of that signal goes unused across the retail industry — and honestly, we haven’t extracted all of it either.

Your job is to build the things that turn those signals into revenue: for our merchants, and for us.

WHAT THIS ROLE IS

Not growth marketing. Not backend engineering. Something in between that most companies don’t hire for.

You’ll find problems, build solutions, ship them fast, measure whether they worked, and either kill them or scale them.

Discover Build Experiment Measure Iterate

You’ll have enough engineering ability to build things yourself, without waiting for a sprint slot. And enough curiosity about the business to pick the right things to build.

WHAT YOU’D ACTUALLY WORK ON

Real examples of problems sitting on our list right now:

- Merchant activation. A retailer signs up but never runs their first campaign. Why? Find the drop-off, build something that fixes it, measure whether activation moves.
- AI agents for retail ops. A merchant asks “which customers haven’t visited in 60 days and spend above 5,000?” — and gets an answer, not a dashboard to navigate.
- Segmentation and lifecycle automation. Build the engine that decides which customer gets which message, when, on WhatsApp — across thousands of stores with very different buying cycles.
- New products. Some of what we’ll be selling in two years doesn’t exist yet. Take a hunch about where retail is going, build a working version of it, put it in front of merchants, and find out if you were right.
- Internal leverage. Sales, onboarding and support run on manual work that shouldn’t be manual. Automate it, and the whole company moves faster.
- Growth surfaces. Interactive calculators, self-serve onboarding,



in-product prompts — things that generate qualified interest without a sales rep in the loop.

You won’t do all of these. You’ll pick up whatever is most broken or most valuable at the time.

WHAT WE’RE LOOKING FOR

- 2–5 years of hands-on engineering. You can ship to production without supervision.
- Robust fundamentals over specific frameworks — we care more about how you think than what you’ve used.
- A builder’s instinct: you see a problem and reach for a prototype, not a document.
- Comfort with ambiguity. Most of what you work on won’t arrive as a written spec.
- Genuine interest in why something matters commercially, not just how it works technically.
- Willingness to kill your own ideas when the data says so.
- Curiosity that pulls you outside your current stack.

You don’t need retail or SaaS experience. You do need to be the kind of person who gets restless watching someone do something manually for the fifth time.

HOW WE BUILD

AI is not a side experiment here — it’s part of the daily workflow.

We use Claude Code, Cursor, Codex and similar agents as force multipliers. That means you should be able to:

- Give an agent enough context and constraints to produce something useful
- Review, challenge and debug what it produces
- Use it to move fast through unfamiliar codebases and technologies
- Know when to stop using it, because deterministic engineering is the better answer

We’re wary of two failure modes: engineers who won’t use AI, and engineers who ship whatever it produces.

STACK

You won’t know all of this. You should be able to pick up most of it.

Backend

Node.js, TypeScript, Express / NestJS, REST APIs, webhooks, event-driven systems

Frontend

React, Next.js,



responsive UI

Data

MySQL / PostgreSQL, MongoDB, Redis, data modelling, query optimisation

AI

LLM APIs, function calling, RAG, agents, prompt engineering

Infrastructure

AWS, Linux, Docker, CI/CD, production debugging

THINGS WORTH KNOWING BEFORE YOU APPLY

We’d rather you self-select out now than three months in.

- Schedule. Monday–Friday in office, Saturday from home. It’s a six-day week. Sundays are yours.
- Ambiguity is the default. You will regularly be handed a problem, not a solution. If that sounds stressful rather than interesting, this isn’t the role.
- Cross-functional by force. You’ll talk to sales, ops and merchants. You’ll be on calls that aren’t about code.
- Some of what you build will be thrown away. That’s the point of experiments. If you get attached to your work, it will hurt.
- Small team, wide surface area. Real ownership, but also less structure than a larger company.

ABOUT BILLFREE Billfree Labs builds the post-purchase layer for offline retail.

Retailers already have billing software. It records what happened. We connect to it and help them use what happened — customer profiles, digital bills, loyalty, feedback, Google Reviews, WhatsApp campaigns, retention automation — to influence what happens next.

The bill shouldn’t end the customer relationship. It should start the next one.

We work with [X]+ businesses across India today.

HIRING PROCESS

1. Intro call — 30 minutes, mutual fit.

2. Technical conversation — walk us through something you’ve built end-to-end.

3. Build round — a real problem from our backlog, take-home or paired, your choice.

4. Final round — with leadership, on how you think about problems and outcomes.

We aim to close within two weeks of the first call.

Compensation : depending on experience.

TO APPLY

Send your CV to [email protected] & call us at (phone hidden)— and one paragraph on something you built because it annoyed you that it didn’t exist.

That paragraph matters more to us than the CV.

📌 Urgent Hiring I Growth Engineer I Billfree (Noida)
🏢 Billfree
📍 Noida