Location
Germany
Job Type
full-time
Work Format
๐ŸŒ Remote Worldwide
Salary
Not specified
Posted
November 16, 2026

Job Description

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.

๐ŸŽฏ Who is this job for?

Suitable for a Senior Frontend Engineer with substantial experience shipping and maintaining production React and TypeScript applications and owning complete user workflows.

They should have strong JavaScript, HTML, CSS, accessibility, responsive design, frontend architecture, performance debugging, API/state management, and meaningful browser testing skills, with React, TanStack Query, TanStack Router, and Tailwind CSS experience preferred.

The person should be familiar with turning ambiguous product needs into focused changes, building onboarding and data-heavy investigation interfaces, handling all loading and error states, improving information hierarchy and visualizations, and carrying work from design through verification and release.

๐Ÿ’ฌ Potential Interview Questions

How would you structure a React and TypeScript console that supports onboarding, connection health, review results, and investigation evidence without becoming difficult to maintain?

I would organize the application around clear feature boundaries, shared UI primitives, typed API models, and route-level data loading. Each workflow would own its domain logic while common components handle consistent interaction, accessibility, and visual patterns.

How would you use TanStack Query to manage asynchronous review data and connection status?

I would define query keys around stable resources such as repositories, connections, review runs, and findings, then configure appropriate stale times, retries, and invalidation rules. I would explicitly model loading, empty, partial, error, and refetching states rather than treating all non-success responses the same.

How would you design routing with TanStack Router for a review-results and evidence-investigation workflow?

I would use nested routes for shared review context, with route parameters identifying repositories, runs, findings, and evidence items. Route-level loaders or queries could ensure required data is available while preserving navigable URLs, browser history, and deep links to specific evidence.

How would you keep frontend and Rust backend API contracts consistent?

I would establish a typed contract at the API boundary, ideally generated or validated from an OpenAPI or equivalent schema, and centralize request and response transformations. I would also add contract tests and ensure the UI handles versioning, missing fields, and meaningful backend errors gracefully.

How would you make complex code-review evidence understandable in the interface?

I would establish a clear hierarchy from finding summary to affected code, supporting evidence, confidence or status, and recommended next actions. Progressive disclosure, anchored navigation, filtering, and visualizations should reduce cognitive load without hiding information needed to verify the finding.

What loading, empty, incomplete, and failure states would you consider for the review console?

I would design each state around the user’s next decision: show meaningful skeletons during loading, explain what an empty result means, identify unavailable or still-processing evidence, and provide actionable recovery for failures. I would avoid generic spinners and preserve already-loaded context whenever a secondary request fails.

How would you test an important user journey such as connecting a repository and inspecting a finding?

I would combine unit tests for state transformations and components with browser tests covering the complete journey, including authentication or setup, asynchronous updates, navigation, and error recovery. Tests should assert user-visible outcomes and accessible interactions rather than implementation details.

How would you ensure the console is accessible and responsive?

I would use semantic HTML, keyboard-complete interactions, visible focus states, correct labels and landmarks, sufficient contrast, and appropriate announcements for asynchronous changes. I would test representative layouts at narrow and wide breakpoints, ensuring evidence views remain readable without relying solely on horizontal scrolling.

How would you diagnose and improve frontend performance in a data-heavy React application?

I would use browser performance tools and React profiling to identify excessive renders, large bundles, slow network requests, and expensive visualizations. Improvements might include route- and component-level code splitting, virtualization, stable query and component boundaries, memoization where measured, and efficient pagination or incremental loading.

How would you use AI coding tools responsibly while owning the quality of the resulting frontend code?

I would use AI to accelerate exploration, boilerplate, test cases, and debugging hypotheses, but I would verify every change against the product requirements, API contracts, accessibility expectations, and existing architecture. I would review generated code carefully, run targeted and end-to-end tests, and reject suggestions that add unnecessary complexity or obscure ownership.

๐Ÿ“‹ Job Summary

Proofline is building a developer-focused web console that helps engineers connect repositories, understand code-review findings, and investigate supporting evidence. As a Senior Frontend Engineer, you’ll own complete user workflows across onboarding, connection health, review results, and data-rich investigation pages, while shaping product decisions and improving accessibility, responsiveness, performance, and testing. You’ll work with React, TypeScript, TanStack Query, TanStack Router, Tailwind CSS, and a Rust backend in a remote-first role with flexible hours and preferred Berlin-time-zone overlap; regular Berlin travel is required, and visa sponsorship is unavailable. The package includes a competitive location-based salary and meaningful founding-team equity, plus the chance to work directly with the founder and have substantial influence on a product used to make complex engineering evidence clear and actionable.

Required Skills

React TypeScript TanStack Query Tailwind CSS Rust JavaScript HTML CSS

Never miss a JavaScript opportunity

Subscribe to get similar jobs and weekly insights delivered to your inbox

Hiring JavaScript developers?

Post your job to 10,400+ registered developers. Starting free.

See Pricing

Related jobs

Is this your listing? Claim or request removal