Interested in this AI/ML Engineer role at Provn?
Apply Now →Skills & Technologies
About This Role
Provn is helping Envorso Sports recruit a Founding AI Engineer. Please apply on our home page on Provn and take the challenge to stand-out from competition.
About Envorso Sports
Envorso Sports is building the platform that runs a professional sports team's entire fan-facing business: ticketing, website, mobile app, and increasingly commerce, CRM, and marketing, from one system instead of six disconnected vendors.
Today, most teams run a fragmented stack: a website vendor, a ticketing provider, a separate mobile app, CRM tools, marketing automation, and game-day engagement solutions bolted together. Teams don't want to pay five vendors and contractors to stitch the data together. That creates a disconnected fan journey and leaves revenue on the table.
Our platform is live today with the Seattle Seawolves of Major League Rugby, and the league itself is now on the platform, with individual teams onboarding through the season. Ticketing, website, and mobile app are shipped and in production with paying customers. CRM, marketing automation, personalization, and revenue operations are what we build next, AI-native from the start. We want candidates to know exactly where the product stands before they join.
About the Founding Engineer Role
You'll be our first in-house engineer. This is a founding role: you'll own the fan data platform for the long term and help shape how we grow engineering, not ship one feature and move on.
The problem is simple to state. Our teams and the league sit on a large fan database: ticket transactions, web and app activity, shop purchases, and email engagement. Today almost none of it is used. One salesperson calls season-pass holders; one marketer sends a broadcast email and sees who bites. Your job is to turn that data into revenue: unify what we know about each fan across ticketing, web, app, shop, and email; decide which fans should get which offer; and deliver it through email and in-app offers or push.
Offers are concrete: a promo code for an abandoned cart, a season pass or match pass, a merch bundle, a seat upgrade. Getting the wrong offer to the wrong fan costs real money and real trust with a small, loyal fan base.
You'll build for a three-to-five-year horizon, not just this quarter. We need someone who thinks like an architect (data model, scale, failure handling, consent, cost) while still shipping something a team can use in weeks.
You'll also be the engineer closest to our customers' front offices. Part of the job is understanding how a team's revenue and marketing operations actually work, and helping decide what we build first based on impact and effort.
You'll report to Gopal Rao and work alongside our five-engineer team in Argentina as one small group. Expect real overlap-hours collaboration, and expect to take a problem, make the call, and ship without waiting on someone else.
What You'll Do
- Own the fan data platform end to end: a unified fan record across ticketing, web, app, and email, designed to hold up as we grow from one team's list to a whole league's
- Ship fan segmentation and a targeted offers engine that decides which fans get which offer, and delivers it by email reactivation and in-app offers or push
- Build marketing ops and revenue ops driven by agentic AI: fan identity, segments, campaign builder and automation, and propensity, churn, and pricing models
- Bring commerce into the fan record: shop purchases alongside tickets, so offers can cross-sell merch, passes, and seat upgrades
- Build the surfaces people use, in TypeScript and Next.js on web and in our mobile app, so offers are something a marketer reviews and a fan acts on, not just an API response
- Design for production from day one: consent and opt-in enforcement, no duplicate sends, failures that are visible instead of silent, and costs you can explain
- Work with team front offices to understand their revenue goals, and sequence the roadmap by impact and effort
- Make AI how we ship: build an AI-native product where models change the outcome for a marketer or a fan, and run an agentic development process (AI-SDLC) with coding agents, specs and tests as guardrails, and human review before anything reaches a fan
- Help decide how engineering grows: how we scale with our Argentina team, what we build in-house, and who we hire next
How We Hire
Apply through Provn by completing a short challenge and video walkthrough. If your submission clears the bar, you'll move straight to a conversation with our team. We don't wait to batch candidates. The process: a screen with Gopal, a technical interview, then a panel with engineering and product leaders.
Work Authorization
Must be authorized to work in the US. No employer-sponsored visas for this role.
Salary Context
This $125K-$145K range is in the lower quartile for AI/ML Engineer roles in our dataset (median: $180K across 1953 roles with salary data).
View full AI/ML Engineer salary data →Role Details
About This Role
AI/ML Engineers build and deploy machine learning models in production. They work across the full ML lifecycle: data pipelines, model training, evaluation, and serving infrastructure. The role has evolved significantly over the past two years. Where ML Engineers once spent most of their time on model architecture, the job now tilts heavily toward inference optimization, cost management, and integrating LLM capabilities into existing systems. Companies want engineers who can ship production systems, and the experimenter-only role is fading fast.
Day-to-day, you're writing training pipelines, debugging data quality issues, setting up evaluation frameworks, and figuring out why your model performs differently in staging than it did on your dev set. The best ML engineers are obsessive about reproducibility and measurement. They instrument everything. They know that a model is only as good as the data feeding it and the infrastructure serving it.
Across the 10,419 AI roles we're tracking, AI/ML Engineer positions make up 75% of the market. At Provn, this role fits into their broader AI and engineering organization.
Demand for AI/ML Engineers has been strong and consistent. Unlike some AI roles that spike with hype cycles, ML engineering is a foundational need. Every company deploying AI models needs people who can keep them running, and the gap between research prototypes and production systems keeps growing.
What the Work Looks Like
A typical week might include: debugging a data pipeline that's silently dropping 3% of training examples, running A/B tests on a new model version, writing documentation for a feature flag system that lets you roll back model deployments, and reviewing a junior engineer's PR for a new evaluation metric. Meetings tend to be cross-functional since ML touches product, engineering, and data teams.
Demand for AI/ML Engineers has been strong and consistent. Unlike some AI roles that spike with hype cycles, ML engineering is a foundational need. Every company deploying AI models needs people who can keep them running, and the gap between research prototypes and production systems keeps growing.
Skills Required
Python and PyTorch dominate the requirements. Most roles expect experience with cloud platforms (AWS, GCP, or Azure) and familiarity with ML frameworks like TensorFlow or JAX. RAG (Retrieval-Augmented Generation) has become a top-3 skill requirement as companies integrate LLMs into their products. Docker and Kubernetes show up in about a third of postings, reflecting the production focus of the role.
Beyond the core stack, employers increasingly want experience with experiment tracking tools (MLflow, Weights & Biases), feature stores, and vector databases. Fine-tuning experience is valuable but less common than you'd think from reading Twitter. Most production LLM work is RAG and prompt engineering, not fine-tuning. If you have both, you're in a strong position.
Companies that are serious about AI/ML hiring tend to post specific infrastructure details in the job description: the frameworks they use, their model serving stack, their data pipeline tools. Vague postings that just say 'ML experience required' without specifics are often companies that haven't figured out what they need yet.
Compensation Benchmarks
AI/ML Engineer roles pay a median of $213,800 based on 16,346 positions with disclosed compensation. Mid-level AI roles across all categories have a median of $193,200. This role's midpoint ($135K) sits 37% below the category median. Disclosed range: $125K to $145K.
Across all AI roles, the market median is $214,834. Top-quartile compensation starts at $266,000. The 90th percentile reaches $321,730. For comparison, the highest-paying categories include AI Safety ($274,500) and Research Engineer ($252,000). By seniority level: Entry: $114,400; Mid: $193,200; Senior: $230,000; Director: $272,100; VP: $235,000.
Provn AI Hiring
Provn has 5 open AI roles right now. They're hiring across AI/ML Engineer. Positions span New York, NY, US, Chicago, IL, US, Seattle, WA, US. Compensation range: $145K - $200K.
Location Context
AI roles in Seattle pay a median of $226,700 across 1,337 tracked positions. That's 6% above the national median.
Career Path
Common paths into AI/ML Engineer roles include Data Scientist, Software Engineer, Research Engineer.
From here, career progression typically leads toward ML Architect, AI Engineering Manager, Principal ML Engineer.
The fastest path into ML engineering is through software engineering with a self-directed ML education. A CS degree helps, but production engineering skills matter more than academic credentials. Build something that works, deploy it, and measure it. That portfolio project is worth more than a Coursera certificate. For career growth, the fork comes around the senior level: go deep on technical complexity (staff/principal track) or move into managing ML teams.
What to Expect in Interviews
Expect system design questions around ML pipelines: how you'd build a training pipeline for a specific use case, handle data drift, or design A/B testing infrastructure for model deployments. Coding rounds typically involve Python, with emphasis on data manipulation (pandas, numpy) and algorithm implementation. Take-home assignments often ask you to build an end-to-end ML pipeline from raw data to deployed model.
When evaluating opportunities: Companies that are serious about AI/ML hiring tend to post specific infrastructure details in the job description: the frameworks they use, their model serving stack, their data pipeline tools. Vague postings that just say 'ML experience required' without specifics are often companies that haven't figured out what they need yet.
AI Hiring Overview
The AI job market has 10,419 open positions tracked in our dataset. By seniority: 117 entry-level, 4,975 mid-level, 3,840 senior, and 1,487 leadership roles (Director, VP, C-Level). Remote roles make up 6% of the market (580 positions). The remaining 9,776 roles require on-site or hybrid attendance.
The market median for AI roles is $214,834. Top-quartile compensation starts at $266,000. The 90th percentile reaches $321,730. Highest-paying categories: AI Safety ($274,500 median, 90 roles); Research Engineer ($252,000 median, 580 roles); AI Engineering Manager ($250,811 median, 72 roles).
Demand for AI/ML Engineers has been strong and consistent. Unlike some AI roles that spike with hype cycles, ML engineering is a foundational need. Every company deploying AI models needs people who can keep them running, and the gap between research prototypes and production systems keeps growing.
The AI Job Market Today
The AI job market spans 10,419 open positions across 16 role categories. The largest categories by volume: AI/ML Engineer (7,849), AI Product Manager (516), AI Software Engineer (513). These three account for the majority of open positions, though smaller categories often have higher per-role compensation because of specialized skill requirements.
The seniority mix tells a story about where AI teams are in their maturity. Entry-level roles (117) are outnumbered by mid-level (4,975) and senior (3,840) positions, reflecting that most companies are past the 'build a team from scratch' phase and need experienced engineers who can ship production systems. Leadership roles (Director, VP, C-Level) total 1,487 positions, representing the bottleneck between technical execution and organizational strategy.
Remote work availability sits at 6% of all AI roles (580 positions), with 9,776 requiring on-site or hybrid attendance. The remote share has stabilized after the post-pandemic correction. Senior and specialized roles (Research Scientist, ML Architect) are more likely to be remote-eligible than entry-level positions, partly because experienced hires have more negotiating power and partly because these roles require less hands-on mentorship.
AI compensation is structured in clear tiers. The market median sits at $214,834. Top-quartile roles start at $266,000, and the 90th percentile reaches $321,730. These figures include base salary with disclosed compensation. Total compensation (including equity, bonuses, and sign-on) runs 20-40% higher at companies that offer those components.
Category matters for compensation. AI Safety roles lead at $274,500 median, while Prompt Engineer roles sit at $140,000. The spread between highest and lowest-paying categories reflects the premium on specialized technical skills versus broader analytical roles.
The most in-demand skills across all AI postings: Python (2,350 postings), Aws (1,173 postings), Azure (1,030 postings), Rag (986 postings), Gcp (714 postings), Pytorch (649 postings), Kubernetes (583 postings), Claude (581 postings). Python dominates, appearing in the vast majority of role descriptions regardless of category. Cloud platform experience (AWS, GCP, Azure) is the second most common requirement. The newer entrants to the top skills list (RAG, vector databases, LLM APIs) reflect the shift from traditional ML toward generative AI applications.
Frequently Asked Questions
Get Weekly AI Career Intelligence
Salary data, skills demand, and market signals from 16,000+ AI job postings. Every Monday.