Senior Software Engineer

Lyric is an AI-first healthcare technology company focused on improving payment integrity in the healthcare ecosystem. They are seeking a Senior Software Engineer to lead front-end modernization, deliver full-stack features, and leverage AI tools to enhance development processes while ensuring high-quality standards in healthcare applications.

Responsibilities:

• Design and build React applications that are modular, testable, and accessible by default – with a real point of view on component architecture, state management, routing, and shared libraries
• Own the experience layer end to end: design system contributions, responsive layouts, accessibility (WCAG), client-side performance, error and loading states, and the small details that separate a workflow people tolerate from one they trust
• Partner with UX on flows that hold up under real customer workloads – dense tables, long-running operations, complex permissioning – not just happy-path mockups
• Shape and extend the .NET APIs your front end consumes – RESTful, versioned, and built for correctness and maintainability, not just 'it works.'
• Make pragmatic backend changes: adding endpoints, refactoring service boundaries, tightening contracts, and replacing legacy .NET code where it’s blocking the experience you’re trying to ship
• Get your hands into SQL when the UI demands it – query performance, indexing, transactional correctness – and contribute to data pipelines (Kafka, event-driven flows) when the work calls for it
• Use AI agents (Cursor, Claude Code, Codex) to power through component migrations, framework upgrades, API extraction, test scaffolding, and documentation – while catching hallucinations and preventing regressions before they hit a PR
• Build reusable playbooks the team can actually follow: prompt templates, repo-level agent instructions, migration checklists, review heuristics, and clear 'definition of done' standards for AI-assisted changes – on both the front-end and backend sides of the codebase
• Build with security and privacy as defaults, not afterthoughts – both on the client (safe data handling, careful state, sensible telemetry) and on the server (least privilege, auditability)
• Put real quality guardrails in place: component and integration tests, end-to-end coverage on the flows that matter, CI that blocks bad changes, structured logging, and front-end observability that tells you what users actually experience before they tell you
• Review code thoughtfully, have honest architectural conversations, and raise the bar without being a jerk about it
• Partner with analysts, stakeholders, designers, and other engineers to turn business problems into working software – not just technically correct software, but software that actually solves the problem
• Help build delivery plans that are honest about trade-offs. 'Right' vs. 'right now' is a real tension – you’ll help the team navigate it with pragmatic milestones

Requirements:

• 5+ years building and shipping production systems. Not side projects – real software with real users. You're able to work independently and collaboratively in fast-moving teams
• Deep front-end experience with React/Next.js (or comparable depth in Angular with a willingness to lead in React). You've built and maintained non-trivial applications: component architecture, state management, routing, forms, accessibility, and performance. You've worked at the scale where shared libraries and design systems become real problems – not slides
• Strong fundamentals across the modern web platform: TypeScript, HTML, CSS, browser performance, accessibility, testing (unit, component, end-to-end), and the build/release tooling that goes with it
• Solid working experience with C# and modern .NET (Core and beyond). You don't need to be the deepest backend engineer in the room, but you can confidently read, extend, and refactor service code – and you've done meaningful work in real codebases, not just greenfield
• Comfortable with SQL – enough to design reasonable schemas, write and tune the queries your UI depends on, and recognize when a performance problem belongs at the database, not the client
• API design experience – you've built and consumed service-oriented APIs with real versioning, auth, reliability, and testing practices, and you have opinions about what makes a backend pleasant (or painful) to integrate with from a front end
• Cloud experience with AWS and/or Azure. AWS is particularly relevant here
• You actually use AI coding tools as a daily driver. Cursor, Claude Code, Codex, or similar – and not just for autocomplete. You've used agents for multi-file refactors, migrations, test generation, and review workflows. You have opinions about what works and what doesn't
• You've led or played a significant role in a real front-end modernization – AngularJS to React, jQuery to a modern framework, a monolithic UI to micro-frontends, or similar. You know where the bodies are buried and you have the scars to prove it
• Deep design system or component library experience – you've built one, contributed substantially to one, or hauled a team off a tangle of one-off components onto something coherent
• You've done a legacy ASP.NET / .NET Framework modernization on the backend side
• Experience with distributed systems tooling – Kafka, event-driven architectures, or working with Postgres alongside SQL Server
• You've helped establish agent-friendly engineering practices: writing repo instructions that AI tools can follow, breaking work into agent-sized tasks, setting up CI guardrails for AI-generated code, feature flags, canary deployments – any part of the progressive delivery toolkit
• You communicate clearly. Good PR descriptions, straightforward design docs, pragmatic collaboration, low ego. We don't need a rockstar – we need someone the team trusts
• Background in regulated domains (healthcare, fintech, payments) where 'move fast and break things' will get you fired