\u003C/figure>\n\u003C!-- /wp:image -->\n\n\u003C!-- wp:paragraph -->\n\u003Cp>\u003Cstrong>2. Call out languages and technologies that you used as part of your work experience.\u003C/strong>\u003C/p>\n\u003C!-- /wp:paragraph -->\n\n\u003C!-- wp:paragraph -->\n\u003Cp>An alternative to the previous approach is to mention the tools you used in each position. This gives more context on when you used these technologies or frameworks and what problems you solved using them. You could just list these out separately at the end of each position like this:\u003C/p>\n\u003C!-- /wp:paragraph -->\n\n\u003C!-- wp:image {\"id\":16999,\"sizeSlug\":\"large\"} -->\n\u003Cfigure class=\"wp-block-image size-large\">\u003Cimg src=\"https://stackoverflow.blog/wp-content/uploads/2020/11/image-1.png\" alt=\"\" class=\"wp-image-16999\"/>\u003C/figure>\n\u003C!-- /wp:image -->\n\n\u003C!-- wp:paragraph -->\n\u003Cp>However, I recommend “weaving in” the languages and technologies to the description itself. This both reads better, and you can give even more context:\u003C/p>\n\u003C!-- /wp:paragraph -->\n\n\u003C!-- wp:image {\"id\":17000,\"sizeSlug\":\"large\"} -->\n\u003Cfigure class=\"wp-block-image size-large\">\u003Cimg src=\"https://stackoverflow.blog/wp-content/uploads/2020/11/image-2.png\" alt=\"\" class=\"wp-image-17000\"/>\u003C/figure>\n\u003C!-- /wp:image -->\n\n\u003C!-- wp:heading -->\n\u003Ch2 id=\"h-standing-out-results-impact-and-numbers\">Standing out: results, impact, and numbers\u003C/h2>\n\u003C!-- /wp:heading -->\n\n\u003C!-- wp:paragraph -->\n\u003Cp>One thing I wish more resumes had is specifics. The majority of CVs I’ve read tend to list responsibilities, what work was assigned, or have a hand-wavy explanation of the work. Here’s an example of a resume snippet that recruiters and hiring managers see all too commonly:\u003C/p>\n\u003C!-- /wp:paragraph -->\n\n\u003C!-- wp:image {\"id\":17001,\"sizeSlug\":\"large\"} -->\n\u003Cfigure class=\"wp-block-image size-large\">\u003Cimg src=\"https://stackoverflow.blog/wp-content/uploads/2020/11/image-3.png\" alt=\"\" class=\"wp-image-17001\"/>\u003C/figure>\n\u003C!-- /wp:image -->\n\n\u003C!-- wp:paragraph -->\n\u003Cp>While the person writing these details probably felt they were showcasing the work they were doing—the hiring manager gets little to no context on the specifics of the work. To stand out, be specific. To be specific, follow this approach:\u003C/p>\n\u003C!-- /wp:paragraph -->\n\n\u003C!-- wp:list -->\n\u003Cul>\u003C!-- wp:list-item -->\n\u003Cli>\u003Cstrong>Use numbers\u003C/strong> and quantify whatever you can. Numbers can be the number of users, service load numbers, number of customer support tickets you proactively resolved, and many others.\u003C/li>\n\u003C!-- /wp:list-item -->\n\n\u003C!-- wp:list-item -->\n\u003Cli>\u003Cstrong>Use active language\u003C/strong> that shows what you have done and how you have been proactive. For example, instead of stating \u003Cem>“Fixing various bugs that improve the user experience”\u003C/em>, you could use active language and more specifics and write \u003Cem>“Reduced user reported defects by 50% after I identified and fixed root causes of the four most common user reports.”\u003C/em> The first version reads more passive: “fixing” might be seen as “I was told to be fixing”. In the second version, you make it clear what it was that you did and the results you achieved.\u003C/li>\n\u003C!-- /wp:list-item -->\n\n\u003C!-- wp:list-item -->\n\u003Cli>\u003Cstrong>Mention specific languages and technologies \u003C/strong>where they make sense. This gives more context and makes your resume details more interesting as well.\u003C/li>\n\u003C!-- /wp:list-item -->\u003C/ul>\n\u003C!-- /wp:list -->\n\n\u003C!-- wp:heading -->\n\u003Ch2 id=\"h-tailor-your-resume-to-the-position\">Tailor your resume to the position\u003C/h2>\n\u003C!-- /wp:heading -->\n\n\u003C!-- wp:paragraph -->\n\u003Cp>Having a “master” resume and tailoring it for every position you apply for is a great strategy. The tailoring doesn’t have to be drastic. However, if you are applying for a company where the job listing lists the stack as React and Node—and you have experience with these, among other languages—moving these up front could be a small change with a big impact. Similarly, if you’ve done work similar to what the position is asking for, having these bullet points listed first are all good ways to grab the attention of the person reading the resume earlier.\u003C/p>\n\u003C!-- /wp:paragraph -->\n\n\u003C!-- wp:paragraph -->\n\u003Cp>One last thing I need to call out, as developers seeking jobs bring it up: the application tracking systems (ATS), and robots “rejecting” your resume. This is false. Your resume will be read by a human. At tech companies, \u003Ca href=\"https://thetechresume.com/samples/ats-myths-busted.html\">ATSes do not “reject” resumes\u003C/a>, and “robot rejection” does not exist in tech. Be wary of any resource that claims this is true: they are probably using the tactic to create fear, uncertainty, and doubt as an incentive for you to buy their service. I’m saying this both as a hiring manager who has worked with ATSes and as an author who interviewed recruiters at all major tech companies. I asked them about robot rejections; they all confirmed that they have not seen or heard of such a practice.\u003C/p>\n\u003C!-- /wp:paragraph -->\n\n\u003C!-- wp:heading -->\n\u003Ch2 id=\"h-things-that-will-help-you-beyond-the-resume\">Things that will help you beyond the resume\u003C/h2>\n\u003C!-- /wp:heading -->\n\n\u003C!-- wp:paragraph -->\n\u003Cp>Applying for a job does not end with having a good resume. A few things can greatly help your job search: referrals, cover letters, LinkedIn, GitHub, and Stack Overflow.\u003C/p>\n\u003C!-- /wp:paragraph -->\n\n\u003C!-- wp:paragraph -->\n\u003Cp>\u003Cstrong>Employee referrals\u003C/strong> are the best way to increase your chances of hearing back from a company. If you have a strong referral, much of the above becomes less relevant. How do you get a referral? You ask. Ask around in your network to see who is hiring. Ask on public forums where tech professionals gather like Twitter or LinkedIn—potentially even Blind. You can try and reach out for a cold referral: but if you do, add context on why you think you are a great fit for a job and offer an easy way out for the person to not refer you if they do not feel comfortable doing so. \u003C/p>\n\u003C!-- /wp:paragraph -->\n\n\u003C!-- wp:paragraph -->\n\u003Cp>\u003Cstrong>Cover letters\u003C/strong> are a coin toss. For larger companies, these places usually either don’t ask for one, or don’t pay much attention to it. At smaller firms and startups, where hiring managers are likely to read resumes and cover letters, it’s a better investment to spend time on this. Keep it short, sweet, and relevant. Don’t repeat your resume: add additional details that make your case stronger as to why you are a good fit for the position you are applying to.\u003C/p>\n\u003C!-- /wp:paragraph -->\n\n\u003C!-- wp:paragraph -->\n\u003Cp>\u003Cstrong>Even if you are not looking for a job today, invest in growing your professional network.\u003C/strong> The larger your network, the easier you can get referrals from people who know the professional “you.\" To grow your network, build genuine relationships with others, help people, and make yourself visible. You don’t have to do this on social media: you can start right now at your workplace, within and outside your team.\u003C/p>\n\u003C!-- /wp:paragraph -->\n\n\u003C!-- wp:paragraph -->\n\u003Cp>LinkedIn, GitHub, and Stack Overflow are all sites where having an up-to-date profile will greatly help your job search. Keep your LinkedIn up to date: it’s a good idea to refresh it as you write your resume. For GitHub, consider creating a GitHub README to present yourself and your key projects more effectively. Make sure projects you mention in your resume or those that you pin to your GitHub profile also have READMEs that share what the project is about. On Stack Overflow, tailor \u003Ca href=\"https://stackoverflow.com/users/story/join\">your Developer Story\u003C/a> to make it easy for recruiters and hiring managers to find you with relevant opportunities.\u003C/p>\n\u003C!-- /wp:paragraph -->\n\n\u003C!-- wp:paragraph -->\n\u003Cp>For more advice, tips from recruiters in tech companies, and real-world “before” and “after” resume examples that worked, you can always grab \u003Ca href=\"https://thetechresume.com/\">The Tech Resume Inside Out\u003C/a>. The book is complimentary for devs currently out of a job.\u003C/p>\n\u003C!-- /wp:paragraph -->\n\n\u003C!-- wp:paragraph -->\n\u003Cp>Good luck with writing your resume!\u003C/p>\n\u003C!-- /wp:paragraph -->","html","2020-11-25T15:55:09.000Z",{"current":789},"how-to-write-an-effective-developer-resume-advice-from-a-hiring-manager",[791,799,804],{"_createdAt":792,"_id":793,"_rev":794,"_type":795,"_updatedAt":792,"slug":796,"title":798},"2023-05-23T16:43:21Z","wp-tagcat-code-for-a-living","9HpbCsT2tq0xwozQfkc4ih","blogTag",{"current":797},"code-for-a-living","Code for a Living",{"_createdAt":792,"_id":800,"_rev":794,"_type":795,"_updatedAt":792,"slug":801,"title":803},"wp-tagcat-hiring-process",{"current":802},"hiring-process","hiring process",{"_createdAt":792,"_id":805,"_rev":794,"_type":795,"_updatedAt":792,"slug":806,"title":807},"wp-tagcat-resume",{"current":807},"resume","How to write an effective developer resume: Advice from a hiring manager",[810,816,822,828],{"_id":811,"publishedAt":812,"slug":813,"sponsored":778,"title":815},"e10457b6-a9f6-4aa9-90f2-d9e04eb77b7c","2025-08-27T04:40:00.000Z",{"_type":10,"current":814},"from-punch-cards-to-prompts-a-history-of-how-software-got-better","From punch cards to prompts: a history of how software got better",{"_id":817,"publishedAt":818,"slug":819,"sponsored":12,"title":821},"65472515-0b62-40d1-8b79-a62bdd2f508a","2025-08-25T16:00:00.000Z",{"_type":10,"current":820},"making-continuous-learning-work-at-work","Making continuous learning work at work",{"_id":823,"publishedAt":824,"slug":825,"sponsored":12,"title":827},"1b0bdf8c-5558-4631-80ca-40cb8e54b571","2025-08-21T14:00:25.054Z",{"_type":10,"current":826},"research-roadmap-update-august-2025","Research roadmap update, August 2025",{"_id":829,"publishedAt":830,"slug":831,"sponsored":12,"title":833},"5ff6f77f-c459-4080-b0fa-4091583af1ac","2025-08-20T14:00:00.000Z",{"_type":10,"current":832},"documents-the-architect-s-programming-language","Documents: The architect’s programming language",{"count":835,"lastTimestamp":836},15,"2025-02-20T15:02:27Z",["Reactive",838],{"$sarticleModal":839},false,["Set"],["ShallowReactive",842],{"sanity-b-VmTP5l_1hxONPcgyv1TYzNPUHG6P1wN03RiM2L_9c":-1,"sanity-comment-wp-post-16997-1756370398420":-1},"/2020/11/25/how-to-write-an-effective-developer-resume-advice-from-a-hiring-manager"]