Senior Software Engineer

ComPsych Ⓡ is the worldwide leader in organizational mental health, well-being, and absence management, dedicated to igniting human potential in workplaces across the globe.

For over 40 years, we have combined the best in technology with unmatched human expertise to help individuals and their organizations thrive.

Our GuidanceResources Ⓡ and AbsenceResources Ⓡ solutions deliver end-to-end mental health, well-being, work-life, health navigation, and absence support to more than 75,000 customers worldwide, touching more than 160 million lives across 200 countries.

Visit compsych.com to find out why 40% of the Fortune 500 choose ComPsych for their mental health and absence management needs.

We're modernizing how ComPsych builds technology — new customer-facing web and mobile experiences, a unified design system, and AI-powered capabilities across our products.

That means raising the engineering bar for how we design, build, and operate software, with Engineering, Product, and Design working together end to end.

We're looking for a Senior Software Engineer who has hands-on experience with modern, AI-led development practices and wants to help shape how our engineering organization builds software going forward.

This is a high-leverage role: you'll spend more time on system design, task decomposition, and technical direction than on writing code line-by-line.

You'll use AI tools to generate code, automated tests, and first-pass reviews, then apply your own judgment to validate and refine that output before it ships.

AI changes what your time goes toward.

You're still accountable for the full lifecycle — planning, design, code, tests, review, production — but your hands-on role in each shifts:

• Plan and design as your core contribution. You own problem framing, sequencing, and tradeoffs with Product and Design, and the system design that follows — the data model, the API contracts, the failure modes.
• Direct implementation rather than writing it line by line. Decompose the work, write the specs, and let AI agents build — dropping into the code yourself when debugging or complexity demands it.
• Own testing as a design decision. You decide what needs coverage and at what level, direct AI to build it, and validate that the tests prove what they claim — not just that they pass.
• Build security, reliability, and observability in from the start. They're design inputs, not production afterthoughts — the systems you ship can be operated safely and understood when they fail.