Refolk
10 min readMarkdown

Squarespace Wants Player Coaches: Rewrite Your EM Resume to Match

Squarespace, Coinbase and Block now want hands-on player-coaches. Here's how a laid-off engineering manager rebuilds the top third of the resume to match.

If you managed engineers at Squarespace, or at any company copying its move, the postings you're reading now ask for a hybrid your resume doesn't show. A page of headcount and sprint ceremonies now reads like the job that was just cut. On Nov. 2, 2026, Squarespace cut about 300 jobs, mostly in product and engineering, and Anthony Casalena's memo called for "smaller teams, more player coaches, and a simplified organizational structure." The fix goes in the top third of page one, where team size and shipped work need to sit in the same line.

What did Squarespace actually announce, and why does it matter for your resume?

Squarespace cut roughly 300 people, reported as 19% of staff, and described it as a change to how the company is organized, not a cost target. For your resume, that framing matters more than the percentage.

A few details are worth getting right before you repeat them in an interview:

  • The percentage is soft. 300 out of a reported ~1,800 staff is closer to 17% than 19%, and FinalRound notes the pre-cut headcount "has not been settled publicly."
  • It wasn't framed as financial or as AI. Casalena said the cuts weren't tied to a financial target. Neither Squarespace nor The Verge linked them to AI.
  • The runway is real. Severance is at least 16 weeks of base pay plus extra weeks for tenure, and benefits run through May 2027.

Here's what that means for a laid-off engineering manager's job search. The memo said the shape of the job changed, and your resume probably still describes the old shape. Use the first weeks of severance to rewrite the page. Mass-applying with the old one comes later, if at all.

What does a player coach job description ask for?

A player-coach is a manager who still builds. They own part of the technical work while developing the people around them. On a resume, that means three things: a team, a system you own, and evidence of recent hands-on work.

Three companies have now said this publicly:

  • Squarespace (Nov. 2, 2026): Anthony Casalena's memo called for smaller teams, more player coaches, and a simplified organizational structure.
  • Coinbase (May 5, 2026): about 700 cuts (14%), a cap of 5 layers below the CEO/COO, and leaders running 15+ direct reports. Brian Armstrong's model eliminates pure managers. Every leader has to be an active IC.
  • Block (Feb. 2026): headcount fell from over 10,000 to under 6,000. Jack Dorsey and Roelof Botha's model has three roles: ICs, DRIs, and player-coaches who combine building with developing people. A DRI (directly responsible individual) is the one person accountable for a specific outcome.

When you read a player coach job description, translate the phrases into what the hiring manager will look for on your resume:

  1. "Hands-on" or "will write code" means recent commits, PRs, or prototypes, dated within the last year.
  2. "Owns technical direction" means a named system you were accountable for, not a team you "supported."
  3. "Flat org" or "large span of control" means a team-size number. At Coinbase, that number is 15 or more.
  4. "Raises the bar on quality" usually means code review and design review. Put a number on how much you did.

How many engineering managers look like player-coaches on paper?

Almost none. In Refolk's index of professional profiles, 43,107 US profiles hold an "Engineering Manager" title, and only 345 carry an explicitly hybrid title such as Tech Lead Manager, Hands-On Engineering Manager, or Player Coach. That's 0.8% of the pool.

SegmentUS profiles / shareSource
"Engineering Manager" title43,107Refolk's index
Hybrid titles (TLM / Hands-On EM / Player Coach)345Refolk's index
Hybrid as share of EM pool0.8%Derived
EMs per hybrid-titled profile~125 : 1Derived
EM headlines matching "player coach hands-on"0Refolk's index
EMs doing hands-on work, 2025 → 202620% → 35%LeadDev survey

Read the last row against the rest. In LeadDev's surveys, the share of engineering managers doing hands-on work went from 20% in 2025 to 35% in 2026. On profiles, under 1% show it in the title and none show it in the headline. What managers actually do and what their profiles say have drifted far apart.

0.8%
Share of US engineering-manager profiles with an explicitly hybrid title

345 of 43,107 profiles in Refolk's index, while a third of managers report more hands-on work.

