Applied AI Engineer

Massachusetts, United States Mid Level AI/ML Engineer

Interested in this AI/ML Engineer role at Snowplow?

Apply Now →

Skills & Technologies

ApolloClaudeClayLemlistN8NPythonSalesforceSmartleadZapier

About This Role

AI job market dashboard showing open roles by category

About Snowplow

Snowplow is the real-time customer context layer that collects, validates, enriches, and delivers behavioral data for advanced analytics, ML, and AI agent decisioning. Snowplow's event tracking is leveraged across 2M+ websites and applications globally, processing over one trillion events per month.

More than 250 companies, including Experian, AutoTrader, Strava, Condé Nast, and HelloFresh, rely on Snowplow to build a well-governed, first-party data foundation that powers their customer-facing AI agents, in-session personalization and recommendations, and real-time analytics.

This Opportunity

Snowplow is rebuilding how the company runs its own work, and the Applied AI team owns Firn, the data and AI platform that work runs on, and the engineering standards that go with it. This role is an Applied AI engineer embedded with one business team, the way a site reliability engineer sits inside a product team: your line manager, your code reviewers and your career path come from Applied AI; your backlog and your day come from the team you serve. The Senior Director you report to still ships code.

Your team is Growth, the group inside Marketing that books new meetings for our sellers. Its workflows already produce pipeline: an always-on outbound engine that scores accounts daily and sends hundreds of personalized sequences, a campaign builder that turns an AE's target list into a reviewed campaign, a morning routine that ranks warm contacts by intent signal, enrichment and signal pipelines from Apollo, Vector, Kettlepoint and reo.dev into Snowflake, and a paid-media loop that adjusts ads. They were built by people close to the work to get results fast, and they did. Now they need an engineer who makes them production grade and keeps them improving.

You take over that estate, make it reliable, and make it better every week. The Director of Growth sets what matters, which is what moves pipeline now. You decide how it gets built and you build it. You work with our data engineers on scoring models and the semantic layer, with the platform engineer on the framework your workflows move onto, and with the Growth Associates and AEs who use what you ship. The engineering standards are Applied AI's; the tempo is Growth's.

What you will own

  • The GTM workflows in production. The outbound orchestrator and its sequences, the campaign builder, the intent-signal routine, the enrichment and signal pipelines, and the paid-media loop. You know how each one runs, what it costs, and what to do when it breaks.
  • Review steps before anything sends. Agents that check the list, confirm each signal is current, and review the copy before a sequence goes out, with a holdback gate and sampled human sign-off on anything headed for an inbox we have not already had a reply from.
  • The learning loop. Replies and meetings booked feed back into who we contact and what we say. You instrument the sends, run A/B tests on variants, and show the Growth team which messaging is working.
  • Signals and enrichment. The pipelines that bring third-party signals and first-party behavior into Snowflake: Kettlepoint job-change and hiring signals, Apollo firmographics, and our own event data. You also own the fields the Growth team needs exposed through our MCP tools, and the work with our data engineers that gets them there.
  • Skills and routines for sellers. The Claude skills the Growth Associates and AEs run each morning, the campaign tooling, and the short working sessions that get a new team using them.
  • Deliverability and suppression. One set of contact rules every sender reads, warm-inbox discipline, and the suppression windows that keep us welcome in people's inboxes.
  • Engineering standards on your estate. Version control, alerting, tracing, runbooks and documented handover for every workflow you run, and a steady move of those workflows onto the Firn factory framework.
  • The weekly cadence. A standing backlog with the Director of Growth, priorities set by pipeline, and a short written account of what shipped and what it did. When a priority and an engineering standard conflict, the Director of Growth and the Senior Director of Applied AI settle it together.

We would love to hear from you if you have

  • Written software that runs in production. Python and SQL are your working languages, you use git every day, and when you meet a new API you read the docs and use it. Tools like n8n, Clay or Zapier are in your kit, and when they run out you write the code.
  • Built with LLMs for real work. Prompts, tools, structured outputs and evaluation, and the failure modes of each. You know what a model does when a prompt does not say where to get its data, and you design against it.
  • Run something that could not go down. Alerting, error handling, retries and recovery are habits, and when something does fail you fix the class of problem, not the instance.
  • Moved data into a warehouse. You have built or maintained pipelines into Snowflake or an equivalent, and you can model a table in dbt or learn to quickly.
  • Sat with sellers and marketers. You can take a growth director's ask, work out what they need, and come back with something they use the next week. When an ask is a symptom of a broken process, you say so before you build it.
  • A fast tempo. The team you serve measures in meetings booked per week. You are measured on what you build: whether it runs, what it costs, and what it changed for the team. You ship small, measure, and say plainly when something is not working.
  • An AI-native way of working you can show us. A workflow, automation or agent you built and still use. Expect to demonstrate it during the interview process.
  • Comfort being embedded. You can sit inside another team, take its priorities, and still hold the engineering standards your own team sets.

Bonus points for

  • Experience with Salesforce, Apollo, Smartlead, Lemlist or similar GTM tooling and their APIs.
  • Experience with email deliverability at volume.
  • Experience with paid-media platform APIs.

How we hire for this role

The interview process includes a short technical exercise in code and a working session where you walk us through how you work with AI on a real task, using your own setup. We work this way ourselves, and you are welcome to use AI when applying.

What you get in return for being awesome

  • Meaningful equity stake
  • Competitive Base Salary
  • Flexible working
  • Generous PTO
  • Medical, Dental & Vision Insurance
  • 401k
  • MacBook and home office equipment allowance
  • Enhanced Family leave

Role Details

Company Snowplow
Title Applied AI Engineer
Location Massachusetts, United States
Category AI/ML Engineer
Experience Mid Level
Salary Not disclosed
Remote No

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 Snowplow, 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

Apollo Claude (6% of roles) Clay Lemlist N8N Python (23% of roles) Salesforce (2% of roles) Smartlead Zapier

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.

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.

Snowplow AI Hiring

Snowplow has 1 open AI role right now. They're hiring across AI/ML Engineer. Based in Massachusetts, United States.

Location Context

Across all AI roles, 6% (580 positions) offer remote work, while 9,776 require on-site attendance. Top AI hiring metros: New York (3,785 roles, $222,480 median); San Francisco (3,262 roles, $261,300 median); Los Angeles (1,896 roles, $210,000 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

Based on 16,346 roles with disclosed compensation, the median salary for AI/ML Engineer positions is $213,800. Actual compensation varies by seniority, location, and company stage.
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.
About 6% of the 10,419 AI roles we track offer remote work. Remote availability varies by company and seniority level, with senior and leadership roles more likely to offer location flexibility.
Snowplow is among the companies actively hiring for AI and ML talent. Check our company profiles for detailed breakdowns of open roles, salary ranges, and hiring trends.
Common next steps from AI/ML Engineer positions include ML Architect, AI Engineering Manager, Principal ML Engineer. Progression depends on whether you lean toward technical depth, people management, or product strategy.

Get Weekly AI Career Intelligence

Salary data, skills demand, and market signals from 16,000+ AI job postings. Every Monday.