Where the data comes from
Koaches runs a job data service that reads postings directly from company career sites, through their public job boards. It does not scrape LinkedIn.
On 25 October 2026, we collected 6,612 open postings from these job boards and from the public Amazon Jobs search. We kept only engineering and research roles, and removed sales, solutions and recruiting roles. That left 3,074 postings in three groups:
- AI labs (976 postings): OpenAI, Anthropic, xAI, Perplexity, Cohere and Thinking Machines.
- Amazon (1,031 postings): our FAANG sample. Google, Meta and Apple do not publish their postings on these public job boards.
- Other big tech (1,067 postings): Stripe, Cloudflare, DoorDash, Datadog, Coinbase, Reddit, Lyft, Pinterest, Robinhood, Airbnb, Figma, Instacart and Dropbox.
A posting counts for a language when its text names that language. One posting can name many languages.
Python is the base. Rust is the signal.
Languages named in engineering postings
Show as a table
| Language | AI labs | Amazon | Other big tech |
|---|---|---|---|
| Python | 50.9% | 50.6% | 38.7% |
| C++ | 10.8% | 70.1% | 11.0% |
| Java | 4.1% | 67.7% | 19.5% |
| Rust | 18.8% | 13.0% | 8.7% |
| Go | 12.5% | 2.4% | 29.8% |
| TypeScript | 9.6% | 2.9% | 12.0% |
| SQL | 8.1% | 4.7% | 17.7% |
| Ruby | 0.0% | 13.7% | 9.6% |
| CUDA | 2.7% | 1.5% | 0.5% |
- Python is the shared language. Half of lab postings and half of Amazon postings name it.
- Rust is the lab signal. 19% of lab postings name Rust. At other big tech companies, 9% do. At xAI the number is 31%, and at Perplexity it is 44%.
- Java almost disappears. Only 4% of lab postings name Java. At Amazon, 68% do.
- C++ is an Amazon language. 70% of Amazon postings name it. Labs ask for it in 11% of postings, mostly for inference and GPU work.
- Go belongs to infrastructure companies. Datadog names Go in 46% of postings and Cloudflare in 44%.
Many lab postings name no language at all
41% of lab engineering postings name no programming language. At Amazon, 20% name none. A lab posting names 1.2 languages on average. An Amazon posting names 2.2.
When a lab posting names a language, it often gives you a choice:
"Production-quality coding ability in at least one of Python, Go, Rust, or TypeScript."Anthropic engineering posting, October 2026
"Rust or C++ experience is useful but not required."OpenAI engineering posting, October 2026
The labs tell you this directly. They want strong engineers who learn a new stack fast. A keyword match on your resume does not get you the job.
What lab postings ask for instead
Skills named beyond languages
Show as a table
| Skill | AI labs | Amazon | Other big tech |
|---|---|---|---|
| Evaluation | 31.9% | 17.5% | 15.9% |
| LLMs | 29.9% | 21.4% | 17.3% |
| Distributed systems | 29.7% | 43.9% | 31.9% |
| Kubernetes | 15.7% | 1.1% | 17.2% |
| AWS | 10.8% | 54.0% | 16.0% |
| Reinforcement learning | 9.7% | 10.8% | 3.2% |
| PyTorch | 7.9% | 5.8% | 5.8% |
| JAX | 5.6% | 3.4% | 0.6% |
Lab postings name evaluation and large language models about two times as often as big tech postings. They name Kubernetes and JAX more often too. Amazon postings name AWS in 54% of cases, because AWS is Amazon's own cloud.
Most lab work is still normal engineering. 30% of lab postings name distributed systems. A strong backend or infrastructure engineer can do much of this work.
The other half of the posting is about you
Postings do not only list skills. They also tell you what kind of person the company wants. We counted these words too.
Values and behaviors named in engineering postings
Show as a table
| Word group | AI labs | Amazon | Other big tech |
|---|---|---|---|
| Mission | 81.4% | 27.7% | 71.4% |
| Safety | 76.3% | 20.3% | 22.9% |
| Collaboration | 78.6% | 67.7% | 81.6% |
| Communication | 69.6% | 44.7% | 63.2% |
| Ownership | 60.1% | 54.0% | 60.0% |
| Ambiguity | 39.4% | 25.2% | 27.9% |
| Curiosity and learning | 16.9% | 35.4% | 27.2% |
| Fast pace | 18.3% | 19.3% | 28.6% |
81% of lab postings talk about the mission. 76% talk about safety. At Amazon, the numbers are 28% and 20%.
Some of this text is the company's standard paragraph. That is the point. The lab puts its mission in front of every candidate, and the interview checks it.
Amazon is different in one way. Its postings ask for curiosity and learning more often (35%). This agrees with its Leadership Principle "Learn and Be Curious".
The interview tests it
Each of these companies runs a behavioral part of the interview. The difference is what they measure you against.
What each company says about its interviews
- Resume review
- Recruiter or hiring manager call
- Skills assessment
- Final loop4-6 hours with 4-6 people. Looks for collaboration, communication, openness to feedback and "alignment with our mission and values"
- Application
- Live codingColab or CodeSignal
- Experience and motivationFirst value: "Put the mission first"
- ScreensVary by role
- Loop with 2 to 7 AmazoniansQuestions on 16 Leadership Principles, answered with STAR, with a Bar Raiser
- ScreensVary by role
- Onsite loopThe same questions and scale for every candidate. Looks for "emergent leadership"
Big tech tests behavior against a written list. At Amazon, that list is the 16 Leadership Principles. You can prepare one story for each principle.
Labs test behavior against a mission. That is harder to prepare. You must connect your own work to their mission in your own words. A memorized answer does not do this.
Anthropic's candidate AI policy makes one more point clear. In a live interview, "this is all you". But the same policy encourages candidates to use AI to prepare. The practice happens before the interview.
Case study: a traditional engineer reads an OpenAI posting
Most engineers who apply to a lab do not come from a lab. So we took a traditional software engineering resume and a real lab posting, and read them the way a Koaches job analysis does.
- The resume: a senior software engineer with seven years of checkout and commerce APIs, in Python, TypeScript and PostgreSQL. This is John Doe, the fictional sample profile in Koaches.
- The job: OpenAI, Software Engineer, Monetization Product & Platform, San Francisco. The posting names no programming language.
The job analysis
Software Engineer, Monetization Product & Platform
- Safety, privacy and user trustStrong17 mentions
Uphold the highest levels of safety, privacy, fairness, and policy compliance across all monetization systems
- Distributed systems at scaleStrong11 mentions
Architect distributed systems and services that operate at massive scale with strong reliability
- Builds new systems from nothingStrong7 mentions
Thrive in 0→1 environments where systems, architecture, and user experiences must be defined from scratch
- Works closely with Product, Design and ResearchMeaningful7 mentions
Work closely with Product, Research, and Design to translate product requirements into high-quality technical solutions
- Partner APIs and integrationsMeaningful5 mentions
Develop advertiser-facing APIs and tools that enable the creation, management, and measurement of ads
- Technical strategy and roadmapMeaningful5 mentions
Contribute to technical strategy, propose new directions, and help shape the roadmap
Matched
- Product, Design, Research: "Aligned product and operations on a gated March launch."
- Partner APIs: "Built API integrations and improved incident runbooks."
Partial
- Distributed systems: the checkout migration cut failures from 2% to 0.6%. Add traffic numbers to show scale.
- Safety and trust: idempotency keys cut duplicate orders from 40 to 2 a week. No line on privacy yet.
Gaps you can close
- New systems: the resume shows migrations and fixes, not a system built from nothing.
- Roadmap: the resume shows delivery, not strategy.
- Build a story about a time you protected users or their data while you shipped. Put trust first, then speed.
- Build a story about a system you started with no spec: what you decided, and what happened.
- Prepare "Why OpenAI, and why ads?" Say how ads can keep user trust. This is the mission question.
- Add scale numbers to the checkout bullet: orders per day and requests per second.
This engineer does not need a new language. The posting does not ask for one. The engineer needs two new stories and one strong answer to the mission question.
The rounds tell the same story:
Predicted rounds for this job
- Round 1Recruiter callWhy OpenAI, why monetization, and your timeline.
- Round 2Technical screenPractical coding in the language you choose.
- Round 3System designAn ads or billing system that keeps user data private.
- Round 4Project deep diveYour checkout migration: the decisions, the trade-offs and the result.
- Round 5Hiring manager and valuesCollaboration, feedback, ambiguity and the mission.
Three of the five rounds test behavior or mission. Your code gets you to the final loop. Your stories get you the offer.
How to prepare with Koaches
Koaches prepares you for the rounds that test you as a person: the recruiter call, the behavioral rounds, the project deep dive and the hiring manager. It does not cover coding or system design.
From posting to practice
- Add your resume
Upload a PDF or Word file. Koaches reads it into sections you can edit.
- Paste the job
Read who the company wants, how you fit, and what to do. Every trait shows its quote from the posting.
- Open the prep plan
Get a plan for each round: likely questions, the stories to use, and the stories to build.
- Write a starting answer
Generate an answer from your own resume and stories. Fill the blanks with your own facts.
- Practise out loud
Answer by voice or by typing. Get scores on five dimensions, what worked, what to fix, and a stronger version of your answer.
- Update after each round
Upload your notes or transcript after a real round. The next round's prep changes to match.
The labs hire engineers who can explain why.
Practise that answer before the interview. New accounts get $5 of free credits.
Method and limits
- We collected the postings on 25 October 2026 from each company's public Greenhouse or Ashby job board, and from the Amazon Jobs search (US, five engineering search terms).
- We kept postings whose title names an engineer, developer, researcher, scientist or member of technical staff. We removed sales, solutions, customer and recruiting titles.
- We counted a language when the posting text names it. For Go, we counted "Golang", and "Go" only in a list of languages.
- Mistral and Character.AI moved their job boards, so their postings are not in this data. Google DeepMind, Google, Meta and Apple do not publish on these job boards.
- OpenAI and Anthropic have more open roles than the smaller labs, so they have more weight in the lab numbers.
Sources
- OpenAI, Interview guide: openai.com/interview-guide
- Anthropic, Careers: anthropic.com/careers
- Anthropic, Guidance on candidates' AI usage: anthropic.com/candidate-ai-guidance
- Amazon, What it is like to interview at Amazon: aboutamazon.com
- Amazon, Leadership Principles: amazon.jobs
- Google re:Work, Structured interviewing: rework.withgoogle.com
koaches