Senior Frontend Engineer

Own the web console that helps engineers set up Proofline, understand review results, and investigate the evidence behind a finding.

Remote first · Flexible hours · Berlin time zone overlap preferred

You must be able to travel to Berlin for work. We do not offer visa sponsorship.

The role

Proofline reviews code changes and gives engineers findings they can inspect and act on. The web console is where people connect their repositories, manage setup, inspect connection health, and read review results and investigation evidence.

You will own that experience, working directly with our founder, Mohsen Azimi. Take a confusing interaction or an unmet user need through design, implementation, verification, and release. This role combines frontend engineering with product judgment: deciding what a screen needs to communicate, what someone can do next, and which details belong elsewhere.

Our console uses React and TypeScript, TanStack Query and Router, and Tailwind CSS, with a Rust backend. You will work across API contracts and frontend state to keep the interface consistent with the system behind it.

Read about how we work and what we offer.

What you will own

  • Build and improve onboarding, connection health, review results, and read-only investigation pages.
  • Make complex evidence readable through clear navigation, information hierarchy, and useful data visualizations.
  • Own interaction quality, accessibility, responsive layouts, and frontend performance, including loading, empty, incomplete, and failure states.
  • Maintain shared components and frontend architecture that make the next change easier to ship and verify.
  • Use customer feedback and your own experience with Proofline to identify friction, choose improvements, and carry them through release.

What you bring

  • Substantial experience shipping and maintaining production React and TypeScript applications, with ownership of complete user workflows.
  • Strong JavaScript, HTML, and CSS fundamentals. You can debug asynchronous state, API interactions, and browser performance problems.
  • A strong eye for typography, spacing, interaction details, and accessibility. You can explain how your design decisions help someone complete a task.
  • Experience choosing and writing tests that catch meaningful failures, including browser tests for important user journeys.
  • Product judgment and clear communication. You can turn an ambiguous problem into a focused change and explain the tradeoffs.
  • Effective use of AI coding tools, with responsibility for the architecture, correctness, and quality of the code you ship.

Experience with developer tools, cloud infrastructure products, or interfaces that present complex data is useful. Prior Rust experience is not required.

Logistics & Compensation

  • Location: Remote globally, with overlap in the Berlin time zone preferred and full access to our Berlin office.
  • Travel: You must be able to travel to Berlin regularly for working sessions, in addition to our quarterly team offsites. Because we do not offer visa sponsorship, you must hold work authorization in your country of residence and have visa-free (or self-sponsored) travel access to the Schengen Area.
  • Compensation: Competitive base salary localized to your location, paired with meaningful founding-team equity. Specific salary and equity ranges for your location are shared prior to the first interview.

How to apply

Use Proofline before you apply. We want to understand your frontend and product judgment through specific observations from using the web dashboard.

  1. Run a review. Sign up at proofline.sh and run a Proofline review on any repository you choose. Open the review run in the web console and copy its proofline.sh URL.
  2. Critique the dashboard. Describe what you tried to do, what worked, and where the experience became confusing or difficult. Choose the improvements you would prioritize, explain why, and describe how you would approach them. Screenshots or sketches are welcome.
  3. Email careers@proofline.sh. Include the role title, a brief introduction and relevant work or a résumé, the proofline.sh link to the review run you completed, and your dashboard critique.

Your application must include both the proofline.sh review run link and the dashboard critique. A GitHub pull request link alone does not meet the review-link requirement. Candid criticism is welcome.