<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Hamza Hassan</title>
    <description>The latest articles on DEV Community by Hamza Hassan (@hamzahassan).</description>
    <link>https://dev.to/hamzahassan</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4201016%2F20336b1b-214c-441c-b03f-1cd56dad7ea1.png</url>
      <title>DEV Community: Hamza Hassan</title>
      <link>https://dev.to/hamzahassan</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/hamzahassan"/>
    <language>en</language>
    <item>
      <title>Software engineer resume in 2026: how to show the work AI isn't doing</title>
      <dc:creator>Hamza Hassan</dc:creator>
      <pubDate>Mon, 09 Nov 2026 20:12:08 +0000</pubDate>
      <link>https://dev.to/hamzahassan/software-engineer-resume-in-2026-how-to-show-the-work-ai-isnt-doing-2fcb</link>
      <guid>https://dev.to/hamzahassan/software-engineer-resume-in-2026-how-to-show-the-work-ai-isnt-doing-2fcb</guid>
      <description>&lt;p&gt;A strong software engineer resume in 2026 shows more than the code you wrote. Most developers now use AI to help write code, so recruiters see the same "built features with React and Node" bullets on every resume. Production skills stand out more: deploying, monitoring and fixing systems that real users depend on.&lt;/p&gt;

&lt;p&gt;The data backs this up. In Stack Overflow's &lt;a href="https://stackoverflow.blog/2026/10/06/the-results-of-the-2026-developer-survey-are-here/" rel="noopener noreferrer"&gt;2026 Developer Survey&lt;/a&gt; of more than 30,000 developers, 66% use coding agents, and developers mostly use AI to write code in familiar areas (67%) and to debug (61%). Only 20% use AI for deploying, operating or troubleshooting production systems.&lt;/p&gt;

&lt;h2&gt;
  
  
  What should a software engineer resume include in 2026?
&lt;/h2&gt;

&lt;p&gt;Your resume should cover the code you shipped and how you kept it running. Recruiters still want your stack and the features you built. Production experience is what separates you from other candidates with the same stack.&lt;/p&gt;

&lt;p&gt;Production experience includes:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;setting up or fixing a CI/CD pipeline&lt;/li&gt;
&lt;li&gt;writing infrastructure as code with Terraform, Pulumi or CloudFormation&lt;/li&gt;
&lt;li&gt;adding monitoring, alerts or logging that caught a real problem&lt;/li&gt;
&lt;li&gt;handling an incident or writing the postmortem&lt;/li&gt;
&lt;li&gt;making deploys safer with feature flags, rollbacks or staged rollouts&lt;/li&gt;
&lt;li&gt;reducing a cloud bill&lt;/li&gt;
&lt;li&gt;migrating a database or service without downtime&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Small versions count. A side project with a real deploy and real users is production work.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you write resume bullet points for production work?
&lt;/h2&gt;

&lt;p&gt;Describe what was going wrong and what changed. Name the tool, but lead with the result. These examples are illustrative:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Before:&lt;/strong&gt; Worked on CI/CD pipelines.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;After:&lt;/strong&gt; Moved deploys from a manual script to GitHub Actions with automatic rollback, so a bad release could be undone in one step.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Before:&lt;/strong&gt; Responsible for AWS infrastructure.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;After:&lt;/strong&gt; Rewrote our AWS setup in Pulumi so a new environment could be created from code instead of by hand.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Before:&lt;/strong&gt; Participated in on-call rotation.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;After:&lt;/strong&gt; Traced a recurring checkout timeout to a missing database index during an incident, and added an alert so the team would see it earlier next time.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Only include numbers you can back up. If a deploy went from 40 minutes to 8, say so. If you don't know the number, describe the change and leave it out.&lt;/p&gt;

&lt;h2&gt;
  
  
  Will these keywords help with ATS?
&lt;/h2&gt;

