Frontend Engineer

What You’ll Shape

• Product interfaces for autonomous AI – Build real-time views into ingestion, schema inference, and retrieval runs. Users should understand agent intent, confidence, and receipts at a glance, with backend partners feeding you the signal you need.
• Living data visualizations – Show nested structures, relationships, and deltas across thousand-page corpora. Help people spot what changed during a four-hour run, with data engineers ready to explain every curve.
• The face of Southbridge – Own southbridge.ai, interactive explainers, and launch materials that make “agentic data layers” intuitive to engineers, execs, and partners. We’ll support you with stories straight from live deployments.
• Docs & trails – Create Lumentis-style documentation, walkthroughs, and examples that sit alongside working code. Ship artifacts developers can clone and extend, with the rest of us reviewing for clarity and correctness.
• Internal tooling – Craft evaluation dashboards, diff viewers, and debugging consoles the team relies on daily. Expect to iterate with the people using them most.

The Canvas & Tooling

• React + Next.js (RSC, streaming, edge rendering) with full TypeScript coverage.
• Tailwind, custom design tokens, and animation libraries where motion clarifies agent behavior.
• D3.js, Recharts, or bespoke canvas work for large-scale data visualizations.
• Real-time transport over WebSockets, Server-Sent Events, and experimental streams straight from Tadpole.
• Build pipelines shared with the backend team: Vercel deployments, Playwright smoke passes, visual regression where it counts.
• Everyday tools: Claude Code, Cline, Gemini CLI, Cursor, v0, our component workbench, and an internal design crit each week.

How We Work With You

• Designers are you—we expect taste, spacing discipline, and the ability to narrate decisions, and we make time for design reviews so you’re never alone in that call.
• You sit next to backend and infra peers (in person or timezone-close) to shorten the loop between capability and UI, with regular pairing time on the calendar.
• We prototype in public. Nothing ships without interactive receipts or at least a story of why this interface helps users trust the agent, and we’ll help gather those receipts.
• “Wide is better than deep” applies here too: we iterate on design systems as models change, not twice a year, and we compare notes as we go.

You Might Thrive Here If

• You’ve shipped complex TypeScript frontends where correctness and performance both mattered, ideally with a tight feedback loop to the people using them.
• You can read a JSON schema or API trace and immediately imagine how to visualize it, then talk through trade-offs with whoever produced the data.
• You’re comfortable owning the stack from lint rules to deployment, and you set guardrails before glitter, inviting the rest of us to test along the way.
• You’ve built interfaces for AI products—streaming chats, diff viewers, prompt builders, evaluation consoles—and you have thoughts on what made them humane.
• Words matter to you. Microcopy, onboarding flows, and empty states are product work, not afterthoughts, and you enjoy pairing with product and research on them.

Signals We Love

• Open-source components, design systems, or tools others already rely on—and notes about what you’d improve in version two.
• Screenshots or recordings of dashboards you’ve crafted that balance detail with calm, plus a sentence about the constraints you managed.
• Stories where you persuaded teams to delete complexity and explain things visually instead—and what happened after launch.
• Curiosity about the models themselves—you run evals, test new releases, and adjust UI affordances when behavior shifts, often in conversation with the rest of the team.

Why This Work Matters

Hiring Process

1. Portfolio share – Links, repos, production screenshots, or a short Loom/Tella walk-through. Show us what "taste with teeth" means to you and tell us the context behind it.
2. ⭐️ If you would like to skip the Take-Home Challenge Phase (Below) than please walk us through one of your Design Projects in the video you submit, share your screen and dig into the planning, codebase and decisions that you went through to help us understand how you approach engineering.
3. Take-home challenge – We'll hand you a Tadpole trace or interface problem to work through. Realistic constraints, time to think.
4. Meet one of the team – 30-minute conversation to see if the work resonates and answer your initial questions.
5. Interface deep dive with our CEO Hrishi – Walk through your solution end to end, explore trade-offs together. We'll also review a prior project of yours to understand your approach.
6. Your questions for us – Dedicated time for you to interview us on anything that matters to your decision.
7. Pairing session – Co-create or refine a live component in our codebase with the team. Expect Tailwind, streaming data, and honest feedback both ways—we'll share the brief beforehand.
8. Offer & runway – We tune scope, compensation, and relocation support so you can operate at full pace, and we map out the support you'll have on day one.