<?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: Rory</title>
    <description>The latest articles on DEV Community by Rory (@rornic).</description>
    <link>https://dev.to/rornic</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.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3408986%2F3bb20017-b784-420f-aef0-dc85c7f86a68.png</url>
      <title>DEV Community: Rory</title>
      <link>https://dev.to/rornic</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/rornic"/>
    <language>en</language>
    <item>
      <title>How to Write a Great Software Engineering CV (With Free Template)</title>
      <dc:creator>Rory</dc:creator>
      <pubDate>Sun, 03 Aug 2025 06:40:26 +0000</pubDate>
      <link>https://dev.to/rornic/how-to-write-a-great-software-engineering-cv-with-free-template-374e</link>
      <guid>https://dev.to/rornic/how-to-write-a-great-software-engineering-cv-with-free-template-374e</guid>
      <description>&lt;blockquote&gt;
&lt;p&gt;Your CV isn’t a memoir — it’s a spec sheet.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;I’ve been on both sides of the hiring table in tech and I keep seeing the same issues crop up again and again.&lt;/p&gt;

&lt;p&gt;So I decided to condense everything I’ve learned into one clear and simple guide. As a bonus, I put together a CV template to go with it.&lt;/p&gt;




&lt;h2&gt;
  
  
  The TL;DR
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Use a clean, readable format (no fancy colours, no 2-column designs).&lt;/li&gt;
&lt;li&gt;Lead with your impact.&lt;/li&gt;
&lt;li&gt;Show what you &lt;em&gt;did&lt;/em&gt;, not what you were “responsible for”.&lt;/li&gt;
&lt;li&gt;Quantify everything: “improved p99 latency by 80%”, “increased conversion by 1.5%”.&lt;/li&gt;
&lt;li&gt;1–2 pages max. PDF only. Use a real filename.
&lt;/li&gt;
&lt;li&gt;Tailor your CV to the role (and stack) you’re applying to.&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  Use the Free CV Template
&lt;/h2&gt;

&lt;p&gt;I’ve turned this advice into a downloadable &lt;a href="https://docs.google.com/document/d/1-wZw0wuH5P7aCPIMxB2ovePEg9Euf4gKi3EOqS_skqI/template/preview" rel="noopener noreferrer"&gt;Google Docs template&lt;/a&gt; you can copy and make your own. It’s based on my own CV so it’s tried, tested, and continuously improved.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Link: &lt;a href="https://docs.google.com/document/d/1-wZw0wuH5P7aCPIMxB2ovePEg9Euf4gKi3EOqS_skqI/template/preview" rel="noopener noreferrer"&gt;Download the CV Template&lt;/a&gt;&lt;/p&gt;
&lt;/blockquote&gt;




&lt;h2&gt;
  
  
  Full Breakdown
&lt;/h2&gt;

&lt;p&gt;If you want the full article that goes into CV anatomy, red flags to avoid, and formatting tips, I’ve written that up here:&lt;br&gt;&lt;br&gt;
&lt;a href="https://rornic.dev/posts/software-engineer-cv-tips" rel="noopener noreferrer"&gt;How to Write a Great Software Engineering CV&lt;/a&gt;&lt;/p&gt;




&lt;h2&gt;
  
  
  Final Thoughts
&lt;/h2&gt;

&lt;p&gt;Your CV’s only job is to earn you a conversation.&lt;/p&gt;

&lt;p&gt;Make it clean. Make it focused. Make it easy for someone to say: &lt;em&gt;“We should interview this person.”&lt;/em&gt;&lt;/p&gt;




&lt;p&gt;Looking for high-quality tech jobs? &lt;/p&gt;

&lt;p&gt;Check out &lt;a href="https://findatechjob.dev" rel="noopener noreferrer"&gt;findatechjob.dev&lt;/a&gt; for a blazing-fast search over thousands!&lt;/p&gt;

&lt;p&gt;If this helps, drop a comment or feel free to share your own CV tips below.&lt;/p&gt;

</description>
      <category>career</category>
      <category>productivity</category>
      <category>learning</category>
    </item>
  </channel>
</rss>
