Onomondo Β· CSM Round 2 Β· Complete Mastery Playbook

The Full Interview Playbook β€” Pitch, Tasks, STAR & Scripts

Everything you need to stand out elegantly: the 90-second opener, Onomondo intel, interviewer brief, 30 live-test scenarios, 20 behavioural STAR answers, tough-question handlers, salary & permit scripts, and the close.

Quick Jump

Foundation Β· Before the Call
🎯

The 90-Second Opener β€” Memorise This

PitchCritical

Benedicte's first question will likely be "Tell me about yourself." This is the answer β€” written for your career arc. Confident, specific, no apologies.

Your career timeline (visual map)
2017–2020
Dhaka, BAT / Unilever / Banglalink
Customer-first thinking, FMCG rigour, telecom service ops
2020–2024
Saimon Enterprise
Project ownership, multi-stakeholder operations
2024–Now
Netto / Salling Group
Operations leadership in Denmark, customer-facing every day
2025–2026
MSc Roskilde + HubSpot Certs
CSM transition: theory + tooling + commercial frame
The pitch itself

"My background is operations and customer-facing work across two countries. I started in Bangladesh β€” three years across British American Tobacco, Unilever and Banglalink β€” where I learned that operations only matters if it improves the customer's experience."

"I moved to Copenhagen for my MSc in Business Administration & Leadership at Roskilde, and for the last year I've been running operations at one of Salling Group's Netto stores β€” managing a team, owning store performance, dealing directly with customers every day."

"What pulled me towards Customer Success specifically is that it sits exactly at the intersection of what I'm already good at: operations rigour, customer empathy, and stakeholder management β€” but with measurable retention impact on the commercial side. I'm HubSpot Service Hub certified, completing the CRM certification, and I've been studying the SaaS CSM playbook in depth for the last six months."

"Onomondo specifically β€” what caught my attention is that your customer is technical, your product is critical infrastructure for them, and your CSMs need to balance commercial outcomes with deep customer understanding. That's exactly the kind of role I want to grow into β€” and the kind I think I can be excellent at."

Delivery rules: 75–90 seconds total. Slow down on "operations rigour, customer empathy, stakeholder management" β€” those three words are your value triangle. End on Onomondo, never on yourself.
Avoid: Apologising for not having a SaaS CSM title. Never say "I haven't worked in SaaS but..." Lead with what you have, frame what's transferable.
🌐

Onomondo at a Glance β€” Intel Dashboard

IntelCritical

Drop two or three of these facts naturally in conversation. It signals you've done real homework β€” not just read the front page.

βš™ What they do
Software-defined global IoT connectivity. One SIM, one platform, real-time observability. They own the core network β€” they're not just reselling MVNO connectivity. That's the technical moat.
🎯 Who they sell to
Logistics, mobility, EV charging, asset tracking, smart-device OEMs. Buyers are usually product/engineering leaders at series-A through enterprise scale.
πŸ—£ Brand voice
Engineering-first, transparent, no jargon-as-shield. Match this tone β€” be specific, not flowery. They value "the network is software" thinking.
πŸ’° Stage & investors
Scale-up, well-funded (Verdane and others). Scaling international expansion β€” meaning CS hires are about retention & expansion of strategic accounts, not just firefighting.
πŸ₯Š Competitors
Wireless Logic, EMnify, 1NCE, Pelion, Twilio IoT, Telna. Onomondo's edge: core network ownership + observability. Be ready to name 2 if asked.
🧠 Customer profile
Technically sophisticated. They'll push you on technical depth. CSMs need to be substantive β€” light-touch chat won't survive a quarterly review.
What this means for the interview
  1. Don't pretend to be technical β€” but do show technical curiosity. Ask about their network architecture in your questions.
  2. Use words like infrastructure-grade, observability, uptime. Avoid "customer love", "passionate about people" β€” that lands flat.
  3. Their customers are not naive. Position yourself as someone who'll do the technical reading, not someone who'll wing it on charm.
Drop this naturally"What I find compelling about Onomondo's positioning specifically is that you own the core network rather than reselling MVNO β€” that changes what 'customer success' actually means, because you can deliver structural fixes, not just workarounds."
πŸ‘€

The Interviewer Brief β€” Benedicte & Audur

IntelCritical

Knowing the room shapes how you show up. Read these like dossiers, then forget them β€” they should inform your tone, not script it.

BR

Benedicte Ravn Β· Head of Customer Success

The decision-maker. Reads structural thinking. Danish professional norm β€” calm, evidence-based, allergic to hype.
What she's looking for
  1. Can you own a portfolio independently within 60–90 days?
  2. Do you think in metrics (NRR, GRR, ticket aging, adoption) or in vibes?
  3. Will you make her team look good β€” or will she be cleaning up after you?
  4. Are you a believable hire for Onomondo's customer profile (technical, mature buyers)?
What turns her off
  1. Over-confidence. ("I'd transform your CS function in 30 days" β€” no.)
  2. Generic CS clichΓ©s. ("I love helping people.")
  3. Avoiding the awkward bits (permit timing, no SaaS title) instead of addressing them clean.
  4. Filling silence. Danes tolerate pauses; Americans rush to fill them. Don't rush.
A

Audur Β· Likely senior CSM or CS Ops

She'll listen for "day-to-day credibility" β€” would she trust you with one of her accounts on a Friday afternoon?
How to read the room
  1. If they go silent after your answer β€” don't fill it. They're processing. Wait.
  2. If Benedicte asks short, drilling follow-ups β€” she's interested. Stay precise.
  3. If Audur leans in / takes a note β€” you said something useful. Don't oversell what worked.
  4. Match the energy. Calm if calm. Bright if bright. Never higher-energy than them.
Mantra for the room"Calm. Specific. Curious. One second of silence before each answer."
🧭

Your Fit Map β€” What You Have ↔ What They Need

Self-Knowledge

If they ask "why should we hire you over someone with SaaS CSM experience?" β€” this is the map you reason from.

What you bring
Operations supervision (Netto)
Customer-facing every day, Danish context
FMCG + telecom service ops (BAT, Unilever, Banglalink)
HubSpot Service Hub certified + CRM in progress
MSc Business Administration & Leadership
Two-country professional experience
β†’
What Onomondo needs
Owning a portfolio with rigour
Customer empathy without softness
Service-industry instinct + commercial outcome focus
CRM fluency on day one
Strategic framing of customer relationships
Cross-cultural fluency for international accounts
The line that ties it together"What I don't have is a SaaS CSM title on my CV. What I do have is the operational rigour that makes a good CSM, the customer instinct that makes a great one, and the formal CS training to close the gap fast. I'd rather hire someone who already speaks both languages than someone who only speaks one."
Part 1 Β· HubSpot On the Screen (1–18)
1

