- Growth StageExpanding market presence
- Recently fundedRaised funding in the past six months
In office
Not Available
About the job
About Leon Capital Group
Leon Capital Group is a multi-billion-dollar holding company with operating businesses across healthcare, real estate, and financial services. Within the Financial Services Group (FSG), we are building an AI-native operating model from the ground up: a dedicated, full-lifecycle innovation function that identifies, designs, builds, delivers, and implements AI products across our portfolio companies.
About the Role
This is two halves of one job: The Data Platform & Machine Learning Engineer will own the data platform every FSG and healthcare AI product depends on, and you build the first machine learning models on top of it. The two are inseparable, because the models are only as good as the proprietary, provenance-tracked data beneath them, and that data is yours to design, capture, and own. Not a pipeline specialist, not a modeling specialist, but the engineer who does both, as a member of a small data platform team, on foundations that range from ones you stand up yourself to established platforms you extend and modernize.
The role has a deliberate arc. The first few months lean heavily toward data engineering: the canonical model and warehouse, ingestion that forces messy external data into our schema, and judgment capture that turns every human decision into labeled training data. As that corpus matures, the center of gravity shifts toward building the first risk and recommendation models on it. You work across portfolio companies in both FSG and healthcare, standing up or extending each one's data layer and models and reusing the same patterns and discipline rather than reinventing the approach each time. We want someone energized by both halves, not someone tolerating the foundation to reach the models, or the reverse.
You will work across both ends of the maturity curve. Some portfolio companies run established platforms (cloud warehouses, dbt, orchestration, BI) that need extending, hardening, and integrating; others, including businesses we acquire, run on spreadsheets, vendor portals, and flat-file feeds with no platform at all. You need to be productive in both: respecting what already works in a mature stack, and building from zero where nothing exists.
You will also be expected to use AI as part of how you work, not only what you build. A small team covering two sectors and many portfolio companies only scales if everyone already uses AI tools every day to write and review code, draft pipelines and tests, profile data, and explore modeling approaches. The bar is judgment: you verify what AI produces, own everything you ship, and know when not to use it. Unreviewed output and blind trust in a model are not acceptable here, and critical thinking matters more to us than any tool.
Key Responsibilities
- Co-design and own key components of the canonical data model and warehouse, built to remain ours regardless of which vendors we buy.
- Build the data platform and models as reusable patterns, standing up each portfolio company's own instance rather than a bespoke build each time.
- Work across mature and immature stacks: extend and integrate with established platforms where they exist, and stand up lightweight, production-ready foundations from zero where they do not.
- Migrate and modernize legacy pipelines and data stores onto the shared platform without disrupting the reporting and operations that depend on them.
- Build ingestion pipelines that pull from hostile, heterogeneous sources into our schema with full provenance, including vendor servicing output, flat-file and SFTP partner feeds with no API, and public registry data.
- Stand up judgment capture from the first transaction: structure every decision and correction as labeled training data, the raw material that human-in-the-loop workflows and future models both depend on.
- Lay the groundwork for risk and recommendation models: feature engineering, training-set construction, model evaluation, and calibration.
- Build validation, monitoring, and lineage so data-quality issues are caught before they reach models or decisions.
- Enforce the data-ownership bar in every buy decision: vendor output must land in our canonical structure, in our schema, and remain portable on exit.
- Partner closely with AI Engineers, providing the models, data, and serving interfaces their decision surfaces and the production AI agents already live in the portfolio are built on.
Qualifications
Required:
- 5+ years building data systems end to end, including required experience at a startup or in a 0-to-1 build environment, as an early or founding data hire who took a data function from nothing to production rather than owning one stage of a large team.
- Hands-on experience with both mature and immature data stacks: you have worked inside an established modern data platform (e.g., a cloud warehouse or lakehouse, dbt, Airflow or Dagster, CI/CD for data) and you have built where there was no platform at all. You know when to adopt the existing pattern and when to build from scratch.
- AI-augmented daily practice. You already use AI to accelerate your engineering work and can show how: what you delegate, how you verify it, and where it got something wrong and you caught it. You treat AI output as a draft to be challenged, not an answer to be trusted. Critical thinking comes first; tool fluency comes second.
- Strong data engineering fundamentals: schema design, ETL and ELT pipeline architecture, and production experience with PostgreSQL.
- Comfort owning data infrastructure in a major cloud environment (we use a mix across Azure and AWS); you can stand up and run the warehouse and pipelines without a dedicated platform team.
- Comfort building under regulatory and fiduciary constraints, and handling sensitive, regulated data (PHI under HIPAA, and financial and policyholder data) with the secure practices it requires.
- Applied machine learning and statistical modeling depth: feature work, model evaluation, calibration, and the judgment to reason about model risk. You orchestrate and apply models; you do not need to publish research.
- Working fluency with LLM orchestration and agentic workflows (e.g. LangGraph) on production model platforms (e.g. Anthropic Claude, AWS Bedrock), retrieval-augmented generation, and disciplined prompt and evaluation practices.
- Excellent judgment under ambiguity and the ability to prioritize across multiple portfolio companies without close oversight.
Note to Search Firms and Agencies:
Leon Capital Group does not accept unsolicited submissions from search firms or employment agencies. Any resume submitted to any employee of Leon Capital Group without a valid written search agreement in place will be deemed the sole property of Leon Capital Group, and no fee will be paid in the event the candidate is hired.
About the company
- Growth StageExpanding market presence
- Recently fundedRaised funding in the past six months






