About the role You have personally shipped a consumer financial product to real users — and you can name the line of code, the policy clause, or the CS conversation that broke things and what you did about it. Not "led a team that shipped." Not "owned the roadmap." You wrote the spec, you sat in CS calls, you queried the data yourself, you watched the dashboards on launch night. That is the qualifying condition for this role. Everything else in this document is for people who pass that bar. If you do not pass it, no amount of brand-name PMs on your resume, MBA pedigree, or strategy deck experience makes up for it. We will know within ten minutes of an interview. Save us both the time. If you do pass it, this is the role you have been waiting for. The bet Every fintech in India is shipping the same feature set: savings, cards, investments, wrap-around banking. We are betting that the company that ships them with the most opinionated taste — fewer screens, fewer settings, fewer apologies — owns the next decade of consumer finance in India. That bet runs through every PM here. You will own a consumer-facing surface end to end. Roadmap, specs, design partnership, engineering partnership, CS feedback loops, compliance review, launch operation, post-launch retention. You will not have a strategy team. You will not have a research team. You will not have a launch ops team. You will be all of those things. The team you'll work with — small, young, fast, default-AI Most of the people you will work with are in their twenties or early thirties. The defaults are "build it yourself, ship it tonight, fix it tomorrow." Meetings are short. Documents are shorter. The right hire treats this as a feature, not a compromise. You will be one PM among a handful, owning a meaningful surface. You will move at the engineering team's pace, not slower. You will earn their respect by writing the SQL alongside them, not by holding alignment reviews. If you have spent the last three years building scaffolding around yourself — PgM partners, ops partners, strategy partners, BI partners — you will struggle here. If the thought of doing your own data pull at 11pm to settle a launch question makes you happy, read on. What makes this different from the same title anywhere else The surface is the company, not a screen. Most PM roles at this band own a flow. You will own a value-prop. The decision on whether we launch a feature on a regulated entity vs. a PPI rail goes through you. You will use AI as a first-class teammate, not as a feature to add. The spec you write, the CS analysis you do, the user research you run, the launch comms you draft — they all use models. You won't get points for "leveraging AI." You will lose points for not. It is regulated infrastructure, and that is a feature. Two RBI-licensed entities sit underneath the surface. Most of your launches will pass through a compliance review you will sit in. The moat that comes with doing it right is real. You will work next to peers who match your bar. The Director of Product (AI), the Director of Engineering (AI), and the founding PMs all hire to this same filter. What you'll own The end-to-end PRD. Customer problem statement, the chosen segment, the named alternative we will not build, the metric we will move, the kill criteria. Written in markdown, not Confluence. No longer than two pages. The launch decision. Whether we ship, whether we delay, whether we kill. You will own the data pull that supports the call. You will own the conversation with the founder when the data disagrees with the plan. The CS feedback loop. You will read CS tickets for your surface daily. You will sit on a CS call weekly. You will know the top three reasons users complain about your feature within a week of launch. You will turn at least one of them into a shipped fix within two weeks. The compliance partnership. You will sit in the compliance review for every regulated decision. You will know what RBI, NBFC, PPI, and DPDP each constrain and where they intersect. You will not delegate this to a compliance partner who walks into the meeting cold. The taste call. You will be the final arbiter of one specific screen, one specific copy line, one specific entry point. When engineering disagrees, you will hold it. When design disagrees, you will hold it. When you are wrong, you will admit it within a week and ship the fix. What we're looking for, beyond the qualifying filter Operator instincts. When something is wrong with a launch, you read the events, write the SQL, talk to the user, file the bug. You do not "ask the team to look into it." Range across products. You will not own one surface for years. As Jupiter moves, your remit will too — savings one quarter, cards the next, payments the one after. If you need 18 months to "really understand a domain" before you can contribute, this is not a match. You are at home in week three on a new product because you read the events, talked to ten users, and shipped a small fix. This one is non-negotiable. Fintech experience is a tailwind, not a requirement. If you have shipped consumer products in another domain — health, ed-tech, gaming, commerce — the qualifying filter and the operator instincts matter more than the category. The compliance literacy is teachable in the first 90 days; the operator instincts are not. Spec discipline. Your specs are short, specific, and falsifiable. You name the metric, the threshold, and the kill criteria upfront. You do not write "drive engagement." Default-AI fluency. You can write a Cursor or Claude agent prompt that pulls a product question from the team Slack and answers it from the metrics warehouse. You have done this. You can show us. Cost and latency taste. You know how much an LLM call costs and how long it takes. You know which decisions belong to a model and which belong to a rule. You have killed a feature for being too slow, and you can tell us which one. Comfort with a small, fast team. You see "the team is small" as freedom, not as understaffing. You ask "can an agent do this" before you ask "who can we hire to do this." What you won't do Run quarterly OKR ceremonies. Write 20-page strategy decks no one reads. Outsource customer research to a vendor. Hand off launches to a launch operations team. Build scaffolding to feel senior. Spend any time defending why product matters at Jupiter. The bet is made. What success looks like at six months You own your surface end to end. Leadership is no longer in the launch decision Slack thread. The top three CS complaints from your launches are down meaningfully against a day-one baseline. You have shipped at least one decision that the rest of the org has copied. The team that was small and fast when you joined is still small and fast. The basics Experience: 3 to 5 years. We are looking for PMs early in the build-it-yourself phase of their career, not people who have already moved on to running rituals. Compensation: ₹30L to ₹50L cash, plus an equity package sized to be material at exit. We pay at the top of the Indian consumer fintech market for this band. If you are exceptional, we will go higher. We will be specific about valuation, strike, vesting, and the math in the conversation. Location: Bangalore, in person. This is not a remote role. Reporting: Reports to the Director of Product. How to apply Send us the product you shipped. A link to the live feature, a screenshot of the dashboard on launch day, a screen recording of the user reaction. One paragraph on what you would change about it now and why. We will read this before we read your resume.