The hiring process that outlived the problem it was solving
A founder I spoke with needed a senior designer for a specific redesign — six to eight weeks of focused work. By the time they'd written the job description, screened candidates, run interviews, and made an offer, three months had passed. The redesign that prompted the hire had been handled by someone else in the meantime, out of necessity. The new hire arrived to a team that had already solved the urgent problem and wasn't sure what to hand them next.
This isn't a rare story. It's the default outcome of treating every design need as a full-time-hire problem.
The real question isn't "hire or don't." It's "what shape is the problem?"
A full-time hire makes sense when the need is ongoing, broad, and likely to keep generating new work indefinitely — a growing product with a continuous design backlog, a team that needs someone accountable for design decisions long-term.
An embedded designer makes sense when the need has an edge to it: a specific feature, a defined redesign, a stretch of work with a start and an end, even if that end is "and then we'll decide if we continue." The scope is the difference, not the seniority or the quality of work.
What "embedded" actually means (and what it doesn't)
Embedded doesn't mean a freelancer who delivers files over email once a week. It means:
Working on your team's schedule, inside your existing rituals — standups, sprints, reviews
A clear, agreed scope for the engagement, so there's no ambiguity about what "done" looks like
Direct collaboration with your product and engineering team throughout, not just at handoff
Done well, it should feel closer to a temporary team member than a vendor relationship. The output is a shipped feature, not a set of deliverables you then have to integrate yourselves.
What to watch for
Not every "embedded" arrangement is actually embedded. A few signs it's not working:
No real access. If the designer can't join your tools, your standups, or talk directly to engineers, they're not embedded — they're an external contractor with a fancier title.
No defined scope. "Help out with design stuff this month" isn't a scope, it's a source of scope creep and eventual disappointment on both sides.
No handoff plan. If the engagement ends and no one knows what happens to the work, that's a sign the scope was never actually clear.
The test that actually matters
Before choosing between a hire and an embedded designer, ask: is this need going to look roughly the same in six months, or will it have a natural endpoint? If you can picture the moment the work is "done" — a shipped redesign, a validated feature, a month of focused capacity — an embedded engagement gets you there faster, with less risk, and without the multi-month hiring timeline standing between you and the work actually starting.
