← Pantomath / Sr. Product Manager
candidate_questions / art_ecreldRZvf4
Interviewer
Bo Brunton is Head of Product Strategy at Pantomath, a role he stepped into in May 2025 after progressing from PM to Director of Product over 4.5 years at the company — making him one of its earliest and most tenured product leaders. Before Pantomath he spent nearly four years at GE Aviation, culminating as Enterprise BI Program Leader and Sr. Data and Information Architect, giving him direct hands-on data and BI experience that mirrors what this role demands. He also co-founded TadPoL, a startup he candidly describes as 'an incredible solution without a problem,' signaling self-awareness and an appreciation for customer-validated product thinking. As Head of Product Strategy he will likely probe strategic thinking, roadmap prioritization, and how Felix's technical depth translates into product decisions. Shared context: both Bo and Felix have deep BI/data backgrounds — Bo from GE Aviation's enterprise BI program, Felix from IBM's BI products and Kaiser's SOA/Splunk platform work — and both have founder experience.
Questions to ask them (20)
| category | question | why |
|---|---|---|
| interviewer_experience | You've been at Pantomath for over four years and grown from PM to Head of Product Strategy — that kind of tenure at an early-stage company is rare. What's kept you here, and what's changed most about the product vision from when you first joined? | Surfaces what makes Pantomath sticky for someone who could go anywhere, and reveals how the product has evolved — useful for calibrating ambition and stability. |
| interviewer_experience | Your time at GE Aviation as Enterprise BI Program Leader and Data Architect clearly shaped how you think about data products. How much does that background influence how Pantomath approaches the connectors and integrations layer today? | Builds rapport by acknowledging his technical roots and draws out whether the product philosophy is grounded in real data engineering pain — which is directly relevant to this role. |
| interviewer_experience | You described TadPoL as 'an incredible solution without a problem' — that's a hard-won lesson most founders carry for life. How has that experience shaped how Pantomath validates connector demand before committing engineering resources? | Shows genuine curiosity about his founder journey, builds rapport, and surfaces the company's customer discovery and validation discipline for connectors specifically. |
| role_team_dynamics | What does success look like at 30, 60, and 90 days for this role? Specifically, is the expectation to audit the existing connector landscape first, or is there a specific integration or initiative already waiting for an owner? | Gets concrete about ramp expectations and whether there's a burning near-term deliverable versus a more strategic onboarding window. |
| role_team_dynamics | How is the connectors team structured today — is this PM role leading a dedicated engineering pod, or working across shared engineering resources? And how does the connectors roadmap get prioritized relative to the broader platform roadmap? | Clarifies reporting lines, resource ownership, and whether the PM will have real roadmap authority or be competing for eng bandwidth. |
| role_team_dynamics | What are the one or two biggest unsolved challenges in the connectors ecosystem right now — the things that have been hardest to crack and that this hire is expected to make real progress on? | Identifies the actual hard problems versus the polished job description framing, and signals that Felix is thinking about impact from day one. |
| role_team_dynamics | How does the connectors PM interact with Go-to-Market and customer-facing teams? Is there a formal launch process, or is it more ad hoc today? | Surfaces cross-functional maturity and whether Felix would need to build GTM processes from scratch or plug into an existing motion. |
| technical_environment | When you think about Pantomath's connector architecture today — are connectors built on a shared internal framework, or is each integration more bespoke? And where are the biggest reliability or scalability pain points in the current approach? | Gets into the actual technical state of the product, which is critical for a role that requires hands-on technical judgment about build vs. buy and long-term maintainability. |
| technical_environment | The JD calls out a broad modern data stack — Fivetran, dbt, Airflow, Snowflake, Databricks, Tableau, Power BI. Which of those integrations are most mature today, and which represent the biggest gaps or customer demand that's currently unmet? | Reveals where the roadmap whitespace actually is and lets Felix demonstrate familiarity with the stack without being asked directly. |
| technical_environment | How does the team currently handle connector observability — things like error rates, latency monitoring, and alerting when an integration degrades in production? Is that infrastructure in place, or is it something the next PM would help define? | Tests whether the success metrics mentioned in the JD are aspirational or operational, and surfaces a concrete area where Felix's platform infrastructure background at Intuit and Splunk would add immediate value. |
| culture_working_style | How does Pantomath handle disagreements between product and engineering on technical direction — especially when a PM has strong opinions about architecture or feasibility? Is that kind of tension welcomed or does it create friction? | Gauges psychological safety for a technically opinionated PM and whether the culture rewards or punishes PMs who push back on engineering decisions. |
| culture_working_style | How much autonomy does a Senior PM have over roadmap prioritization versus alignment required with leadership? I want to understand where the decision rights actually sit day to day. | Directly relevant for someone coming from Staff PM roles with significant ownership — helps Felix assess whether this is an empowered PM role or a more execution-focused one. |
| culture_working_style | Pantomath is still in a growth phase. How would you describe the working pace and how the team balances moving fast on new connectors versus maintaining reliability on existing ones? | Surfaces the real operational tempo and whether there's a mature approach to technical debt and reliability — critical for a connectors role where uptime is a trust signal. |
| growth_development | You moved from PM to Director to Head of Product Strategy in about four and a half years — that's a meaningful growth arc. For someone coming in at the Senior PM level, what does the growth path look like from here, and what tends to differentiate the people who advance quickly? | Uses Bo's own trajectory as a concrete reference point rather than asking a generic growth question, and signals Felix is thinking about long-term fit. |
| growth_development | Does Pantomath invest in technical or domain development for PMs — things like access to conferences, data engineering communities, or time to stay current on the stack? Given how fast the modern data stack moves, I want to understand how the team stays sharp. | Signals that Felix takes the technical currency requirement seriously and probes whether the company supports it structurally. |
| strategy_vision | Where does Pantomath see the connectors ecosystem fitting into the broader product vision over the next two to three years — is it primarily a distribution and adoption play, or is there a deeper technical differentiation story around how Pantomath's connectors work versus what customers could get from Fivetran or native integrations? | Gets at the strategic moat question — whether connectors are table stakes or a genuine competitive differentiator — which shapes how ambitious the roadmap should be. |
| strategy_vision | As data observability and lineage become more central to the modern data stack, how is Pantomath thinking about the intersection of connectors and metadata — things like propagating lineage through integrations or surfacing connector-level observability to end users? | Demonstrates awareness of where the market is heading and probes whether Pantomath is thinking ahead on this, which is directly relevant to the preferred qualifications around observability and lineage. |
| strategy_vision | What's the biggest strategic bet Pantomath is making in the next 12 months, and how does the connectors roadmap either enable or depend on that bet? | Surfaces company-level priorities and whether connectors are on the critical path or a supporting function — important for understanding the role's actual leverage and visibility. |
| shared_context | Your GE Aviation BI work and my time at IBM building enterprise BI products and at Kaiser running a Splunk-based observability platform overlap in interesting ways — both dealing with large-scale data infrastructure in complex enterprise environments. How much of Pantomath's connector customer base today is enterprise versus mid-market, and does that mix shape how you think about reliability and SLA requirements for integrations? | Builds genuine rapport through shared BI and enterprise data infrastructure experience, while gathering useful signal about the customer profile and what 'production-grade' actually means in this context. |
| shared_context | I noticed you co-founded TadPoL while working full-time at GE — I've been running two AI startups alongside consulting work, so I appreciate the discipline that requires. How does Pantomath think about founder-minded PMs who bring that bias toward ownership and shipping? Is that energy welcomed on the product team? | Creates a peer-level moment of shared founder experience, signals entrepreneurial drive, and probes cultural fit for someone with a strong ownership orientation. |
Conversation starters
- I saw you were at GE Aviation as Enterprise BI Program Leader right before joining Pantomath — I spent several years at IBM working on enterprise BI products and later at Kaiser building out a Splunk-based observability platform, so I'm curious what the jump from a large industrial enterprise to an early-stage data startup felt like in those first months.
- Your note about TadPoL being 'an incredible solution without a problem' stuck with me — I've had that exact experience with one of my own ventures and it completely rewired how I think about customer discovery before committing to a roadmap. Would love to hear more about what you took from that into how you approach product at Pantomath.
- Congrats on the Head of Product Strategy move in May — going from PM to that level in four and a half years at the same company is a real signal about what you've built there. I'd love to hear what the company looks like now versus when you first joined.
⚠ Handle carefully
- Bo recently transitioned to Head of Product Strategy just a few months ago — avoid questions that imply instability in the product leadership structure or that probe whether the Director of Product role he vacated is now the one being filled, as that could feel politically sensitive.
- TadPoL is described candidly as a failure in his own words — while it's a great conversation starter, don't dwell on it or probe the failure too deeply; use it as a bridge to product philosophy and move on.
- Pantomath is a growth-stage startup and Bo has been there since near the beginning — avoid framing questions in ways that imply the company or its processes are immature or behind industry norms, as he has significant personal investment in what's been built.