Why "full-stack developer" doesn’t work as positioning
It describes a category, not a person — dozens of other candidates say the same three words. Replace it with something specific: the stack you are actually strong in, the kind of systems you like solving, and one metric or outcome that proves it (latency cut, users shipped to, scale handled).
What to lead with
- 2–3 shipped projects, each with the problem, your role, the stack, and the outcome — not just a screenshot and a repo link.
- Your actual stack, specific versions and tools, not a generic buzzword cloud.
- How you think — a short note on your approach to code, review, or system design.
- Links that matter — GitHub and one or two things you're proud of, not everything you've ever touched.
FAQ
Do software engineers need a personal website if they have GitHub?
Yes — GitHub shows code without context. A personal website adds the story: the problem you solved, your role, the stack, and the outcome, which is what a recruiter actually screens for.
What should an engineer put on their personal website?
2–3 shipped projects with real outcomes, your actual stack, a short note on how you approach engineering, and links to GitHub — kept to one focused page.
Should I include a blog or just a portfolio?
A portfolio of shipped work with clear outcomes beats a blog for getting hired. Add writing only if you already have strong posts worth linking to.