ATS CompatibleTwo columnNo photo

Technical

Technical answers the first question an engineering reviewer asks - what does this person work with - by putting skills, certifications and languages in a fixed left column. Experience, projects and education take the full main column so bullet points have room to be specific. The two columns are separated by a hairline rule rather than a colour block, which keeps the page quiet and the document lighter to print. Because it is a two-column layout, prefer Minimal ATS when you are applying through an unknown employer portal.

Use this template Back to gallery

What makes it different

Technical stack visible in the first two seconds
Full-width main column, so experience bullets stay readable
Hairline column divider rather than a heavy colour block
Certifications and languages grouped away from the narrative

Best for

Software engineering roles · Infrastructure and platform roles · Applications sent directly to an engineering team · CVs with a long tool list

When to choose something else

Two columns. Some older parsers read straight across the page, which can interleave your sidebar skills with your experience.
For an application through a large employer portal, a one-column layout is the safer choice.
The fixed sidebar width does not suit a very short tool list, which leaves the column looking empty.

Where your sections go

Skills, Certifications, Licences & Registration, Languages, Interests, Professional Memberships sit in a column divided by a hairline rule. Everything else — your summary, experience, education and any section you add — runs down the main column in the order you set. A section this layout has no sidebar slot for appears in the main column too, so nothing is ever dropped.

Parses correctly in normal use, with some visual structure. Suitable for most direct applications.

Ali Raza

Full Stack Developer · TypeScript, Node.js & PostgreSQL

ali.raza@example.com+92 300 5550142Lahore, Pakistanlinkedin.com/in/example-ali-razagithub.com/example-aliraza

Profile

Full stack developer with six years in small product teams, strongest on the back end: Node.js, TypeScript and PostgreSQL, with enough React to own a feature through to the browser. Recent work includes a payments integration processing around £2m a month and a query-tuning programme that cut dashboard load times by 90%.

Professional Experience

Senior Full Stack DeveloperMay 2022 – Present

Meridian Freight Systems · Lahore, Pakistan

Own the shipment tracking service end to end: PostgreSQL schema, Fastify API, React dashboard and the on-call rotation that covers it.
Built the carrier payments integration handling roughly £2m a month, including idempotency keys, a reconciliation job and an audit trail the finance team uses directly.
Traced a 9-second operations dashboard to a missing composite index and a per-row subquery; the rewrite as a lateral join brought it to 240ms and removed the nightly caching workaround.
Moved releases from manual deploys to GitHub Actions with blue/green on ECS, cutting release time from around 40 minutes to under 6.
Wrote the decision record for moving off a shared database to service-owned schemas, and led the four-month migration with no customer-visible downtime.

Node.js · Fastify · PostgreSQL · React · AWS · Terraform

Full Stack DeveloperAugust 2019 – April 2022

Karachi Labs · Karachi, Pakistan

Built three client products from empty repository to production, covering authentication, billing, admin tooling and the customer-facing app.
Introduced Prisma and a migration review step after a manual schema change caused two hours of downtime; no repeat incident in the following two years.
Added Sentry and structured logging across the estate, which turned "the site is broken" reports into traceable errors and cut mean time to diagnosis noticeably.
Interviewed and onboarded four developers, and wrote the onboarding guide that got new starters to their first merged pull request within a week.

Node.js · Express · React · PostgreSQL · Prisma · Docker

Selected Projects

pgcheck

Author

A command-line tool that reviews PostgreSQL migration files for locking operations that would block writes on a large table.
Flags the six patterns responsible for most accidental table locks and suggests the concurrent equivalent.
Used internally across three teams before being released publicly.

TypeScript · PostgreSQL · Node.js

github.com/example-aliraza/pgcheck

Education

BS Computer ScienceSeptember 2015 – June 2019

National University of Computer and Emerging Sciences · Lahore, Pakistan

Final-year project: a distributed job queue with at-least-once delivery guarantees.

CGPA 3.6 / 4.0

Usman Khan

Cloud & Platform Engineer · AWS, Terraform, Kubernetes

usman.khan@example.com+44 7700 900477Birmingham, United Kingdomlinkedin.com/in/example-usman-khan

Profile

Cloud and platform engineer with six years across AWS and Azure. Brought a 140-resource estate under Terraform, moved 12 services to GitOps delivery, and reduced monthly cloud spend by roughly a third without reducing workload capacity. Comfortable owning incident response and the on-call rota.

Professional Experience

Senior Platform EngineerFebruary 2022 – Present

Ardenfield Insurance · Birmingham, United Kingdom

