Software Developer Intern

This is a short write-up of the work and what it taught me.

The product had not launched. There were already people paying attention - interested customers, people participating, investors - and the company needed a site that turned that attention into momentum toward the product, before there was a product to ship.

I designed and built five pages end to end - Home, FAQ, About, Get Started, and Our Stories. Together they had one job: explain what the company was building and give a visitor a clear next step toward it.

The product's details and go-to-market plan were still being worked out while I built the site. So the pages had to carry a value proposition that could survive the specifics changing under it, and the structure had to make swapping content - copy, sections, the Get Started flow - cheap as things firmed up.

Placeholder routes stood in for the parts of the flow that would become dynamic once the product and its systems existed, so wiring them up later would be a slot-in rather than a restructure.

Rather than style each page as a one-off, I built a set of reusable components the five pages share - a header, a card, a section layout, a call-to-action - defined once and used everywhere.

It sharpened how I turn a design reference into responsive, production-ready UI - working out what the reference is actually specifying across screen sizes, not pixel-copying.

And it was the first time I built a front-end whose job was conversion, not just correctness. A page that renders fine but does not move anyone toward the product has not done its job - a different bar than whether the component works.