Senior Software Engineer, Tech Lead

The Role at a Glance

We build the customer-facing web applications our policyholders use to manage their coverage — the digital front door to their relationship with us. You'll lead a small team of mid-level and junior engineers building and evolving those applications on a modern Java/Spring and React stack.

This is a technical leadership role, not a people management one. You won't run 1:1s or own performance ratings, but you will own the technical direction of your team's work, and your voice carries real weight in how we evaluate, hire, and grow engineers. The engineers on this team are early enough in their careers that your example sets the standard — how you review code, how you write things down, and how you respond when someone asks a basic question will shape this team more than any process we could put in place.

What you'll be doing

• Own technical direction for a portfolio of customer-facing applications: architecture, design decisions, technical tradeoffs, and the sequencing of work that keeps the codebase healthy while features ship.
• Lead a team of mid-level and junior engineers day to day — breaking down ambiguous work into tractable pieces, unblocking people, and making sure the hardest problem isn't always landing on the same person's plate.
• Grow the engineers around you. Code review that teaches rather than just gates. Design docs the team actually reads. Pairing on the problems that don't fit in a ticket. Setting the expectation that questions are cheap and silent confusion is expensive.
• Set the team's standards for AI-assisted development: reusable skills and workflows that make everyone faster, expectations for how generated code gets reviewed and tested before it ships, and clear judgment about which work shouldn't be delegated to a tool at all. Your team will lean on these tools heavily; you're the one making sure that's a strength rather than a source of quiet technical debt.
• Partner with product, design, compliance, and security. Translate technical constraints into terms partners can act on, and translate their constraints back into engineering decisions.
• Represent engineering in planning and prioritization: push back on scope when it's warranted,