Why this works
Every prospect, every recruit, and every analyst wants to know how you actually build. Most companies show them a logo wall and a sanitized values page. A developer walking through a real architecture decision earns more credibility in five minutes than a quarter of marketing.
Who you'll feature
The engineer who built the thing. Not the VP, not the architect on paper, the person who shipped it.
A peer reviewer or pairing partner who can name the trade-off.
An engineering manager in a one-line framing of why this work mattered.
How to capture it
Open MarketScale → Requests → New Request. Three prompts:
What problem were you trying to solve?
What did you try first that didn't work?
What does the system do today that it couldn't do before?
Have the engineer pair their answers with a screen recording of the codebase, dashboard, or whiteboard.
For a peer-reviewed conversation, use Remote recording so two engineers can debate the trade-off live.
Tighten the brief with AI Writer so the engineer arrives knowing exactly what to demo.
Reuse it (the 1:10 framing)
One engineering spotlight becomes:
A flagship 5-minute deep-dive video.
A 60-second LinkedIn cut showing the trade-off.
An engineering blog post with embedded clips.
A conference-talk submission abstract.
A quote graphic with the "what didn't work" line.
A recruiting asset for engineering hires.
A sales engineer enablement clip for technical buyers.
A diff-and-design slide for analyst briefings.
An onboarding video for new engineers joining the team.
A pinned spotlight on your Channel feed for the engineering brand.
Bundle the assets into a Collection in Ready to Share tagged Engineering, and route any cut through Request Edit Now.
Common mistake
Letting marketing rewrite the engineer's voice. The credibility comes from how engineers actually talk, including the hedge words and the rough edges. Edit for length, not for tone. Writing Edit Briefs That Get Your First Draft Right covers how to instruct an editor without scrubbing the voice out.