Read a Customer Record & Tell Me What You See

HubSpotHigh Likelihood
Scenario"Here's a customer account. Take 2 minutes β€” tell me what you see and what you'd do."
What they're testing
Can you interpret data and turn it into action β€” not just read fields aloud?
Company Β· NordicFreight A/S
Last Activity42 days ago
Renewal Date14 July 2026 (58 days)
Open Tickets3 open Β· 1 over 14 days
Email Engagement (90d)0 of last 4 opened
MRR€4,200
Devices Active↓ 18% MoM
Prev CSM note (Mar 14): "Onboarding delays β€” customer raised concern about latency in Germany."
How you tackle it β€” out loud
  1. Start with timing: "Renewal in 58 days and no contact in 6 weeks. That's my first concern."
  2. Stack the signals: "3 open tickets, one aging past 14 days, devices dropping 18% β€” this account is disengaging quietly."
  3. Pull the history: "Previous note shows unresolved latency in Germany. That's likely the root cause of the drop."
  4. State your move: "Tier-1 risk list today. Call the primary contact within 24 hours, formally own the German technical issue with a deadline, and book a renewal QBR for 30 days out."
Say this"I'm not reading fields β€” I'm building a picture. The picture is: a customer with real product friction, no recent advocacy from us, and a renewal clock ticking. That's a save-or-churn account."
2

Build a Customer Health Report from Scratch

HubSpotHigh Likelihood
Scenario"Build me a report that shows portfolio health at a glance."
  1. Top nav β†’ Reports β†’ Create report β†’ Single object β†’ Companies.
  2. Visualization: Table (best for portfolio scans).
  3. Columns: Company, Owner, Last activity, Renewal date, Open ticket count, Email engagement (30d), MRR, Health score.
  4. Filters: Renewal date is within next 90 days AND Last activity date more than 30 days ago.
  5. Sort: Renewal date ascending.
  6. Save β†’ Pin to a dashboard named "My Portfolio Β· Weekly Risk Scan."
Say this"This is the view I'd open every Monday before stand-up. Top 10 rows = phone calls that week. I'd pair it with a ticket-aging report so I'm catching support drift before it becomes a renewal problem."
Power move: Mention you'd add a custom property "Days Since Last Contact" for cleaner sorting across mixed activity types.
3

Log a Customer Call Activity Properly

HubSpotHigh Likelihood
Scenario"You just got off a call where the customer raised a pricing concern. Log it."
  1. Open the Contact/Company β†’ Log activity β†’ Call.
  2. Set Date/time, Direction (Outbound), Outcome (Connected), Duration (15 min).
  3. Associate the call with the right Deal AND Company, not just the contact.
  4. Write a structured note (template below).
  5. Create a follow-up Task linked to the same Deal with a due date.
Call Β· 17 May 2026 Β· 15 min
WHO: Lars MΓΈller (Head of Ops), NordicFreight A/S
CONTEXT: Quarterly check-in, customer raised pricing

DISCUSSED:
β€’ Competing offer from Wireless Logic at ~22% lower €/SIM
β€’ Pain is renewal budget pressure, not product dissatisfaction
β€’ Volume grew 30% this year β€” they want a tiered discount

AGREED NEXT STEPS:
β€’ Volume-tier proposal to commercial by 20 May
β€’ Follow-up call 24 May 10:00 CET

RISK: Medium. Sticky product, but no tiered offer by 28 May β†’ churn risk rises sharply.
Say this"A note isn't a diary β€” it's a handoff. I write so anyone covering this account can be useful within 30 seconds of opening the record."
4

Set Up a Re-Engagement Sequence

HubSpotMedium
Scenario"Customer hasn't responded to 3 emails in 3 weeks. Set up a follow-up plan."
  1. Automation β†’ Sequences β†’ Create sequence.
  2. Day 0: Personal email referencing the unanswered thread. Token: {{contact.firstname}}.
  3. Day 3: Auto-task β€” "Call this contact, mention a specific value point."
  4. Day 7: Low-pressure email β€” "Should I close the loop, or is there a better person to speak with?"
  5. Day 10: LinkedIn touch task (manual β€” never automate B2B social).
  6. Set sending hours Mon–Thu 9–15 CET; exclude weekends.
Say this"After two unanswered emails, I switch channels. If they're opening but not replying, the copy is the issue. If they're not opening, the subject line or sender is. Diagnose before you escalate volume."
5

Set Up a Renewal Deal & Cadence

HubSpotHigh Likelihood
Scenario"This customer renews in 60 days. Stand up the renewal process."
  1. Company record β†’ Deals tab β†’ + Add deal.
  2. Name: NordicFreight β€” Renewal β€” Jul 2026 (always: Customer β€” Renewal β€” Month Year).
  3. Pipeline: Renewals. Stage: Renewal Discovery. Close date = actual renewal date.
  4. Amount = previous ARR + target uplift (e.g., 5%). Note rationale.
  5. Create 4 linked tasks: T-60 kickoff. T-45 QBR. T-30 proposal sent. T-14 final decision.
  6. Tag renewal-at-risk if any health flags exist.
Say this"I never let a renewal sneak up. 90 days out it's on my radar. 60 out, we're having the conversation. 30 out, the proposal is in their hands. The day before renewal should never have surprises."
6

Read a Dashboard & Recommend Action

HubSpotHigh Likelihood
Scenario"Here's a dashboard. Walk me through what you see and what you'd do."
  1. "First I look at risk overlap β€” low activity AND near-term renewal. That's the top of my list."
  2. "Then ticket-volume spikes β€” sudden increases usually signal product friction or onboarding gaps."
  3. "Then usage trends β€” anything dropping 15–20% MoM gets a proactive call before the customer raises it."
  4. "Then what's missing β€” is there a sentiment score? An adoption metric? A last-QBR-date column? Often the biggest insight is what's not shown."
Power closer: "What I don't see here that I'd want to add is X. Do you currently track that elsewhere?" Asking what's missing shows strategic thinking, not operational thinking.
7

Create a Custom Property for Churn Risk

HubSpotMedium
Scenario"We want a way to flag accounts by churn risk. Set it up."
  1. Settings βš™ β†’ Properties β†’ object: Company β†’ Create property.
  2. Group: Customer Success. Label: Churn Risk Score. Type: Dropdown β€” Low / Medium / High / Critical.
  3. Description: "Set by CSM weekly. Critical = active save plan in progress."
  4. Visible in: sidebar, Reports, Workflows.
  5. Build a workflow: Critical β†’ Slack alert to Head of CS + high-priority task on owner.
Say this"A scoring field is only useful if it triggers action. I never create a property without asking β€” what fires when this value changes? Otherwise it's just a dropdown nobody updates."
8

