Interested in this AI/ML Engineer role at Minerva?
Apply Now →Skills & Technologies
About This Role
ABOUT MINERVA
Minerva builds AI for marketing leaders. We work together with marketers to automate and accelerate their workflows with AI agents. Our agents augment the end-to-end workflow of the marketer by automating analysis, campaign planning, activation, measurement and reporting.
Customers like the NBA, Ramp, Wander, Hard Rock Stadium Group and Luxury Presence use Minerva to develop a better understanding of their customers and introduce AI specifically built to understand the customer into their commercial organizations. Our campaigns outperform other tools because we built the entire stack: from identity to enrichment to data integration as well as agents to action and report on the analysis.
We've raised $20M from The General Partnership, 8VC, Lingotto, NBA Investments, Topology Ventures, Future Positive, Background Capital and many others. Our team brings together operators and investors from Citadel, Dentsu, Bridgewater, Meta Superintelligence, Growthloop, Amazon and Lazard, alongside engineers and researchers from Berkeley, MIT, Stanford and Cambridge.
OUR STACK
- Agents: Claude across the company (in Slack, through the API, with skills and MCP), plus Mastra for the agents we build ourselves and Temporal for long-running work.
- Code: Python and TypeScript, scheduled jobs and webhooks.
- The systems your agents work across: Slack, Google Workspace, Notion, and the CRM, recruiting, HR, finance and compliance tools a growing company runs on.
THE ROLE
We build agents for marketers. This seat builds them for us.
Every company our size runs on work nobody sees. Someone copies a new hire's details into six tools. Someone remembers which contract renews next month. Someone answers the same security questionnaire for the fourth time. Most companies hire a coordinator for that work. We're hiring an engineer.
You're a forward-deployed engineer for Minerva itself. Other companies call this an AI operations engineer or an internal AI engineer. Your customers are every team here: operations, finance, people, recruiting, sales and the founders. You sit with them, find the work they'd most like to stop doing, and replace it with a system that runs without them and leaves an audit trail.
You report to our COO and work closely with engineering, which owns anything that touches production.
WHAT YOU'LL DO
- Own the company's knowledge agent. One agent over our docs, Slack, calls and tickets, with Slack as the front end. It answers with sources, and people trust it.
- Automate the processes that run the company. Hiring, onboarding and offboarding, access provisioning, vendor reviews, customer security questionnaires, contract renewals and billing. Start where the hours or the risk are highest.
- Run the skill library. Every team gets Claude connected to the tools it uses and a set of skills, each with a named owner on that team, an eval and the right permissions. What one person figures out, everyone gets.
- Own the source of truth. Decide where each kind of information lives, move it there and keep it findable by people and by agents. When an agent spots something out of date, it proposes the fix and a person approves it.
- Build the plumbing under our operating dashboards: the metrics, controls and board reporting that today get stitched together by hand from five systems.
- Put the guardrails in first. Least-privilege access, a human approval before any agent writes to a system of record, and audit trails that double as compliance evidence.
- Sit with your users. Watch how a recruiter, a seller or our finance lead actually works, then automate the part they hate.
- Measure adoption. Which systems get used, by whom and at what cost, including what we spend on models and which agents can touch what. Retire what nobody opens, and write the runbook for what stays.
WHAT YOU HAVE
- You've shipped agents or automations that coworkers use every week, and you can show the usage: who stopped doing what, and how many hours came back.
- Production Python or TypeScript, with LLMs wired into real APIs. You're comfortable with OAuth scopes, webhooks and scheduled jobs, and with the ways each of them fails.
- You know how a company runs. You can talk to a recruiter, a controller and a security auditor in their own terms, and you fix the process before you automate it.
- A controls instinct. Before you ship, you've decided who approves what and what happens when the agent is wrong.
- You're current. You know what shipped in AI tooling this month, and you can show us your own setup.
- You write clearly. People follow your runbooks without asking you.
- You're in New York City or willing to relocate.
YOU MIGHT BE A FIT IF YOU ARE…
- A founder or founding engineer who automated your own company's back office because someone had to.
- A chief of staff or business operations lead who learned to build and stopped writing specs for engineers.
- A solutions or forward deployed engineer who wants the whole company as your customer.
- A GTM or internal tools engineer who automated a sales team and wants scope beyond the sales stack.
- Or you don't fit any of these neatly, but you've automated your own job at least once. Apply.
NICE TO HAVES
- You've rolled out Claude or another model platform to a whole company: access, permissions, usage and cost.
- You've been through a SOC 2 or similar audit on the side that produces the evidence.
- Hands-on time with the systems a startup runs on: HRIS, ATS, CRM, billing and spend tools.
WHAT THIS ISN'T
- An IT helpdesk. You'll automate the tickets away, not answer them.
- Product engineering. Our customer-facing agents and production infrastructure belong to the engineering team.
- An AI strategy role. You ship systems people use. Nobody here needs a deck about transformation.
- The owner of the work you automate. Our compliance lead still owns the security answers, and whoever runs sales ops owns the CRM. You build the systems that do the work for them.
WHAT SUCCESS LOOKS LIKE
- First 90 days: the knowledge agent is live in Slack and used daily. A new hire gets set up in every tool in under an hour, and the access record writes itself. At least three workflows run without a person in the loop and are still in use four weeks later.
- First 6 months: security questionnaires go out the same day without a founder writing them. Contract renewals, notice windows and price increases surface before they cost us money. Every team has a system it would fight to keep.
- The number you own: hours of manual work retired each month, measured against a baseline you set in your first month.
COMPENSATION
$186,000–$236,000 base salary, depending on experience. Meaningful equity. Medical, dental and vision.
HOW TO APPLY
Skip the cover letter. Show us one thing you built that other people used: a demo, a repo, or a few paragraphs on what the process looked like before, what you built, how many people used it and what broke. Applications without one won't be reviewed.
WHERE WE WORK
We work in person from our office at 300 Kent Avenue in Williamsburg, Brooklyn.
BENEFITS
Every full-time role includes equity; medical, dental and vision coverage; unlimited PTO; a monthly fitness stipend; and an annual company offsite. We'd rather pay people well than buy perks nobody uses.
PAY TRANSPARENCY
The salary range in this posting is our good-faith range for the role in New York City at the time of posting. Where an offer lands depends on the level and experience we see in the interview process.
APPLYING
Apply on this page. We don't take applications by email, and we don't accept unsolicited submissions from recruiting agencies. If you need an accommodation at any point in the process, write to hiring@minerva.io.
WORK AUTHORIZATION
You'll need to be authorized to work in the United States. We consider visa sponsorship case by case, so tell us on the application if you'll need it.
EQUAL OPPORTUNITY
Minerva is an equal opportunity employer. We make hiring decisions without regard to race, color, religion, creed, sex, pregnancy, sexual orientation, gender identity or expression, national origin, citizenship status, age, disability, marital status, veteran status or any other characteristic protected by federal, New York State or New York City law.
RECRUITMENT FRAUD
Our hiring runs through Ashby and @minerva.io email addresses. We will never ask you for money, bank details or other financial information during the process. If a message claiming to be from Minerva looks wrong, forward it to hiring@minerva.io.
Compensation Range: $186K - $236K
Salary Context
This $186K-$236K range is above the median 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 Minerva, 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. Disclosed range: $186K to $236K.
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.
Minerva AI Hiring
Minerva has 1 open AI role right now. They're hiring across AI/ML Engineer. Based in New York, NY, US. Compensation range: $236K - $236K.
Location Context
AI roles in New York pay a median of $222,480 across 3,785 tracked positions. That's 4% 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.