Frontend / UX Engineer

About Atira

Atira builds the commercial brain for industrials. Our agents 10x the sales engineers of today by offering the complete toolbox of tasks needed in complex environments. They handle everything from extracting and classifying requirements from incoming RFQs, orchestrating communication and information retrieval across multiple stakeholders and systems, while generating outcomes like documentation, production system inputs, or configuration recommendations. CRM. Atira. ERP.

We are one of the fastest growing teams in Munich and are looking for you to join us!

Why UX engineers are foundational to what Atira ships

As a UX / Front-End Engineer at Atira, you turn frontier AI from "demo-able" into "usable" inside the daily work of a sales engineer. Our agents handle some of the hardest workflows in industry: parsing 1000-page RFQs, reconciling specs against ERP tables, generating outputs that flow into SAP, Salesforce, and PLM systems. None of that matters unless a human can review, trust, and intervene in the agent's work at the right moment.

You will design and build the surfaces where agents and humans meet and interact: Chat with human-in-the-loop, document review UIs that render complex multi-modal inputs (tables, drawings, configurator rules), agent timelines and trace views, diff and approval flows, internal tooling for our FDEs and AI engineers, and the design system that ties it together.

A misread requirement can cost a manufacturer six figures, so the UI that surfaces that requirement to a human reviewer is crucial. The challenges are real and the margin for error is thin.

Where you trained matters less than what you've built and the taste you bring. Atira is at a stage where you must own problems end to end, because what you ship today is what our customers use tomorrow.

What you will do

• Own the surfaces where agents meet humans. Chat with HITL, agent step-by-step traces, approval flows, inline reviewing, editing of agent outputs and generative UI. The best agentic functionality is only as good as its usability & the underlying user trust

• Lead our frontend architecture and design. You will own our frontend architecture and be responsible for our team shipping UI / UX in a scalable, consistent framing

• Render complex, data-heavy documents. Industrials live in 1000-page RFQs, Excel pricing lists, BOMs, technical drawings, configurator outputs. You'll build the UIs that make these reviewable, diffable, and editable without dragging the browser to its knees

• Build full-stack features end to end. From the React component to the route to the API contract, you ship vertical slices. You partner with FDEs and backend engineers but you do not wait on them

• Set the bar for craft. Motion, interaction, latency, polish. You define the design system, component primitives, and patterns the rest of the team builds on. You care that a button feels right, not just that it works

• Reliability and tests. Playwright coverage on the flows that matter. You think about loading states, error states, empty states, and what happens when the agent stream stalls at token 4,732

What we are looking for

Taste, depth, and taking problems personally, go deep until the interaction feels right, and own the outcome including the parts that broke.

Your profile

• Very strong frontend fundamentals. Excellent TypeScript / React skills. You understand rendering behaviour, suspense, server components, concurrent features, and the gap between "code that works" and "code that won't haunt the next person." You can read someone else's production frontend, understand why it was built that way, and ship changes that make it more scalable

• Strong taste. You understand and are opinionated around the right way of designing UI / UX to reduce user friction & unlock feature adoption

• Experience with our stack or close alternatives: React, Next.js, the Tanstack ecosystem (Query, Table, Router and Start), Vite, Playwright. Tailwind, shadcn/ui, Radix etc.

• You've gone further than most with AI-assisted development. Whether it's Claude Code, Cursor, Codex, or your own setup, you've invested seriously in building the skills, context, and workflows to get maximum leverage from coding agents

• You are a strong technical decision maker who knows how to make tradeoffs on rendering strategy, state management, data fetching, and component architecture, and can explain the pros and cons of every solution

• You've demonstrated ownership and initiative: a company you started, a serious open-source contribution (UI library, design system, real commit history), a side project that grew to production scale, or a role where you owned a user-facing surface that others would have delegated. We want to see evidence that you build things without being told to

• Degree in Computer Science, HCI, Design Engineering, or a related technical field from a strong technical university, or an equivalent record of shipped work

• Full working proficiency in English. German is not required

What you'll get

• Real ownership: you'll be one of the early team members and shape both product and architecture, while working closely with customers

• Strong peers: work with people who have built and shipped AI systems in industrial environments at scale before, and the chance to learn directly from them

• Impactful work: your code is deployed all across Europe's and the US's industrial backbone, affecting how complex products and services are sold and configured worldwide

• Competitive salary & equity package and additional benefits including Wellpass, JobRad, and company dinners

• Most importantly: collaborate and thrive in a high-performing but caring culture. We will own the industrial sales function but will do so with modesty and integrity

What success looks like after a few months

• You've shipped the agent and human interaction surfaces that customers spend their day in, and FDEs cite them as a reason deals close faster

• You own a core surface (chat, document review, agent trace, internal tooling, the design system) and the team trusts your judgment on how it should evolve

• When something breaks on the frontend, you can trace issues across React, Next.js or Tanstack Start, the API contract, and the backing services, and fix them end to end

• The frontend is fast under real load: Your architectural decisions have held up and you can explain the tradeoffs you made and what you'd do differently