Procurify Panel Week Prep (Mar 3-6, 2026)

Schedule

Interviewer Intel

Riley Szulc (Product Round X2 -- Tue Mar 3)

• Background: 6 yrs fintech/eCommerce. Nest Wealth (B2B SaaS, onboarding/client lifecycle), Nōwn POS (merchant experience, eCommerce, analytics)
• Style: UX-focused (General Assembly UX cert), strong on stakeholder management, analytics (Google Analytics, Mixpanel)
• Domain at Procurify: Unclear. No domain qualifier in title. Given Fred owns AP and Tony owns accounting/billing, Riley likely owns Procurement (buying/PO side) or Expense & Card Management
• Joined: Sep 2025 (~same cohort as Tony -- both relatively new)
• Rapport angle: Also comes from fintech. Both know what it's like to build product in regulated/complex financial domains. His Nest Wealth onboarding experience parallels the operational cadence work Andrea would do

Fred Pinto (Product Round X1 -- Thu Mar 5)

• Background: 7.5 yrs at BILL (Procurement & Payment Experience, Invoice2Go, Mobile). Intuit (QuickBooks Brazil). Dartmouth Tuck MBA
• Title at Procurify: "Product - AP Automation" (since Nov 2025)
• Style: Data-driven, detail-oriented (recommendations consistently cite this). Experienced in enterprise B2B. Brazilian, speaks Portuguese + Japanese
• Domain at Procurify: AP Automation -- invoice processing, bill management, bill payments, three-way matching
• Rapport angle: Both worked in complex B2B environments. His BILL experience (procurement + payments) is core Procurify territory. He'll care about how Andrea would coordinate across his domain

Tony Wang (Product Round X3 -- Fri Mar 6)

• Background: Xero (2.5 yrs, redesigned Bills/Spend Management experience), CARET (legal billing), Rose Rocket (billing, accounting, integrations), Flipp
• Title at Procurify: "Senior Technical Product Manager" (since Sep 2025)
• Tagline: "Building easy accounting software"
• Style: Technical (UofT CS, AI & ML specialization, patent holder). Data-driven. Recommendations describe him as conscientious and tenacious
• Domain at Procurify: Accounting / Billing / possibly integrations with accounting systems (QuickBooks, NetSuite, Sage, etc.)
• Rapport angle: Technical depth. Andrea can speak to working closely with technical teams and translating between business and engineering. His Xero modernization experience = large-scale transformation, similar to Ting migration

Lindsie Canton (Problem Solving -- Thu Mar 5)

• Title: Director of Product Design (since Aug 2025)
• Background: 15 yrs design leadership. Workleap (Manager, Product Design), Prodigy Education (Design Operations), Rangle.io, CAPREIT
• Style: Systems thinker. Cares about operating models, rituals, feedback loops, "guardrail governance without overburdening teams." Certified Group Facilitation Methods. Reposted Jonathan Su's hiring post
• Key quote from About: "co-designing guardrail governance without overburdening teams with process"
• AI angle: "I'm especially interested in how AI can act as a force multiplier for product teams"
• What she'll evaluate: How Andrea thinks about designing processes, facilitating alignment, and enabling teams without creating bureaucracy

Neil Power (Problem Solving -- Thu Mar 5)

• Title: Senior Director of Engineering (since May 2025)
• Background: 5+ years at Procurify (longest tenure of all interviewers). Previously Hootsuite, SEDNA Systems. Vancouver-based
• Manages: Web Application, Mobile, Platform, DevSecOps, Data Engineering
• Style: "High trust and deep collaboration." Empowers teams closest to information to make decisions. Warm, candid personality (per recommendations)
• What he'll evaluate: Whether Andrea can work effectively with engineering. Whether she'll add clarity or bureaucracy. He has institutional knowledge -- he's seen what works and what doesn't at Procurify

Narratives to Deploy

Product Operations at Ting (ready to tell)

Framing: "I built the operational infrastructure the org didn't know it needed yet, because I needed it to do my own job well."

Key beats:
1. Asana experiment: Moved team from Google Sheets to Asana for prioritization. Hit real limitations -- units of measurement for product work, prioritization frameworks didn't map well. Rather than forcing it, adapted: went back to simpler tools (Sheets + Jira) that actually worked. Shows operational maturity -- don't over-engineer process
2. Knowledge base (Google Sites):
- Nobody asked for it, nobody had tried before
- Built it for herself first ("I needed cheat sheets" -- products, pricing, quick reference)
- Designed for broad consumption: concise summaries, easy navigation
- Used daily, which kept it alive and current (not a rotting wiki)
- Covered products, pricing, deprecations -- became institutional memory and chronology
- Later a formal KM team was hired, but scoped to customer-facing support. Andrea's internal reference tool filled a distinct gap that persisted
3. Beta program operations (to be captured):
- Managed end-to-end: finding beta customers, logistics, working with teams on go-to-market
- Full narrative TBD -- Andrea to revisit

Best for: Riley (operational maturity), Lindsie (process design without over-engineering), Neil (adds clarity not bureaucracy)

Ting Migration (already banked from HM round)

Best for: Fred (complex cross-functional coordination), Tony (large-scale platform transformation), Problem Solving round

Lalamove Strategic Lead (flagged in HM notes -- needs full capture)

Best for: All rounds -- covers tracking initiatives, collaboration, updates/reporting/presentations

Product Rounds Strategy (30 min each)

These are likely "would I want to work with this person" conversations. The PMs are evaluating:
- Does Andrea understand product work well enough to coordinate it?
- Will she add value or just add process?
- Will she respect their domain expertise while bringing strategic perspective?

Approach:
- Ask what they own, what's hard about it right now, what coordination challenges they face
- Listen more than pitch. 30 min goes fast -- don't over-talk
- Show curiosity about their specific domain, not just generic "product ops" answers
- Demonstrate that you'd make their life easier, not harder

Problem Solving Round Strategy (90 min)

Format unknown. Likely a case exercise. Lindsie (design leader, systems thinker) + Neil (engineering leader, institutional knowledge) together suggests they want to see:
- How Andrea approaches ambiguous problems
- How she facilitates and structures thinking
- Whether she can bridge product/design/engineering perspectives
- Whether she adds clarity or complexity

Prep: Bank the beta program story for this round -- it's end-to-end operational problem solving.