Build a New-Customer Onboarding Workflow

HubSpotMedium
Scenario"Every new customer should get the same start. Build a workflow."
  1. Automation β†’ Workflows β†’ object: Company.
  2. Trigger: Lifecycle Stage = Customer AND Onboarding Status is unknown.
  3. Set Onboarding Status = Kickoff Pending; create owner task: "Welcome email + kickoff call in 3 business days."
  4. Day 7: check kickoff call logged; if no β†’ alert CSM lead.
  5. Day 14: adoption check-in email. Day 30: NPS / feedback ask.
  6. Day 45: set Onboarding Status to Onboarded or Stalled based on milestones.
Say this"The first 90 days predict the next 900. My onboarding flow isn't about ticking boxes β€” it's about catching the customer who isn't activating, while there's still time to course-correct."
9

Filter Contacts by Inactivity

HubSpotMedium
Scenario"Pull me every active customer we haven't spoken to in 30+ days."
  1. Contacts β†’ + Create view.
  2. Filter: Lifecycle = Customer/Evangelist AND Last activity > 30 days ago AND Owner = me.
  3. Columns: Company, Last activity, Last contacted, Email opens 30d, Phone.
  4. Save as "30+ Day Quiet Customers."
  5. Bulk action β†’ create tasks β†’ "Reach out β€” 30+ day silence."
Watch: "Last activity" includes automated emails. If automation is heavy, use "Last contacted" β€” human-logged only.
10

Handle a Service Hub Ticket Escalation

HubSpotMedium
Scenario"Ticket open 9 days. Customer frustrated. Take it from here."
  1. Read every prior reply top to bottom before acting.
  2. Priority = High. Status = Waiting on us. Assign yourself temporarily for ownership.
  3. Internal note: tag support lead + product owner β€” "Now CSM-owned. Need root cause + ETA today."
  4. Pick up the phone β€” don't email. Customers escalate when they feel unheard.
  5. After call: log activity β€” what you heard, what you committed, by when.
  6. Follow-up task for yourself, day after committed ETA.
Say this"When a ticket ages out, silence becomes the problem, not the technical issue. First move is making the customer feel heard, then chasing internal with a deadline I'll own publicly."
11

Merge Duplicate Company Records

HubSpotLower
Scenario"Two records for the same company. Clean it up."
  1. Identify the master (more activity, longer history, correct owner).
  2. On the duplicate β†’ Actions β†’ Merge.
  3. Choose master as primary; resolve property conflicts deliberately.
  4. Re-associate orphaned deals/tickets/contacts before finalising.
  5. Leave a note: "Merged from record ID xxxxx on 17 May 2026. Original creation date preserved."
Never: delete the duplicate. Always merge. Deletion loses associations and audit history.
12

Pull a Renewals-in-Next-90-Days List

HubSpotMedium
Scenario"Show me everything renewing in the next 90 days."
  1. Sales β†’ Deals β†’ switch to Renewals pipeline.
  2. Table view. Filter: Close date next 90 days AND Stage not Closed Won/Lost.
  3. Columns: Company, Amount, Close date, Stage, Owner, Last activity, Churn Risk Score.
  4. Sort by close date ascending. Save view. Pin to dashboard.
Say this"This is the Monday-morning view, paired with my health-risk report. The two together tell me where to spend my week."
13

Set Up an NPS / CSAT Survey

HubSpotLower
Scenario"We want a customer feedback loop. Set up NPS."
  1. Service β†’ Feedback Surveys β†’ NPS.
  2. Send 30 days post-onboarding completion (reuses workflow trigger).
  3. Detractor follow-up: "What's the main reason for your score?"
  4. Promoter follow-up: "What's the one thing we should never change?"
  5. Workflow: Detractor β†’ task on owner in 24h. Passive β†’ next QBR. Promoter β†’ referral / case-study ask.
Say this"A score without follow-up is a vanity metric. The point of NPS is the conversation it triggers."
14

Track Product Adoption Milestones

HubSpotMedium
Scenario"How would you track whether customers are actually using the product?"
  1. Custom Company properties: First SIM activated date, 10 SIMs milestone, API connected y/n, Active devices 30d.
  2. Populate via integration or weekly CSV import.
  3. Workflow: Active devices 30d drops >20% WoW β†’ flag account + alert owner.
  4. Report: First SIM activated >14 days ago AND no second milestone = stuck-onboarding cohort.
Say this"Adoption is the leading indicator. Churn is the trailing indicator. If I'm watching churn I'm already too late β€” so I instrument the early signals."
15

Schedule a Quarterly Business Review (QBR)

HubSpotMedium
Scenario"Set up a QBR with a Tier-1 customer."
In HubSpot
  1. Company record β†’ + Create task β†’ Meeting type β†’ due in 14 days.
  2. Share QBR-specific Meetings link from Sales β†’ Meetings.
  3. Sub-task: "Pull QBR data β€” usage, ticket history, ROI β€” 2 days before meeting."
  4. Post-meeting: log activity with action items + send recap email within 24h.
QBR agenda (memorise)
  1. Their world (10m) β€” what's changed on their side?
  2. What we delivered (15m) β€” usage, ROI, support summary.
  3. What's next from them (15m) β€” roadmap on their side.
  4. What's next from us (10m) β€” product roadmap relevant to them.
  5. Commitments + dates (10m) β€” three each side.
16

Segment Accounts into Tiers

HubSpotLower
Scenario"How would you decide which customers get the most attention?"
  1. Custom Company property: CSM Tier β€” T1 / T2 / T3 / Tech-touch.
  2. Criteria: ARR, strategic logo, growth potential, complexity.
  3. Workflow suggests tier based on rules (e.g., ARR > €50k = T1 candidate); CSM overrides.
  4. Cadence: T1 monthly call + QBR. T2 quarterly call + QBR. T3 semi-annual touch. Tech-touch automated + reactive.
Say this"Equal attention isn't fair attention. The customer driving 30% of revenue and the one driving 0.3% shouldn't get the same cadence. Tiering lets me be intentional about where hours go."
17

Automation: Alert on Old Open Tickets

HubSpotMedium
Scenario"Alert me when a ticket is open more than 7 days. Build it."
  1. Workflows β†’ object: Ticket.
  2. Trigger: Status β‰  Closed AND Create date > 7 days ago.
  3. Action 1: Priority = High. Action 2: Email/Slack ticket owner + manager. Action 3: Task on Company owner.
  4. Re-enrolment OFF.
Detail interviewers love: exclude tickets where Status = Waiting on customer from the trigger β€” don't punish your team for customer delays.
18

Sales Sequence vs. Marketing Email β€” Know the Difference

