We’re looking for a Staff / Principal Front-end Engineer to own the technical direction of our front-end: how we architect, build, ship, and evolve user-facing experiences across our product.

You’ll be the person who:

• Sets the bar for front-end architecture, performance, accessibility, and developer experience.
• Lives and breathes the front-end ecosystem: modern CSS, JavaScript and TypeScript features, patterns around SPA/SSR/SSG, and the wave of new tools (including Rust-powered compilers, bundlers, and linters).
• Helps us make sensible, pragmatic decisions about which trends to adopt and which to ignore – and turns those decisions into real code and practices.

This is a hands-on technical leadership role, not a people manager role. You’ll be writing code regularly, while also driving cross-team initiatives and mentoring other engineers.

• Generous cash + equity compensation along with various fringe benefits (e.g., healthcare, lunch, wellbeing, etc.).
• Our operations are profitable, in addition to fast growth.
• You’ll be an integral part of the small yet mighty team of around 60 people, challenging the status quo to positively impact the lives of many.
• You’ll work in small teams of experts with real ownership and short decision paths.
• 27 nationalities in total, with 6 different ones in the management team.
• We foster a community-like atmosphere: we often enjoy each other’s company after work, e.g., munching on BBQ made by Ruben, our CEO by day and master chef by night.

• Location: Helsinki (Maria 01) or remote within a compatible time zone (roughly European working hours).
• Work mode: Hybrid / remote-friendly. You’re welcome in the office, but we’re open to remote for this role.
• Level of expertise: Staff / Principal (very senior individual contributor).
• Employment type: Full-time and permanent.

Technical leadership & architecture

• Own and evolve the front-end architecture: routing, state and data-fetching patterns, composition, error handling, performance strategies, and testing approach.
• Define and maintain front-end standards for performance, accessibility, security, and code quality – and make them easy to follow through tooling, documentation, and examples.
• Lead the evolution of our design system and component library, ensuring consistency, accessibility, and great UX while keeping things practical for engineers.
• Evaluate and introduce modern tooling and approaches where they genuinely improve developer experience or performance – not just because they are shiny.
• Collaborate closely with product, design, and backend teams to turn ambitious ideas into clear, scalable implementations.

Hands-on engineering

• Design and implement some of the most challenging front-end pieces: complex interaction flows, highly dynamic UIs, and shared infrastructure like theming, layout primitives, routing, and reusable form patterns.
• Drive performance work: core web vitals, loading strategies, bundle size, interaction latency – using metrics and profiling tools, not just gut feeling.
• Keep accessibility as a first-class concern: semantics, keyboard navigation, ARIA, contrast, motion preferences, and inclusive patterns baked into components and layouts.
• Strengthen our testing strategy: from unit and component tests to integration tests where they add real confidence; help define what “good coverage” means for us in practice.

Cross-team impact

• Act as a mentor and coach for other front-end engineers: thoughtful code reviews, design discussions, pairing sessions, and architecture reviews.
• Lead cross-team initiatives that simplify our front-end landscape, reduce tech debt, and improve developer experience (tooling, documentation, internal libraries, CLI helpers, etc.).
• Be our front-end ecosystem radar: track key changes in CSS, JavaScript/TypeScript, browser APIs, frameworks, and tools – and translate them into concrete proposals and migration plans, rather than random experiments.
• Communicate trade-offs clearly when making architectural decisions, and help non-front-end stakeholders understand the impact on delivery, UX, and long-term maintainability.

You don’t need to tick every box, but you’ll recognize yourself in most of these:

• Extensive experience – typically 8–10+ years working as a front-end or full-stack developer with a strong front-end focus.
• Deep TypeScript expertise: you’re comfortable with strict mode, generics, utility types, and designing safe, ergonomic APIs for components and hooks.
• Modern front-end architecture: solid experience with both SPA and SSR / SSG patterns, including client/server boundaries, caching, data-loading strategies, and code-splitting.
• CSS mastery:
  • You’re fluent in modern layout systems and responsive design.
  • You use newer features like container queries, style queries, logical properties, CSS variables.
• Design systems & components: you’ve helped build or evolve a design system / component library before, and you understand how to balance headless primitives, accessibility, and flexibility for consumers.
• Tooling mindset: strong experience with modern build tooling and dev workflows, and curiosity about newer, faster tools (including Rust-based compilers/bundlers/linters) as a way to speed up feedback loops.
• Testing and quality: you’re comfortable putting a testing strategy in place for complex front-ends (unit, component, and selected integration tests) and setting clear expectations in the team.
• Backend collaboration: you can work productively with Node-based APIs and backend teams, and you think in terms of contracts, resilience, and failure modes, not just “happy path” UI.

Nice-to-haves

None of these are required, but they’d be great signals:

• Previous experience in a Staff / Principal (or equivalent) role, with a track record of driving technical initiatives.
• Experience building accessible user interfaces and applying practical accessibility best practices in everyday work.
• Experience in data-heavy or infra/AI-focused products (cloud consoles, analytics dashboards, devtools, etc.).
• Experience improving developer experience: codemods, custom lint rules, documentation tooling, or internal libraries.

• You take pride in your work and care about details – without losing sight of delivery and impact.
• You can get your expert opinion across clearly while playing well with others and staying open to being challenged.
• Your critical thinking and readiness to make an impact are on by default.
• You learn new things not because you have to but because you genuinely love it – and you naturally share that curiosity with the people around you.

• You’ve developed a deep understanding of our front-end landscape and can contribute productively across multiple areas of the codebase.
• You’ve led at least one significant architectural or performance initiative that clearly improved developer or user experience.
• You’ve become one of the go-to people for complex front-end questions in the company – from debugging tricky issues to advising on feature architecture.
• You’ve helped raise the bar for the whole front-end team, through mentoring, reviews, and by putting better patterns and tools in place.

We know this is a very senior role, and we respect your time. Our process is designed to be practical and conversational rather than a puzzle contest.

• Introduction chat with the TA Partner (30–45 mins): Learn more about Verda and share your story and goals.
• Interview with the CTO (30 mins): Align on expectations for Staff / Principal-level impact and how this role fits into our roadmap.
• Technical deep-dive (60–90 mins):
  A discussion-based session where you walk us through systems you’ve built before (architecture, trade-offs, failures, lessons), plus some targeted problem-solving around front-end architecture and UX.
• Practical session (optional, format tailored):
  Depending on your background, this may be a short, focused exercise – for example, reviewing or extending an existing code snippet, or walking through a small technical design.
• Final interview (60 mins): Meet more of the team you’d collaborate with and discuss how we’ll work together in practice.

We’ll keep you informed at every step, and we’re happy to adapt details of the process for very senior candidates where it makes sense.

Apply sooner rather than later. This job ad will be removed once we’ve found the right person.

Please submit your application through our Careers page. We don’t accept applications sent by mail.

For more information, you can reach out to our Talent Acquisition Partner, Marina, at marina (at) datacrunch.io