It's a strange time to be learning to code.
Workflows have shifted. Some handwrite to build fundamentals, some pair with AI to get unstuck, some orchestrate agents.
But the quality of what you produce still matters.
So we rebuilt our AI code review to measure exactly that ๐งต
How to make your engineering job application stand out (from the perspective of someone looking at hundreds of resumes):
1. Your resume should be one page. If you really need more space, link to a website. You don't need 10+ bullets for each job.
2. You will immediately stand out >90% of applications if you link a personal website that has some intentionality behind it.
3. If you are going to link your X, you might want to clean up your posts? Seems obvious but... people post some wild stuff.
4. You should link your GitHub. Please avoid doing a profile README that looks like a MySpace profile with the badges and images. I'm trying to look at code and your ability to build interesting ideas.
5. You should try to customize your application to the company. If you're applying to a startup, the courses you took in college probably don't matter as much. Maybe more if you're trying to make it through the ATS screening for FAANG.
6. I'm seeing a surprising number of resumes which don't talk about AI or agents at all. Software engineering is changing and it's a pretty fair assumption that you will be expected to learn or understand coding with AI for your job. That should be reflected on your resume and projects (and I'm not just saying this because I'm at Cursor).
7. Take your LinkedIn seriously. Most devs are here hanging out on X but surprisingly still most people will send around your LinkedIn internally.
8. Find ways to show your unique strengths/tastes/interests. It's nice to see people are smart, well-rounded, and thoughtful. Maybe this is a collection of books you enjoyed and why. Or some writing you've done. Or films you liked. At the end of the day, people want to work with other people they like and respect. If nothing else, it will be a good conversation starter ("oh I love [book] as well!").
9. Do not use AI to write your cover letter or resume text. It's incredibly obvious, especially if you are applying to an AI company. You can still use it to ideate on ideas or phrases, but write it by hand (don't fall victim to the overused in-the-distribution-AI-phrases). See: /humanizer skill.
10. No photos on resumes. Save those for whatever you link out to.
11. Quality over quantity. 3 really good, thoughtful, detailed, interesting projects versus a wall of 27 AI-slop ones.
Remember that hiring managers / recruiters are getting hundreds or thousands of applications for a role. They're not going to spend 20 minutes on every single application. You need to cut the cruft and get to the point. I hope this helps you stand out!
We've just launched a new PREMIUM challenge! ๐
Build a multi-page site for a tech conference. Browse the speakers, filter the schedule by day and track, and save talks.
Optional bonus: pull the content from a CMS.
More details ๐
๐ This is a premium challenge for Pro members
Our premium challenges are the highest-quality projects that make standout portfolio pieces.
https://t.co/rXyU8K3rVH
We're launching a new premium challenge tomorrow, so here's a quick preview!
Build a multi-page site for a fictional tech conference. Browse the speakers, filter the schedule by day and track, and save talks.
Optional bonus: pull the content from a CMS โจ
Boris Cherny, the creator of Claude Code, recently said "coding is solved" at Sequoia AI Ascent 2026.
He hasn't written code by hand in 2026 and ships dozens of pull requests a day from his phone.
We wrote up what this all means for learners ๐งต
The bar for portfolios has shifted. A couple of years ago, two or three intermediate-level projects could get you noticed.
Now it's closer to: full-stack projects, ideally hosted, ideally with some users (even if those users are you and a couple of friends).