Daniel Okafor

Senior Software Engineer

daniel.okafor@example.com · +44 7700 900142 · Manchester, United Kingdom · linkedin.com/in/example-profile · github.com/example

Skills

TypeScript · Go · React and Next.js · Node.js · Docker · Kubernetes · AWS · GitHub Actions · Technical leadership · Mentoring · Incident management

Seven years building high-traffic payment and order services. I work on deployment safety, observability and latency in systems with very little tolerance for error. Have led three teams technically and spend a fair share of my time on code review culture and mentoring.

Work Experience

Senior Software Engineer

March 2022 – Present

Fintech company · Manchester

  • Split the payments service into six microservices; deployment time fell from 45 minutes to 7.
  • Designed a caching layer for an API taking 12 million requests a week; p95 latency dropped from 480 ms to 120 ms.
  • Rebuilt the incident response process; mean time to resolution improved by 38%.

Software Engineer

January 2020 – February 2022

E-commerce platform · Leeds

  • Migrated the order management module to TypeScript; type-related production defects fell 60%.
  • Raised automated test coverage from 31% to 74%; regression rollbacks went from 9 a quarter to 2.
  • Built the autoscaling configuration that absorbed 4× traffic through promotional periods.

Software Developer

July 2018 – December 2019

Technology agency · Sheffield

  • Built React and Node.js interfaces across nine client projects.
  • Created a shared component library that cut new project setup from two weeks to three days.
  • Set up the continuous integration pipeline and removed every manual deployment step.

Interests

Open source, chess, mountain biking

Education

September 2014 – June 2018

University of Manchester

BSc, Computer Science · First Class

September 2012 – June 2014

Sheffield College

Foundation Degree, Web Development · Distinction

Projects

Payments Service Decomposition

Broke a monolithic payments application into six services, using a dual-write strategy for a cutover with no downtime. Deployment frequency went from once a week to six times a day.

Observability Pipeline

Built the distributed tracing and structured logging stack; median time to find root cause fell from 52 minutes to 19.

Certifications

  • AWS Certified Solutions Architect – AssociateAmazon Web Services · 2024-04
  • Certified Kubernetes Application DeveloperCNCF · 2023-09

Languages

  • English · Native
  • French · Proficient
The Software Split template with sample content — shown at true A4 size.

Resume Template

Software Split

Tech stack in a full-width band; a project-led body

Who it suits

  • entry level, mid level, senior roles
  • Applications sent directly to an employer or by email
  • Most kinds of application
Layout
Tech stack
ATS compatibility
Very good
Photo
No photo

Although the page divides into several areas, the sections are built with flex rather than tables and the text layer stays linear, so common parsers take the information in the right order.

There is no photo area; the header stays pure text, so parsers read the name and contact lines without breaking them apart.

Tech stack in a full-width band; a project-led body. The tech stack sits as a full-width band directly under the header, with projects and experience splitting into two columns below. Technical reviewers scan the stack first and look for evidence second; the order follows that habit.

Layout

How the Software Split template is built

Knowing how information sits on the page before you pick a template directly affects how your application gets read.

Tech stack grid

The tech stack sits as a full-width band directly under the header, with projects and experience splitting into two columns below. Technical reviewers scan the stack first and look for evidence second; the order follows that habit.

Typography

Body and headings share one sans-serif family, reading equally cleanly on screen and in print.

Section headings

Section headings are distinguished by weight alone, leaving no decorative element on the page.

Use of colour

Colour appears only in fine rules and headings; the rest of the page stays white.

Density

Line spacing is balanced — the middle ground between readability and fit for most applications.

How skills are presented

Skills are listed on one line separated by dots. It is the safest form for keyword matching.

When not to choose this template

  • Applications where a visual portfolio is expected in the document itself
  • Applications where the employer mandates its own template
  • Very long career histories running past three pages

You can compare the alternatives side by side in the template comparison table.

Recommended for

Roles we recommend the Software Split template for

This layout suits the application processes for the roles below. Each page carries an example resume and tips for that job.

Frequently asked questions

About the Software Split template

Is the Software Split template ATS-friendly?

ATS compatibility for this template is rated “very good”. Although the page divides into several areas, the sections are built with flex rather than tables and the text layer stays linear, so common parsers take the information in the right order.

Does the Software Split template include a photo?

There is no photo area; the header stays pure text, so parsers read the name and contact lines without breaking them apart. If you are applying to employers who expect a photo, pick one of the templates that carries it as part of the design.

Can I change template later?

Yes. The template is only a presentation layer; what you write is stored separately and carries over intact when you switch.

Will the PDF match this preview?

Yes. The preview and the PDF come from the same component: A4 (210×297 mm), accented characters and a selectable text layer are all preserved.

Can I change the colour in the Software Split template?

Yes. The accent colour control in the editor applies to this template too — pick any of the six presets.