Career & Leadership › Career Growth

Glue Work

Essential but invisible work that keeps teams running.

Glue work is the coordination and maintenance work that helps a team function but may be difficult to see in feature counts. Examples include connecting teams, improving onboarding, documenting a fragile process, resolving recurring handoff problems, or organizing a release.

This work can have real impact. A clear runbook may help several engineers respond safely, and a shared interface agreement may prevent repeated integration delays. But glue work can also become invisible labor assigned repeatedly to the same people without recognition or time for their own growth.

Make the outcome visible: describe the recurring problem, what changed, who benefits, and how the work will be maintained. If you are doing a large share of coordination, discuss it with your manager and ask how it fits your role and evaluation. Do not assume that being helpful requires accepting every task that has no owner.

Backend glue work might be stabilizing a deploy path or reconciling service contracts. Frontend glue work could be aligning design tokens or clarifying accessibility ownership. Data glue work often means documenting lineage or repairing a handoff between producers and consumers. If you take on such work, record time spent and outcomes achieved. Ask that it appear in planning and reviews, and rotate it when one person carries it too long.

Managers should distribute this work fairly and include it in planning and recognition. Engineers should connect it to team outcomes rather than presenting activity alone. The goal is not to avoid helping, but to make necessary work sustainable and valued. See promotion, staff engineer, and developer experience.