$275k Aviator AI Roles Screened in Under Five Minutes

Three Roles, One Hiring Bet

Three new AI positions appeared on Aviator's job board within the last two weeks, and together they sketched the team's shape for the quarter: engineers who wrap large language models into software people pay for. Two sat in San Francisco, one was remote-friendly, and comp clustered in the upper six figures. Aviator had not previously carried this density of AI-specific titles on its careers page, and the descriptions leaned on "production experience" and "shipped to real users", language that signaled an interview loop closer to a backend interview than a Kaggle-style evaluation. The full breakdown:

Read as a program, the three postings split along execution layers. The applied LLM seat sat closest to model behavior: prompt design, evaluation pipelines, integrating third-party foundation models, shipping chat and retrieval features to end users. The platform role kept inference fast, observability honest, and model swaps from one provider to another from eating a quarter of engineering time. The generative AI product engineer sat between the two, building the APIs and front-ends that turned model output into something a paying customer clicked.

That shape matched where AI hiring was heading. Companies stopped posting pure "research scientist" roles the way they did in 2023; the listings that drew applicants almost always paired model work with shipping discipline. A candidate who could fine-tune a model but had never paginated through a Postgres slow-query log was a harder sell than one who could do both. Recruiters often listed a single req that turned into three offers, so it was too early to say how many hires the three postings represented, but the intent was plain. Aviator wanted builders, not bench researchers.

What the Screen Looked For

The first cut happened fast. Recruiters screening résumés for these roles said it ran on a tight checklist and often took only a few minutes per file.

The foundation. Every CV that survived the initial pass showed working Python. PyTorch, the OpenAI SDK, Hugging Face, and LangChain all shipped Python-first, so a candidate who listed only Java or Go was filtered before a human read the file. SQL sat next to Python on the list; fluency with SELECT, WHERE, and JOINs across at least three tables mattered because the data an AI system trained on or retrieved from lived in relational stores, and interviewers probed for it in the first technical round. API architecture rounded out the baseline: a candidate who couldn't describe request/response flows, authentication, and rate limits didn't make it past the recruiter call.

The CAM layer. Once the foundation held, the screen checked for what one widely circulated AI-engineering framework called CAM: Context engineering, AI APIs, and Models. Context engineering had become near-mandatory, the ability to shape what a model saw before it generated, including system prompts, retrieved documents, and tool definitions. Résumés that mentioned only "prompt engineering" read as outdated; the current phrasing was context engineering, RAG pipelines, and retrieval design. On the API side, candidates needed hands-on experience calling OpenAI or Anthropic endpoints, handling structured outputs, and managing token costs. The "M" (running your own models) pointed to Hugging Face, where candidates were expected to have loaded a checkpoint, swapped in an adapter, or quantized a model rather than only consuming hosted APIs.

The four-skill production layer. Above CAM, the screen tested for what separated a notebook demo from a deployed system: RAG, agents, deployment, and evaluation/governance. RAG was table stakes because most companies held private data ChatGPT had never seen; a candidate who had built a retrieval pipeline (embedding, vector store, reranker) got a closer look. Agents and the Model Context Protocol (MCP), which let agents reach into external apps, were where the screen was moving fastest. "This is where the entire AI industry is sprinting right now," a video roadmap observed, and résumés that ignored agents already read as a year behind.

Deployment was where most candidates failed. Docker, AWS, and GCP together determined whether someone could take a model out of a notebook and put it behind a real endpoint. "Learning Docker, AWS, and GCP will increase your chances by so much, because so few people actually spend the time to learn it well," the same video noted. Evaluation and governance closed the loop: frameworks like DeepEval for hallucination and consistency testing, plus model routing to balance cost against quality as bills climbed at scale.

Proof over claims. The screen weighed tangible evidence (public projects, certifications, and visible work) heavier than buzzwords. Hiring managers had moved past "basic prompt engineering" and tutorial-grade repos; what registered was a deployed RAG service on AWS, a Hugging Face model with real downloads, or a credential on a LinkedIn profile that signaled depth rather than enthusiasm.

What Aviator's screen tested for, at a glance

The combined effect was a screen that punished generalists and rewarded engineers who could move a model from a Jupyter cell to a billed, monitored endpoint, and who could prove it.

The Market Underneath the Three Postings

Aviator's three AI postings sat on top of a tech labor market that was, by most measures, no longer loosening; it was re-tightening around a smaller pool of qualified candidates. Median Canadian tech salaries rose 3.5% year-over-year through 2025, almost exactly matching allocated budgets and leaving little room for the off-cycle bumps that defined 2021–2023. Year-over-year tech turnover fell from a peak of 13% to 8% as workers stayed put; for recruiters trying to lure a candidate out of a stable seat, that inertia was the binding constraint.

