About the role  VIVIO Health is transforming how it operates with AI, and we are hiring a senior engineer to build the features that make that real: language-model capabilities for our clinical, client success, and member experience teams, built on AWS Bedrock and related models and shipped to real users. Your job is to take a business problem from one of those teams, work out where a model helps and where it does not, and deliver something the team uses every day. This is not a research role. The AI work lives inside our production platform, so you will also ship application features, work with the integrations that exchange data with our partners and build the test and quality practices that keep all of it reliable.  Our clinical programs are the first area we are transforming with AI, so your early work will be with the clinical team and the documents, reviews, and decisions that run through it. Other business areas follow as the platform stabilizes.  The role is remote, with structured written communication as the default working mode. You report to the Head of Engineering and work directly with the business owners of the problems you solve.  What you will do  Build and extend LLM-backed capabilities on AWS Bedrock and related models: document OCR and extraction on clinical and claims paperwork, summarization and decision support for clinical review, Knowledge Bases for retrieval over plan and policy documents, and workflow automation for internal teams  Establish and maintain evals for the AI features you ship, so we know when quality drifts  Handle the practical side of production AI: structured output, failure modes, cost, latency, and knowing when a deterministic approach beats a model  Use agentic coding tools (Claude Code and Kiro) as a core part of your workflow, and own the verification of what they produce  Design, build, test, and ship features in our Python and FastAPI back end on MySQL and AWS, and our Jinja2, Tailwind, and Alpine.js front end, with a bias toward fixing what is broken before adding what is new  Work with the integrations that exchange eligibility, accumulator, and claim data with carriers and pharmacies, including NCPDP D.0 and X12 270/271 transactions and the file formats behind them  Put test and lint gates in place where they are missing, and treat CI as part of the definition of done  Treat PHI handling as a first-class design constraint in everything you build  Write clear specs, prompts, and design notes; at this level, written communication is an engineering skill  How we work  Development happens in a managed Linux environment that you reach by remote desktop from a Windows endpoint; PHI never lands on a laptop. You need to be fluent in both: Linux for the actual engineering, Windows as the workstation you get there from.