The Frontend Role I Didn't Apply For
I was hired to build UI. I ended up translating ambiguity, closing decision gaps, and learning that this quiet glue work is a form of leadership.
I was hired to build interfaces. Somewhere along the way, I became the person who turns fuzzy requests into shippable decisions. A missing state, a half-finished design, a requirement no one wrote down yet. The work still has to move, so it moves through frontend.
There is a cost to being the glue. The context switching is constant, the accountability is implicit, and the most important work rarely maps cleanly to tickets. You become the person who will "just figure it out," and if you are not careful, that sentence becomes your whole operating model.
What changed for me was simple: less hero mode, more structure. Write the open questions early. Add constraints on purpose. Use placeholders and previews to create momentum before everything is perfect. Over time I realized this is leadership, just quieter leadership: not "I will fix everything," but "I will make this easier to ship for everyone after me."