Role Responsibilities

• Own the front-end architecture end to end for the governance product: assess what's been built so far, decide what to keep and what to rethink, then build it.
• Design and build the interfaces where humans review and act on what the governance agents surface: policy violations, compliance risks, and governance findings, often derived from ambiguous, non-deterministic signals.
• Make complex organizational structure and knowledge-graph relationships legible and navigable, so a user can see how a finding connects across the org and why it matters.
• Bring real product and UX sense to inherently complex, high-stakes governance and compliance workflows, not just technical execution.
• Build and maintain the front-end (we lean TypeScript, but we care far more about your track record than an exact stack match).
• Contribute to the backend as needed: understand data structures, APIs, and enough of the graph and agent layer to build and reason about the surfaces on top of it. The backend leans toward the AI, graph, and data stack, and we're technology agnostic.
• Take true end-to-end ownership: propose the approach, defend it, then build it, without waiting for someone else to set the direction.
• Build inside a fully AI-driven workflow, using tools like Claude Code as a core part of how you ship, not an occasional assist.
• Partner closely with the AI and backend engineers building the governance engines to turn agent-driven insight into surfaces people rely on.

Key Requirements

• Strong front-end fundamentals: you know the basics cold and can make real architectural calls, not just implement someone else's design.
• Real product and UX sense: good taste, ideally built for real end users on a genuine product, with the judgment to make complex, information-dense workflows feel clear and trustworthy.
• A track record of turning complex or ambiguous data into clear, usable interfaces: dashboards, review and triage flows, visualizations, or similar. A real plus if you've made non-deterministic or probabilistic output legible to people.
• Comfortable across the stack: solid grasp of backend fundamentals (databases, data structures, APIs, general system design), even with front-end as your focus.
• Technology agnostic: you've worked across multiple stacks before and can pick up whatever this team needs. We care about your track record more than your specific stack.
• Genuine ownership: a history of starting things from zero and owning them end to end, not just delivering on initiatives someone else already scoped. You propose the design, defend it, then build it.
• Strong software engineering fundamentals and the independence to thrive in a fast-moving, remote-first, senior-heavy team with very little process.
• Heavy, real fluency with AI coding tools (e.g. Claude Code): you build with AI as a core part of your workflow, not an occasional assist.

Preferred Experience

• Experience building for governance, risk, compliance, security, or other regulated or data-heavy domains, or any product where clarity and trust in the interface genuinely matter.
• Experience visualizing graphs, networks, or relationships (knowledge graphs, org structures, dependency maps, or similar).
• Experience at a startup where you had to build something from scratch with little existing structure to lean on.
• Backend build experience (for example Python in the AI and graph stack, or Node.js), even if it's not your primary focus.
• Comfortable working fully remote across time zones, ideally with solid overlap with EU hours, on a small, high-caliber team with little hand holding.