Technical lead with 9 years of software engineering experience, currently leading a team of 7 engineers building scheduling and dispatch software for field service companies. Delivered a route optimization feature that cut technician drive time by 17% for 1,200 customers. Brings hands-on coding, delivery planning and steady mentoring.
Experience
Technical Lead, Fieldcraft Software (Salt Lake City, UT)
May 2022 – Present
Lead 7 engineers on scheduling and dispatch, planning quarterly roadmaps with product and design
Delivered route optimization with OR-Tools, cutting technician drive time 17% for 1,200 customer companies
Introduced RFCs, pairing rotations and a testing standard that lifted coverage from 45% to 80%
Coached 2 engineers to senior promotions and still contribute 30% of team code reviews
Senior Software Engineer, Bonneville Freight Software (Salt Lake City, UT)
Mar 2019 – Apr 2022
Built TypeScript and PostgreSQL services for load tendering used by 300 carriers
Led the migration from AngularJS to React, completed 2 months ahead of plan
Software Engineer, Alta Health Records (Provo, UT)
Jun 2017 – Feb 2019
Developed patient scheduling features in Ruby on Rails for 400 clinics
Education
B.S. Computer Science, Brigham Young University (Sep 2013 – Apr 2017)
Skills
Languages: TypeScript, Python, Ruby, SQL
Systems: Node.js, React, PostgreSQL, AWS, Google OR-Tools
A strong Technical Lead resume shows the systems you built, the scale they run at, and the measurable effect on speed, reliability or cost. Lead with scope and impact: the size of the systems, budgets or teams you influenced, and the decisions you owned.
Sections, in order
Summary
Experience
Projects
Skills
Education
Length: One page is ideal; two pages are fine with 10+ years of relevant experience.
Summary: Open with your specialty and years of experience, then one or two signature results.
Skills to feature
Programming languages
System design
Cloud platforms (AWS, GCP, Azure)
CI/CD
Testing and code review
Databases and SQL
Observability
Security fundamentals
APIs and integrations
Technical documentation
Example bullet points
Rebuilt the checkout service in Go, cutting p95 latency from 900 ms to 180 ms for 2M monthly users
Introduced contract tests and staged rollouts, reducing production incidents by 45% in two quarters
Migrated 30 services to Kubernetes with Terraform, lowering cloud spend by $250k a year
Tips from recruiters
Group skills by category (for example "Languages: Go, TypeScript") so recruiters and ATS parsers find them quickly.
Link to a repository, demo or write-up for at least one project you can talk about in depth.
Name the stack inside each bullet; keyword matching happens at the bullet level, not only in the skills list.
Recommended templates
Classic (ATS-friendly): Jake's-style LaTeX classic: small caps and hairline rules
Tech (ATS-friendly): Developer style: mono headings and tags, sans body
Modern (ATS-friendly): Clean single column with accent headings and rules
Technical Lead resume FAQ
What should a Technical Lead resume include?
A Technical Lead resume should show the systems you built, the scale they run at, and the measurable effect on speed, reliability or cost. Use these sections in this order: Summary, Experience, Projects, Skills and Education. Lead with scope and impact: the size of the systems, budgets or teams you influenced, and the decisions you owned.
What is the best resume template for a Technical Lead?
Classic, Tech and Modern work well for Technical Lead roles. They are single-column with standard headings, so applicant tracking systems (ATS) parse them reliably.
How long should a Technical Lead resume be?
One page is ideal; two pages are fine with 10+ years of relevant experience.
Which skills should a Technical Lead put on a resume?
Prioritize the skills named in the job posting. Common ones for Technical Lead roles are Programming languages, System design, Cloud platforms (AWS, GCP, Azure), CI/CD, Testing and code review and Databases and SQL.
How do I write strong Technical Lead resume bullet points?
Start with an action verb, say what you did, and end with a measurable result such as latency, uptime and deploy frequency. For example: "Rebuilt the checkout service in Go, cutting p95 latency from 900 ms to 180 ms for 2M monthly users."