From ‘Hello world’ to an engineering portfolio
1. Overview
I rebuilt giro-dev.github.io from a placeholder page into an engineering portfolio. The goal was to make my work and experience easy to find.
In this post I will show what changed and why I made these changes.
2. Goal
I wanted to move from a placeholder page to an online profile for applications to Staff Engineer, Principal Engineer, and Software Architect roles in product-led companies.
3. What changed
- Portfolio page — one page with a clear hero, executive summary, core competencies, experience, engineering portfolio, education, and contact details.
- Data-driven content — content is stored in YAML and TOML files, so updates are straightforward.
- Hugo and GitHub Actions — Hugo builds the site and GitHub Actions deploys it continuously.
- Blog section — the site now has a place for ADRs, case studies, and technical notes.
4. Why it matters
Recruiters and hiring managers at companies such as Grafana, Red Hat, IQVIA, or Roche may spend only a few seconds scanning a profile. A focused portfolio shows my architecture, leadership, and real projects in one place.
This gives them a clear reason to continue the conversation.
5. Conclusion
The new site is a better starting point for my next career step. It explains what I do, shows my experience, and gives me space for technical writing.