Skip to content
aitrainer.work - AI Training Jobs Platform
Engineering Full-Time
Rox

Applied AI Engineer (US)

Rox • San Francisco

Company

Rox

Annual salary

$200k – $275k/yr

Location

San Francisco

Listed

32d ago

Experience:
1 to 6 years
Workplace:
5 days in-office in San Francisco, CA (no relocation support)
Equity:
Highly competitive equity

On-site in San Francisco.

Send us your LinkedIn and CV. If your experience fits, we'll introduce you to the recruiter filling this role.

Apply for a referral →

The recruiter emails you before anything happens and may suggest other jobs that suit you better.

About this role

At Rox, we believe in empowering people to do their best work.

Our platform supercharges sellers with autonomous revenue agents to do the manual work so they can focus on what they do best: selling. Just as coding agents 10x’d engineering, revenue agents 10x customer work.

We are reimagining the revenue stack by building the world’s first revenue operating system, from the application layer to the system of context. With Rox, humans are evolving to orchestrators while agents manage the end-to-end customer lifecycle.

Rox powers Global 2000 leaders in banking, hardware, construction, and sovereign AI, while serving dominant AI winners like Ramp and Cognition.

Underlying all of this success is an unwavering, shared belief in the mission, with an unreasonable commitment of doing whatever it takes to make it a reality.

What you'll do

  • Design and run research programs tied directly to the four above.
  • Build evaluation frameworks that measure trajectory quality, not just final output, because most eval infrastructure measures end results and we care about the path.
  • Work on agent memory, retrieval, and context systems alongside elite and competitive engineering minds.
  • Translate findings into infrastructure with measurable production impact. Help define where Rox Research goes next.

Why This Role Exists

Foundation models are commoditizing. Defensibility comes from specialized models, proprietary training signals, and evaluation ownership. Every applied AI company we benchmark against like Decagon, Harvey, Sierra, Cursor has already moved. The window to claim frontier applied AI for revenue is closing in the next few months.

Rox is in market. We run agents against enterprise data at scale, every day. We see exactly where research meets production and where the data is dirty, state is changing, and being wrong costs (a lot of) money. The Applied Research team exists to close that gap permanently.

Four problems we care about right now:

  • Cost-efficient inference for Clever Columns. Distill a Rox-trained model from frontier teachers so per-account enrichment runs at 1/20th the cost without quality loss. Ships first. Doesn’t require trajectory attribution.

  • Signal classification across the public knowledge graph. A small, fast classifier that distinguishes genuine buying signals from noise across the news, jobs, and filings corpus we already ingest at scale. Powers Recommended Next Moves and Auto Prospecting. Cleanest data subset.

  • Personalization grounding and hallucination detection. A reward model that catches fabricated prospect context in Sequences in real time. This is the most underrated production failure mode in outbound AI. Trained on cross-customer consensus edits.

  • Sequencing policy under sparse, delayed rewards. Offline-to-online RL on multi-touch trajectories with intermediate signals as proxies for terminal outcomes. Long-horizon flagship. Hard.

These are not benchmark problems. They have real SLAs and real customers depending on them.

Why Join Now

We are at an unusual moment. Large enough to have real scale, real customers, and interesting research problems. Small enough that you are one of a handful of people shaping what the Applied Research function looks like and what it prioritizes.

The team is extraordinary: IMO, IOI, and ICPC medalists, researchers from DeepMind and OpenAI. The feedback loop is a live enterprise system, not a leaderboard. If that’s not more interesting to you than publishing for the sake of publishing, this probably isn’t the right fit. San Francisco, onsite. We relocate exceptional people.

What Success Looks Like

  • First few weeks: you understand Rox’s architecture, where the production problems are, and where the research gaps are. You have opinions and you share them.

  • First few months: you are running experiments that directly inform how we build. Something you worked on is in production.

  • Over time: you are defining the research agenda for the most interesting applied AI problem in the enterprise. The systems you build are things no one else has built before, because no one else has the structural data position to build them.

Common questions

How do I apply for the Applied AI Engineer (US) role at Rox? +

Use the Apply for a referral button on this page to send us your LinkedIn and CV. If your experience fits, we'll introduce you to the recruiter filling this role. They'll email you to check you're interested, then put you forward for this job or others that suit you better. It's free.

What does this Rox role pay? +

The listing gives $200k – $275k/yr.

Is this role remote? +

The listing gives the location as San Francisco. 5 days in-office in San Francisco, CA (no relocation support).

AI Engineer interview prep

Questions AI Engineer interviewers often ask. They aren't taken from this listing.

How do you decide which evaluation metric to optimize for a classification model when the classes are imbalanced?

Accuracy is misleading on imbalanced data because a model can score well by always predicting the majority class. I look at precision, recall, and F1 for the minority class specifically, and pick the metric that matches the real cost of false positives versus false negatives in the deployment context, since those costs are rarely symmetric in practice.

What is your process for debugging a deep learning model that trains fine but performs poorly at inference time?

I start by checking for a train/inference mismatch: different preprocessing, batch normalization behaving differently in eval mode, or data leakage during training that inflated validation scores. Comparing the exact input pipeline used at training time against the one used at inference usually surfaces the discrepancy before I need to touch the model architecture itself.

How do you approach feature selection when working with high-dimensional tabular data?

I start with correlation and mutual information analysis to drop obviously redundant features, then use a tree-based model's feature importance as a first pass filter. From there, recursive feature elimination with cross-validation tells me where the marginal value of additional features drops off, which keeps the final feature set both smaller and more robust to overfitting.

Explain how you would detect and address data drift in a production machine learning pipeline.

I monitor the statistical distribution of input features and model outputs over time, using something like population stability index or KL divergence against a reference window. When drift crosses a threshold, I retrain on recent data rather than the full historical set, and I keep an alert in place so drift is caught before it shows up as a quality regression.

See all 10 AI Engineer interview questions →

Related roles

Rox

Browse all referral roles

Salaried roles at startups, AI companies and established businesses, all filled by referral. One application covers every role.

See all referral roles →