HubSpotLower
Scenario"You want to send the same email to 50 customers. What do you use?"
  1. Marketing email β€” one-to-many newsletters, product updates, broadcasts. Branded.
  2. Sales sequence β€” 1:1-feeling outreach at small scale (under 50). Comes from your inbox; personal.
  3. Workflow + template β€” when behaviour-triggered (e.g., on milestone hit).
Say this"The question isn't 'what tool can do this' β€” it's 'how do I want the customer to feel when they open this email?' Branded broadcast, or personal note? That answer decides the tool."
Part 2 Β· Beyond HubSpot (19–30)
19

Write a Customer Email After a 4-Hour Outage

BeyondHigh Likelihood
Scenario"Customer's devices were down 4 hours yesterday. Write the email."
  1. Specific times β€” not "yesterday afternoon."
  2. Plain-language cause β€” no jargon shield.
  3. Three concrete prevention steps, not "we'll do better."
  4. Concrete next step β€” two date options.
  5. Personal ownership β€” "I take full ownership," not "we apologise."
Avoid: "We sincerely apologise for any inconvenience." Templated. Lifeless. Tells the customer you're not really listening.
20

Prioritise a List of 8 Accounts

BeyondHigh Likelihood
Scenario"Rank these 8 customers by where you'd spend time this week."
AccountRenewalLast TouchTicketsUsage Ξ”Priority
NordicFreight58 days42 days ago3 open↓ 18%CRITICAL
BalticTel21 days4 days ago0↑ 4%HIGH
DanIoT180 days67 days ago2 open↓ 8%HIGH
CopenhagenLogistics72 days14 days ago1 openflatMEDIUM
NorrlandSmart95 days8 days ago0↑ 12%LOW
OsloCharge240 days30 days ago1 open↑ 22%LOW
HelsinkiAuto33 days20 days ago0flatMEDIUM
StockholmGrid120 days3 days ago0↑ 8%LOW
Frame the ranking"My framework: combined risk = time pressure Γ— engagement gap Γ— negative-signal density. One bad number is fine. Three bad numbers stacked is critical."
21

Role-Play: First Onboarding Call

BeyondHigh Likelihood
Scenario"Pretend I'm a new customer. First onboarding call. Go."
Open with"Thanks so much for taking the time, Lars. Really excited to be working with you. Before I walk you through anything on our side, I'd love to understand your world a bit first. Can you tell me β€” what was the main problem you were trying to solve when you chose Onomondo? And what does success look like for you in the first six months?"
Discovery questions (use 4–5)
  1. "Who else on your team will be using this day-to-day?"
  2. "What's your timeline for the first wave of deployments?"
  3. "What are you measuring internally to know this is working?"
  4. "Where do you think the biggest risk is β€” technical setup, internal adoption, something else?"
  5. "How do you prefer to be communicated with β€” email, calls, Slack, async updates?"
Close with three things
  1. Clear summary of what you heard back to them.
  2. Three commitments β€” one from you, two from them β€” with dates.
  3. Next touchpoint in the calendar before you hang up.
Avoid: Pitching features in the first call. Discovery first. Always.
22

Role-Play: Angry Customer on the Phone

BeyondHigh Likelihood
Scenario"Customer calls furious about being billed wrong. Handle it."
  1. Listen, don't defend β€” let them vent fully. Most angry customers calm in 90 seconds if uninterrupted.
  2. Acknowledge specifically β€” "You were billed €240 over the agreed rate, and nobody flagged it. That's on us, and I understand why you're frustrated."
  3. Own it without overselling β€” "I'm fixing this personally. Here's what I'll do in the next hour..."
  4. Concrete timeline β€” "Answers back to you by 16:00 today." Then beat it by 30 minutes.
  5. Close in writing β€” log call + follow-up email by end of day.
Interview version"My instinct in those calls is to drop the script. Angry customers don't want a process β€” they want a human who'll take it on personally. So I try to be the one human in the chain who says 'I've got this' rather than passing them around."
23

Pitch a Price Increase to an Existing Customer

BeyondMedium
Scenario"At renewal you're raising their price 8%. How do you have that conversation?"
  1. Lead with value, not the number β€” recap the year: usage growth, tickets resolved, value delivered.
  2. Anchor on market & investment β€” "Across our customer base we've added capacity, X feature, improved reliability to Y. To keep investing at that pace, pricing adjusts 8% across the board this cycle."
  3. Frame it mutual β€” "Let's walk through the agreement and make sure the tier matches where you're going next year."
  4. If they push β€” don't break price first. Offer term length, payment timing, service add-on. Discount last, never first.
  5. Always show the alternative β€” what happens if they don't renew. As a real cost, not a threat.
Say this"I never lead with 'we're raising your price.' I lead with what we've done β€” and only then frame the increase as how we keep doing more of it. Price conversations are value conversations in disguise."
24

Build a 30-60-90 Day Onboarding Plan

BeyondMedium
Scenario"What does a great onboarding look like in your first 90 days with a new customer?"
Day 0–30 Β· Setup & Trust
  1. Welcome email within 24h of contract signing. Names, calendar invite, no jargon.
  2. Kickoff call in week 1 β€” discovery + alignment on success definition.
  3. Technical setup tracked weekly. First milestone by day 21.
  4. Stakeholder map: who decides, who uses, who pays.
Day 31–60 Β· Adoption & Habit
  1. Adoption check-in β€” are people actually using it daily?
  2. Identify the internal champion.
  3. First mini-win documented and shared back.
Day 61–90 Β· Value & Expansion
  1. ROI conversation β€” quantify what's been delivered.
  2. First formal QBR with decision-makers.
  3. Set the next 90-day expansion plan together.
Say this"First 90 days is the entire relationship in compressed form. If trust isn't earned in 30, adoption isn't sticky in 60, and value isn't visible in 90 β€” the renewal is already in trouble, you just don't know it yet."
25

Write a Save Plan for an At-Risk Account

BeyondMedium
Scenario"A customer is signalling churn. Write the save plan."
  1. Diagnose the real reason β€” not the cited one. "Too expensive" is usually "we never got value."
  2. Right person in the room β€” decision-maker, not just the user. Bring your manager or their VP if needed.
  3. Concrete offer β€” not vague reassurance. Waived month, dedicated technical session, roadmap commitment in writing.
  4. 14-day re-evaluation β€” "Let's revisit on date X based on what's changed."
  5. Honesty if it's lost β€” leave them as an alumnus who'd come back, not a customer you fought to the last day.
Say this"Saves work when you can credibly change the thing that's wrong. They don't work when you're trying to talk a customer out of a decision they've already made. The first 10 minutes is figuring out which one you're in."
26

Respond to a Cancellation Threat

