issue 01 portfolio open to work
Junior software developer
I build web applications end to end — the database, the server, and the part people actually click. I finished [Your Bootcamp / Degree] in [Year], and since then I've shipped [number] projects on my own: a task tracker with real user accounts, a small booking tool, and a browser game I keep coming back to. I'm looking for a first full-time role on a team that reviews code and lets juniors grow.
Right now I'm strongest in JavaScript and Python, comfortable in React and Node, and I've spent enough time in Postgres to know why a query is slow. What I don't know yet, I'd rather learn on a real codebase than in another tutorial — so if you're hiring, the fastest way to judge me is to read the code in the projects below.
- Looking forJunior / entry-level developer role
- Based in[Your City] · open to remote
- Reply timeWithin a day, usually
issue 01 selected work drag the band →
Projects
Four things I built to learn something specific. Each one has a live link and a public repository, so you can see the code and not just the screenshot. Drag the band sideways to move through them.
-
01
[Project name]
Full stack · solo build
[One or two sentences on what this does and who it's for — e.g. a task tracker where each person signs in and sees only their own lists.]
-
02
[Project name]
Front end · solo build
[What it does, in plain words — e.g. a booking page for a small studio, with a calendar and a confirmation email.]
-
03
[Project name]
Backend · API
[What it does — e.g. a REST API that serves the data behind another project, with tests and documentation.]
-
04
[Project name]
Experiment · browser
[Something small and playful you made for fun — a game, a visualiser, a tool you use yourself.]
Drag sideways to see the rest. Keyboard: focus the band and use the arrow keys.
issue 01 about the long version
How I got here
I came to programming sideways. [One or two sentences about what you were doing before — a job, a degree, a project that got out of hand — and what made you decide to do this properly.] The first thing I built was [something small and slightly embarrassing], and the fact that it worked at all is still the reason I keep going.
Since then I've been deliberate about filling gaps rather than collecting tutorials. When I didn't understand why my app got slow, I learned to read query plans. When I kept breaking things on deploy, I learned to write tests before I pushed. [Add one more specific thing you taught yourself and how.]
What I'm looking for is a team where code gets reviewed, where "I don't know" is an acceptable answer, and where a junior is expected to get better rather than just get through the backlog. I'd rather join somewhere I can stay three years than somewhere that looks good on a CV for six months.
Outside of work I [one honest line — a hobby, a sport, something you read or make]. It shows up in how I build: [one sentence connecting it, or cut this line entirely].
What I'd bring in week one
- Working code, not opinions. I'll read the codebase before I suggest changing it, and I'll ask before I assume.
- Small, reviewable pull requests. I'd rather ship five clear ones than one enormous one nobody wants to read.
- Questions written down. I keep a running list so I interrupt you once with six questions instead of six times with one.
- Honest estimates. If I don't know how long something takes, I'll say so and break it down until I do.
issue 01 word of mouth people I've worked with
What people say
Mentors, teammates and the people whose projects I built. Ask any of them for a longer reference — I'll send you their details.
[A sentence or two from someone who supervised or mentored you — what you were like to work with, what you picked up quickly, what they'd trust you with next. Keep it in their words, not yours.]
[A line from a teammate on a group project — how you handled your part, how you communicated when something slipped, what you were like in code review.]
[A line from someone you built something for — a small business, a friend's side project, a volunteer group. What you understood about their problem and what the finished thing did for them.]
[A line from an instructor, bootcamp lead or course tutor — what you were like in the room, how you asked questions, what you did when you got stuck.]
Every quote here is a placeholder until the person has agreed to be named — replace the text and the attribution, or delete the card if you'd rather keep the page short.
issue 01 tools honest levels
What I work with
No percentage bars. Just what I've actually used to build something that runs.
Comfortable
- JavaScript (ES6+)
- HTML & CSS
- React
- Git & GitHub
- Node.js
Used on real projects
- Python
- Postgres & SQL
- REST APIs
- Next.js
- Docker (basics)
Learning now
- TypeScript
- Testing (Jest, Playwright)
- CI pipelines
- [Whatever you're on this month]
issue 01 contact say hello
Hiring? Start here.
If you have a junior role, an internship, or a contract that suits someone early in their career, I'd like to hear about it. Tell me what the team works on and I'll tell you honestly whether I'm a fit.