AI/ML Engineering Lead
Summary
Hands-on AI/ML engineering lead at Protective Life who owns the path from ML/GenAI experimentation to governed production on Azure Databricks. Day to day: setting MLOps standards with MLflow, building RAG/LLM systems, mentoring ML and data engineers, and ensuring model reliability, monitoring, fairness, and regulatory compliance.
Protective Life is transforming how it builds and operates software — moving to a product operating model organized around empowered, outcome-oriented teams — and is investing in machine learning and generative AI to serve customers and run the business better. Voyager is one of these product pods, spanning our Life, Annuities, and Employee Benefits lines.
The AI/ML Engineering Lead is a hands-on technical leader who owns the path from experiment to governed production for machine learning and GenAI on our Databricks Lakehouse on Microsoft Azure. You will set the engineering standards for the ML lifecycle, mentor ML and data engineers, and personally deliver critical components — while working closely with product managers, data engineers, and Model Risk partners. As a regulated life insurer, we hold models to disciplined standards: this role is accountable not only for shipping models but for their reliability, monitoring, documentation, fairness, and explainability.
KEY RESPONSIBILITIES
- Lead the design and delivery of production ML and GenAI systems on Azure Databricks — from problem framing and data sourcing through deployment, monitoring, and retraining.
- Set technical direction and standards for the ML lifecycle — experimentation, feature engineering, training, evaluation, deployment, drift detection, and retraining — and hold the team to them.
- Provide hands-on technical leadership and mentoring to ML and data engineers through design and code reviews, pairing, and raising the bar on engineering craft.
- Build and operate MLOps foundations using MLflow (experiment tracking, model registry), Databricks Model Serving, and Unity Catalog for governed feature and model management.
- Architect GenAI capabilities — retrieval-augmented generation (RAG), embeddings and vector search, prompt/system design, evaluation harnesses, guardrails, and human-in-the-loop review.
- Depend on the pod's data stack — dlt (dltHub) ingestion, dbt models, and Dagster orchestration — to ensure training data and features are reliable, versioned, and reproducible.
- Establish CI/CD for ML in Azure DevOps (ADO) — automated testing, model packaging, and repeatable, auditable deployments across environments.
- Own model performance and cost — monitoring accuracy and output quality, latency, and drift, and managing training/serving compute with a FinOps mindset.
- Partner with Model Risk, Data Governance, Legal, and Security so models meet documentation, validation, explainability, bias/fairness, and privacy expectations.
- Translate product outcomes into ML solutions with product managers — balancing discovery experimentation against production reliability and time-to-value.
- Contribute to AI governance — model inventory, documentation, approval workflows, and responsible-AI practices aligned to company and regulatory expectations.
- Guide pragmatic adoption of the applied-AI landscape appropriate to a mid-sized carrier, avoiding hype and over-engineering.
QUALIFICATIONS
REQUIRED QUALIFICATIONS
- 8+ years in software, data, or ML engineering, including several years building and operating production ML systems.
- Demonstrated technical leadership — mentoring engineers, setting standards, and leading the design of non-trivial systems (formal people management not required, but valued).
- Strong Python and SQL, with deep experience across the end-to-end ML lifecycle and common ML frameworks (e.g., scikit-learn, PyTorch, or TensorFlow).
- Hands-on MLOps experience — experiment tracking, model registry, deployment/serving, monitoring, and retraining — with MLflow and Azure Databricks strongly preferred.
- Experience delivering GenAI/LLM applications: RAG, embeddings and vector databases, prompt/system design, and structured evaluation.
- Experience with the modern data stack the pod uses — dlt (dltHub) ingestion, dbt modeling, and Dagster orchestration — on a Databricks lakehouse (Delta Lake).
- CI/CD experience with Azure DevOps (ADO) and Git-based, test-supported development practices.
- Working knowledge of Microsoft Azure — compute, storage, identity, and Azure AI/OpenAI services.
- Demonstrated rigor in documentation, model evaluation, and secure, compliant handling of sensitive data.
- Bachelor's degree in Computer Science, Data Science, Statistics, Engineering, or a related field — or equivalent practical experience.
- Experience in financial services or insurance ML — underwriting, actuarial, fraud, claims, or customer models — and familiarity with model risk management practices (e.g., SR 11-7-aligned validation).
- Familiarity with Databricks Mosaic AI, Feature Store / Unity Catalog features, or Vector Search, and with Azure Machine Learning.
- Experience applying responsible-AI and model-governance techniques — bias/fairness testing and explainability (e.g., SHAP, LIME).
- Experience with streaming or real-time inference and low-latency serving.
- Experience coaching or formally managing engineers.
- Advanced degree in a quantitative field.
- Relevant certification such as Databricks Certified Machine Learning Engineer or Microsoft Azure AI Engineer Associate.
PREFERRED QUALIFICATIONS
Skills
- AI
- Azure
- Azure DevOps
- CI/CD
- Dagster
- Data Governance
- Data Science
- Databricks
- dbt
- Delta Lake
- DevOps
- Embeddings
- Feature Engineering
- FinOps
- Generative AI
- Git
- Lakehouse
- LLM
- Machine Learning
- MLflow
- MLOps
- Model Evaluation
- OpenAI
- Python
- PyTorch
- RAG
- scikit-learn
- SQL
- Statistics
- TensorFlow
- Test Automation
- Unity
- Vector Databases
- Vector Search
As published by lever · 12 questions · 6 written answers
Basics
Which location are you applying for?, Resume/CV, Full name, Email, Phone, Current location, Current company, LinkedIn URL, GitHub URL, Portfolio/video resume URL, Other website
Short answers (1)
- What is your target compensation (salary and bonus)?
Pick from a list (5)
- As part of any recruiting and hiring process, Protective collects and processes personal information relating to job applicants. The Company is committed to being transparent about how it collects and uses that information and to meeting its information protection obligations. In the recruitment and hiring process the “personal information” we collect includes: General Identifying and Contact Information (e.g., name, mailing address, phone number, email address), Employment History Information, Education History Information. Please be aware that the personal information you provide during the application process may be shared internally with employees of Protective as well as our designated third-party vendors for the purposes of the recruitment and hiring process, including contacting you regarding your application and assessing your qualifications for job openings with Protective. California applicants should review the state-specific notice provided in accordance with the California Privacy Rights Act. By clicking “Consent” below you understand and freely give your consent to Protective and our designated third-party vendors collecting and processing your personal information relating to your potential employment with Protective. Applicant Notice - California: As part of Protective’s commitment to transparency related to personal information, and in order to comply with the California Privacy Rights Act (“CPRA”), we are providing you with this disclosure regarding the categories of personal information we may collect from you and the purposes for which that information may be used. Information We Collect: In the recruitment and hiring process the categories of “personal information” we collect include: General Identifying and Contact Information (e.g., name, mailing address, phone number, email address), Employment History Information, Education History Information. Use of Personal Information: The personal information we collect during the application process is used to assess your qualifications for the purposes of the recruitment and hiring process, including contacting your regarding your application and assessing your qualifications for job openings with Protective. The personal information you provide will not be “sold to” or “shared with” a third-party as those terms are defined by the CPRA. The Company will not collect additional categories of personal information or use the personal information we collect for materially different, unrelated, or incompatible purposes without providing you notice. Retention of Information: Each of the categories of information you provide are subject to our internal policies on retaining employee and applicant information. These policies are based on applicable legal retention requirements for retaining personal information of applicants and/or employees. As part of our internal policies, we have a process in place to determine when this information is no longer needed and can be disposed of in a secure manner. Additional Information: For more information on your rights under the CPRA, please see the Company’s California Privacy Rights Act Policy. optional
- Are you legally authorized to work in the United States?
- Do you now, or will you in the future, require immigration sponsorship for work authorization (e.g., H-1B)?
- Have you ever been employed with Protective or one of its affiliates?
- How did you hear about this opportunity? optional
Written answers (6)
- Do you have any family members who are employed with Protective?
- Tell me about the last AI or machine learning system you built that real people used every day. What did it do, and how long did it run?
- What tools have you used to schedule and orchestrate pipelines? Did that orchestrator run outside your main data platform, and did it coordinate steps across more than one system?
- On a recent project, who owned what between the platform or infrastructure team, the data engineers, and whoever built the models? Where did work get stuck between them?
- Once a model or AI feature is live, how do you know it's still working correctly?
- What have you built with large language models that went to production — not a prototype? How did you check the output quality?