A US engineering-heavy SaaS, post-Series A, had been building product without a dedicated designer for 18 months. Their engineering team had shipped functional features, but the product was beginning to feel inconsistent — different patterns for similar interactions, design tokens defined twice in two places, no documented voice for empty states or error messages. They needed a senior UI/UX designer who could speak the engineering team's language: Figma tokens, component libraries, design ops, and version control for design systems. The role was IC, embedded with the engineering team, not in a separate design org.
Designers who can thrive embedded on engineering teams are rare for cultural reasons that aren't well understood. The design industry typically socializes designers into design organisations — design crits, design directors, design ops as a separate function. Engineers expect different things: same Slack channels as the rest of the team, design specs that include component variants for every state (not just the happy path), tokens that compile into code without manual translation, and contributions to the component library that follow the same PR-and-review process as code. Designers who came up in design organisations often experience this as a cultural shock and bounce after 6–12 months. The client's three prior design hires had all left within a year. The CTO had nearly decided to just keep going without a designer when the cost of design inconsistency became measurable: customer support tickets about UI confusion had risen 40% over a year, and two enterprise prospects had cited 'product polish' as a deal-breaker. The next hire had to stick — meaning the screen had to filter for engineering-collaboration aptitude as aggressively as for design quality.
The portfolio review was the key filter. Our senior design recruiter (formerly head of design ops at a SaaS scaleup) reviewed each portfolio with three explicit questions: does this designer have design-system or component-library work in their portfolio? Are the design files structured like engineers would structure code (modular, versioned, properly governed)? Have they ever worked embedded on an engineering team without a design org as a buffer? Of 520 candidates passing the AI scoring, 140 cleared portfolio review on these dimensions. 48 of 140 completed a 4-hour written assignment: audit the client's existing component library (de-identified) and propose a 90-day cleanup plan with specific contribution guidelines. The assignment was a hard cut — most candidates submitted visual redesigns instead of governance proposals. 18 candidates produced governance-first proposals. The live design round (90-minute, paired with our recruiter playing a frontend engineer) was designed to surface design-handoff aptitude: design a single new component, then hand it off as if our recruiter would implement it. The handoff revealed which candidates produced spec-grade documentation versus pretty mockups. 9 cleared. Cultural interview probed engineering-team fit: how would you handle disagreement with a frontend engineer about a component implementation detail? What's your relationship to design crits versus PR review? 4 cleared. Final round (2-hour, with the CTO and the lead frontend engineer) was a paired design+code session: the candidate designed a component and the engineer wrote pseudo-code in parallel, simulating how they'd work together day-to-day. The winning candidate (Pune-based, 7 years experience, previously embedded on engineering teams at two prior roles) shipped the paired session like a normal Tuesday — no design-org-veteran posturing, no resistance to feedback from the engineer.
Offer day 16 at top-of-band. Accepted within 72 hours. Started day 22. The designer's first 90 days focused on three deliverables: an audit of the existing component library with a categorized cleanup backlog, a documented contribution guidelines for engineers to extend components, and shipped revisions of the five components with the most customer-confusion tickets. Customer support tickets about UI confusion dropped 50% in the following quarter. Design-to-ship cycle time halved: features that previously took 3 weeks of design plus 2 weeks of engineering were now shipping in 2 weeks total because the design specs were complete enough for the engineers to start coding the same day. By month six, the engineering team was contributing to the component library themselves (using the designer's documented guidelines) — a pattern the CTO had wanted for 18 months but had never seen materialize. The designer is still with the team 11 months in; converted to full-time at month five with a Lead Designer title. Two enterprise prospects who had previously cited polish concerns signed contracts in the following quarter.
Two-hour call with the CTO + the lead frontend engineer. Reviewed three failed prior design hires (all design-organisation-veterans who couldn't adapt to engineering-team cadence) and the specific design-ops patterns the engineering team wanted.
AI scoring downweighted candidates whose portfolios were purely visual (no design-system or component-library work). 1,721 applicants became 520 after the design-system filter; 140 cleared portfolio review by our senior design recruiter.
48 candidates completed a 4-hour assignment: audit the client's existing component library (de-identified) and propose a 90-day cleanup plan. 18 cleared. Live design round paired the candidate with our recruiter to design and hand off a single component.
Top 4 went to the client. Engineering-collaboration probed by asking each candidate to walk through how they'd onboard with the existing 6-engineer team. Offer day 16. Started day 22.
For embedded-design roles on engineering teams, portfolio review has to filter for design-system work and governance documents, not visual polish. The aesthetic-portfolio candidates who dominate design-org hiring don't thrive embedded on engineering teams — they want crit culture, design direction, and a separation from code review. Filtering them out aggressively at the portfolio stage saves the client interview time. Second lesson: paired design+code sessions in the final round surface the cultural fit signal that interviews can't. Watching a designer work alongside an engineer for 2 hours reveals whether they'll be collaborative or defensive when the implementation reveals ambiguities in the design spec — which is the everyday friction that causes embedded-design hires to fail.