Senior Frontend Engineer (React) in Sheffield

CRU has been producing commodity market data and analysis for over 50 years. We serve clients across global metals, mining and fertilizer markets — organisations who use our data to make pricing, supply chain, and investment decisions at scale. Our Sheffield engineering team builds and maintains the digital products through which those clients access our intelligence.

About the role: We're looking for a senior engineer who sets the bar rather than meets it: someone who owns the technical direction of what they work on and feels responsible for it long after the ticket is closed. If that sounds like how you work, read on.

What You'll Own

• The technical quality bar for CRU's customer-facing web applications — architecture decisions, code review standards, and the patterns the rest of the team builds on.
• End-to-end delivery of new features: from early ideation with Product and UX through to production, iteration, and the next cycle.
• The engineering culture your team operates at — you raise it, you protect it.
• The translation layer between technical complexity and business decisions — stakeholders should leave conversations with you able to act, not just informed.

Who You Are

These aren't requirements to tick off — they're descriptions of how you work:

• You've built something nobody asked you to, because you could see it needed to exist.
• When requirements are unclear, you form a hypothesis and move — clarifying as you go rather than waiting for a spec to appear.
• You push back on product or design decisions when you think they're wrong. With evidence, not volume. And you're willing to be wrong back.
• You've broken something in production. You can tell me what you did, what you learned, and what changed because of it.
• You have strong technical opinions. Some of them you've revised. You know exactly what changed your mind.
• You measure whether what you shipped made a difference. When you can't measure it, you say so.

This Isn't for You

• If you're looking for a project to deliver and hand off, not a codebase to own.
• You need detailed requirements before you can start forming an opinion.
• You measure success by stories closed, not by what customers can now do.
• You haven't shipped and maintained software used by real paying users in production.

Technical Bar

• Cloud platforms — Azure preferred. You've worked with the infrastructure your code runs on and you've engaged with it directly, not just handed tickets to an ops team.
• Testing, CI/CD, SDLC — You write tests because you've felt what happens when you don't.
• Full-stack exposure — you can navigate a backend when you need to. Python is a genuine bonus, not a nice-to-have footnote.
• Communication — you can explain a technical tradeoff to a non-technical stakeholder without dumbing it down or losing the room.
• Experience level — you've been through enough full delivery cycles to have opinions about what breaks them and what doesn't.
• BSc in Computer Science or related field, or equivalent experience.

What You'll Get

• Technical influence — your architectural decisions shape products used daily by industry analysts and strategists worldwide.
• Meaningful domain — the engineering problems here are real: complex data relationships, demanding expert users, high-stakes outputs.
• The team — A focused engineering team that values technical opinions backed by evidence, ownership over 'just finishing tickets,' and the occasional debate over the right way to build for the long term.
• Hybrid working — Sheffield base, (2 days/week in office).