skip to content
← cd ../projects

~/projects/project-one $ cat README.md

[Project One]

[One sentence: what it is, who it's for, and the headline result.]

role
[Lead backend engineer]
timeline
[X months, 20XX]
team
[Solo / team of X]
project-one/app — main screen
[hero screenshot]
[X%][What improved, e.g. faster page loads]
[X][What grew, e.g. active users]
[$X][What it saved, e.g. monthly cost]

The problem

[What was broken, slow or missing, and who it affected. Two or three sentences with the context a reader outside the company needs.]

[Why it mattered: the cost of leaving it alone, in time, money or users.]

My role

[What you personally owned versus the team. Be specific: “I designed the data model and built the sync service.”]

Approach

[How you tackled it, in plain language. Walk through the architecture at a level a hiring manager can follow.]

architecture.svg
[architecture diagram]
[One-line caption explaining the diagram.]

Key decisions

  • [Decision one, e.g. chose X over Y]

    [Why, and what you gave up in exchange.]

  • [Decision two]
    [Why, and what you gave up in exchange.]

Results

[What changed after launch, with the numbers from the cards above and how you measured them.]

[What you’d do differently next time. One honest sentence here builds a lot of trust.]

  • --react
  • --node
  • --postgres
  • --aws

Want something like this built?

Tell me about your team or project.

get in touch

Command palette

esc
# pages
cd ~/
cd projects/projects
cd resume/resume
cd services/services
cd about/about
cd contact/contact
cd uses/uses
# projects
open [Project One]/projects/project-one
open [Project Two]/projects/project-two
open [Project Three]/projects/project-three
# actions
./download-resumepdf
toggle themedark / light
copy emailevanreynolds95@proton.me
email memailto
open github↗
open linkedin↗