Maya took the job.

She started on a Monday in March. By Friday, she had taken the Work Style Assessment. Her results were clear: the role was structured for an Operator, and Maya was a Builder. Her note afterward: "The assessment basically described everything that felt off. I just wish I'd done it before I signed."

The role wasn't misrepresented, exactly. But job descriptions are written by people who want you to say yes. They're marketing documents. And like all good marketing, they use language that feels specific while telling you almost nothing.

The Translation Table

Here's what the standard phrases actually mean in practice — especially at startups and fast-growing tech companies, where Maya's new employer lived:

What the JD says
What it usually means
"Fast-paced environment"
Priorities change frequently. Expect to restart work you've already done. There may not be a defined process for deciding what matters most this week.
"Self-starter"
Management bandwidth is limited. You will need to find your own direction, generate your own feedback, and advocate loudly for your own work to get resources.
"Wear many hats"
The role is not well-defined. Your responsibilities will expand into whatever gaps exist. Expect scope creep to be a feature, not a bug.
"Collaborative culture"
Decisions involve a lot of people. Alignment takes time. Individual autonomy may be lower than it appears.
"High ownership"
You will be accountable for outcomes you don't fully control. The question is whether you also have the authority that should come with it — often, you don't.
"Scrappy team"
Lean resources, limited tooling, and a general expectation that you'll figure things out without much support infrastructure.
"Passionate about our mission"
The work may not always be intrinsically rewarding. The expectation is that belief in the mission compensates for that. Sometimes it does.

None of these phrases are lies. Some of them describe environments that genuinely suit certain people. The question isn't whether the phrase is accurate — it's whether what it describes matches how you actually work.

What Maya Found on Day One

Maya's new job description had said "high ownership" and "moves fast." She'd told herself she could handle that. She'd handled ambiguity before.

But there's a difference between the kind of ambiguity that comes from building something new — where you get to define the shape of the work — and the kind that comes from an organization that hasn't figured out what it wants yet. The first kind energizes builders. The second kind exhausts everyone.

"There was a roadmap. But by Wednesday, the founder had already had two meetings that changed it. No one told me. I found out in standup."

By the end of week one, Maya had identified something important: the role wasn't asking her to build. It was asking her to react. Quickly, confidently, with a smile — but react. Her job was to execute someone else's shifting vision, not to drive her own.

That's not a bad job. Some people are wired for that and they're excellent at it. Maya was not one of them. And she hadn't known it, because no one had ever asked her to think about it that way.

A note from Clarisa: Before accepting any offer, try this: take every phrase in the job description and ask "what would a bad day look like if this were true?" Fast-paced? A bad day is rerailing work you finished last week. High ownership? A bad day is being blamed for something you had no control over. If the bad day sounds familiar — like something that has already worn you down before — pay attention to that.

Three weeks in, Maya wasn't thinking about the job description anymore.

She was thinking about herself.

Tomorrow: Three months in, the role was objectively fine. The team was good. The product was interesting. So why was Maya dreading Sunday nights?