RoundHound
?Sign inAccess
Prepare
HomeHomeTargetsTargetsPractice historyHistoryProgressProgress
Get full access?Sign in
Targets/Meta

Content Designer (UX Writing)

Meta · Mid-level / Senior

Research from Sep 63 rounds, none tried
How did it actually go?

Recommended next: your first attempt

Do the Past-work review round.

A complete first attempt shows where you stand before any narrow practice starts.

Set up this round →Rehearse the full day
Length40 min · Mid-level / Senior level

The loop

3 rounds · 2 h

Pick a round to see what it asks of you and where you stand on it.

Past-work review

Present your own work as a decision narrative that makes personal ownership, craft choices, evidence and learning easy to examine.

Portfolio review · 40 minSet up this round →
Not tried yetNo attempt yet.

What strong sounds like

  • Separate your decisions and constraints from the team’s work, with a clear user and business problem.
  • Walk through alternatives and concrete changes to the experience, showing why the final choice fits the need.
  • Connect research or observed results to decisions and distinguish measured impact from assumptions.
  • Explain disagreement, your response and a specific lesson that changed how you work.

Expect to be pushed on

The reviewer challenges whether the result came from your change.
A partner preferred the alternative you rejected.

Shapes of problem you may get

  • Past-work presentation: decisions, craft, partnership and measured impact

How to prepare

  1. 01
    Select two decision-rich projects

    Choose two projects with a clear user and business problem, a major content decision, one discarded alternative, your exact contribution, and evidence of the result.

    Reported Meta process experience highlights past-work storytelling about context, decisions, results, and stakeholder friction. Current process details remain uncertain.

    Company researchStorytelling in Meta’s past-work interview

  2. 02
    Rehearse ownership and learning

    For each project, outline your role, constraints, disagreement, response, final trade-off, measured result, assumption, and one behavior that changed afterward. Briefly rehearse one explanation.

    Content design at Meta includes language, structure, timing, accessibility, and product collaboration. These areas help you explain more than visual or feature details.

    Company researchGet to know Susie: Content Design at Meta

Then try the round

You have two project outlines with ownership, alternatives, evidence, disagreement, and learning clearly marked, plus one concise explanation ready to test.

Resources to focus on
  • Get to know Susie D., Head of Content Design and Accessibility, Meta

    Focus on “What is the role of content design at Meta?” and “Where does accessibility fit into design?”

    Use the role context to identify language, structure, timing, accessibility, and audience choices in your examples.

  • Content Design Portfolio | Natalie Sacks

    Focus on “MY ROLE,” “THE PROCESS,” “THE SOLUTION,” and “THE OUTCOME.”

    Use its case-study structure to check that your ownership, constraints, trade-offs, and results are easy to follow.

Do

  • Choose work with important decisions you can reconstruct.
  • Explain one discarded alternative and why it lost.

Avoid

  • Do not give a feature tour without a problem and outcome.
  • Do not claim a team result without explaining your contribution.

A first attempt takes the full 40 minutes.

What this loop tests

Researched 27 days ago

Prepare to explain past work, write a clear product flow and defend decisions with cross-functional partners. Official Meta content-design accounts emphasize language, structure, accessibility and experimentation; candidate reports support portfolio and writing assessment. Current public evidence does not establish a universal loop. The three 40-minute rounds here are compact practice adaptations, including a live writing exercise in place of any recruiter-specified advance assignment.

They reward

  • Make the user’s next action clear.
  • Keep consequences and product behavior accurate.
  • Build inclusive language into the flow.
  • Connect content decisions to evidence.

What to avoid

  • Do not give a feature tour without a problem and outcome.
  • Do not claim a team result without explaining your contribution.
  • Do not hide a consequence behind cheerful tone.
  • Do not use testing language without a task or decision to evaluate.
  • Do not cast a teammate as the obstacle without their perspective.

How sure we are

Worth redoing if you hear something from the recruiter that contradicts this.

Confirmed · 4
  • Meta’s content-design account describes language, voice, tone, structure and timing as part of product design.
  • The official account connects content decisions to accessibility and a broad global audience.
  • A candidate who completed a Meta content-design process describes a past-work interview and storytelling about decisions and results.
  • Historical Meta candidate reports include a UX writing test and questions about work and stakeholders.
Likely · 3
  • Public evidence reviewed does not establish the current order, timing or take-home versus live format of a complete Meta content-design loop.
  • A 40-minute written flow is a bounded practice adaptation for content judgment, not a claim about Meta’s current test duration.
  • Prepare context, alternatives and outcome evidence so partners can evaluate the reasoning behind concise interface language.

Worth asking them

Questions that close the gaps above.

How early do content designers join problem framing?
How does the team evaluate content beyond conversion metrics?
Which localization and accessibility partners shape the work?

Research status

Collected Sep 6. If the recruiter tells you something this brief contradicts, correct it after the interview and the brief updates.

Correct this brief

Attempts

Every session saved against this target, newest first. Standings live on the round cards.

All attempts in History →

Past-work review, UX writing exercise, and Cross-functional partnership have no attempts yet.