These days, a web developer is usually expected to be well-rounded and specialize in several aspects of the web. The industry continues to grow exponentially, and anyone involved should know that no one can specialize in all of it. So what do I mean when I say I'm a web developer? Let me start by sharing the more specific web roles I consider myself a good fit for, and why:
Working within a large, established design system meant a different kind of challenge than greenfield work — precision and consistency mattered more than individual creative direction. I built out sections across several product areas (Quest, Quest Accessories, Horizon, Meta for Work, VR for Good, Meta Experiences) using Meta's custom XML/XHP component sets, and carried that same work through oculus.com and portal.facebook.com ahead of their migration into meta.com.
Beyond building, I reviewed sections built by teammates and Meta staff for design adherence, copy accuracy, and code quality — work that required understanding the system well enough to hold others to it, not just follow it myself. I also took on an analytics audit across several meta.com pages: comparing existing event logging against best practices, recommending specific changes, and helping establish clearer standards going forward, which I then implemented once approved.
It was a good lesson in what "quality" means at scale — less about any one page looking good, and more about hundreds of pages staying consistent, accurate, and maintainable over time.












