About five months into the new role, Maya got a LinkedIn message from a recruiter. Senior PM at a well-funded Series C. Strong engineering culture. Remote with quarterly offsites. The job description used the phrase "deep ownership" — which, by now, she knew to investigate rather than take at face value.

Her question, when she shared it: "How do I actually know this time?"

That's the right question. And it has an answer — but it requires knowing yourself first.

Most people evaluate job offers by researching the company. They check funding, read Glassdoor, look up the leadership team on LinkedIn. These things matter. But they tell you whether the company is a good bet — not whether the role is a good fit for how you work.

Here's the framework. It's organized around the six dimensions of work style that drive satisfaction or misery in any role, regardless of company quality.

The Six Questions That Actually Matter

1. Ambiguity — How defined is the work?

"Can you describe what my first 90 days would look like in concrete terms? What would I be expected to have shipped or decided?"
If they can answer this specifically, the role has structure. If they give you a vague answer about "getting up to speed" and "exploring priorities," the ambiguity is real — and you need to decide if that energizes or drains you.

2. Decision Authority — Who actually decides?

"Walk me through a recent product decision. Who proposed it, who debated it, and who made the final call?"
This question reveals the real decision structure — not the org chart, not the job description. If the answer involves the founder weighing in on most things, that's useful information. If PM decisions are genuinely made by PMs, that's also useful information.

3. Autonomy — How much of the work is solo vs. collaborative?

"On a typical week, how much time is this person in meetings vs. doing independent work?"
There's no right answer — there's only your answer. Some people do their best work in deep collaboration. Others need significant stretches of uninterrupted solo time. Know which one you are, and listen carefully to what the role actually requires.

4. Pace — What does urgency look like here?

"What's the most recent example of something that changed direction unexpectedly? How was that communicated and managed?"
This tells you how the organization handles pressure and change — not how they aspire to, but how they actually do. Maya's startup had answered "fast-paced" on the JD. What they hadn't said was that "fast-paced" meant the roadmap changed without notice every time the founder had a new meeting.

5. Improvisation — Is the work defined or invented?

"Does this role have established processes, or is building the process part of the job?"
Some people are energized by creating systems from scratch. Others do better work when the systems exist and they can optimize within them. Neither is a weakness — they're just different work styles. This question cuts through vague claims about "ownership."

6. Independence — How much support and interaction is expected?

"How does the team usually communicate? Is this person expected to be responsive throughout the day, or is async the norm?"
Communication style is a proxy for how much constant interaction the role requires. Constant Slack responsiveness and a culture of quick alignment meetings suit some people perfectly. Deep-focus workers find it death by a thousand pings.

How to Use the Answers

The goal isn't to find a role where every answer is perfect. It's to go in knowing where the friction points are — and deciding consciously whether you can live with them.

"I didn't know what questions to ask because I didn't know what I needed. Now I do. That changes everything."

Maya went through this process before her next interview. She came back with notes on all six dimensions. Two of them were yellow flags — the pace was going to be fast, and decisions involved more stakeholders than she'd prefer. But three of them were genuinely aligned: real ownership of a defined problem space, deep solo work time built into the culture, and a team that preferred async communication by default.

She made a conscious choice, not a hopeful one. There's a difference.

A note from Clarisa: The best job interviews are the ones where you are also interviewing them — not aggressively, but genuinely. A hiring manager who can't answer "who made the last major product decision?" is telling you something important. A team that looks uncomfortable when you ask about pace is also telling you something. The information is there. You just have to ask.

Maya did something else before her next interview. She took the Ask Clarisa Work Style Assessment — properly, this time, without trying to answer the way she thought she should. The report confirmed what she'd already come to understand, but in sharper language. It also generated a fit report directly against the job description she'd pasted in.

The fit level came back: Good Fit with one significant watch item.

She knew exactly which one it was. She asked about it directly in her final interview. And the answer they gave her was the right one.

Tomorrow: Maya turned down the first offer. Then she found the right one. How it ends.