The reason is simple. "Player-coach" is an employer's word, not a candidate's word. Three CEOs used it in memos. A headline keyword search across US EMs in Refolk's index for "player coach hands-on" returned zero matches.

The closest title that already exists is Tech Lead Manager (TLM), a role that combines a team's technical lead with its people manager. Nearly all of the 345 hybrid profiles use it, and Google (6) and Meta (3) top the 25-profile sample. If you weren't at one of those companies, don't make the title up. Describe your role the way a TLM's is scoped: one owned system plus one team.

The cost of getting this wrong is invisibility. A recruiter or matching tool searching for posting language like "hands-on" or "player-coach" pulls up almost nobody, and a displaced manager whose headline matches 43,000 others is easy to scroll past. That's not a judgment on your skills. Your profile doesn't use the words they're searching for.

The upside: a pool that looks this uniform is easy to stand out from. Two lines of honest, evidence-backed hybrid language move you out of the 43,107 and toward the 345.

Is moving to a hands-on role a step down?

No. At Coinbase, a player-coach carries 15+ direct reports and does IC work, so the scope is bigger than a pure manager's. The resume shouldn't choose between leading and building. It should show both in the same line.

The old idea that going back to coding is a demotion is already outdated. Block went through this a year before its 2026 restructuring: in March 2025 it cut 80 managers and moved 193 managers into IC roles.

193
Managers Block moved into IC roles in March 2025

The move that used to look like a demotion became a standard reorg step a year before Block's 2026 cuts.

The people doing the hiring feel it too. LeadDev's 2026 Engineering Leadership Report surveyed 600 leaders: 37% are doing more hands-on technical work than a year ago, and one in three managers is considering going back to IC. The manager reading your resume may be making the same move.

If you're going fully back to IC

An engineering manager back to IC resume should lead with systems, not people. Make your most recent role's first two bullets about architecture you designed or code you shipped. Then keep management as a single line of scope ("led a team of [N] while owning [system]"). Don't delete it. Hiding years of management leaves an unexplained gap, and the leadership line is part of what separates you from other IC applicants.

How do you rebuild the top third of a player-coach engineering manager resume?

Rewrite the headline, summary, and first role so every block pairs team size with a system you owned and dated hands-on work. Nothing in the top third should be about ceremonies.

Work through it in this order:

  1. Headline. Keep the title you actually held and add the scope: "Engineering Manager (hands-on), Payments Platform." Use "player-coach" in the summary, where you can back it up with evidence, rather than in a title you never held.
  2. Summary (two to three lines). One sentence each: team size and seniority mix, the system you owned, and what you built or reviewed in the last 12 months.
  3. First bullet of your latest role. Team and shipped outcome in one line. This is the most important line on the page.
  4. A review-and-design bullet. Count design docs authored, PRs reviewed, and incidents you led technically.
  5. One bounded hands-on bullet. A specific contribution you wrote, including AI-assisted work, with its scope stated plainly.

Here's what that looks like in practice (fill in your own numbers; the brackets are placeholders):

Before (reads like the cut role)After (reads like a player-coach)
Managed a team of [N] engineersLed [N] engineers while owning the [checkout API]; shipped [outcome]
Ran sprint planning and standupsReviewed [N] PRs/quarter; set API design standards for [system]
Hired [N] engineers in 2025Hired [N] engineers and onboarded them onto [system] I designed
Partnered with product on roadmapBuilt [migration tool] with AI-assisted code; cut [task] from [X] to [Y]

What to cut

  • Agile ceremonies listed as achievements (standups, retros, sprint planning).
  • Headcount bullets that don't mention what the team built.
  • "Fostered a culture of" lines that don't say what changed.
  • Long lists of project-tracking and HR software in your skills section.

What to keep

  • Team size and span, always attached to an owned system.
  • Hiring, but tied to what those hires shipped.
  • Performance and promotion outcomes, in one line, lower on the page.
  • Incident command and architecture calls, which are hands-on work.