&lt;p&gt;Yes, if they're true. Applicant tracking systems and recruiters search for specific tools, so name them: "GitHub Actions", "Terraform", "Kubernetes", "Datadog". Use the same wording the job posting uses. If the posting says "CI/CD", write "CI/CD" rather than only "deployment pipeline". Don't list tools you haven't used. They come up in technical interviews.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where should production experience go on a resume?
&lt;/h2&gt;

&lt;p&gt;Put it under the job where you did it, as its own bullets. If it was a real part of the role, it deserves two or three bullets, not one line at the end. If your current job doesn't include production work, add a project section with one project that has a live deploy, monitoring and a short write-up of something that broke.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you talk about it in an interview?
&lt;/h2&gt;

&lt;p&gt;Prepare one story you can tell in two minutes: what broke or needed changing, how you found the cause, what you changed, and what you'd do differently. Interviewers ask follow-up questions about production work because it's hard to fake, so pick something you know well.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Should I put DevOps experience on a software engineer resume?
&lt;/h3&gt;

&lt;p&gt;Yes. Even if you're applying for a backend or full-stack role, deployment and infrastructure work shows you understand how software runs after it's merged.&lt;/p&gt;

&lt;h3&gt;
  
  
  Is it okay to use AI to write my resume?
&lt;/h3&gt;

&lt;p&gt;You can use it to tighten wording or point out vague bullets. Write the facts yourself first, and check that every claim is true and specific. Generic AI phrasing makes your resume look like everyone else's.&lt;/p&gt;

&lt;h3&gt;
  
  
  How long should a software engineer resume be in 2026?
&lt;/h3&gt;

&lt;p&gt;One page for most people with under ten years of experience. Two pages is fine for senior engineers if every bullet earns its place.&lt;/p&gt;




&lt;p&gt;You can check your bullets with &lt;a href="https://resumize.ai/" rel="noopener noreferrer"&gt;Resumize's free resume checker&lt;/a&gt;, which flags vague claims and shows which line each comment refers to. (Disclosure: I'm the founder.)&lt;/p&gt;

&lt;p&gt;What production work have you done that never made it onto your resume?&lt;/p&gt;

</description>
      <category>career</category>
      <category>resume</category>
      <category>ai</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Job seekers are rewriting their applications so they don't sound like AI</title>
      <dc:creator>Hamza Hassan</dc:creator>
      <pubDate>Mon, 26 Oct 2026 18:26:46 +0000</pubDate>
      <link>https://dev.to/hamzahassan/job-seekers-are-rewriting-their-applications-so-they-dont-sound-like-ai-383b</link>
      <guid>https://dev.to/hamzahassan/job-seekers-are-rewriting-their-applications-so-they-dont-sound-like-ai-383b</guid>
      <description>&lt;p&gt;&lt;em&gt;Disclosure: I'm the founder of Resumize, a resume tool that uses AI.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Last week Greenhouse published its &lt;a href="https://www.greenhouse.com/newsroom/6-in-10-job-seekers-are-rethinking-how-they-write-to-avoid-sounding-like-ai-even-as-most-use-it-in-their-search" rel="noopener noreferrer"&gt;2026 Future of Hiring Candidate Report&lt;/a&gt;, a survey of more than 2,800 job seekers in the U.S., U.K., Ireland, Germany and Australia. 77% of U.S. job seekers used AI in their search in the past year. 60% changed, or thought about changing, how they write so their applications wouldn't be mistaken for AI-generated content, and 39% actually rewrote one.&lt;/p&gt;

&lt;p&gt;So most people use AI, and most of them now worry it shows. Sharawn Tipton, Greenhouse's Chief People Officer, said: "For the first time I can remember, neither side thinks hiring is working."&lt;/p&gt;

&lt;p&gt;I spend a lot of time reading resumes, many of them written with AI, and I think the worry is fair. Where people go wrong is hunting for single "AI words" to delete. What gives a resume away is that every bullet sounds like every other candidate's.&lt;/p&gt;

