Careers
We spent a few years building a product that works — small team, no hype, no shortcuts. The 0 to 1 is done. What is left is the part that needs more people whose thinking we trust.
Five seats, all in Bengaluru. We read every application ourselves.
You will own Recepto's story and how it travels - founder-led LinkedIn, how we show up in answer engines, our own signal data, and the rooms where our buyers already gather. You are the first marketing hire, so you will build the engine rather than inherit one.
You will own the pipeline end to end - finding and qualifying prospects, running demos, and closing them - and then stay with the accounts you closed. It suits someone early in their career who wants to learn B2B SaaS sales from the founders rather than from a playbook.
You will own customers after they sign - onboarding them, getting them to actually use the product, and going deeper into the accounts you look after. It suits someone early in their career who wants to learn B2B SaaS customer success from the founders rather than from a playbook.
We're hiring for a role we haven't finished naming. Design Engineer, Product Designer - call it whatever fits on your LinkedIn. What matters is that you own products end to end, from the messy problem to the thing people pay for.
We are looking for a creative Content Writer Intern to help tell the Recepto story. You'll work closely with the marketing team to craft compelling blog posts, case studies, and social media content.
Not values on a wall. These are the things that actually decide whether a piece of work is finished here, written down so you can tell before you apply whether you would enjoy it.
Nobody here is handed a queue. The work starts at the messy thing nobody has written down yet — a broken flow, an account that has gone quiet, a number that stopped making sense — and framing it well enough that the team can act on it is most of the job.
Every piece of work says which number it is meant to move, and someone goes back to check. Shipped, sent, signed, renewed — if it did not move a number, it is not done.
We would rather have the pattern that holds at ten times the volume than the heroic one-off, whether that is a product primitive or the way we onboard an account. One-offs are cheap to make and expensive to keep, and we have rewritten enough of them to know it.
We read what you owned end to end and what it changed — a portfolio, a pipeline, a launch, a customer who stayed. What it was called matters least of all.
The product got built by a small team over a few years without either, and it is the same reason we would rather talk to thirty people looking for us than spam three hundred who are not. We would rather be quietly correct than loudly early.
We are one room. That is a real constraint on hiring, and we treat it as one — being excellent is not a substitute for being good to work beside.
There is no portal and no tracking number. Every role on this page applies by email, and the address goes to us rather than to a queue.
Send
One email to hr@recepto.ai, with the role in the subject line.
Show
One thing you owned end to end and the number it moved. For design roles we would rather see a portfolio than a CV.
Skip
The cover letter. Titles are the least interesting part of an application — we have posted roles we had not finished naming.
We do not always post everything, and the best hires we have made wrote to us before there was a listing. If you think you belong here, say so and show us what you have owned.