Software Engineer, Product & Platform

Location
:
Portslade, Brighton & Hove

Office
:
Hybrid, with at least one Brighton office day per week

Salary
: £40,000 to £50,000 depending on experience

Level
:
Mid-level

Workshop by Bikebook builds software for repair and service businesses.

We started with bike repair shops, helping them manage bookings, jobs, customers and day‑to‑day workshop operations. That is still a big part of what we do, but the product is now moving into a broader space: repairs, stock, retail, POS, ecommerce, customer management and workflows for other service‑led businesses.

We are growing the engineering team and looking for a software engineer who wants to work closely with the product, customers and technical decisions.

This is a mid‑level role in a small product and engineering team. You would be joining as our third software engineer, so you will get more ownership than you might in a larger company, but you will not be expected to be expert in every area on day one. We are looking for someone who can own meaningful work, learn quickly, communicate clearly and make pragmatic engineering decisions.

Our day‑to‑day stack is mainly C#/.NET on the backend and Type Script, React and Next.js on the frontend, with some mobile work in React Native. The product also involves relational data, APIs, background jobs, third‑party integrations, observability, CI/CD and production systems. You do not need to know every part of this stack already, but you should be comfortable learning across it.

You will work across the product and platform. Some work will be close to the customer experience, and some will be deeper engineering work behind the scenes.

You will not work on all of these areas at once, but broadly the work falls into four areas.

You might build new workflows for bookings, repairs, stock, payments, ecommerce, POS, customer management and reporting, mostly in the web app and sometimes in our mobile app.

Example projects could include improving the stock adjustment workflow, building better repair job views, adding reporting for workshop performance, or improving how customers book and manage services.

You might work on APIs, webhooks, background jobs, realtime updates, event‑driven parts of the system and third‑party integrations.

Example projects could include integrating with an ecommerce or payments provider, improving webhook reliability, or building internal tools to make integrations easier to support.

You might improve busy parts of the app, including React rendering, data loading, caching, observability and production debugging.

Example projects could include making a slow bookings screen faster, improving error visibility, or making background jobs easier to monitor and retry safely.

You might improve tests, CI/CD, monitoring, infrastructure, deployment workflows and developer experience.

Example projects could include improving test coverage around important workflows, simplifying local development, or making deployments safer and easier to reason about.

This is a good fit for someone who enjoys product engineering but also wants technical depth. You will own meaningful product work across the frontend, backend and the systems behind the product.

This role is likely to suit someone with roughly 4+ years of professional software engineering experience, especially if you have shipped and maintained production web applications.

The exact number of years matters less than whether you can own work, learn quickly and make good decisions.

You should be able to:

• take a vague product or technical problem and turn it into a clear plan
• work independently without needing every step defined
• communicate clearly when trade‑offs, risks or uncertainty appear
• write clean, maintainable code
• test your work properly
• debug issues calmly and systematically
• understand a product area quickly
• make pragmatic decisions without creating unnecessary complexity
• care about the product and customer experience, not just the code

You should also have experience working with production web applications. You do not need to know our exact…