&lt;h2&gt;
  
  
  What makes a resume read as AI-written
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Verbs nobody uses out loud, like "spearheaded", "leveraged", "orchestrated" and "drove synergies". People say "led", "used", "ran" and "built".&lt;/li&gt;
&lt;li&gt;Numbers with nothing behind them. "Improved efficiency by 30%" doesn't say what was measured or how, so a recruiter can't check it and an interviewer will ask.&lt;/li&gt;
&lt;li&gt;The same sentence shape in every bullet: verb, task, "resulting in" outcome, eight times in a row. Real work isn't that tidy.&lt;/li&gt;
&lt;li&gt;A summary that could describe anyone. "Results-driven professional passionate about delivering impact" would still read the same with another candidate's name on top.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  A before and after
&lt;/h2&gt;

&lt;p&gt;&lt;em&gt;This example is made up for this post.&lt;/em&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Before:&lt;/strong&gt; Spearheaded the optimization of customer onboarding processes, leveraging data-driven insights to drive a 35% increase in efficiency.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;After:&lt;/strong&gt; Rewrote our onboarding checklist after noticing most support tickets came from the same two setup steps. New customers now finish setup in one call instead of three.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;The second one names the problem, says what you did, and gives a result you could explain in an interview without notes.&lt;/p&gt;

&lt;h2&gt;
  
  
  What not to do
&lt;/h2&gt;

&lt;p&gt;The same report found that some candidates trying to get past automated screening add skills or keywords they don't have, and some hide text meant for AI reviewers.&lt;/p&gt;

&lt;p&gt;I'd avoid both. A skill you don't have tends to come up in the first technical interview. Hidden text can show up the moment someone pastes your resume into a plain-text field, and after that the recruiter is questioning your honesty, which is a lot harder to recover from than a weak bullet.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to use AI without sounding like it
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Write the facts first, in your own words: what you worked on, what changed, and how you know. Rough notes are fine.&lt;/li&gt;
&lt;li&gt;Ask AI to shorten a bullet or point out vague phrases. If you ask it to "make this sound more impressive", it will add claims you can't back up.&lt;/li&gt;
&lt;li&gt;Read every bullet out loud. If you wouldn't say it that way to a colleague, rewrite it.&lt;/li&gt;
&lt;li&gt;If you can't say where a number came from, remove the number.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;People in the report said they want to show employers more than an application allows, and 52% want to show they can learn and adapt. A bullet about how you noticed a problem and fixed it shows that better than a percentage nobody can check.&lt;/p&gt;

&lt;p&gt;If you'd like a second opinion on your bullets, &lt;a href="https://resumize.ai/" rel="noopener noreferrer"&gt;Resumize&lt;/a&gt; flags vague and unsupported claims and shows exactly which line each comment refers to.&lt;/p&gt;

&lt;p&gt;Have you changed how you write applications because of AI? I'm curious what people are cutting.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>webdev</category>
      <category>resume</category>
      <category>career</category>
    </item>
    <item>
      <title>Turn a GitHub project into three resume bullets a recruiter will believe</title>
      <dc:creator>Hamza Hassan</dc:creator>
      <pubDate>Thu, 22 Oct 2026 18:58:22 +0000</pubDate>
      <link>https://dev.to/hamzahassan/turn-a-github-project-into-three-resume-bullets-a-recruiter-will-believe-2lkl</link>
      <guid>https://dev.to/hamzahassan/turn-a-github-project-into-three-resume-bullets-a-recruiter-will-believe-2lkl</guid>
      <description>&lt;blockquote&gt;
&lt;p&gt;Built a full-stack web app using React, Node.js and PostgreSQL.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;It's true, but it tells the reader almost nothing. Thousands of people have built a React app. A recruiter wants to know what problem you solved, which parts you did yourself, and how they can tell it worked.&lt;/p&gt;

&lt;p&gt;I write project bullets by answering three questions, using evidence that's already in the repo.&lt;/p&gt;

