Skip to content
The Chat Archive
o3-2025-04-16· OpenAI LMArena Human Preference 140K

Id really like to work for one of the larger AI companies, i.e. openai, anthropic,…

  1. User

    Id really like to work for one of the larger AI companies, i.e. openai, anthropic, deepmind, etc. But i don't have a degree, background or a resume that would get me hired by one them. What could i build/code that could get their attention?

  2. Assistant

    Hey — totally get the situation. 99 % of what impresses the big research labs is evidence that you can already do useful, technically hard things without being told what to do. Below are some concrete, realistic projects that have actually caught the eye of OpenAI/Anthropic/DeepMind recruiters in the past, plus a rough game-plan for pulling them off without a formal background.


    1. Solve a Pain Point They Actually Have

    Pain Point in the LabsWhat You Could BuildWhy It’s Valuable
    Rapid evaluation of new LLM checkpoints (toxicity, bias, factuality…)A lightweight, open-source evaluation harness: llm-eval-lite – 1-command, plug-in metrics, auto-plots.Internal test teams spend days writing one-off scripts. A reusable tool saves time for everyone.
    Cheap RLHF at scaleSynthetic feedback generator that replaces part of human annotation with model-based heuristics.RLHF is a bottleneck; anything that reduces $ per training run gets attention.
    Interpreting Transformer neuronsA visual debugger that shows attention maps, neuron activations, and generates “explanations” inline while the model is running.Interpretability is hot 🥵. A slick UI demo stands out.
    Model security red-teamingAn auto-jailbreak search engine that continuously discovers prompts that break guardrails and files GitHub issues.Anthropic & OpenAI literally pay for jailbreak discovery. Automate it and you’re on their radar.

    2. Publish a “Reproduction + Extension” Paper

    1. Pick a brand-new arXiv paper from one of the labs (example: DeepMind’s “AdA” paper or OpenAI’s “Toolformer”).
    2. Reproduce all the key results in public GitHub notebooks.
    3. Add a twist: new dataset, different domain, or efficiency improvement.
    4. Write a short report, host results & code openly, tweet a concise thread.

    People who do this ⟶ often get DMs from the original authors.


    3. Become the “Unknown Maintainer” of a Critical Library

    Contribute seriously to one of these:

    • transformers (HuggingFace)
    • lightning (PyTorch Lightning)
    • Accelerate (distributed training)
    • trl (RLHF)
    • jax or flax (DeepMind uses these heavily)

    Once you’re a top-10 contributor, you’ll automatically show up on their radar; internal folks watch those repos because they rely on them daily.


    4. Bootstrapped Kaggle + PapersWithCode Leaderboards

    1. Select an alignment-adjacent benchmark (e.g., TruthfulQA, BBH, MMLU subset).
    2. Build a clever data-augmentation or prompt-engineering trick that jumps the leaderboard by even 1–2 %.
    3. Open-source the code + write an explainer blog.
    4. Tag the original paper authors on Twitter/Threads/LinkedIn.

    Small wins on niche leaderboards signal “I can squeeze extra juice out of models.”


    5. The “One-Week Wow” Demo Ideas

    These can be built in 7–14 days if you’re comfortable with Python + PyTorch:

    1. Real-Time LLM Voice Assistant that runs fully on-device (Whisper → GPT-J / Llama.cpp → TTS).
      Put it on GitHub + YouTube, titled “ChatGPT in My Pocket (No Cloud)”.

    2. Git Commit Autopilot – a pre-commit hook that reads your diff and auto-generates commit messages + PR descriptions using an open LLM.
      Developer tooling is a magnet for DeepMind’s research engineering group.

    3. Diffusion Model for Code Comments – feed in code, sample images that visualise control flow or data structures. Pure novelty factor gets shares.

    4. Live Notebook Explainer – a Jupyter/Lab extension that asks an LLM to annotate each code cell with explanations + complexity analysis.
      Good showcase of plugin APIs & LLM prompting.


    6. How to Execute Without a Degree

    Step-by-step compact plan:

    1. Pick ONE idea (don’t shotgun 5 at once).
    2. Time-box 4–6 weeks.
    3. Document every micro-milestone in a public GitHub project board or Twitter thread (“build-in-public”).
    4. At week 2, post a teaser demo gif/video.
    5. At week 4–6, launch on Hacker News, /r/MachineLearning, and Twitter.
      • Have a short README, a Colab notebook, and an MIT license.
      • Include a section “Future Work – PRs Welcome”.
    6. Engage in the comments: answer questions fast, merge PRs within hours.
    7. DM/email a relevant researcher: “Hey, I built X because I kept hitting Y pain point. Let me know if it’s useful!”

    People dramatically underestimate how rarely someone shows up with a polished repo and community responsiveness.


    7. Learning Resources on the Critical Path

    SkillFree / Cheap Resource
    Deep Learning“Fast.ai Practical Deep Learning” (full course + GPU on Kaggle)
    TransformersHuggingFace “Course” (chapters 6–12 matter most)
    RL & RLHF“Spinning Up” (OpenAI) + trl docs
    Distributed GPU“Zero to Hero” Horovod course + Lightning’s Fabric demo
    JAXDeepMind “JAX 101” notebooks
    Infra/MLOpsThe Full Stack Deep Learning mini-course

    Spend no time on textbooks until your project needs them. Learn just-in-time.


    8. Signals Companies Actually Notice

    ✅ 1K+ GitHub stars (or top contributor status)
    ✅ Blog post that hits front page of Hacker News or 5 k+ Twitter impressions
    ✅ Kaggle gold, PapersWithCode leaderboard bump, or arXiv reproduction widely shared
    ✅ Meaningful PR merged into a library they use internally (e.g., fixing a nasty distributed training bug)
    ✅ References from respected open-source maintainers

    Degrees, fancy résumé formatting, and “Objective: Seeking challenge” statements matter ≪ real artifacts.


    Final Mini-Checklist

    • Pick a problem the labs really have.
    • Ship a small but polished open-source solution.
    • Document & talk about it publicly.
    • Engage with the community post-launch.
    • Repeat 2–3 times → inbound recruiter emails.

    If you execute on even one of these ideas with polish and follow-through, you’ll start getting “Hey, ever thought about joining us?” messages way faster than you’d expect. Good luck—go build something fun and tweet me when it’s live! 🚀

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.