Engineering
AI Experience Builder
A product-minded frontend engineer: React and Next.js, about 70% engineering and 30% design
- Location
- Bengaluru, India
- Workplace
- Hybrid, 3 days a week in Bengaluru
- Type
- Full-time
- Experience
- 3 to 7 years
- Start
- Jan 2027
You own how delightful Rapidflare is to use. You're the first to imagine new ways to create impact, spot roadblocks and papercuts, and fix them before anyone asks.
What we're building
Millions of times a day, the world asks questions about electronics. Too often, the answers are inaccurate, incomplete, inefficient or low quality. Rapidflare builds AI agents for the electronics industry that deliver delight to humans and agents in these moments of truth.
Engineers, sales teams and support teams use our agents to find the right part, get deep technical questions answered from datasheets and documentation, compare products, and reach a design decision faster. The agents run on our customers' websites, in our admin dashboard, in Slack and Discord, and in a Chrome extension.
Behind those surfaces is a lot of hard backend work: ingestion, product catalogs, retrieval, evaluation. Our customers rarely see any of it. What they see is the experience, and for an AI product, the experience is most of what they judge us on.
Why this role exists
AI has changed how fast we build. Anyone on our team can take an idea to a working prototype in a day. Our designer edits the frontend codebase directly; our AI engineers build the UI for the features they ship. That velocity is real, but it has a cost. Prototypes arrive unpolished, patterns drift between codebases, and small papercuts pile up faster than anyone owns them. Today too much of that lands on two people: our frontend lead, who has carried the frontend codebase largely alone for a long time, and our design lead, whose time is better spent on where the product goes next than on the next UI request.
You would close that gap. Not a designer who codes a little, and not a frontend engineer who takes tickets. A builder, roughly 70% engineering and 30% design, who cares about the product the way a founder does.
What you will own
- The everyday experience. You use Rapidflare every day from the customer's seat. You find the papercuts and the big opportunities, bring them to the team, and are usually the first one out of the gate to fix them.
- Our frontend, together with our frontend lead. You co-own our frontend monorepo: the admin dashboard, the embedded agent, our embed SDK and the Chrome extension, built on Next.js, React and TypeScript. You review frontend contributions from across the team, make and maintain framework choices, and help start the frontend rotation we don't have yet.
- Prototype to product. Engineers and designers hand you rough proofs of concept, often built with AI in an afternoon. You turn them into something customers love, without breaking what's around them.
- The system that lets the team scale. If frontend contributions double or triple, the codebase should get more consistent, not less. You build and maintain our component library with our design lead, and make components shareable across our split codebases.
- Full-stack work in lockstep with the AI team. Many of our biggest features cross the stack: streaming agent answers, product catalogs, search. You understand the backend side well enough to know what your change touches.
- Several features at once. That's normal here. You juggle them, sequence them, and say plainly what's slipping.
Who you are
How you think. You start from the user. You think in flows, states and feedback before pixels, and you care about polish, fit and finish because you notice them in the products you use. You hold strong opinions about UX and frontend architecture, and you change them when someone shows you something better.
How you work. You use AI relentlessly, and agents write a lot of your code, but you stay in charge of it. You read what the agent produced, catch what it got wrong, and can explain every line you ship. You would rather talk to a customer than guess what they want. You write and speak clearly.
What you've built. Three to seven years building frontends, most of it in React, with real depth in Next.js: server and client components, rendering and hydration, performance with large amounts of data. You learned the fundamentals before AI wrote code for you, and it shows. You've shipped features people use, working alongside designers, backend engineers and product people. Visual design skills, AI product experience, a frontend operations mindset and experience running experiments are all welcome; none of them is required.
Where this can go. This role can grow into owning an entire product surface at Rapidflare: its users, its roadmap and its outcomes.
Who this isn't for. It isn't for you if you prefer to work alone, or if you need a finished spec before you start. It isn't for you if all of your development experience is AI-driven and you haven't built without it. It isn't for you if you'd rather be right than get it right; we give each other direct feedback, often, and that includes feedback to the founders. And if your next step is managing a team, this isn't that role. It is an individual builder role with a lot of ownership.
What it's like to work here
We're a small team punching above its weight class. Every person carries a lot of ownership, makes decisions daily and drives impact on their own. The AI space changes daily, and our team has learned to deal with ambiguity and rapidly evolving priorities. We move quickly and expect you to as well. If that sounds draining, it's better that you know now. If it sounds like the place you've been looking for, keep reading.
How we hire
We want to understand what makes you a great fit and how you think about your work. This is how we'll run our interviews.
- Your application. We don't want a generic application. We're looking for motivated applicants who can show us what makes them special and a great fit. Respond to these three prompts:
Tell us:
- If you had 30 to 45 seconds to give an elevator pitch about yourself, what would you say?
- What is one thing you built that you are proud of, and what was your role in it?
- AI is now great at designing and building frontends. How have you evolved, and what has changed in the way you work?
Choose a way to respond. The application form shows the prompts again, under Your answers:
- Record a short selfie video, two minutes or less, and paste the link (Loom, unlisted YouTube or Google Drive) in the video or audio link field.
- Record an audio clip answering the three prompts, upload it to Google Drive, and paste the link in the same field.
- Write your answers in the form, or attach them as a document.
- Screening conversation (45 min). Your background, what you're looking for, and whether this is a fit both ways.
- Technical interview I: Frontend (60 min). A collaborative code and architecture review in a Next.js codebase we built for the interview. Bring the AI tools you use every day. We want to see how you work with them, and where your own judgment takes over.
- Product interview I (75 min). At the start of the call we send you a rough clickable prototype and a short design problem, then leave you to it. You get 30 minutes on your own to make it better, with any tools you like, AI included. Then we rejoin, you show us what you made, and we talk it through. No code is judged, and there's nothing to prepare beforehand.
- Technical maturity and stewardship (60 min). The same problem from Product interview I, now as a real Next.js codebase. We discuss how you would take it to product-grade inside our system and bring others along.
- Principal engineer interview (60 min).
- Closing conversation (30 min).
We hire based on demonstrated capability and potential, not your pedigree. If what we described is not exactly your profile, but it is how you envision yourself, we encourage you to apply.
Want to know what working here is like? See how we work.
AI Experience Builder
Add your CV and your responses in a video, audio clip or note. A person on the team reads every application.