interview_prep_doc / art_R47TjQKS16U

Content

{
  "markdown": "# Pantomath Interview Prep\n## Questions to Ask Bo Brunton\n\n---\n\n## 1. Interviewer Summary\n\nBo Brunton is Head of Product Strategy at Pantomath, a title he stepped into in May 2025 after a four-and-a-half-year arc that took him from individual contributor PM to Director of Product and now into strategy leadership. That kind of tenure at a growth-stage startup is unusual and meaningful \u2014 it signals both personal conviction in the company's direction and a level of institutional trust that makes him one of the most informed voices you could speak with about what Pantomath actually is versus what it says it is.\n\nBefore Pantomath, Bo spent nearly four years at GE Aviation, finishing as Enterprise BI Program Leader and Senior Data and Information Architect. That background is directly relevant to this conversation: he has lived the pain of enterprise-scale data infrastructure, BI pipelines, and integration complexity from the practitioner side \u2014 the same world Felix inhabited at IBM and Kaiser. This is not a conversation with a generalist product leader who has read about data stacks. It is a conversation with someone who has built on them.\n\nBo also co-founded TadPoL, which he describes in his own words as \"an incredible solution without a problem.\" That level of candor about a failed venture is a strong signal \u2014 he values intellectual honesty, customer-validated thinking, and the hard lessons that come from shipping something real. Felix's parallel founder experience at Streamio AI and Fintellect AI creates genuine common ground here.\n\n**Likely focus areas for Bo in this conversation:**\n- Strategic thinking and how Felix translates technical depth into product decisions\n- Roadmap prioritization philosophy and how Felix handles trade-offs under constraint\n- Whether Felix's founder energy and ownership orientation fit Pantomath's culture\n- How Felix's enterprise data background (IBM, Kaiser, Intuit, Splunk) maps to the connectors problem space\n\n**What kind of conversation this is likely to be:**\nBo will probably run this as a peer-level strategic discussion more than a structured interview. He has enough shared context with Felix \u2014 BI backgrounds, founder experience, enterprise data infrastructure \u2014 that the conversation could go deep quickly. Thoughtful questions from Felix will do double duty: they gather real signal about the role *and* demonstrate the strategic and technical seriousness the job demands.\n\n---\n\n## 2. Best Questions to Ask Bo Brunton\n\n---\n\n### A. Interviewer Experience and Rapport\n\n**Question 1.**\n**\"You've been at Pantomath for over four years and grown from PM to Head of Product Strategy \u2014 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?\"**\n\n**Why this is a good question:** Surfaces what makes Pantomath genuinely compelling to someone who could go anywhere, and reveals how the product has evolved over time. The answer calibrates ambition, stability, and whether the company's direction has sharpened or drifted \u2014 all useful signal for a candidate evaluating long-term fit.\n\n---\n\n**Question 2.**\n**\"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?\"**\n\n**Why this is a good question:** Builds genuine rapport by acknowledging Bo's technical roots rather than treating him as a generic product leader. It also draws out whether Pantomath's connector philosophy is grounded in real data engineering pain \u2014 which is directly relevant to what this role requires. Felix's IBM BI and Kaiser observability background creates a natural bridge here.\n\n---\n\n**Question 3.**\n**\"You described TadPoL as 'an incredible solution without a problem' \u2014 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?\"**\n\n**Why this is a good question:** Opens a peer-level moment of shared founder experience and signals that Felix takes customer discovery seriously. More importantly, it surfaces the company's actual discipline around validation \u2014 whether connector prioritization is driven by rigorous demand signals or by internal assumptions.\n\n> *Use this as a conversation opener and then move on \u2014 don't dwell on the failure itself. The goal is to bridge to product philosophy, not to dissect TadPoL.*\n\n---\n\n### B. Role and Team Dynamics\n\n**Question 4.**\n**\"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?\"**\n\n**Why this is a good question:** Gets concrete about ramp expectations and whether there is a burning near-term deliverable versus a more strategic onboarding window. The answer also reveals how much context-building time Felix would have before being expected to ship.\n\n---\n\n**Question 5.**\n**\"How is the connectors team structured today \u2014 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?\"**\n\n**Why this is a good question:** Clarifies reporting lines, resource ownership, and whether the PM will have real roadmap authority or be perpetually competing for engineering bandwidth. These are the structural conditions that determine whether a strong PM can actually execute.\n\n---\n\n**Question 6.**\n**\"What are the one or two biggest unsolved challenges in the connectors ecosystem right now \u2014 the things that have been hardest to crack and that this hire is expected to make real progress on?\"**\n\n**Why this is a good question:** Cuts through polished job description framing to identify the actual hard problems. Asking this signals that Felix is thinking about impact from day one, not just about fitting a role description.\n\n---\n\n**Question 7.**\n**\"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?\"**\n\n**Why this is a good question:** Surfaces cross-functional maturity and whether Felix would be plugging into an established GTM motion or building one. Given the JD explicitly calls out launch readiness and technical enablement, understanding the current state matters.\n\n---\n\n### C. Technical Environment and Architecture\n\n**Question 8.**\n**\"When you think about Pantomath's connector architecture today \u2014 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?\"**\n\n**Why this is a good question:** Gets into the actual technical state of the product, which is essential for a role that requires hands-on judgment about build vs. buy and long-term maintainability. Felix's experience scaling Intuit's ICE platform to 675M+ engagements and 50K TPS gives him a credible frame for evaluating the answer.\n\n---\n\n**Question 9.**\n**\"The JD calls out a broad modern data stack \u2014 Fivetran, dbt, Airflow, Snowflake, Databricks, Tableau, Power BI. Which of those integrations are most mature today, and which represent the biggest gaps or unmet customer demand?\"**\n\n**Why this is a good question:** Reveals where the roadmap whitespace actually is, and lets Felix demonstrate genuine familiarity with the stack without being asked to prove it directly. The answer also helps Felix assess whether the most interesting technical work is ahead of the team or already largely done.\n\n---\n\n**Question 10.**\n**\"How does the team currently handle connector observability \u2014 error rates, latency monitoring, alerting when an integration degrades in production? Is that infrastructure in place, or is it something the next PM would help define?\"**\n\n**Why this is a good question:** Tests whether the success metrics mentioned in the JD are aspirational or operational. Felix's background running Splunk Logging-as-a-Service at Kaiser (1.7 TB daily, 200+ enterprise customers) and owning Search Orchestration at Splunk gives him direct credibility in this space \u2014 and the answer reveals whether there's an immediate high-value contribution to make.\n\n---\n\n### D. Culture and Working Style\n\n**Question 11.**\n**\"How does Pantomath handle disagreements between product and engineering on technical direction \u2014 especially when a PM has strong opinions about architecture or feasibility? Is that kind of tension welcomed or does it create friction?\"**\n\n**Why this is a good question:** Gauges psychological safety for a technically opinionated PM. Felix has operated at Staff PM level with significant technical authority at Intuit and Splunk \u2014 understanding whether Pantomath's culture rewards or punishes PMs who push back on engineering decisions is critical for fit.\n\n---\n\n**Question 12.**\n**\"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.\"**\n\n**Why this is a good question:** Directly relevant for someone coming from Staff PM roles with real ownership. Helps Felix assess whether this is a genuinely empowered PM role or a more execution-focused one where strategy is set above.\n\n> *Frame this with curiosity rather than skepticism:* **\"I want to make sure I set myself up to add the most value \u2014 so I'm curious where the decision rights actually sit day to day.\"**\n\n---\n\n**Question 13.**\n**\"Pantomath is still in a growth phase. How would you describe the working pace, and how does the team balance moving fast on new connectors versus maintaining reliability on existing ones?\"**\n\n**Why this is a good question:** Surfaces the real operational tempo and whether there is a mature approach to technical debt and reliability. For a connectors role where uptime is a direct trust signal with customers, this is not a soft culture question \u2014 it is a product quality question.\n\n---\n\n### E. Growth and Development\n\n**Question 14.**\n**\"You moved from PM to Director to Head of Product Strategy in about four and a half years \u2014 that's a meaningful growth arc. For someone coming in at the Senior PM level, what does the path look like from here, and what tends to differentiate the people who advance quickly?\"**\n\n**Why this is a good question:** Uses Bo's own trajectory as a concrete reference point rather than asking a generic career growth question. It signals that Felix is thinking about long-term fit and contribution, not just landing the role.\n\n---\n\n**Question 15.**\n**\"Does Pantomath invest in technical or domain development for PMs \u2014 conferences, data engineering communities, time to stay current on the stack? Given how fast the modern data stack moves, I'm curious how the team keeps its edge.\"**\n\n**Why this is a good question:** Signals that Felix takes the technical currency requirement seriously and probes whether the company supports it structurally. It also subtly reinforces Felix's identity as a technically grounded PM, not a generalist.\n\n---\n\n### F. Strategy and Vision\n\n**Question 16.**\n**\"Where does Pantomath see the connectors ecosystem fitting into the broader product vision over the next two to three years \u2014 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?\"**\n\n**Why this is a good question:** Gets at the strategic moat question \u2014 whether connectors are table stakes infrastructure or a genuine competitive differentiator. The answer shapes how ambitious the roadmap should be and how much strategic latitude the PM actually has.\n\n---\n\n**Question 17.**\n**\"As data observability and lineage become more central to the modern data stack, how is Pantomath thinking about the intersection of connectors and metadata \u2014 things like propagating lineage through integrations or surfacing connector-level observability to end users?\"**\n\n**Why this is a good question:** Demonstrates forward-looking awareness of where the market is heading and probes whether Pantomath is thinking ahead on this. It maps directly to the preferred qualifications around observability and lineage, and positions Felix as someone who has already thought past the current state.\n\n---\n\n**Question 18.**\n**\"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?\"**\n\n**Why this is a good question:** Surfaces company-level priorities and whether connectors are on the critical path or a supporting function. Important for understanding the role's actual leverage, visibility, and stakes.\n\n---\n\n### G. Shared Context\n\n**Question 19.**\n**\"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 \u2014 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?\"**\n\n**Why this is a good question:** Builds genuine peer-level rapport through shared BI and enterprise data infrastructure experience, while gathering concrete signal about the customer profile. It also reframes \"production-grade\" \u2014 a term used throughout the JD \u2014 in terms of what it actually means for this specific customer base.\n\n---\n\n**Question 20.**\n**\"I noticed you co-founded TadPoL while working full-time at GE \u2014 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?\"**\n\n**Why this is a good question:** Creates a peer moment of shared founder experience and signals entrepreneurial drive without overselling it. It also probes cultural fit for someone with Felix's strong ownership orientation \u2014 important context before accepting an offer.\n\n---\n\n## 3. Best Conversation Starters\n\nUse one of these in the first two minutes to set a warm, peer-level tone before moving into questions.\n\n### Opener A \u2014 The GE-to-Pantomath jump\n> \"I saw you were at GE Aviation as Enterprise BI Program Leader right before joining Pantomath \u2014 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 genuinely curious what the jump from a large industrial enterprise to an early-stage data startup felt like in those first months.\"\n\n### Opener B \u2014 The TadPoL lesson\n> \"Your note about TadPoL being 'an incredible solution without a problem' stuck with me \u2014 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.\"\n\n### Opener C \u2014 The Head of Product Strategy move\n> \"Congrats on the Head of Product Strategy move in May \u2014 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.\"\n\n---\n\n## 4. Topics to Handle Carefully\n\n### Bo's recent leadership transition\nBo moved into Head of Product Strategy just a few months ago. **The risk:** questions that imply instability in the product leadership structure, or that probe whether the Director of Product role he vacated is the one now being filled, could feel politically sensitive \u2014 especially this early in his new mandate.\n\n**Ask this instead:**\n> \"As you've stepped into the Head of Product Strategy role, how has your relationship with the connectors roadmap changed \u2014 are you more hands-off now, or still closely involved in the technical direction?\"\n\n---\n\n### TadPoL \u2014 the failed startup\nBo describes TadPoL candidly as a failure in his own words. It's a great conversation opener, but dwelling on the failure itself or probing what went wrong in detail could feel uncomfortable. **The goal is to use it as a bridge to product philosophy and move on.**\n\n**Softened framing:**\n> \"What you took from that experience into how you approach product validation at Pantomath is what I'm most curious about \u2014 not the startup itself.\"\n\n---\n\n### Implying the company or its processes are immature\nBo has been at Pantomath since near the beginning and has significant personal investment in what's been built. Framing questions in ways that imply the company is behind industry norms \u2014 even unintentionally \u2014 can land poorly.\n\n**Softening phrasings to reuse:**\n- *\"Is that something the team has formalized, or is it still evolving?\"* (instead of \"Do you have a process for X?\")\n- *\"How does the team currently approach X?\"* (instead of \"Does the team have X in place?\")\n- *\"I'd love to understand how this works at Pantomath's stage\"* (instead of comparisons to larger companies)\n\n---\n\n## 5. Best Questions to Prioritize During the Call\n\nIf the conversation moves fast and time is short, these five questions carry the most signal:\n\n1. **Question 6 \u2014 The unsolved challenges.** Cuts through job description polish to reveal what the role is actually being hired to fix. The answer tells you more about the real job than anything else.\n\n2. **Question 8 \u2014 Connector architecture and pain points.** Essential for a technically grounded PM. You need to know whether you're inheriting a coherent framework or a collection of bespoke integrations \u2014 and what the hardest engineering problems are.\n\n3. **Question 16 \u2014 Strategic differentiation vs. table stakes.** Determines whether connectors are a competitive moat or infrastructure plumbing, which shapes how ambitious and visible the PM's work will actually be.\n\n4. **Question 12 \u2014 Where decision rights actually sit.** Empowered PM or execution PM? This is the structural question that determines whether Felix's strengths will be used or constrained.\n\n5. **Question 4 \u2014 30/60/90 day success.** Grounds the conversation in concrete expectations and reveals whether there's a burning deliverable waiting or a genuine onboarding window.\n\n---\n\n## 6. Suggested Call Flow\n\n### Opening \u2014 Establish rapport (first 2\u20133 minutes)\nStart with one of the conversation starters above. Opener A (the GE-to-Pantomath jump) is the strongest because it immediately establishes peer-level technical credibility and invites Bo to tell a story.\n\n> \"I saw you were at GE Aviation as Enterprise BI Program Leader right before joining Pantomath \u2014 I spent several years at IBM on enterprise BI products and later at Kaiser running a Splunk-based observability platform, so I'm curious what that jump to an early-stage startup felt like.\"\n\n### After discussing backgrounds \u2014 Anchor on the product\nOnce the rapport is warm, pivot to the strategic question that shows you're already thinking like an owner:\n\n> \"I'd love to understand where connectors fit in the broader product vision \u2014 is it primarily a distribution play, or is there a deeper technical differentiation story you're building toward?\"\n\n### When discussing the role \u2014 Get concrete\nMove into the operational questions that reveal what the job actually is:\n\n> \"What are the one or two biggest unsolved challenges in the connectors ecosystem right now \u2014 the things this hire is expected to make real progress on?\"\n\nFollow with the architecture question (Question 8) and the 30/60/90 question (Question 4).\n\n### Near the end \u2014 Culture and fit\nClose the substantive questions with the working style and autonomy questions:\n\n> \"How does Pantomath handle it when a PM has strong technical opinions that differ from engineering's instincts? I want to make sure I understand the culture around that kind of productive tension.\"\n\n### Closing \u2014 Leave on growth and shared energy\nEnd with something that signals long-term investment:\n\n> \"You moved from PM to Head of Product Strategy in four and a half years here \u2014 for someone coming in at the Senior PM level, what tends to differentiate the people who grow quickly?\"\n\n---\n\n## 7. Final Recommended Question Set\n\nIf time is short and you can only ask four to six questions, use these:\n\n1. **What are the one or two biggest unsolved challenges in the connectors ecosystem right now \u2014 the things this hire is expected to make real progress on?**\n2. **Is the connector architecture built on a shared internal framework, or is each integration more bespoke \u2014 and where are the biggest reliability or scalability pain points today?**\n3. **Where does Pantomath see connectors fitting into the broader product vision over the next two to three years \u2014 table stakes infrastructure, or a genuine competitive differentiator?**\n4. **How much autonomy does a Senior PM have over roadmap prioritization, and where do decision rights actually sit day to day?**\n5. **What does success look like at 30, 60, and 90 days \u2014 is there a specific initiative already waiting for an owner, or is there an audit-first onboarding window?**\n6. **You moved from PM to Head of Product Strategy in four and a half years here \u2014 what tends to differentiate the people who grow quickly?**\n\n---\n\n## 8. Strong Closing Line\n\nUse this \u2014 or a version of it \u2014 to close the conversation on a memorable, grounded note:\n\n> \"I've spent the last twelve years at the intersection of data infrastructure, developer platforms, and product leadership \u2014 from IBM's enterprise BI products to Splunk's search orchestration to scaling Intuit's platform to 675 million engagements. What excites me about this role is that it asks for all of that at once, in a space \u2014 connectors and integrations \u2014 where I've felt the pain from both sides. I'd love the chance to bring that into Pantomath.\"\n\n---\n\n## 9. Final Reminder\n\nThis conversation should demonstrate:\n\n- **Technical peer credibility** \u2014 Bo has a real data engineering background; speak his language, not around it\n- **Strategic ambition** \u2014 You're not just asking about the job, you're already thinking about the roadmap and the moat\n- **Founder-level ownership** \u2014 Your questions should signal that you think about outcomes, not just deliverables\n- **Intellectual honesty** \u2014 Bo values candor (see: TadPoL); don't oversell, don't hedge everything\n- **Long-term fit** \u2014 You're evaluating Pantomath as seriously as they're evaluating you; that confidence is appropriate and attractive",
  "source_artifact_id": "art_ecreldRZvf4",
  "source_kind": "candidate_questions",
  "doc_type": "questions_to_ask"
}