The Role
We are looking for a React developer to build the frontends that sit on top of our Laravel backends. Every system we deliver — client portals, dashboards, reporting interfaces, and our own product ecosystem — has a React SPA as its primary interface. The frontend is not an afterthought here. It is the part of the system that users interact with every day, and the quality of that experience determines whether the system gets adopted or abandoned.
Our frontend stack is React 18 with Tailwind CSS, shadcn/ui components, and Lucide icons. We use react-router-dom v6 for routing, and the SPAs communicate with Laravel APIs via RESTful endpoints with Sanctum authentication. Real-time features are powered by Pusher, and we use Vite for builds. The design system is shared across multiple products — the Dashboard, the Beacon Lens browser extension, and the Beacon Workbench desktop application — so component architecture and token consistency matter.
The role covers both client projects and internal product development. Client work means building interfaces for specific business domains — a legal firm’s matter management dashboard looks different from a recruitment agency’s pipeline view, even though they share architectural patterns. Product work means contributing to the Beacon suite, where you are building a commercial product used by paying customers, with all the polish and reliability that implies.
What the Day-to-Day Looks Like
You might spend a morning building a data visualisation component for a client’s reporting dashboard, an afternoon refactoring a shared component in the design system so it works correctly across light and dark themes, and the next day implementing real-time notification handling for the Beacon Pulse mobile companion. The work moves between projects regularly, which keeps things interesting but also requires the discipline to context-switch cleanly and leave code that someone else can pick up.
You will work closely with the backend team — and in a team this size, “closely” often means the same person. Understanding how the API is structured, what data is available, and how to handle loading states, error boundaries, and optimistic updates is part of the job. You do not need to be a Laravel expert, but you need to be comfortable reading API documentation and occasionally digging into the backend to understand why a response looks the way it does.
Client interaction is part of the role. When a client describes what they want a screen to do, you are often the person working out how to present that information effectively. That means having opinions about UI patterns, being able to explain trade-offs between different approaches, and pushing back when a request would create a confusing user experience.
What We Are Looking For
Required:
- Strong experience with React (hooks, context, functional components) — not class components from 2018, but current patterns
- Proficiency with Tailwind CSS or utility-first CSS approaches, and the ability to build responsive, accessible interfaces without relying on heavy UI libraries
- Experience consuming RESTful APIs from a React SPA, including authentication flows, error handling, and state management
- Understanding of component architecture — building reusable, composable components that work across different contexts without becoming fragile abstractions
- Ability to work independently, manage your own priorities, and communicate clearly about progress and blockers
Valuable but not required:
- Experience with shadcn/ui or Radix UI primitives
- Familiarity with React Native or NativeWind (for Beacon Pulse mobile work)
- Experience building browser extensions (for Beacon Lens)
- Understanding of real-time data patterns (Pusher, WebSockets, polling)
- Experience with data visualisation libraries (charts, graphs, interactive displays)
- Design sensibility — you do not need to be a designer, but noticing when something looks wrong and knowing how to fix it is valuable
What We Offer
- Design influence — you shape how the product looks and feels, not just how it functions. Component decisions, interaction patterns, and UX trade-offs are part of your remit
- Cross-platform exposure — web SPAs, browser extensions, and desktop applications on the same design system
- Meaningful products — interfaces that businesses use daily for real operations, not marketing microsites
- Remote flexibility — UK-based, remote-first, with flexibility around core hours
- Technical depth — work with real-time systems, AI-powered interfaces, and multi-product design token architecture
- Small team impact — your components ship to production and you see how users interact with them
How to Apply
Send an email to careers@digitalroyalty.co.uk with your CV and a brief note on what draws you to this role. If you have a portfolio, GitHub profile, or live projects you have built, include them — seeing your work in context is more useful than a list of technologies on a CV. We do not use recruitment agencies.
The process: an initial conversation, a short practical exercise building something representative of the work you would do here, and a final discussion about the role. No whiteboard puzzles or abstract algorithm challenges.