BeyondMedium
Scenario"Customer emails: 'We're considering cancelling at renewal.' What do you do in the next hour?"
  1. Don't reply by email. Phone within an hour. Speed signals seriousness.
  2. Open: "I got your email and wanted to call rather than write. Can you walk me through what's behind that?" β€” listen 5+ minutes.
  3. Three "and what else" questions before responding. Surface the real reasons.
  4. Don't commit on the call. "I want to come back to you in 48 hours with a concrete plan rather than a half-answer."
  5. Internally: brief your manager, loop product/support, build the save plan. Return in 48h.
Avoid: Discount-first responses. "I can give you 15% off" tells the customer the price was never real. Address the cause first.
27

Run a QBR Live

BeyondMedium
Scenario"Walk me through running a Quarterly Business Review."
  1. 00:00–10:00 Β· Their world β€” "Before we dive in, what's changed on your side since we last met?"
  2. 10:00–25:00 Β· Our delivery β€” usage, value, support summary. Data, not adjectives.
  3. 25:00–40:00 Β· Roadmap exchange β€” map our roadmap onto their priorities visibly.
  4. 40:00–55:00 Β· Risks & opportunities β€” honest conversation about friction.
  5. 55:00–60:00 Β· Commitments β€” three each side, owners, dates. Recap email within 24h.
The QBR test: if the customer can't name three things they got from the hour, the QBR failed. It's their meeting, not yours.
28

Spot & Pitch an Upsell / Cross-Sell

BeyondLower
Scenario"Customer using 60% of plan. Turn it into an upsell."
  1. Open with their growth β€” "Your active SIMs grew 40% since January. Strong year."
  2. Surface the natural ceiling β€” "At current pace, you'll hit plan ceiling around September. I want to plan rather than surprise you mid-deployment."
  3. Present 2–3 options β€” "Stay + overage, move tier with headroom, or restructure to volume tier. Each has trade-offs." Options = agency.
  4. Frame cost of inaction β€” what breaks if no upgrade.
  5. "Let me think" β†’ set next conversation in calendar before hangup.
Say this"Upsell shouldn't feel like a sales call. It should feel like the CSM saw a problem coming and helped them plan. If the customer feels protected, expansion is the natural outcome."
29

Handle a Feature Request That Won't Be Built

BeyondMedium
Scenario"Customer wants feature X. Product says no. What do you tell the customer?"
  1. Never blame product. Never "they won't build it." Undermines internal trust.
  2. Acknowledge the real need. Feature is surface; problem underneath may be solvable another way.
  3. Probe: "If we had that feature, what would change day-to-day?" Often reveals a workaround we have.
  4. Be honest: "Not on the roadmap for the next two quarters. Here's what we can do instead..."
  5. Real alternative: workaround, integration, custom report, manual help.
  6. Log the request internally. 5 customers asking = product case. You're the voice of the customer, not the wall.
Say this"Honesty buys more trust than vague 'we'll look into it.' Customers respect 'not this quarter, here's the alternative' far more than 'I'll pass it along' which they know means nothing."
30

Explain Your First 90 Days at Onomondo

BeyondHigh Likelihood
Scenario"If we hired you Monday, what would your first 90 days look like?"
Day 1–30 Β· Listen, learn, map
  1. Shadow every CSM, sales rep, support engineer. Sit on calls without speaking.
  2. Read last 90 days of notes for every account I'll own. One-pager per customer.
  3. Map the tech stack: HubSpot setup, product telemetry, ticketing flow, data movement.
  4. Interview 5+ customers β€” not to pitch, but to understand how they see us.
Day 31–60 Β· Pattern-find & structure
  1. Identify top 3 recurring frictions β€” onboarding gaps, ticket types, billing clarity.
  2. Propose one structural improvement to HubSpot β€” small, shippable, measurable.
  3. Own my portfolio end-to-end. First round of QBRs.
Day 61–90 Β· Deliver & advocate
  1. Ship the improvement. Measure. Present results internally.
  2. 3+ product-relevant customer insights back to product team.
  3. Set 6-month goals with manager grounded in what I've learned.
Close with"What I won't do is come in with opinions on day 1. The first month I want to be the quietest person in the room. By day 90 I want to have earned the right to a strong point of view β€” and shipped at least one thing that makes the team's life easier."
Part 3 Β· Behavioural STAR Answers (31–50)
31

"Why Customer Success?"

BehaviouralHigh Likelihood
Answer"Because it's where my three strongest instincts converge. From FMCG and telecom I learned customer empathy. From operations at Netto I learned process rigour. From my MSc I learned to think about commercial outcomes β€” retention, expansion, lifetime value. Customer Success is the role where all three are required at once. Most other roles let you specialise in one. CSM rewards range."
Why this lands: Specific personal arc + a structural reason why CSM (not "I like helping people"). Avoids generic CS clichΓ©s.
32

"Why Onomondo Specifically?"

BehaviouralHigh Likelihood
Answer"Three reasons, ranked. One β€” your product is infrastructure, not a tool. That means customer success is high-stakes and high-trust, and the conversations are substantive. Two β€” you own the core network rather than reselling, which means CSMs can deliver structural fixes, not just workarounds. That's a meaningfully different job. Three β€” you're scaling internationally, which is the phase where CS as a function gets built into something that lasts. I want to be useful in that phase."
Power detail: One Onomondo-specific fact ("you own the core network") signals real homework, not a generic answer recycled across applications.
33

"Why Are You Leaving Netto?"

BehaviouralHigh Likelihood
Answer"Netto has been the right role for the last year β€” it sharpened my operational instinct in a Danish workplace and gave me real responsibility quickly. What it doesn't do is move me towards the commercial side of customer relationships, which is where I want to grow. I've used the time to get HubSpot-certified, finish my MSc, and study how SaaS CS teams operate. Onomondo is where I'd actually do the work I've been preparing for."
Never say: Anything negative about Netto. The interviewer will hear it as "this is how you'll talk about us in two years."
34

Tell Me About a Time You Turned Around an Unhappy Customer

BehaviouralMedium
Situation
At Banglalink, a high-value postpaid customer escalated after three failed billing corrections over six weeks. They threatened to port out and posted publicly.
Task
I picked up the case mid-escalation. The customer no longer trusted email β€” every prior response had failed to resolve it.
Action
I called within two hours, didn't open with apologies β€” I opened by reading back what I understood and asking what I had wrong. I confirmed the actual billing error on the call, committed to a written resolution within 24 hours, and gave them my direct line. I followed up 22 hours later with the fix in writing, copied my manager, and asked a single question: "Did we close this properly?"
Result
Account was retained. Customer renewed for two more years. Public post was edited to thank the team. What I took from it: trust isn't restored by apology β€” it's restored by speed and specificity.
35

Tell Me About a Difficult Colleague

