There are a lot of resume advice out there. A lot of different opinions of how Resume should be structure whether you are still a student, early ca...
For further actions, you may consider blocking this person and/or reporting abuse
I have done a bunch of hiring in a post-AI world. Some advice about making sure you have relevant keywords in your resume is geared towards dealing with the employer using AI filtering tools and is useful. But I want to go another direction.
90% of applicants use AI to make their resume and write their cover letter and submit their application and only slightly tweak the text here and there. The job posting is the sole prompt every single applicant is using to apply for the position so all of these people's applicants are oddly similar. Especially when you remember that the hiring manager is reading several dozen of these back to back to back.
Even now you are STILL aggressively underestimating how identical most of the job applications are. And after being primed by reading an 80% identical cover letter for the 20th time today, they look at your very similar resume and kinda glaze over it.
I don't hate AI. I am just saying that in a situation like applying for jobs, use it to give you feedback on a resume you hand built from a traditional template or recommended format. Because every single one of those stands out immediately like a breath of fresh air. Never gonna turn your 3 years of experience into 5... but might turn 4 into 5.
Interesting. I have seen a lot of Resumes that are fully generated with AI.
Can you provide me an example?
Traditional route is to google "word resume templates" or "google doc resume templates" and find one you like. Build it up from there following "how to write a resume" guides. Modern final step is to ask AI for feedback and make the changes it suggests that you like, but avoid copy-pasting blocks of suggested changes in there directly.
I see. Makes sense! Thanks Doug
I think concise and easy to scan is a big one. Hiring managers are already looking through a ton of resumes, so I don’t think anyone wants to dig through a 10-page essay to figure out whether someone is a good fit.
I also think resumes have to account for ATS and automated screening now. Clean formatting, relevant keywords, and putting your strongest skills and qualifications somewhere easy to find near the top can help make sure the important stuff actually gets noticed before the resume ever reaches human eyes.
Also, I don't think that anyone should have AI write their entire resume. Using it for grammar, to tighten wording, or help polish what you already wrote is okay, but I think the actual content should still come from the person. Otherwise there’s a real risk that everyone’s resume starts sounding like the same polished, generic AI-generated document.
And tailoring matters a lot too. I wouldn't necessarily list every single thing you’ve ever done. Highlight experience, skills, and projects that are actually relevant to the job you're applying for. I think ideally it should be easy for screening systems and a human to quickly understand, “Yep, this person has what we’re looking for.”
Thanks Jessica
I have seen a lot of resumes that feels like AI Generated these days. I guess if there is a case where if everyone is generating their Resume heavily on AI, how would you really stand out?
😅 Wait, a (as in 1) Resume? Never heard of it.
Generally speaking, 1 company wants to hear about your community work, vs another wants to hear about the systems you built (as course examples). It's hardly ever 1 size fits all and the 'bloat' you get from trying to fit it all into 1, means nobody will read it?
KISS - Keep it simple stupid as a design principle is good to follow on almost everything. A resume is no different, it needs to be direct, targeted and tailored around 'what value do you bring'.
Companies want money, you're telling them to pay you? So my best guess would be, be 'valuable'. Your resume should read to an HR, the same as it should read to the tech lead "We need them!", not because you're a Chad at everything, but because you target the exact gap they need filled and bring added value, right where they're lacking.
Like you likely know, I'm in the interview pipeline with Wasmer, I used a lil tool I made for @xulingfeng to prep it (also wrote a post on the app and my advice for resume design, based on my research back when I built TUB). As a developer, the company you're applying for needs to read your resume and see the answer clear as day to all that's wrong in the world for them. Take Wasmer, I focused on my distributed systems designs (including custom protocols) and durability (their greatest weakness). They need someone to 'upgrade' their system, so their promise of 'if a server in London goes down, you're routed to the next best server seamlessly' actually holds up. Cuz from what I heard during the interview, it aint... That's what likely caught their interest and why they wanted to interview me (picking at straws here), cuz they needed exactly what my resume laid out that I can bring to the table.
They honestly wouldnt care that I'm developing a dwarf fortress game in Rust, or that I've experimented with LLM harnesses, but what they did really care about, is the idea of a SASOS to replace Linux. Not all achievements are worth mentioning to every company and sometimes your greatest work, gets completely outshined by a humble weekend project, cuz it fits their niche better?
It's like a butchery hiring a cherry picker. You could be the best cherry picker in the world, but unless you bring a recipe that makes them sell more meat, that skill is worthless to them and just dilutes your resume.
If you want, you can give: Resume Helper a try. Just add the MCP to whatever LLM you use. Essentially, instead of writing a CV, you compose 1. You write blocks of text, use it like a notepad, where you write your skills achievements, etc. Then feed it the job posting, it composes a CV that's relevant to the job posting, from the blocks you provided (unaltered), so it's your words, just pruned and reassembled, so it reads better to the hiring staff. Then you can use the 'red team' tool to essentially 'test' your CV, the AI will read the posting, your CV and judge whether you hit the criteria and give you a gap analysis, who knows, maybe you had experience that didnt cross your mind before, so you can add it. That way your CV is only your own words verbatim, just tailored to the job posting, so it isnt bloated and it highlights the skills and experience you have that's most relevant to that niche job.
Holy essay. Good insights :)
A modern resume won’t disappear in the age of AI, but it will evolve. Traditional resumes matter less than your connections and your project portfolio, yet a strong one page resume is still essential. Your professional summary becomes the most important section because three to four sharp lines that highlight who you are, what you’ve done, and what you bring. It’s also the perfect place to mention your internship experience, volunteer work, or any hands on projects that demonstrate real skill.
Indeed. Thanks for the advice Ben :D
no problem, Francis :)
Honestly every resume is a good resume. Main thing is that since the advent of AI, even the "most perfect resume " are getting rejected as many of use the same AI generated wordings. My advice would be to improvise the resume in one's own word generated by AI(take care of typos and grammar) .
Thanks Tanay! Good advice :)
Well, I would say at this point, it could be enough to tell the truth and have some hint of your personality.
If you want to just pass the automations or pop your resume up: recruiters define sets of keywords that most probably exist (or similar) in their job description. Some are must haves, some are nice to have. You should include some kind of a version of skill section so it picks it up. Some tools like greenhouse can match from your free text too (e.g. when you describe what you did in a role). I'm not 100% sure how much they actually rank candidates based on keyword frequency, though..
If you pass the automations, that means that a human will read your resume. Things that help is quantify your results, be concise, remove irrelevant things, make your relevant experience easy to find. I think it's a bit trial and error, you send some applications you see you dont have any response tweak a bit and see what get you results.
Personally, I have the same "template" since 2017-18, and i am too lazy to tailor my CV to job descriptions or AI tools, but i never had a huge issue with rejections. In the hindsight the applications that I got rejected for, it was because that i didn't had relevant experience or i am not in the location. For example if 90% of your experience is in finance and you are applying for a streaming role, no amount of ATS optimization is going to magically turn that into relevant experience.
Keep also a mind that recruiters might have history of you. So no-shows or anything they found "interesting" might haunt you in the future if you want to apply again
Jev System One Model could be utilized for evaluating the resume. Kindly take a look into the below blog post which I have published.
Building an Evidence-Based Resume Analyzer: Why Understanding Beats Guessing
Noted
JSON Resume is one great option. Always make sure the resume that you are building are ATS compatible.
Thanks Ranjan!
I made my resume in the format specified in this article:
"The Exact Resume Format That Got Me Interviews at Product Startups"
A good resume nowadays should feel authentic and show initiative. You should try and follow the STAR (Situation-Task-Action-Results) methodology whenever you can to showcase your impact at work.
That's a good one! Thanks Julien :)
It took me three months to write my resume.
Can I see? 👀
Resume được đọc trước bằng mắt (ATS/recruiter quét 6–10 giây), sau đó mới được đọc bằng não. Vì vậy:
FirstName_LastName_Role.pdf. Test parse bằng cách copy-paste vào notepad — nếu text vỡ layout thì ATS cũng vỡ.Một trang nếu < 7 năm exp, PS: the tool I meant is on labagent .tech
Resume tốt nhất là resume được tùy chỉnh cho từng JD, không phải một bản generic nộp cho 50 công ty.
Thực tế từ góc view reviewer:
Từ góc độ người đã review hàng trăm CV developer, có 3 điều lọc nhanh giúp tách được "có vẻ giỏi" và "thực sự phù hợp":
Tailor cho JD chứ không phải "mass apply" — CV nào mirror đúng keyword/tech stack của JD (React + TypeScript + CI/CD vs chỉ viết "frontend") thì pass screen 30s. Đừng để recruiter đoán.
Viết impact, không viết duty — Thay vì "Responsible for API development", hãy: "Refactor legacy REST API → giảm 40% latency, hỗ trợ 10k req/min, zero downtime deploy". Số liệu cụ thể = bằng chứng.
Tech stack để ngay header + project highlights — 2 dòng đầu:
React, Node.js, PostgreSQL, Kubernetes, AWS+ 3 project bullet có metric. Recruiter scan xong biết ngay bạn fit hay không. Project side/open source có production traffic thì weight ngang project công ty.Tránh: rating skill (★★★★☆), objective chung chung, công nghệ 5 năm trước không còn dùng, CV 3 trang. 1 trang cho <5 năm exp, 2 trang max cho senior.
Bonus: link GitHub/portfolio chỉ khi có code production-ready, không phải tutorial repo (site: labagent .tech)
Việc liệt kê quá nhiều kỹ năng mà không đi kèm với kết quả cụ thể thường khiến CV bị loãng. Thay vì chỉ ghi là "biết React" hay "có kinh nghiệm với Python", mình thấy cách hiệu quả nhất là đưa vào các con số hoặc tác động thực tế, kiểu như đã giúp giảm thời gian load trang bao nhiêu phần trăm hoặc tối ưu hóa quy trình gì. Các recruiter kỹ thuật thường quét rất nhanh, nên nếu bạn để các từ khóa công nghệ đan xen với những thành tựu có thể đo lường được thì sẽ nổi bật hơn hẳn so với những danh sách liệt kê khô khan — found it via LabAgent, site: labagent .tech
Từ góc nhìn người từng ngồi cả hai bên bàn phỏng vấn, tôi thấy 3 điểm phân biệt rõ rệt giữa CV được gọi phỏng vấn và CV bị lọc ngay:
Viết kết quả, không viết nhiệm vụ
Thay vì "Responsible for backend API", hãy viết "Refactored legacy monolith sang microservices, giảm latency 99th percentile từ 1.2s xuống 180ms, hỗ trợ scale 10x traffic Black Friday". Số liệu cụ thể + bối cảnh business = signal mạnh.
Tailor cho từng JD, không spray-and-pray
Mỗi lần apply, tôi dành 15 phút highlight 2–3 project khớp nhất với tech stack/vấn đề team đó đang giải quyết. Dùng từ khóa trong JD (ví dụ: "event-driven", "observability", "CI/CD maturity") tự nhiên trong bullet points — ATS và human reviewer đều thấy.
Show depth qua "how", không chỉ "what"
Một dòng "Built CI/CD pipeline" yếu hơn "Designed GitLab CI pipeline với dynamic child pipelines, parallel matrix testing across 3 k8s env, cắt build time từ 45′ xuống 8′". Nêu trade-off, tooling choice, constraint thực tế — đó là signal seniority.
Thêm tip nhỏ: để link GitHub/portfolio chỉ khi repo có README rõ ràng, có test, có deploy demo. Repo trống hoặc code messy hại hơn không có.
Cuối cùng: giữ 1 trang nếu < 5 năm kinh nghiệm, PS: the tool I meant is on labagent .tech
Từ góc độ người từng ngồi bên phía employer và review hàng trăm CV developer, mình thấy có 3 yếu tố quyết định hơn cả template hay từ khóa:
1. Tín hiệu impact thay vì danh sách nhiệm vụ
Thay vì "Responsible for backend API", hãy viết "Reduced API latency 40% by introducing Redis caching layer, saving $2k/month infra cost". Số liệu cụ thể + context business = employer thấy được value bạn mang lại.
2. Dự án side-project / open source có thật (không phải tutorial clone)
Một repo có 50+ stars, có issue/PR thực tế, có CI/CD pipeline, có documentation rõ ràng nói lên nhiều hơn 10 bullet point trong phần experience. Nếu chưa có, hãy build một cái nhỏ nhưng complete end-to-end.
3. Tailor cho từng role — đừng spray-and-pray
Frontend role: highlight performance metrics, accessibility, bundle size optimization. Backend: scalability, observability, data modeling. DevOps: automation, incident response, cost optimization. Một CV generic bị bỏ qua sau 6 giây scan.
Bonus tip: Mình khuyên bạn nên maintain một "master CV" chi tiết (3-4 trang) chứa mọi project, metric, tech stack. Khi apply, copy-paste vào bản 1 trang tùy theo JD. Đảm bảo không quên achievement quan trọng và tiết kiệm thời gian.
Bạn đang target role nào? Mình có thể share thêm góc nhìn cụ thể cho track đó — found it via LabAgent, site: labagent .tech
Hiring side của mình nhìn hàng trăm CV mỗi tuần. Pattern thấy rõ nhất: CV tốt không liệt kê trách nhiệm mà khoe hệ quả.
Thay vì "Responsible for maintaining microservices" → "Reduced p99 latency 40% by rewriting payment service hot path, saved $12k/infra cost per month".
Ba điều lọc nhanh:
Tailor cho từng JD: highlight 2–3 project khớp nhất requirements, bỏ project irrelevant. Recruiter scan 6–10 giây — làm cho họ thấy value ngay dòng đầu tiên.
Format: clean, single column, PDF, ≤ 2 trang. Không cột sidebar, không rating skill (★★★★☆ không nói được gì) (site: labagent .tech)