Performance, reliability and engineering quality

You might improve busy parts of the app, including React rendering, data loading, caching, observability and production debugging. You might also improve tests, CI/CD, monitoring, infrastructure, deployment workflows and developer experience.

Example projects could include making a slow bookings screen faster, improving error visibility, adding useful tests around important workflows, or making deployments safer and easier to reason about.

WHAT WE’RE LOOKING FOR

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:

• build maintainable React and TypeScript features in a production web app;
• reason clearly about state, derived data, loading states, error states and retries;
• debug UI behaviour by checking the data, the rendered app and the code path;
• make sensible choices about component boundaries, hooks and naming;
• test your work properly, or explain the right test when time is tight;
• take a vague product or technical problem and turn it into a clear plan;
• work independently without needing every step defined;
• communicate clearly when tradeoffs, risks or uncertainty appear;
• 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 stack already, but you should be comfortable with things like APIs, relational data, asynchronous or background work, performance tradeoffs and unfamiliar codebases.

Backend and platform experience are useful here, but they are not a substitute for strong frontend judgement. We need someone who can be trusted with React-heavy product work and can also understand enough of the surrounding system to make good decisions.

You do not need to be an expert in every area. We are looking for someone who can take ownership, improve quickly and be trusted with important product and engineering work.

USEFUL BUT NOT REQUIRED

Experience with any of the following would be useful, but none are hard requirements:

• C# or .NET;
• payments, ecommerce, POS, stock, inventory or booking systems;
• APIs, webhooks or third-party integrations;
• observability, performance tuning or production debugging;
• CI/CD, infrastructure or developer experience work;
• working in a small company or product-led team;
• mobile development experience, especially React Native.

HOW WE WORK

Our office is in Portslade, in the Brighton & Hove area. Different teams use the office differently: some people are in most days, some a couple of times a month, and some a couple of days a week.

For this role, we would like you to be in the office at least one day per week. Tuesday or Thursday usually works best because those are the days you are most likely to overlap with product, engineering and leadership.

You should be within reasonable commuting distance of Brighton and comfortable joining the team in person regularly.

We are a small company, so you will work closely with the founders, product and customer-facing people. You will get a lot of context, and you will be expected to use that context when making decisions.

We value clear communication, pragmatic engineering and people who want to understand the real problems our customers are trying to solve.

There is currently no formal out-of-hours on-call rota. Engineers do help investigate production issues during working hours, and very rare serious incidents are handled collaboratively by the team.

WHAT SUCCESS LOOKS LIKE

In your first few months, success would look like:

• understanding the product and codebase well enough to make safe, useful changes
• shipping one or two meaningful product improvements, likely with a strong frontend component
• improving an area of reliability, performance or developer experience
• building trust with product, support and the founders
• becoming someone who can own a problem from customer need through to production

BENEFITS

• £40,000 to £50,000 salary depending on experience
• 25 days holiday plus bank holidays
• pension
• work equipment
• hybrid working, usually one office day per week
• flexibility around normal life commitments

HIRING PROCESS

We want the process to be useful for both sides and as close to the real work as possible.

The process is usually:

1. Intro call, around 30 minutes
2. Practical working session, around 60 minutes
3. Final team conversation, if useful, ideally in person in Brighton.

We do not use brainteasers or algorithm puzzles. The practical working session is based on the kind of product and engineering work you would actually do here.

There is no unpaid take-home project. The practical working session is live and collaborative.

We use AI tools day to day, but the practical coding session is AI-free. You can use normal documentation, search and reference material. We ask for no AI assistance during the practical so we can see your own React, debugging and product judgement.

We assess how you understand the problem, communicate, make tradeoffs, test assumptions and respond to feedback. We are not testing memorised syntax or algorithm tricks.

We aim to run the whole process over two to three weeks where schedules allow, and we will keep candidates updated between stages.

INCLUSION AND ADJUSTMENTS

We welcome applications from people of all backgrounds. You do not need a computer science degree to apply.

If you need adjustments during the hiring process, let us know and we will do our best to accommodate them.

RIGHT TO WORK

You will need the right to work in the UK. We are not currently able to sponsor visas.