Remote Senior Software Engineer

About One View Commerce

Retailers with thousands of shops have had two options, and neither is good. Web-native platforms move fast but were never built for a shop floor. Legacy store systems were built for the shop floor but take a year to change anything. One View Commerce is the third option: a headless commerce platform for physical retail that lets the world's largest retailers innovate just as quickly as the smaller ones.

We ship store experiences that deploy fast out of the box, and we give retailers the freedom to build their own on top of a headless transaction engine engineered for the physical store rather than the browser.

Our customers are global retailers who build on One View because it lets them keep moving: new journeys, new channels, and new store formats ship continuously rather than waiting on the next multi-year programme.

Founded in 2010 to close the gap between fast-moving e-commerce and slow-moving in-store systems, One View's founding principle is a single view of customers, orders, and inventory throughout the shopping journey. That remains our mission as we enable retailers to deliver exceptional store experiences that build loyalty.

We are a remote-first team with Viewers working across the globe, and we operate as a trusted provider of digital commerce systems for leading retailers.

Position Summary

One View is looking for a Senior Software Engineer to take on the harder half of what a delivery team builds. The platform serves over a hundred thousand users across global retail estates, on terminals that have to keep taking payments when the connection drops and reconcile perfectly when it comes back. That is where the difficulty lives, and it is the work this role gets.

Reporting to the VP of Engineering and working in a Scrum team alongside a Lead Software Engineer, you will design and build complex features and integrations end to end, from very little direction.

Senior here means three things concretely. You take the problem nobody has scoped yet and come back with something defensible. You lead reviews of other people's work and leave the code better than the review found it. And you contribute to what the team chooses: the methods, the libraries, the tooling, argued on evidence rather than preference.

You will mentor a Software Engineer, usually one at a time, and the measure is whether they got better rather than whether their tickets got closed. This is the rung below Lead Software Engineer and a deliberate step towards it, so the parts of that job you want more of are available to you.

The Lead Software Engineer owns the team's standard, its improvement agenda, and its technical direction, and you are the person they will lean on most to shape all three. Bring them the problems worth solving, argue for what should change, and take the work on. The more of it you can carry, the more of it becomes yours. We use AI throughout our day-to-day work and expect you to find uses for it we have not thought of.

We also expect you to be able to do this job well if it were switched off tomorrow, because the creativity, judgement, and relationships that make the work good are yours rather than the tool's.

Responsibilities

• Design and build complex features and integration services end to end, from little direction, for a platform running continuously across thousands of shops in multiple countries.
• Take the hardest item on the team's backlog and be trusted with it.
• Own the technical design for significant pieces of work. Write it down, take it to the team and the Lead Software Engineer, and change it on the strength of the argument rather than defending it. Design in performance, security, and resilience rather than retrofitting them.
• Lead reviews of colleagues' work, and make review the place code gets better.
• Contribute to the team's choices about methods, libraries, and tooling, argue for them on evidence, and bring the Lead Software Engineer the problems worth solving.
• Work with the Product Owner to shape what gets built: challenge scope that is not worth its cost, surface the technical constraint before it becomes a surprise, and offer the cheaper option when there is one.
• Write the tests that prove your work now and catch the regression later.
• Run the technical investigations nobody else has time for: evaluate the options, prototype where that is what settles it, and come back with a recommendation the team can act on.
• Break a large piece of work into something the team can deliver incrementally, so that…