Engineering
Experience Builder
A product-minded frontend engineer: React and Next.js, about 70% engineering and 30% design
- Location
- Bengaluru, India
- Type
- Full-time
- Experience
- 3 to 7 years
- Start
- Early 2027
You own how Rapidflare feels to use. You find what's wrong with it before anyone asks, and you ship the fix.
What we're building
Rapidflare builds AI agents for the electronics and semiconductor industry. 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
The honest version: we're a small team, and every person carries a lot of ownership. Nobody has the time to manage your work for you, and nobody will try. Priorities move as we learn from customers. 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 don't ask for a cover letter, and we don't rely on portfolios or GitHub profiles alone; AI makes all three easy to produce. We would rather see what you've built and watch how you think.
- Apply with a short video, five minutes or less. Tell us who you are. Show us one thing you built and what you personally did on it. Then walk us through one experience in a product you use every day that you would change, and how you would change it. Add links to anything live you've shipped. Record it however you like, then share it as a link (Loom, unlisted YouTube, or Google Drive) in the links section of the application, next to your CV.
- Intro conversation (45 min). Your background, what you're looking for, and whether this is a fit both ways.
- Frontend session (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 design session. How you think about users, flows and polish.
- Technical maturity and facilitation session. Taking something rough to product-grade, across the stack, and how you bring others along.
- Conversations with a company leader and with our CTO.
We are trying something different with how we hire for this role, and we expect to learn as we go. If the work above reads like yours but your background is unconventional, apply anyway. We hire on the work and the reasoning, not the pedigree.
Want to know what working here is like? See how we work.
Experience Builder
Add your CV and the link to your video. It takes about five minutes, and a person on the team reads every application.