Postings use this vocabulary inconsistently. A Coinbase-style posting cares about span of control. A Block-style one cares about DRI ownership. So the right first line changes from application to application. That's the work Refolk takes off you: I start from your own history, and when you paste a posting, I hand back your resume rewritten for it, with the leading bullet chosen for what that employer emphasizes. The fit score also tells you how well your actual history matches a "player-coach" posting before you spend an evening on it.

How much coding should you claim?

Claim enough to prove you can still build, and not so much that you look like the team's bottleneck. One or two owned systems plus a bounded set of AI-assisted contributions reads better than "wrote 40% of the codebase."

The risk on the other side is real. Engineering leaders writing in LeadDev warn that a manager who becomes the team's top coder creates "bus factor one" risk. Bus factor is the number of people who would have to leave before a project stalls. A manager who writes most of the code pushes it to one, and hiring managers will probe for that in the interview.

A few points about where the hands-on time actually goes:

  • Code review counts. LeadDev's survey measures time spent on coding and code review. One practitioner describes much of managers' renewed technical work as "informed review and technical arbitration than authorship." If you had few commits but real review and design ownership, quantify that.
  • It varies by level, but less than you'd think. The share spending more time on coding and code review: tech leads 41%, managers of engineers 31%, managers of managers 30%, CTOs 44%. Managers of managers sit one point behind front-line managers, so a senior resume still needs a technical line.
  • Scope it like a practitioner. LeadDev's Ferit Topcu was told during his probation check-in that coding was "not optional." His approach: fix small unplanned work himself with AI tools and leave roadmap work to the team. That makes a credible resume bullet.
  • Lead with impact through people. Emma Bostian, an engineering manager at Spotify, argues AI lowered the barrier to coding, but a manager's impact still comes from empowering the team. Your bullets should show both.
Show one system you own and one thing you shipped. Two credible lines beat a claim to be the team's best coder.

Expect the interview to probe sustainability. The same LeadDev report found 45% of leaders working longer hours and 41% saying team motivation is down. If someone asks how you split your week, have a real answer ready, such as a fixed percentage of time for review and a rule for which tickets you take.

FAQ

What is a player-coach engineering manager?

A player-coach engineering manager leads a team while still doing technical work: owning a system, reviewing code, and shipping some of it. Squarespace, Coinbase, and Block have all said publicly that they want leaders built this way. At Coinbase it comes with 15+ direct reports and a requirement that every leader be an active IC.

Should I put "Player Coach" in my job title?

No, unless it was your actual title. Refolk's index found just 345 US profiles with a hybrid title, mostly "Tech Lead Manager," and none with "player coach hands-on" in the headline. Keep your real title, add "(hands-on)" plus your system scope, and use the phrase "player-coach" in your summary with evidence behind it.

How do I show hands-on work if I barely committed code last year?

Count what you did do: PRs reviewed, design docs written, architecture decisions you made, and incidents you led technically. LeadDev's survey treats code review as hands-on work. Then add one small, recent project you built yourself, AI-assisted is fine, so the claim is current and verifiable.

Are a third of engineering leaders really deeply hands-on now?

Not exactly. The widely quoted figure is LeadDev's finding that 37% of 600 surveyed leaders are doing more hands-on work than a year ago. It doesn't measure how many are deeply hands-on. The firmer number for managers is that the share doing hands-on work rose from 20% in 2025 to 35% in 2026.

The data behind this

Put this to work

Paste your career in once. Every application after that is written for you.

Drop a resume or a LinkedIn URL. I rank the live openings against it, rewrite the resume and write a cover letter for the best of them, and fill in the employer's form when you press the button. You read, you decide what goes out.

  1. 01Drop your resume

    A PDF or a LinkedIn URL. About a minute, once.

  2. 02I rank the openings

    Every weekday morning, the live catalog scored against your history. Up to 20 worth your time, not two hundred links.

  3. 03Each one is written up

    Resume rewritten for the posting, a cover letter, a fit score. Press send, or let me fill in the form.

  • New matches ranked and written before you are up.
  • Every bullet stays inside what your history supports. Nothing invented.
  • Queued, submitted, interviewing, offer: one screen, not a spreadsheet.

Free, no card. Up to 25 applications sent a week, and nothing is sent until you say so.

Keep reading