&lt;p&gt;**&lt;/p&gt;

&lt;h2&gt;
  
  
  The three questions
&lt;/h2&gt;

&lt;p&gt;**&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;What problem does the project solve? Answer in one sentence that someone who has never seen the code would understand.&lt;/li&gt;
&lt;li&gt;What did you personally do? This matters most when other people touched the project.&lt;/li&gt;
&lt;li&gt;What evidence is there? Tests, a live deploy, a README, a measured result: anything a reviewer could check.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;A bullet that answers fewer than two of these is really just a list of technologies.&lt;/p&gt;

&lt;h3&gt;
  
  
  A worked example
&lt;/h3&gt;

&lt;p&gt;&lt;em&gt;The candidate and project below are made up for this post.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Sara built ShiftSwap, a small app that lets staff at a café trade shifts. Her README says:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The café's 12 staff used a WhatsApp group for swaps, and requests got lost&lt;/li&gt;
&lt;li&gt;App built with Next.js and PostgreSQL, deployed on Vercel&lt;/li&gt;
&lt;li&gt;Manager approves swaps with one click; both people get an email&lt;/li&gt;
&lt;li&gt;41 tests covering swap rules (no double-booking, no overtime past 40 hrs)&lt;/li&gt;
&lt;li&gt;Used by the café for 3 months&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That's enough material for three good bullets:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Before&lt;/th&gt;
&lt;th&gt;After&lt;/th&gt;
&lt;th&gt;Why it's better&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Built a full-stack web app using React, Node.js and PostgreSQL&lt;/td&gt;
&lt;td&gt;Built a shift-swap app (Next.js, PostgreSQL) that replaced a WhatsApp group for a 12-person café team&lt;/td&gt;
&lt;td&gt;It names the problem and who used it. The stack moves into brackets&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Implemented an approval system&lt;/td&gt;
&lt;td&gt;Added one-click manager approval with email confirmation to both staff, so swaps stopped getting lost&lt;/td&gt;
&lt;td&gt;It says what the feature changed for the people using it&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Wrote tests&lt;/td&gt;
&lt;td&gt;Wrote 41 tests covering scheduling rules, including double-booking and the 40-hour overtime limit&lt;/td&gt;
&lt;td&gt;Naming the rules shows she understood how the café actually works&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Every claim in the new bullets comes from the README or the repo.&lt;/p&gt;

&lt;h3&gt;
  
  
  When you have no users and no numbers
&lt;/h3&gt;

&lt;p&gt;Most side projects never get users, and you shouldn't pretend yours did. You can still describe the engineering.&lt;/p&gt;

&lt;p&gt;Say nobody ever used Sara's app. Her README still shows a deployed demo, a test suite, and a section explaining why she chose optimistic UI updates over waiting for the server. Those become:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Built and deployed a shift-swap prototype (Next.js, PostgreSQL) with a public demo and setup docs&lt;/li&gt;
&lt;li&gt;Designed scheduling rules to prevent double-booking and overtime, covered by 41 automated tests&lt;/li&gt;
&lt;li&gt;Chose optimistic UI updates for swap requests and documented the tradeoff around conflicting edits in the README&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;There's no "increased efficiency by 40%" in there. A reviewer can open the repo and check every line, and I'd trust that over a number I can't verify.&lt;/p&gt;

&lt;p&gt;If you want a second opinion after rewriting, I'm building &lt;a href="https://resumize.ai/" rel="noopener noreferrer"&gt;Resumize AI&lt;/a&gt;. Its free checker flags weak bullets and shows which line each piece of feedback refers to. (Disclosure: I'm the founder.)&lt;/p&gt;

&lt;p&gt;What's the hardest project on your resume to describe? Put it in the comments and I'll try rewriting one or two:))&lt;/p&gt;

</description>
      <category>career</category>
      <category>beginners</category>
      <category>github</category>
      <category>resume</category>
    </item>
  </channel>
</rss>