BehaviouralMedium
Situation
At Netto, a fellow supervisor handled stocking on opposite shifts. Our handovers kept missing β€” wrong stock counts, missed reorders, store performance suffering.
Task
I needed to fix the structural issue without making it personal or going over their head first.
Action
I asked for a coffee outside the store. I led with the data β€” "Here are the three reorders we missed this month, and the cost." Then I asked: "What's making the handover hard from your side?" Turned out their shift was getting hit by deliveries 90 minutes earlier than the schedule said. I'd been blaming a person for a process problem. We redesigned the handover sheet and split the count check.
Result
Misses dropped to near-zero in six weeks. Lesson: when something looks like a people problem, it's almost always a process problem.
36

Tell Me About a Time You Missed a Target

BehaviouralMedium
Situation
During my Unilever internship, I owned a category-distribution KPI for a Dhaka cluster. I missed the monthly target by 6%.
Task
I had to present the miss to my supervisor and propose a recovery plan.
Action
Rather than hiding behind external reasons, I broke down where the miss came from β€” three specific outlets that hadn't restocked due to a wholesaler delay I should have flagged earlier. I owned the part that was mine. I proposed a weekly outlet-health check rather than monthly.
Result
Recovered the gap the following month. The weekly check stuck after I left. Lesson: the part you own and the part you don't are both worth being clear about. People respect that mix.
37

How Do You Prioritise When Everything Is Urgent?

BehaviouralMedium
Answer"I run a quick filter β€” three questions. One: what's irreversible if I don't do it today? Two: what's blocking someone else? Three: what's high-value but no one else is watching? Things failing all three drop. Then I do a 'no surprises' check β€” anything where a customer or my manager would be blindsided gets a heads-up note even if the action waits. That separates urgency from importance, and from anxiety."
38

Tell Me About a Time You Had to Push Back

BehaviouralMedium
Situation
At Saimon, a senior internal stakeholder requested a custom report that would have meant reworking a process two days before a client deliverable.
Task
Say no without damaging the relationship β€” or the deliverable.
Action
I didn't say no flat. I said: "I can do this, but the trade-off is the client deliverable slips by two days. Which do you want to prioritise?" That re-framed it as their decision, not my refusal.
Result
They withdrew the request and we hit the client deadline. The next time they had a similar ask, they pre-framed it themselves β€” "I know this might trade off against X."
39

Tell Me About a Time You Were Wrong

BehaviouralLower
Situation
Early at Netto, I pushed for tightening a stock-replenishment process that I was sure would reduce waste.
Task
Get team alignment and roll it out.
Action
I rolled it out. Within two weeks, fresh-produce out-of-stocks went up 11%. The new process didn't account for demand spikes around weekends.
Result
I reverted it, owned the call publicly to my team, and ran the next process change with a one-week pilot instead of a full rollout. Lesson: confidence isn't a substitute for testing. I default to pilots now.
40

Describe a Time You Spotted Something Nobody Else Did

BehaviouralLower
Situation
At Banglalink, customer-service ticket volume looked stable monthly. I noticed a pattern within the data β€” Tuesdays had a 30% spike that averaged out across the week.
Task
Surface a non-obvious pattern that the dashboards missed.
Action
I pulled three months of Tuesday tickets and found 70% related to a weekly automated SMS sent Monday night. Customers were calling Tuesday confused by it.
Result
Reworded the SMS. Tuesday spikes dropped by half. Lesson: averages hide the truth. Look at the shape of the data, not just the totals.
41

Tell Me About a Time You Sold an Idea Internally

BehaviouralMedium
Situation
At BAT, I noticed our trade-marketing tracker captured outlet visits but not whether the visit changed anything.
Task
Convince a senior manager to add an "outcome" field β€” extra work for the field team.
Action
I didn't pitch it as "we should add a field." I pitched it as a one-week pilot, two reps, ten outlets, with a before/after on category performance. I made it small enough to say yes to.
Result
Pilot showed the outlets with outcome-logged visits outperformed by 8%. The field went into the permanent tracker. Lesson: ideas don't win on logic β€” they win on being small enough to test cheaply.
42

What's the Hardest Customer Conversation You've Had?

BehaviouralMedium
Answer"At Netto, a regular customer escalated about a price discrepancy at the till β€” they felt accused when they pointed it out. I'd been the one who set the shelf price wrong. The hard part wasn't apologising β€” it was apologising in a way that didn't sound like a process apology. I refunded the difference on the spot, walked them to the aisle to show them the corrected label, and gave them a small voucher. They've come back every week since. What I took from it: the apology that lands is the one that's specifically about the person, not generically about the policy."
43

Tell Me About a Time You Under-Promised and Over-Delivered

BehaviouralMedium
Answer"At Saimon I owned a vendor onboarding that the team estimated at four weeks. I told the client six. We finished in four-and-a-half. They sent us a referral two weeks later β€” the explicit reason cited was that we'd 'under-promised and over-delivered,' which made them trust the next promise. The lesson stuck: padding estimates is sometimes more respectful than promising aggressively. The cost of missing is much higher than the cost of being slightly conservative."
44

Describe a Time You Went Outside Your Job Description

BehaviouralLower
Answer"At Netto, the store's customer-feedback handling was scattered across the till logbook, the manager's email, and verbal pass-downs. It wasn't anyone's role. I built a simple shared sheet, trained the team to log feedback in 30 seconds, and reviewed it weekly. Within two months we'd resolved three recurring complaints we hadn't known were recurring. Nobody asked me to. But the cost of not doing it was customers re-experiencing the same issues."
45

What Does Excellent Customer Service Look Like to You?

BehaviouralLower
Answer"Three things. One β€” the customer never has to repeat themselves. Two β€” when there's bad news, the person delivering it owns it personally rather than hiding behind 'company policy.' Three β€” the customer ends the interaction knowing what happens next and when. Most service failures aren't about outcome, they're about uncertainty. Removing uncertainty is the actual job."
46

How Do You Keep Track of Multiple Accounts?

BehaviouralLower
Answer"Three structures running in parallel. First β€” a weekly dashboard view filtered by renewal date + activity gap; that drives the Monday plan. Second β€” a per-customer one-pager with last touch, last issue, last commitment; I update it after every interaction. Third β€” a single sheet of open commitments with dates, reviewed daily. The principle is that I never want to wake up and not know who's at risk, who's owed something, or who I haven't talked to lately."
47

Walk Me Through a Typical Day

BehaviouralLower
Answer"Mornings I look at the dashboard first β€” any account that's gone red, any aging ticket, any renewal within 90 days that hasn't been touched. That sets priority for the day. Mid-morning is proactive β€” scheduled calls, QBRs, follow-ups. Afternoon is reactive β€” inbound, escalations, internal coordination. End of day, I close commitments β€” log activities, update notes, queue tomorrow. I try never to leave a day with an open commitment in my head rather than in the system."
48

