Read this first
You have shipped product design that moved a real metric at scale. And you personally build with AI tools: working prototypes, not static frames, and at least one AI-native experience that reached real users.
If both are true, everything below will read like the role you have been waiting for. If not, stop here. We mean the filter literally: the first interview is you demoing something you built yourself, running live, on your machine. Not a case study. Not a walkthrough of frames. A working thing.
The context
Jupiter is a neobank across savings, payments, cards, loans, investments, and insurance, built on RBI-regulated entities with partner banks. We have made a company-level bet: AI is not a feature layer on the app, it is the next version of the app. A family of production agents already runs inside the business, and the next phase is customer-facing, starting with an agent that replaces our customer servicing stack.
But most of what users touch this year looks nothing like a chatbot. Onboarding. Card activation. Repayment flows. Payment success screens.
The designers who win here carry both: classic consumer design craft where a two percent funnel lift is real money, and the ability to design for a model whose output is not deterministic. And here is the genuinely unsolved part: when an agent moves money, blocks a card, or explains a regulatory protection, the cost of a bad interaction is real financial harm. The design patterns for this do not exist yet. Confirmation without friction. Confidence without overclaiming. Disclosure that satisfies a regulator and still reads like a human wrote it. You will be creating these patterns, not applying them.
What you'll own
Core product surfaces. Depending on fit: onboarding, payments, cards, or lending. Funnels, friction, comprehension, trust. You own design metrics on these surfaces and you move them.
The AI interaction system. A coherent design language for every agentic surface at Jupiter: convers
📌 Senior Product Designer (India)
🏢 Jupiter
📍 India