junior software developer · open to work
I'm a junior developer looking for my first full-time role. I came to this work the long way round — I learned to code by rebuilding things I already used every day, then by breaking them and having to fix them. What I can offer a team right now is not years of experience; it's a habit of finishing what I start, reading the error message properly, and asking for help before I've burned a day on the wrong problem.
Everything on this page is something I actually built and can walk you through line by line. I've written down what each project does, the part that was hard, and what I'd do differently — because I'd rather you judge my thinking than my screenshot.
If you're hiring for a junior role, or you just want to talk about a project, the fastest way to reach me is at the bottom of this page.
Four projects, newest first. Drag the row sideways to see them all — or use the arrows if you're on a keyboard.
01
[solo build · 6 weeks]
[One or two sentences on what this does and who it's for — e.g. "A tool that tracks which of my plants need watering and texts me when I forget."]
The hard part: [the one problem that took you longest — a bug, a design decision, a thing you had to learn from scratch]
02
[team of 3 · 4 weeks]
[What it does, in plain language. What you'd say if a friend asked what you built.]
The hard part: [something you got wrong first and fixed — that's the interesting bit]
03
[coursework · 2 weeks]
[What it does. If it's a learning project, say so — that's honest and it reads fine.]
The hard part: [the thing that made you read the docs three times]
04
[weekend build]
[The small one you built for fun. These are often the most convincing — they show you build without being told to.]
The hard part: [what surprised you]
The honest version, written for someone deciding whether to put me on their team.
[List the languages and frameworks you'd actually be comfortable being handed a ticket in — not everything you've touched once. e.g. JavaScript, Python, React, Node, PostgreSQL, Git.]
I'd rather be honest about the edges of this list than pad it. If something isn't here, I'll say so in an interview and then go learn it.
I read the whole error message before touching anything — most of the time the answer is in the part I skipped. Then I shrink the problem until it's small enough to be obviously wrong or obviously right. Then I write down what I tried, so that when I do ask for help, the question is specific.
I've learned that asking at the twenty-minute mark beats asking at the four-hour mark, and that the second one is a habit you have to build on purpose.
[What you're learning right now — testing, TypeScript, a data structures course, a side project. Being mid-something is a good sign; say what it is.]
I keep a running list of things I don't understand yet and work through it in order. Right now the top of that list is [the thing at the top of your list].
Short, because you'll get the rest in the interview.
[Two or three sentences about how you got here — what you did before, what made you start writing code, and what you want to work on. This is the paragraph a hiring manager actually reads, so make it specific to you rather than a list of adjectives.]
[A second paragraph: what kind of team or product you'd like to join, and what you want to be good at in two years. Concrete beats aspirational.]
Outside of code: [one or two real things — a sport, an instrument, a long-running project, a place you go. It makes you a person rather than a résumé.]
Hiring, or just want to ask about a project? Either is fine.
I reply to everything within a day or two. If it's about a role, a link to the posting helps me answer properly.