← Back to index
Panel Week Prep
Remaining rounds · Mar 3–6, 2026
The product rounds follow a pattern: hypothetical questions about real Procurify problems, testing a PM-style approach to operations. Riley's three themes were simplicity, measuring impact, and design thinking.
Pattern
Questions start abstract, then get more specific if your answer doesn't land. Anchor abstract questions with specific examples from your experience. When a question is too vague, ask for a concrete scenario. Your strongest answers came from lived experience.
Cold start problem
First question is always your weakest. Accept it, breathe through it. The Lalamove scaling story is a good warmup — it's a strong example you know well and can deliver confidently.
The gap to close
You know the product concepts (progressive disclosure, sensible defaults, reducing decision points) but didn't retrieve them under pressure. Keep the vocabulary loaded before each call. Say the words out loud in warmup.
Senior PM, AP Automation. Data-driven, detail-oriented, customer-focused. Deep AP/payments background.
At Procurify
Product – AP Automation (Nov 2025, ~5 mo)
Before
7+ yrs at BILL (Procurement & Payment, Invoice2Go, Mobile)
Education
Dartmouth Tuck MBA
Based in
Orlando, FL (remote)
His domain: AP Automation = the second half of the user journey (where Riley's ends): invoice receipt, matching, payment processing, accounting sync. This is where Procurify competes most directly with Ramp and BILL. He knows the competitive landscape intimately.
Likely Questions & Your Answers
1. Data-informed decision making
He's described as someone who pulls transaction data and analyzes it for UX improvements. Expect questions about using data to prioritize or measure changes.
Ready: Ting WoW dashboard (accelerated scheduling metrics), address serviceability fix (identified data architecture problem through customer feedback patterns)
2. Cross-functional coordination for launches
BILL to Procurify is a transition; he's likely still establishing processes. May ask about GTM readiness for AP product changes.
Ready: Ting phased rollout (proven with Riley), knowledge base cadence for internal tracking
3. Simplification of financial workflows
AP is notoriously painful. How would you reduce overhead while maintaining compliance/audit trails?
Vocabulary: progressive disclosure, sensible defaults, reducing decision points, necessary friction (compliance) vs. unnecessary friction (process). Story: Autzu driver onboarding — added first-time how-to, 50% drop in onboarding calls.
4. Vendor/customer perspective
Both sides of AP (the company paying, the vendor getting paid). How do you balance simplicity for both?
Ready: Lalamove scaling — different markets, different stakeholders, same need for shared language
Rapport: Brazilian-American, Dartmouth MBA. Described as "positive energy" and "easygoing." His career shows someone who cares about craft. If you speak to the detail-orientation of building something right vs. fast, that resonates with his style.
Senior Technical PM. CS background with AI/ML specialization. His LinkedIn About is one sentence: "Building usable accounting products."
At Procurify
Senior Technical PM (Sep 2025, ~6 mo)
Before
Rose Rocket, CARET (legal billing), Xero (Bills/Spend Mgmt), Flipp
Education
UofT CS (AI & ML, minor Statistics)
Based in
Toronto (remote)
His domain: Likely technical/platform side — integrations, accounting sync, data infrastructure. His career is a through-line of making accounting/billing software usable. At Xero, he led a team of 2 PMs to redesign and modernize the 10+ year old Bills experience. A colleague who was ex-Ramp described him as "conscientious, data-driven."
Likely Questions & Your Answers
1. Technical trade-offs in product decisions
Given his CS/AI background, he may ask how you evaluate technical complexity vs. user value.
Ready: Address serviceability fix — identified Google Maps radius was wrong at the data architecture level, brought in GIS team. Shows technical judgment without being an engineer.
2. Modernization of legacy systems
His Xero work was literally redesigning a 10+ year old product. He knows the pain of modernizing while keeping users happy.
Ready: Ting website redesign — replacing an ancient monolith during a corporate brand transition, managing orphaned content, stakeholder buy-in, shipping on deadline.
3. AI/ML in product
His academic background and Procurify's AI push. May ask about operationalizing AI features or measuring their impact.
Context: Ramp article — AI for finance = setting rules, modeling what happened, improving outcomes. Frame your answer operationally: "here's how I'd build the tracking cadence for an AI feature launch."
4. Integrations and ecosystem
His career was all about connecting financial systems. May ask about managing dependencies across systems or teams.
Ready: Ting cross-functional coordination across IS, Care, Field Ops, Design — managing dependencies when no single team owned the full workflow.
Rapport: Younger, technical, concise. Match his energy — be direct, specific, and show you can speak to technical concepts without being an engineer. The shared "usability" lens is a good connector.
This is not a product strategy round. It's about how you structure your thinking when given a messy or ambiguous problem, and how you collaborate with design and engineering.
Lindsie Canton
- Director of Product Design
- 15 yrs in design & design leadership
- Workleap (13 designers, 4 products), Prodigy Education (Design Ops), Rangle.io
- Group Facilitation Methods certified
- Themes: "outcome-driven decision making," "guardrail governance without overburdening with process," "AI as force multiplier," "radical candour"
- Design ops person who became a design leader. Thinks in systems, rituals, process — but hates process for its own sake
Neil Power
- Senior Director of Engineering
- 5+ yrs at Procurify (dev → Sr Eng Manager → Director → Sr Director)
- Manages Web, Mobile, Platform, DevSecOps, Data Engineering
- Before: SEDNA Systems, Hootsuite
- Themes: "high trust and deep collaboration," "decisions made by those closest to the information"
- Values curiosity, craft, candour. Recommendations emphasize teaching and even-tempered leadership
What They're Evaluating
How you structure thinking on messy/ambiguous problems. How you collaborate with design and engineering. Whether you default to process for process's sake or focus on outcomes. Your facilitation instincts.
Likely Format
Probably a scenario or case study. Examples: "Teams are misaligned on priorities — walk us through your approach." "Competing initiatives, limited resources — how do you help leadership decide?" "A major feature launch isn't going well post-release — what do you do?"
How to Approach
1. Think out loud
They want to see your process, not just your answer.
2. Ask clarifying questions
Both Lindsie and Neil value clarity over assumptions.
3. Frame operationally
"Here's how I'd set up the cadence / tracking / feedback loop for this" is your sweet spot and exactly what this role does.
4. Acknowledge both disciplines
You're in the room with Design and Engineering leadership. Show you understand their constraints and can bridge them.
5. Reference Procurify's CARES values
Especially Simplicity ("focus, clarity, streamlining to cut through complexity") and Commitment ("accountability and follow-through"). Not poster words — Lindsie and Neil both live them.
Best Stories for This Round
Ting phased rollout — structured approach to a messy cross-functional problem
Accelerated scheduling — breaking a big problem into shippable increments when you can't get the ideal solution approved
Address serviceability fix — identifying the real problem vs. the surface problem, influencing without authority
Lalamove scaling — culture, communication, shared language at scale
Fresh story not in any other prep doc. Use this for simplicity, measuring impact, and design thinking questions — it hits all three of Riley's themes cleanly.
Context: Autzu was a Toronto startup that rented cars to Uber drivers (fleet rental, single customer type — drivers). Andrea worked in operations, onboarding new drivers by phone and in person.
The Problem
Through direct driver contact during onboarding (calls and in-person meetings), Andrea heard consistent feedback: drivers were confused about how the system worked and how to use the app. This was pure product friction blocking activation — confused drivers don't drive, don't earn, and churn.
What Andrea Did
Worked with the engineering team to build a how-to segment that appeared at the top of the app on first open for new users, walking them through how everything works. Classic progressive disclosure — surfacing guidance at exactly the moment users need it, then getting out of the way.
How She Measured It
Couldn't build deep analytics into the app initially, so used a proxy metric: call volume for specific onboarding questions. Tracked for ~2 months post-release. Call volume for onboarding questions dropped over 50%. Also continued collecting direct qualitative feedback from drivers who found it very useful.
Quant: 50%+ drop in onboarding call volume over 2 months. Qual: direct driver feedback confirmed usefulness.
Why This Story Is Powerful
For simplicity questions: Progressive disclosure in action — introduced complexity only when the user needed it (first-time open), not all at once.
For measuring impact: When you can't build analytics, use what you have. Call volume as a proxy metric is scrappy and valid.
For design thinking: The insight came from being on the ground with users, not from a dashboard. Ops-informed product improvement.
For "cutting to the bone": The app was confusing, but the fix wasn't to remove features — it was to add the right guidance at the right moment. Sometimes simplicity means adding something that reduces cognitive load.
Interview-ready version (~30 sec): "At Autzu, I was onboarding Uber drivers to our car rental platform. Through direct conversations I kept hearing the same thing — drivers were confused about how to use the app. I worked with engineering to build a first-time-user how-to that appeared on initial app open. We couldn't build deep analytics at the time, so I tracked call volume for onboarding questions as a proxy. Over two months, those calls dropped over 50%. The insight came from being on the ground with users, and the fix was progressive disclosure — giving people guidance at the moment they need it, not burying it in a help section."
When questions are abstract, reach for these terms. Say them out loud during warmup so they're close to the surface.
Product Simplicity
Progressive disclosure. Sensible defaults. Reducing decision points. Necessary vs. unnecessary friction. Cognitive load.
Measuring Impact
Leading vs. lagging indicators. Quant + qual pairing. Baseline before change. 30/60/90 cadence. Feedback signal (drop = satisfaction, spike = problem).
Operational Excellence
Operating cadence. Single source of truth. Accountability through visibility. Dependency mapping. Risk register.
Strategic Framing
"Operationally, here's how I'd approach that." "The first thing I'd want to understand is the current baseline." "What does success look like for the business, not just the user?"
Do this before every round. The goal is retrieval priming — getting the right words and stories close to the surface.
- Re-read the relevant section above for whoever you're about to talk to. (5 min)
- Say out loud: one Ting story, one Lalamove story. Don't rehearse perfectly — just practice retrieving. (2 min each)
- Remind yourself: ask for clarification on vague questions. It's not weakness, it's precision.
- Accept: first question will be your weakest. Breathe through it. Warm up.