I designed and built a personal engineering portfolio website to clearly communicate my technical experience, projects, and leadership roles to recruiters and collaborators. The site prioritizes clarity, speed, and scannability, allowing viewers to quickly understand what I’ve built and the impact of each project.
Rather than functioning as a résumé replacement, the portfolio acts as a technical narrative—showing how my skills evolved across cybersecurity, robotics, and systems engineering.
I thought that as a recruiter, I would like to be able to see all the projects at once. So, I have a page where after clicking on a specific project, there is a summary on top so recruiters don't need to read teh full documentation to understand its value. I designed the portfolio on Google Docs and also documented my project process to have an easier time writing. I thought about writing in the portfolio to be much more in depth in all non-software related information compared to GitHub.
I always have these to make sure my portfolio is skimmable:
- Project abstract or summary
- Links to related files
- Helpful visuals and tables
- Chronological process of project
I used Javascript, ThreeJS, and React so I could use 3D models that I thought would be helpful as visuals. Then, I decided to use Cloudflare pages to deploy the website, which is directly connected to the GitHub repository.
This project significantly strengthened my Linux security, scripting, and systems thinking skills.
- Learned how to deploy and host a production website, including managing builds, updates, and live changes
- Turning local projects into publicly accessible, reliable applications
- Developed hands-on experience with JavaScript, React, and Three.js, using them to build interactive, responsive components and visually engaging project presentations
- Gained a strong understanding of how different audiences scan and evaluate technical content
- Designed layouts and writing styles that communicate value quickly while still allowing deeper technical exploration
- Learned how to write clear, concise technical write-ups that balance accuracy with readability
- Focused on explaining why decisions were made and what impact they had, not just how things were implemented