What Does Success Look Like to You in This Role?

BehaviouralMedium
Answer"At 6 months β€” I own my portfolio, my customers know me by name, my renewal pipeline is clean, and I've flagged at least one structural improvement the team has adopted. At 12 months β€” my NRR for the portfolio is at or above team average, I've expanded at least 2-3 accounts meaningfully, and Benedicte trusts me with a Tier-1 customer without backstop. At 24 months β€” I'm someone the team turns to on hard customer conversations, and ideally I've earned the conversation about what's next."
49

How Would You Describe Your Working Style?

BehaviouralMedium
Answer"Three words: structured, direct, calm. Structured because I think in dashboards and one-pagers rather than memory. Direct because I'd rather have the hard conversation in week one than write the apology in week six. Calm because customer-facing work rewards low reactivity β€” the person whose energy doesn't spike when the customer's does. That said, I'm not rigid β€” I adapt cadence to the customer, not the other way around."
50

Tell Me About Your Operations Role at Netto

BehaviouralLower
Answer"I run shift operations as 1st Assistant β€” that means owning a shift end-to-end: team, customers, stock, store performance numbers. Practically, I'm responsible for a small team on shift, the customer experience at the till, the cleanliness and replenishment standards, and the daily KPIs reported up. What's transferable to a CSM role isn't the retail context β€” it's the muscle of running a small portfolio of responsibilities concurrently, being accountable for numbers somebody else will look at tomorrow, and dealing with customers directly when something goes wrong."
Part 4 Β· Tough Questions (51–60)
51

"You Don't Have SaaS CSM Experience"

ToughHigh Likelihood
Answer"That's right β€” I don't have a SaaS CSM title. What I do have is the underlying muscle: operational rigour from running a Netto shift, customer-facing instinct from years of service work, formal CS training through HubSpot certifications, and an MSc that's been heavily focused on how customer-facing functions are organised commercially. What I lack is product-specific learning curve on Onomondo, and I've thought about how to close that fast β€” shadow first 30 days, customer interviews, deep-read the help center. I'd rather hire someone with structure and instinct and ramp them on the product, than someone with the title and bad habits. I think you'd rather too."
Why this works: You name the gap, frame the strength, and end with a confident proposition. No apology, no over-explanation.
52

"What's Your Biggest Weakness?"

ToughHigh Likelihood
Answer"I default to written communication when high-context conversations would resolve things faster. In operations roles I've leaned on dashboards and shared sheets because they scale β€” but the trade-off is sometimes I should have just picked up the phone. I've consciously worked on it in the last year β€” at Netto I run a 15-minute end-of-shift verbal handover with the next supervisor that I used to do as a written note. The shift-to-shift continuity got noticeably better. I'm not finished on it, but I know what the work is."
Don't say: "I'm a perfectionist" or "I work too hard." Both signal you can't introspect.
53

"Why Should We Hire You Over Someone with SaaS CSM Experience?"

ToughMedium
Answer"Two reasons honestly. One β€” most candidates with the title learnt CS inside one company's playbook. I've come at it from operations and service-industry first, and then formal CS training on top. That mix is rarer, and it shows up in how I think about retention β€” I see it as an operational discipline, not a relationship hobby. Two β€” I'm hungry. Someone three years in is calibrating against their last role. I'm calibrating against what I want to be in five years. That difference will show up in the hours I put into learning the product and the customer."
54

"Where Do You See Yourself in 5 Years?"

ToughMedium
Answer"Five years is far enough that the honest answer is β€” I don't know exactly. What I do know: I want to be in a role where customer outcomes and commercial outcomes are the same outcome. Whether that's Senior CSM, CS lead, or CS Operations depends on what becomes visible in the first two years. What I won't do is plan five years out and then push the role to fit. I'd rather earn the right to the next conversation through the first year."
55

"What If You Fail in This Role?"

ToughMedium
Answer"The risk I see is product learning curve β€” Onomondo's customer is technical and I'd be ramping. The way I fail in that scenario is if I hide it for six months instead of asking for help on day five. So the way I de-risk it is the opposite: regular weekly check-ins with my manager that include 'here's what I don't understand yet.' I'd rather look like I'm asking too much in month one than look fluent and be wrong in month three."
56

"What's Been Your Biggest Professional Failure?"

ToughLower
Answer"At Saimon, I once committed to a delivery date for a client without consulting the team behind it. I wanted to look responsive. The team couldn't hit the date and I had to walk it back β€” which was worse than honestly framing it at the start. The cost wasn't the slipped date β€” it was the trust gap with the client and the friction with my own team. I now have a rule: never commit on behalf of others without checking, even if it costs me 24 hours of looking less decisive."
57

"You've Worked in FMCG, Telecom, Retail β€” Why Not Stay in One?"

ToughLower
Answer"Each step was deliberate. BAT and Unilever taught me how disciplined customer-facing organisations operate. Banglalink taught me what a customer interaction looks like when product reliability is critical. Netto in Copenhagen has been about working inside a Danish operations environment with team responsibility. The variety isn't drift β€” it's been about collecting the components that converge into customer success. SaaS CSM is the role where all of them are required at once. Now I want depth in one place."
58

"Have You Been Rejected From Similar Roles?"

ToughMedium
Answer"Yes. I've applied to several CSM and account-management roles in Copenhagen this year. A few moved forward; some didn't. The pattern I've taken from it: the rejections were mostly on title-fit β€” companies wanting someone already inside SaaS β€” and the ones that moved forward were ones where they cared more about the underlying skill mix. That's exactly why Onomondo is interesting. The role description rewards exactly the mix I bring."
Why honesty works: Pretending you're untested looks naive. Honest framing + a constructive lesson signals self-awareness.
59

"What Other Companies Are You Talking To?"

ToughMedium
Answer"I'm in active conversation with a small number of Copenhagen scale-ups in the CS and operations space β€” I won't name them out of respect for those processes. What I'll be straight about: Onomondo is the role I've prepared most deeply for, and it's the one where the role description maps most directly to where I want to grow. If timing aligns, this is the one I'd want to move forward fastest on."
60

"Do You Have Any Concerns About the Role?"

ToughMedium
Answer"Honest answer β€” two. One is the technical learning curve on the product side. I think I close that with proactive shadowing and customer interviews in the first 30 days, and I'd be asking you what resources you'd recommend. Two is making sure I'm ramping fast enough on the commercial side β€” renewal motions, expansion conversations β€” which is the part most learnable from doing it. Those are the two I'd want to talk through in onboarding rather than discover quietly at month three."
Why this lands: Showing concerns proactively + with mitigations = mature professional. Pretending no concerns = naΓ―ve.
Scripts Β· The Three Conversations That Need Rehearsing
πŸ’°

