Terminal: developer resume template
Markdown-style lowercase mono labels and arrow bullets. Plain text under the hood.
Terminal looks like a well-kept README. Section headings are lowercase and monospaced with no rules under them, bullets are small arrow marks, and dates sit in the same monospaced face at the right edge. The name stays a bold sans-serif, so the top of the page still reads as a resume.
- Audience
- Backend · Platform · Open source
- Colour schemes
- Indigo, Ink, Teal
- Photo slot
- No
- Paper
- A4 and US Letter
It was made for backend, platform, infrastructure and open-source engineers applying to engineering-led teams. There the person screening resumes is often an engineer, and a page that looks like their own tools tells them a little about you before they read the detail. Name the stack you actually used in each role, because an engineer reading the page will know what each tool involves. Terminal is a single column of plain text with nothing drawn behind it, which makes it ATS-safe. It is free, and there is nothing to sign up for.
Pick Terminal if…
- You would rather your resume looked like a README than a brochure.
- Engineers screen the resumes at the startups and product companies you are applying to.
- Your work has public evidence: repositories, packages, talks or a technical blog.
- You want a technical look with the least decoration possible.
Lowercase headings, plain structure
- Headings are lowercase monospaced text. They look like a file listing, and they are still ordinary words in the PDF.
- Nothing is drawn on the page. The monospaced headings and the space between sections separate one part from the next.
- Dates are monospaced and right-aligned, so the years line up down the page like a column of figures.
- Each arrow bullet is one character in a narrow indent, which keeps long technical bullets close to the left margin.
How much fits on one page
Arrow bullets and lowercase headings are compact, so Terminal holds about as much as Metro: four or five roles on a page. If you know a long list of tools, group them in Skills by area, with one row each for languages, infrastructure and data. Grouped rows take less height than one long line and are quicker to read. Open-source work reads best as a Projects section: the repository name as the title, your role, and a bullet with something measurable such as merged pull requests, downloads or the size of the team that depends on it.
When to use something else
Terminal tells the reader you are an engineer before they reach your first bullet. Outside engineering and a few technical roles, lowercase monospaced headings look like a style choice the reader has to interpret. If an HR generalist at a large IT services company will read the resume, Metro keeps the technical feel in a more conventional shape, and Plainline drops it entirely.
Terminal works well for these roles
Hands-on engineering roles, where the person reading is often the person you would work beside.
Questions about Terminal
- Will lowercase headings hurt my resume in an ATS?
- They are real words, only lowercased, and most applicant tracking systems match section names without regard to case, so 'experience' is recognised as Experience. To remove even that small doubt for one portal, switch to Metro for that upload. Your content carries over.
- Can I write commands or code in my Terminal bullets?
- Sparingly. Bullets are set in the body sans-serif, so a command reads as plain text. Name tools and versions plainly, such as 'Kubernetes 1.29' or 'PostgreSQL', and keep each bullet about the result: what got faster, cheaper or more reliable.
- Is Terminal a good choice for a data scientist?
- If your work is engineering-heavy, such as building pipelines, putting models into production or writing internal tools, it fits. For analyst or research roles where a business stakeholder reads the resume, Plainline or Ledger will feel more familiar to them.