Product Frontend Engineer

quinn is an app-based, managed payroll and employment-administration service. We run it for private households employing a cleaner, nanny, or caretaker, and for businesses that manage employment relationships  customer stays the legal employer: quinn registers the employment, runs payroll, and handles social insurance, taxes, and filings on their behalf, automated end to end.

Where everyone else sells software, quinn sells the outcome. We don't sell payroll software. We run payroll.

The purpose behind it is simple:
Fair employment. For all. Correct and fair employment, made simple and accessible for any employer and any employee, in any market quinn enters.

Think about what Revolut did to banking. All of the complexity (the regulation, the clearing, the compliance) handled invisibly in the background, and one simple experience at the front. Nobody using Revolut thinks about what happens behind the screen when they open a new account, swap currencies or send money abroad. It just works, in a couple of taps. Nobody should have to think about it in order to employ someone either.

That is what quinn is building, and it is further along than most people assume: a profitable core business, running today in Switzerland, Germany and the UK, expanding into new markets both by launching and by acquiring. By 2030 quinn intends to be the destination brand for fair employment across six countries and more, on one platform, with one experience.

One platform means one frontend. One experience means it looks and behaves like quinn whether you are in Zurich or in London, a household or a company. In this strategy that is not a nice-to-have. It is the strategy.

Which is why the surface matters more than anything else. Everything quinn does is designed to disappear. The interface is the only part the customer ever sees, and it is the whole proof that the complexity behind it is really handled.

Today
, quinn runs on several separate web apps: one per product and market, each with its own frontend, grown over the years as the company grew. Our backend engineers built them alongside everything else, plus an internal admin tool that grew the same way. They all work: thousands of employers run payroll through them every month. But nobody was ever tasked with owning the frontend development, so each one got built the way frontend is built by Backend Developers, seen as a hassle rather than the main aspect users interactive with.

What comes next is one frontend that replaces all of them, built from scratch: one quinn app for employers, employees and our own support team, in the browser first, then in the App Store and Google Play from the same work. Alongside it, the frontend of Maestro, the internal tool that replaces the old admin for batch processes. The phone app is the surface that matters most, so everything is built for it from the first screen rather than adapted to it afterwards.

That is the opening.

Everything on the screen:

• The frontend of the quinn app and the web app. App first. One app for everyone who uses quinn: the employer, the employee, and our own support team working inside the customer's account.

• The frontend of Maestro, our internal batch tool. Desktop and dense: queues, runs, tables, filters, multi-select, keyboard shortcuts. A different discipline from the app, built on the same components.

• The component library across quinn Home and quinn Business: one frontend, one experience, every market and every device.

• Whether the app feels native: response, scrolling, gestures, transitions, biometric login, push. Nothing that gives away it isn't native.

• The quality of what you ship. Nothing leaves your hands half-finished.

We have a design team, and they own how quinn looks and behaves: the flows, the visual design, the tokens, the component specs. You don't design. You own everything from there: how it is built, and everything a design file cannot reasonably specify, such as gestures, keyboard, safe areas, what happens between the drawn breakpoints, the loading, offline, pending and failed states, what a three-line German label does to a layout that was designed for English.

You are in the room before design starts, saying what already exists in the library and what a new pattern costs. Not at the end, receiving a handover. When you and design disagree, they decide how it…