Staff Software Engineer, Frontend at Further AI in India

Job description

• Application
• The role
• Nobody owns our frontend today. It's grown to ~690K lines of TypeScript/React across ~2,250 files — a workflow builder, a citation-backed document viewer, data grids holding tens of thousands of rows, a chat assistant, and live views of agents running for minutes at a time. Features ship every week, but the parts nobody owns pile up: two generations of the workflow builder running side by side mid-migration, the same component built three times, performance with good tooling and no one driving it.
• We're not hiring you to clean up after us. We're hiring you to decide what "good" looks like here, say it out loud, and make it true — while the product keeps shipping.

Responsibilities

• Architecture and stack. State, data fetching, routing, module boundaries, build tooling — what we keep, what we drop, what we add. Today: React, TypeScript, Vite, Tailwind, Radix, TanStack Query, Bun. You decide what it looks like in a year.
• One component system. We have ~90 shared primitives and 231 Storybook stories, and we still write the same component twice. Pick the one that wins, migrate the product onto it, and put a gate in place so it stays that way.
• Performance as a number, not a vibe. Our home route ships ~567KB of gzipped JS before a user can interact. We have bundle budgets, Lighthouse in CI, real-user vitals, and a Sentry digest — nobody's driving them. Own the number, move it, and tell us by how much.
• Product craft. Work with our designers as a peer — critique their work, fill the gaps, hold opinions on layout, density, motion, and hierarchy, and argue for them.
• A codebase that's safe for coding agents to touch. A large share of our code now arrives from coding agents. Typed boundaries, lint rules, visual regression tests, and fast feedback loops are what make that safe at our speed — you design for it.
• The engineers around you. Review, mentor, and hold the bar on every frontend change, across India and the US.
• Two concrete examples of the kind of problem this role exists to solve: converging our two live generations of the workflow builder into one without freezing the product for a quarter, and designing the interaction patterns for agents that stream partial results over minutes — there's no established playbook for this yet, you'd be inventing ours.

Requirements

• 8+ years building production frontend, deep in React and TypeScript — you've shipped customer-facing product fast and lived with the consequences afterward.
• You've owned a frontend codebase, not just features inside one: architecture, build tooling, component systems, test strategy, release safety.
• Demonstrated performance practice — you've held a number and moved it. We'll ask which one and by how much.
• Real product taste — you can look at a screen and say precisely what's wrong with it and why.
• Sharp with coding agents — you push back on what they write rather than merge it on faith, and you build the checks that make agent-written code safe to ship.
• A clear writer — we make most decisions in writing, across time zones.
• Bonus: design systems experience, data-dense or document-heavy products, 0-to-1/early-stage work, B2B SaaS, LLM-backed interfaces.

Skills

Required

• React
• TypeScript
• Frontend architecture
• Build tooling
• Component systems
• Test strategy
• Release safety
• Performance optimization
• Product taste
• Coding agents
• Clear written communication

Preferred

• Design systems experience
• Data-dense or document-heavy products
• 0-to-1/early-stage work
• B2B SaaS
• LLM-backed interfaces