Brought 140 manually created AWS resources under Terraform across three accounts, with remote state and plan review on every pull request; environment rebuilds went from a two-day project to a 40-minute apply.
Moved 12 services to Argo CD with automated rollback on failed health checks: deployments went from twice a month to around 30 a week, and mean time to recovery from 90 minutes to under 10.
Cut monthly AWS spend from roughly $47k to $31k by right-sizing 60 instances, moving batch workloads to Spot and adding S3 lifecycle rules for logs over 90 days old.
Replaced environment variables with HashiCorp Vault for database and third-party credentials, and produced the evidence pack used in the annual external audit.
Reduced paging alerts from around 40 a week to 6 by rewriting two noisy checks and adding proper alert thresholds on the rest.

AWS · Terraform · Kubernetes · Argo CD · Vault

DevOps EngineerMay 2019 – January 2022

Greenway Retail Technology · Coventry, United Kingdom

Containerised nine legacy services and moved them from on-premise VMs to ECS, decommissioning two racks of hardware.
Built the first CI pipeline the team had, taking the release process from a shared checklist document to an automated GitHub Actions workflow.
Set up Prometheus and Grafana, and wrote the first four runbooks for the incidents that had previously required a specific person to be awake.

Docker · AWS ECS · GitHub Actions · Prometheus

Platform Projects

Environment bootstrap module

Author

Reusable Terraform module that stands up a complete review environment, including database, secrets and DNS, from a single pull request label.
Used for around 25 review environments a month across four teams.

Education

BSc (Hons) Computer NetworksSeptember 2014 – June 2018

Coventry University · Coventry, United Kingdom

Upper Second Class (2:1)

George Whitmore

Machine Learning Engineer · Model Serving & MLOps

george.whitmore@example.co.uk+44 7700 900965Cambridge, United Kingdomlinkedin.com/in/example-george-whitmoregithub.com/example-gwhitmore

Profile

Machine learning engineer with five years building and operating model-serving infrastructure. Recent work covers a Triton cluster holding p95 inference at 45ms across four models, a drift-triggered retraining pipeline, and a 58% reduction in monthly inference cost through quantisation.

Professional Experience

Machine Learning EngineerJuly 2022 – Present

Fenland Diagnostics Technology · Cambridge, United Kingdom

Moved four models from notebook hand-off to a Triton serving cluster on Kubernetes, holding p95 inference at 45ms for around 700 requests a second with autoscaling on GPU utilisation.
Built an Airflow retraining pipeline triggered by a drift threshold rather than a fixed schedule, with automatic promotion only when the challenger beat the champion on a held-out week of live traffic.
Cut monthly inference cost by 58% by quantising two models to INT8 with ONNX Runtime and moving the smaller one from GPU to CPU instances with no measurable accuracy loss.
Introduced model versioning and one-command rollback after a bad promotion required a four-hour manual recovery; subsequent rollbacks have taken under two minutes.
Share on-call for the inference platform and wrote the runbook covering the three most common failure modes.

PyTorch · Triton · Kubernetes · Airflow · MLflow

Software Engineer (ML Platform)January 2020 – June 2022

Orrell Data Systems · Manchester, United Kingdom

Built the feature store that replaced six duplicated feature pipelines maintained separately by three teams.
Packaged the team’s training code as a versioned library with tests, which took experiment reproduction from "sometimes" to reliable.
Reduced Spark training data build time from 6 hours to 50 minutes by repartitioning and switching to Parquet with column pruning.

Python · Spark · Docker · AWS

Platform Projects

Inference cost dashboard

Author

Internal tool attributing GPU cost per model and per customer, which made the quantisation case measurable and led directly to the 58% reduction.

Education

MEng Computer ScienceSeptember 2015 – July 2019

University of Manchester · Manchester, United Kingdom

First Class Honours

Showing the Full Stack Developer example. All sample details are fictional.

Professions this layout suits

These examples open on Technical by default. You can pair any profession with any template — the suggestion is a starting point, not a restriction.

Full Stack Developer Python Developer Node.js Backend Developer DevOps / Cloud Engineer QA / Automation Engineer Machine Learning Engineer AI Engineer

Guides that go deeper

Choosing a layout settles how the page looks. These settle what goes on it.

How to Write a Software Developer CVWhat technical reviewers look for, why the stack list is not enough, and how to write about work you cannot show.How to List Skills on a CVGroup them, be specific, and cut anything you would not want to be interviewed on for ten minutes.How to Make an ATS-Friendly CVWhat applicant tracking systems do to your file, the four failures that matter, and which of the usual claims about them anybody can actually stand behind.

If this is not the right layout

The layouts a reader of this page most often wants instead, rather than the rest of the gallery in order.

DeveloperA single column with an accented name, heavy header rule and chip-style skill groups.Data ProfessionalA tinted sidebar for tooling and certifications, with the analysis narrative in the main column.Minimal ATSA plain one-column layout designed to survive applicant tracking systems intact.CompactA high-density single column for long histories that need to fit a strict page limit.