Product-minded frontend engineer · 2026

LinkSync

Reframed a server-backed preview tool into a static-export friendly case study that still communicates product thinking, SSRF risk awareness, and client-side UX craft.

Problem

The original LinkSync MVP used a Next.js route handler to fetch link metadata, which was useful for a dynamic app but incompatible with a pure static export portfolio.

Approach

Separated the product story from the server implementation so hiring reviewers can still understand the architecture and tradeoffs.
Documented why live metadata fetching belongs on a server, including CORS, user-agent handling, and SSRF guardrails.
Kept the case study honest: the portfolio showcases the MVP design without pretending the static export can run server-side preview extraction.

Outcome

The portfolio remains deployable as static assets while LinkSync becomes a concrete artifact demonstrating product scoping, technical judgment, and security-aware implementation decisions.