Key Takeaways
- Apply directly at nousresearch.com/careers — no third-party ATS, no recruiter intermediary
- The free-text 'why' field matters more than the resume; reference specific Nous work
- Open-source artifacts (GitHub, HuggingFace, papers) outweigh job titles at any company
- Expect 45-60 minute technical deep-dives with a founder or senior researcher early in the process
- Nous optimizes for open-source researchers, not hired-gun engineers — alignment on philosophy matters
- Interviews are short (3-5 rounds total) and turn around quickly — 2-4 weeks end to end is typical
- If you're more motivated by compensation than by shipping public research artifacts, larger labs will likely be a better fit
About Nous Research
Application Process
-
1
Review the open roles at nousresearch.com/careers
Nous posts a small, curated set of roles — typically fewer than ten at any given time — directly on their WordPress careers page. Each role links to a dedicated page with a description and an application form. There is no large ATS (no Greenhouse, no Lever). If you don't see an exact match, there is no general 'apply to pool' form — the expectation is you apply to a specific role.
-
2
Prepare a concrete artifact portfolio before you apply
For ML engineer and research scientist roles, the Nous team cares more about code and models you've shipped than your resume. Collect GitHub links, arXiv papers, HuggingFace model cards, training runs, and open-source PRs into a single public URL (personal site, gist, or GitHub README). The most successful applicants have at least one publicly verifiable contribution to foundation model training, distributed systems, RL, or evaluation — ideally tied to a system running at meaningful scale.
-
3
Submit the application on the role page
Open the role's dedicated page at nousresearch.com/{role-slug}/ and complete the application form. It typically asks for your name, contact, resume, and a free-text field for why you want to work on this specific problem. Use the free-text field — that's where most applicants get filtered in or out. Be specific about the Nous work you've followed (e.g., Hermes 4, DisTrO, Psyche) and what you'd want to build.
-
4
Expect a technical conversation with a founder or senior researcher
Because the team is small, first-round interviews are typically conducted by one of the founders or a senior researcher on the relevant sub-team. Expect a focused 45-60 minute conversation about a project on your resume — they will drill into the details. This is not a generic 'behavioral' round; they want to see that you actually built what you claim and understand the failure modes.
-
5
Work sample or paired session
Technical rounds often involve reviewing a real piece of Nous infrastructure or a small open-ended problem — e.g., debugging a training run, sketching a data pipeline, or proposing an evaluation. For research roles, expect a discussion of a paper you've read recently in depth. There is less emphasis on timed LeetCode-style interviews than at larger labs.
-
6
Founder conversation and offer
The final step is typically a conversation with a founder about fit, thesis, and long-term direction. Nous is open-source-first and research-dense, so alignment on that philosophy matters. Offers follow within a week or two of the final round.
Resume Tips for Nous Research
Lead with open-source contributions, not job titles
A GitHub handle with a long training-systems commit history beats a big-tech title on the first page. List your most-starred repos, papers, and model releases near the top. If you have a HuggingFace profile with published weights or evals, link it prominently.
Name specific systems you've worked at scale
Generic 'trained large models' is too vague. State the model size, token count, GPU count, parallelism scheme (FSDP, DeepSpeed, Megatron, custom), and throughput numbers. For RL, state the training algorithm, environment, and reward model details. Concrete numbers signal credibility.
Show evidence of debugging training runs, not just launching them
MLE roles at Nous heavily favor candidates who've recovered runs from divergence, diagnosed loss spikes, profiled throughput bottlenecks, or chased down dataset contamination. Bullet these experiences specifically.
Cite Nous work you've used or followed in your cover note
The free-text application field is where you make yourself memorable. Reference specific Nous papers or models you've read or used — Hermes 4, DisTrO, YaRN, or one of their evaluation datasets. Say what you'd build next.
For Research Scientist: include a citation list
Published or pre-print research with citations matters more than years of experience. Include a short list of your most-cited papers with venue and year. If you've written widely-read technical blog posts that drove community adoption of a technique, include those too — Nous values public-facing research output.
Keep it to one page
The team is small and reads applications closely. Dense one-page resumes with linked evidence outperform multi-page resumes full of bullet points. If you need more space, put it on a personal site and link it.
ATS System: Custom WordPress careers page
Nous does not use a conventional ATS like Greenhouse, Lever, or Workday. Their careers page is a custom-built section of nousresearch.com (WordPress/Elementor), with each role having its own page and application form. There is no public API for their applicant tracking, no branded 'apply with LinkedIn' button, and no automated keyword screening. Your application is read by humans — usually the hiring manager for that role — within days of submission.
- No ATS keyword stuffing needed — a human reads every application
- Apply to the specific role page, not a general inbox
- The free-text 'why' field is the most-read part of the application
- Include direct links to artifacts (GitHub, papers, models) — don't expect recruiters to search for you
- Response times are faster than at large labs — typically 1-2 weeks, not 4-8
Interview Culture
Nous interviews are technically deep and culture-forward.
What Nous Research Looks For
- Demonstrated ability to train large models — stated with specific parameters, token counts, and hardware
- Public artifacts: GitHub commits, papers, model releases, or technical blog posts with real-world traction
- Fluency in the open-source AI research community — you read the papers, you have opinions
- Experience with distributed systems, especially anything involving GPU clusters or parallel training
- A research mindset — willing to run experiments that might fail and report results honestly
- Strong writing: your application, your code comments, your model cards — Nous ships documents as much as code
- Autonomy — the team is small and ownership is high; candidates who need heavy management are a poor fit
Frequently Asked Questions
Does Nous Research hire remotely?
Do I need a PhD to work at Nous Research?
What programming languages and frameworks should I know?
How long does the Nous Research interview process take?
What's it like to work at Nous Research?
Does Nous sponsor work visas?
What should I include in the free-text 'why' field on the application?
What's the compensation like?
Open Positions
Nous Research currently has 7 open positions.
Related Resources
Similar Companies
Related Articles
- LLM Engineer Resume: Prompt Engineering, Fine-Tuning, and Generative AI Systems
- Android Developer Resume: Kotlin, Jetpack Compose, and Play Store Success
- Technical Architect Resume: System Design, Enterprise Architecture, and Technology Strategy
- Software Engineer Resume: Complete Guide with Examples
- 200+ ATS Keywords for Legal Resumes (2026)