Description:
We are seeking a Product Engineer to join our Product Engineering team. This is a high-impact Individual Contributor (IC) role designed for an engineer who excels at execution and technical craft but is equally driven by product strategy and user value.
You will join a cross-functional team (alongside a Product Manager, Product Designer, and other Engineers) to own features from the discovery stage through to deployment and monitoring. You are a builder who wants to ship code that solves real problems for care professionals and care homes.
What You Will Do
- Own Features End-to-End: You will write clean, maintainable Ruby and React code. You are comfortable jumping between the backend business logic and the frontend user interaction.
- Partner with Product: You will be involved before the project is kicked off. You will work with the PM and Designer to assess feasibility, suggest technical trade offs, and refine the solution.
- Mentorship (Not Management): You will set a high standard for code quality. You will review PRs, pair with mid-level engineers, and mentor them technically, but you will not be responsible for HR, hiring, or performance reviews.
- System Health: You will ensure the product is performant and bug-free, writing comprehensive tests and monitoring errors.
What This Role Is NOT
- It is not a Management role: You will have no direct reports. Your focus is contribution and technical influence, not people management.
- It is not a Staff/Principal role: While you will make architectural decisions for your features, you are not expected to spend your days writing RFCs for the entire engineering organisation or managing cross-team dependencies. Your primary focus is execution within the team.
Who You Are
- A Rails & React Veteran: You have significant commercial experience (roughly 5 years) building web applications. You know the "Rails Way," but you also know when to break the rules. You are comfortable with modern React patterns.
- Product-Minded: You don't just execute tickets. You ask questions like: "How does this help a care professional get paid faster?" or "Is this the simplest way to solve the user's problem?"
- Pragmatic: You hate over-engineering. You know that shipping value to users is more important than using the absolute latest trendy library.
- Empathetic: You understand that our users are working in high-stress healthcare environments. Reliability and usability matter.
- Thrive in ambiguity: You dive into the unknown and work to bring people, ideas and problems together to form a clear cohesive plan