Mobile Engineer
Merchant Mobile·Mid-level / Senior
Explore and build a mobile companion that helps restaurant teams keep track of orders away from a desktop.
The job
You will help define the smallest useful merchant experience, then build and evaluate it with restaurant users. Reliability matters more than novelty: staff need clear order status, sensible notifications and an honest indication when a connection is unavailable. You will contribute to both product discovery and the practical engineering needed to release maintainable mobile software.
What you would be doing
- Develop cross-platform mobile interfaces for merchant order awareness and operational tasks.
- Design safe offline and reconnect behaviour with explicit limits on what can be changed offline.
- Integrate push notifications, authentication and secure device storage.
- Collaborate with backend engineers on stable APIs and synchronisation behaviour.
- Test on representative Android and iOS devices, including constrained hardware.
- Improve crash reporting, app performance and release-management practices.
- Work with restaurant users to evaluate prototypes and prioritise the next useful capability.
What we are looking for
- Experience shipping or substantially contributing to a mobile application.
- Strong React Native skills or transferable native iOS or Android experience.
- Understanding of mobile networking, lifecycle behaviour and secure local storage.
- Ability to build accessible touch interfaces and diagnose device-specific problems.
- Experience working with APIs and testing behaviour under intermittent connectivity.
Useful, but not essential
- Experience with Expo, native modules or push-notification delivery.
- Familiarity with merchant devices, kiosk workflows or hospitality operations.
- Experience taking an early product concept through a limited pilot.
Tools you might use
- React Native
- TypeScript
- Expo
- Android
- IOS
- Push notifications
Your first 90 days
- Days 1–30Understand merchant workflows and agree a small mobile use case with product and customer teams.
- Days 31–60Build a testable prototype with authentication, a core workflow and explicit connection states.
- Days 61–90Evaluate the prototype with a small internal or partner pilot and propose a release-ready next step.
The practical bits
- 2 days per week in the Nottingham office and 3 days working remotely within the UK.
- 37.5 hours per week, Monday–Friday. Core collaboration hours are agreed with the team.
- Occasional planned team or customer visits; approved expenses are reimbursed.
What we offer
- 30 days of annual leave plus public holidays
- A company pension contribution
- A £1,000 annual learning budget for courses, conferences or professional development
- A company laptop and role-appropriate equipment; engineering roles include a development setup
- Flexible start and finish times, agreed with your team around customer and collaboration needs
- Wellbeing support and regular development conversations with your manager
- Reimbursement of approved business travel and customer-visit expenses
Apply
Four fields. That is the whole application.
No account, no portal, and no covering letter unless you want to write one. A person reads every application and replies either way.
- Introduction, 25 minutesDiscuss your interests, the role, location, working arrangements and compensation expectations.
- Experience and problem-solving, 45 minutesWalk through relevant work and explain the decisions, trade-offs and lessons behind it.
- Practical conversation, 60 minutesDiscuss how a merchant mobile app should display orders and notifications when the connection drops and later returns.
- Meet the team, 30 minutesMeet someone from another team, see how we work together and ask anything still open.