The Salary Conversation β€” Anchors & Script

ScriptHigh Likelihood

Benedicte said this would come up in the call. Don't volunteer a number first. Anchor to your range, defend it calmly, leave room.

Your salary ladder (DKK, annual)
Floor Β· Walk-Away480,000
Target Zone560,000 – 600,000 + ~15% variable
Stretch620,000 – 650,000 + ~15% variable
Script β€” when they ask first
You Β· Deflection (first move)"Happy to talk numbers. Before I anchor β€” what range have you set for this role? I'd rather not over- or under-shoot what you're working with."
If they push you to go first
You Β· Range anchor (mid-stretch)"Based on the Copenhagen CSM market at this level β€” factoring operations background plus the HubSpot certification track β€” I've been benchmarking in the 580 to 620 thousand range base, plus the usual CSM variable component. Where does that sit relative to your range?"
If they come in below your floor
You Β· Soft push-back"I appreciate that's where the published range starts. Could we talk about how variable is structured, and whether there's flexibility on base for someone who'd bring both the operations rigour and the formal CSM training in?"
If they're firmly below your floor
You Β· Walk-away (keep door open)"That's some distance from where I'd need to land β€” I want to be straight about that rather than waste your time. I'd love to keep talking if there's a path to revisit, even with a deferred start. If not, no hard feelings β€” I'd value staying in touch as you grow the team."
Three rules: never name a single number β€” always a range; always frame around the market, not your wishes; always pair base with total comp (variable, equity if any, pension, holiday).
Never: Apologise for asking. Never say "I'm flexible" before they've named a number β€” they'll anchor low.
πŸ›‚

The Permit & Start-Date Script

ScriptHigh Likelihood

They'll ask. Don't dodge β€” name it cleanly and offer two flexible options. The strength is in the framing.

The honest script
You Β· Permit & Timeline"On work authorisation β€” I have a Danish CPR number and full residency. My MSc at Roskilde finishes June 2026, so until then my student permit limits me to twenty hours per week during semesters. From July 2026 I'm eligible for unrestricted full-time work, no sponsorship needed, and no further administrative steps. If timing works on your side, two options I'd happily explore: a part-time bridge until July, or a deferred start in July. Whichever fits your hiring need better."
Why it works
  1. Leads with what's already done (CPR, residency) β€” removes the "is this complicated?" worry.
  2. Names the constraint precisely (20h cap, until June 2026).
  3. Closes with two flexible options β€” doesn't dump the problem on them.
  4. No apology, no over-explanation.
If they ask "can you start sooner?" β€” "Twenty hours per week is the cap until early July. Within that I'm flexible on schedule β€” that could mean two-and-a-half days in office or distributed across the week. I'd want to make sure the part-time arrangement is useful, not just symbolic."
❓

Questions to Ask Them β€” 15 That Land

ScriptHigh Likelihood

Pick 4–5 based on the flow of the conversation. The closing one is mandatory.

About the Role
  1. What does the first 90 days look like for someone in this role?
  2. How is success measured β€” primarily NRR, GRR, or a balance?
  3. What's the size and profile of the portfolio I'd own?
About the Team
  1. How is the CS team structured today β€” by region, tier, industry?
  2. How does CS interact with product and engineering β€” formal channels or informal?
  3. What's a recent change you've made to how CS operates?
About the Customer
  1. What does a typical customer look like β€” B2B SaaS, IoT integrator, OEM?
  2. What's the most common reason customers churn today?
  3. How technically sophisticated are your customers β€” do they push you on depth?
About Growth
  1. Is there a path from CSM to Senior CSM, CS Ops, or CS leadership over time?
  2. How does Onomondo invest in CSMs' development?
  3. What do you personally look for in a CSM who'd be promoted in 2–3 years?
Closing (Always Ask)
  1. Is there anything in my background you'd like me to address that we haven't covered?
  2. What would make this hire feel obviously right for you 3 months in?
  3. What's the next step from here, and what's your timeline?
The killer move: Q13 ("Anything in my background you'd like me to address?"). It signals confidence, removes hidden objections, and almost no candidate asks it. Always ask it.
πŸ“…

Day-of Checklist & Timeline

PrepHigh Likelihood

The day will fly. Lock the timeline before, so the call itself is the easy part.

T-24h
Reread Onomondo's website + last 3 blog posts. Reread Benedicte's LinkedIn. Print this playbook + the pitch.
T-2h
Light meal. Water. Test camera, mic, lighting, internet. Set up backup phone tethering.
T-30m
10-minute walk outside. Power-pose 60 seconds. Hydrate. Reread the 90-second opener once.
T-10m
Open Teams / Zoom early. Pull up: Onomondo site, your LinkedIn, this playbook, the salary ladder.
T-2m
Camera at eye level. Neutral background. Notebook + pen visible. Smile before joining.
In-call
Match their energy β€” calm if calm. Pause 1 second before each answer. Take visible notes. Don't fill silence.
Last 5m
Ask 2–3 of your prepared questions. Always end with "Anything in my background you'd like me to address?"
T+2h
Send a 4-line follow-up: thanks, one specific thing from the conversation, reaffirm interest, next-step ask.
If tech fails: don't apologise repeatedly. Calmly say "let me reconnect" and rejoin. Composure under tech failure is itself a signal.
🏁

The Final 60 Seconds β€” Closing Script

ScriptCritical

Most candidates fade out. Yours closes deliberately. The last impression is disproportionately what they remember.

The script
You Β· Closing 60s"Thanks so much for the time, Benedicte β€” really helpful conversation. Just to wrap on my side: what's drawn me through every step of this is that the role sits exactly where I want to be β€” operationally substantive and commercially measured. I'd love to keep moving forward. Is there anything you'd like to see from me in the next stage β€” a working example, references, a portfolio walkthrough?"
Then the follow-up email Β· within 2 hours
Why this works: Specific (not "thanks for your time, looking forward to next steps"). Useful (offers to do more). Confident (assumes a next step).

πŸ† The Golden Rules β€” Read Before You Walk In

1. Think out loud. Whatever you're doing β€” narrate it. They cannot see inside your head.

2. Interpret, don't read. Data is data. Your value is the interpretation. Always pair what you see with what you'd do.

3. Calm in the menus. Can't find a button? "I know what I'm looking for β€” let me find the right menu." Don't freeze.

4. Tie back to the customer. Whatever they ask, close the loop with "...and that's why this matters for the customer experience."

5. End strong. After any task, finish with the bigger picture: "And the reason I'd do it this way is because [retention principle]." That separates you from candidates who just answered the question.

6. One second of silence before each answer. Shows you're thinking, not reciting.

7. Match the energy, never exceed it. Calm Dane = calm you. Never higher-energy than the room.