Senior Product Engineer

Start free →

Or apply yourself on the official page →

About the role

Become a part of our caring community   The Senior Product Engineer helps decide what we build, not just how we build it. This is a senior engineering role at its foundation. You design, develop, and deploy scalable web applications end to end, and you meet a high bar for engineering craft. You also own the product: you shape what we build, influence what goes on the roadmap, and are measured by the outcomes your work produces rather than the tickets you close. You explore before you commit, propose the work as often as you receive it, and sharpen requirements rather than simply implement them. You will build accessible user interfaces, implement robust back-end microservices, and integrate the two with GraphQL, all while exercising considerable latitude over technical approach. Strong product instinct here does not lower the engineering bar; it raises the overall one. How We Work We work in an agent-accelerated, skills-driven engineering practice. Our engineers use AI coding tools like Claude Code as a core part of daily development. They also build and maintain the shared skills and tooling that make that workflow effective, rather than only consuming what someone else set up. You will extend your environment, not just operate inside it. This is an emerging practice, not a settled playbook. The line between product and engineering is blurring, and on this team you will help establish how that works rather than inherit a finished process. If building a new way of working sounds like the reason to take the job rather than a source of uncertainty, you are the person we are looking for. Responsibilities • Shape what we build: Propose and challenge what goes on the roadmap, not just how it gets implemented. Turn a rough problem into a defined piece of work, write the stories yourself, and sharpen requirements rather than waiting for them to arrive fully formed. • Own outcomes: Measure success by the impact your work has (adoption, accessibility, performance, reliability), not by the number of tickets closed. Set and pursue the outcomes that matter for the products you own. • Explore before committing: Run discovery, spikes, and prototypes to test whether something is the right thing to build before investing in a full implementation • Stay close to the problem: Engage directly with users and stakeholders to understand the problems behind the requests, when access to them allows; carry what you learn back into the work • End-to-end delivery: Independently design, develop, and deploy full-stack applications, including accessible UIs, GraphQL APIs, and Node.js-based microservices, ensuring seamless integration across all layers • Accessible UI development: Build responsive, WCAG 2.2-compliant user interfaces with accessibility as a first-class concern, including semantic HTML, ARIA, keyboard navigation, and screen reader testing • Performance and security: Optimize application performance (e.g., lazy loading, code splitting, query complexity analysis) and implement security best practices (e.g., OAuth2, JWT, input validation) • Test-driven development: Follow TDD principles to write comprehensive unit, integration, and end-to-end tests. Engineering rigor is non-negotiable regardless of how fast the tooling lets us move. • Microservices architecture: Architect and implement scalable, domain-driven microservices with Node.js, adhering to modern best practices such as API-first design and cloud-native principles • GraphQL expertise: Design and develop efficient GraphQL services, including schema design, query optimization (e.g., batching, caching), and integration with front-end and back-end systems • Cloud integration: Deploy and manage applications on cloud platforms (e.g., Azure, GCP, or AWS), leveraging container technolo

View the official posting →