Loom · Primly Community

Just finished the Loom PM loop. here's what actually happened

mobile_mara · 4 replies

Did the full PM interview at Loom (post-Atlassian acquisition) about 6 weeks ago. Here's the real breakdown.

Recruiter screen: Pretty standard. They asked why Loom specifically, which is a real question not a formality. I talked about async-first culture and that landed well. Know the product cold.

Product sense: They gave me a prompt about a specific Loom feature and asked how I'd improve it. The catch is they want you to think about async video as a category, not just the current product. I over-indexed on copying Notion and got gentle pushback. The interviewer wanted to see original thinking about communication workflows.

Metrics/execution: Two-part. First half is defining success metrics for a hypothetical launch. Second half is a past-project walkthrough where they dig hard on: what did you actually own vs. what did the team own. Don't fudge this, they notice.

Behavioral: Three Atlassian-style situational questions. Cross-functional conflict, async feedback delivery, something about prioritization under ambiguity. Familiar STAR territory but they probe on the async angle specifically.

One thing that surprised me: the interviewers are really engaged. I expected post-acquisition malaise but the PM team seemed genuinely excited about what they're building inside Atlassian. Make of that what you will.

4 replies

apm_aisha

this is gold, thank you. the "what did YOU own vs. what did the team own" question is one I always mess up. do you have a tip for prepping that without sounding like you're throwing teammates under the bus?

jordan_pm

the framing that worked for me: "I was the decision-maker on X, I was a contributor on Y, and Z was a team call I influenced but didn't own." If you're precise about the scope, it reads as self-awareness not credit-grabbing. the worst answer is vague plurals. 'we shipped, we decided' tells them nothing.

pm_priya

the product sense pushback on copying Notion tracks. Loom has a very particular POV on async video that's not 'make Confluence but with faces.' if you come in with lazy comps they will notice.

recruiter_rita

confirming that behavioral probing on async specifically has been consistent in feedback I've seen from Loom roles placed in the last year. it's a real signal they optimize on, not just a culture fluff question.