The pressure showed up most clearly in roles that looked like Aviator's. Data Scientist was the second-fastest-growing "hot job" in the same Canadian survey, with pay up 7.1% YoY. Machine learning and applied-AI postings across U.S. tech employers were tracking the same direction. Stripe's live board, for instance, listed a Machine Learning Engineer role in South San Francisco at $212,000–$318,000, and ASML's board added 64 roles in seven days with a median near $154,000.

The competition was also pulling in from adjacent industries. Deloitte's engineering and construction outlook for late 2025 documented construction wages rising 4.2% year-over-year as the sector lost engineering talent to tech firms chasing AI-adjacent skills, a directional mirror of what was happening inside software. Even finance, rarely framed as AI-talent-competitive, braced for "compensation costs and high technology spending" to pressure efficiency ratios, per Deloitte's October 2025 banking outlook. When banks started budgeting for tech-comp inflation, the signal to a startup recruiter was clear: cash alone would not close a candidate.

"Organizations that succeeded were those that thoughtfully combined competitive compensation with meaningful benefits and flexible work arrangements." — Canadian tech compensation survey, September 2025

That pressure was reshaping how openings were advertised, not just how they were paid for. Nearly half of surveyed Canadian tech firms were now either publishing standardized pay ranges externally or actively exploring it, a transparency shift that compressed the negotiating room candidates used to enjoy. Add the fact that AI layoffs dominated headlines while fewer than 1% of cuts were actually tied to productivity gains, per Gartner's January 2026 analysis, and the picture for a job seeker sharpened: the perceived threat of displacement was loud, but the underlying competition for hybrid AI-plus-software talent was quieter and more structural.

How Applicants Adapted

Candidates chasing Aviator's three open AI roles read the postings like a contract, not an ad. Because the positions blended model development with production-grade software work, applicants rewrote their résumés to lead with shipped systems rather than research credentials. A deployed service or a monitored pipeline went at the top of the page, with model work moved into supporting bullet points.

That shift showed up in how people described themselves on LinkedIn and in cover letters. "Built and shipped" and "owned in production" appeared where "researched" and "explored" used to sit. Candidates dropped hobbies and conference talks from the first screen of a CV and replaced them with stack-specific lines (inference latency work, eval harness maintenance, on-call rotation) because those were the terms Aviator's screen was hunting for.

The advice circulating in candidate Slack groups and on r/MachineLearning was concrete and a little unforgiving, much of it from people who had already been through a hybrid AI/infra screen this quarter:

• Treated the take-home like a production task, not a notebook exercise. Used a real repo structure, wrote a README, and included one test. Reviewers filtered on engineering hygiene as much as on the model itself.
• Were ready to defend every modeling choice against a cheaper baseline. The interview loop probed whether you would reach for a 70B-parameter model when a logistic regression would do.
• Knew their serving stack cold. vLLM, Triton, TensorRT-LLM, and the trade-offs between them showed up in technical screens at multiple companies.
• Quantified latency and cost. Candidates coached each other to memorize two or three numbers from past projects (p99 latency, dollars per million tokens, throughput at a fixed replica count) because the questions were predictable.
• Practiced system design for AI products. This was where candidates without prior infra exposure lost out, and where senior software engineers without deep modeling backgrounds picked up points.

Candidates also widened their search. With Aviator's three postings sitting in a market where Stripe and ASML were adding roles on similar comp, applicants ran parallel processes rather than waiting on one screen. The calculus was straightforward: a hybrid AI/software profile opened doors at multiple shops, and recruiters actively pulled from the same applicant pool.

Résumé tailoring moved from a nice-to-have to the cost of entry. Generic ML résumés got filtered before a human saw them, and applicants responded by maintaining two versions (one tuned for research-heavy labs, one tuned for product companies like Aviator) and switching between them depending on the posting. Several candidates in online threads reported spending two to three hours per application rewording bullets to mirror the language in the job description, then backspacing anything that did not map directly to a stated requirement.

The deeper shift was psychological. People who trained as ML researchers were now describing themselves as software engineers who happened to work on models, an inversion that the applicant pool had learned to perform because the screen rewarded it. Aviator's first cut, the labor data behind it, and the résumé rewrites in front of it were all reading from the same script: the AI hire of this quarter was a builder, not a bench researcher, and the market was making that clearer with every req that went live.

Working in frontier tech? Zero G Talent tracks the openings: see every open ASML role, browse frontier tech jobs, openings at Stripe, and the people building the field.