Skip to main content

Frontend Developer

Own the booking flow that every customer passes through, from the first price to the confirmation screen.

Department
Engineering
Type
Full-time
Workplace
Hybrid
Location
Stockholm
Level
Mid–Senior
Apply for this role

Our customer site is the product for most people who use TheLimoLane. They see a price, they see a car, they pay, and a chauffeur arrives. Everything between those moments is frontend work, and it is measured: a slow quote screen is a lost booking.

You would own that surface. Next.js App Router, TypeScript, Tailwind and TanStack Query, talking to a Go backend over ConnectRPC with a generated, type-safe client — no hand-written fetch calls and no untyped JSON anywhere in the path.

What you would do

  • Build and maintain the customer booking flow, account pages and the marketing surfaces that feed them
  • Keep Core Web Vitals honest on real phones, not just on a laptop — LCP and INP are treated as product requirements here
  • Work against generated ConnectRPC clients and push contract changes back into the proto rather than working around them
  • Write the tests that matter: component behaviour and the property-based checks around pricing and date logic
  • Share the design system across three Next.js apps without letting one app’s change rebuild the other two

What we are looking for

  • Strong React and TypeScript — you are comfortable in a strict codebase with no implicit any
  • Real experience with a modern React framework in production (Next.js App Router preferred)
  • You can reason about rendering cost, bundle size and network waterfalls, and you measure before you optimise
  • Comfortable with CSS at a systems level: Tailwind, design tokens, dark-first theming
  • Professional English, written and spoken

Nice to have

  • Protobuf / gRPC / ConnectRPC experience
  • Accessibility work beyond the automated checks
  • Technical SEO: structured data, indexing behaviour, hreflang

How we hire

  1. 1. Your application. CV plus a short note. We read it; it is not filtered by a keyword matcher.
  2. 2. A conversation. Forty minutes about what you have built and what you want to build.
  3. 3. Real work. A problem from this codebase, discussed together. Not a whiteboard algorithm, and not an unpaid weekend project.
  4. 4. Offer. With the reasoning, in writing.

Apply for this role

Attach your CV and tell us briefly why this one. Fields marked optional are optional.

We use what you send here only to consider your application, and keep it no longer than we need to. See our privacy notice.