jobsearch v0.0.1

← benchling / Product Manager, Infrastructure

interviewer_questions / art_m9KSt3g5AzA

role
benchling / Product Manager, Infrastructure
model
anthropic/claude-sonnet-4.6
created
2026-10-07T18:13

Interviewer

Erik Nichols is a full-cycle recruiter at Benchling who has been with the company for nearly 8 years, making him one of the longest-tenured recruiters on the product team. His background spans technical recruiting at Asana, Nextdoor, Lookout, and Magenic, with deep experience in behavior-based interviewing and candidate experience. As a product-team recruiter rather than a hiring manager or technical leader, Erik's interview focus will center on motivation, culture fit, communication clarity, career narrative coherence, and whether the candidate meets the baseline qualifications Benchling has defined for this role. He will not probe deeply into technical architecture but will assess whether the candidate can articulate their experience in plain language and whether their trajectory makes sense for this specific PM role.

My profile through their lens

From Erik's perspective, Felix is a high-credential, multi-dimensional candidate whose resume may read as unusually broad — founder, staff PM, researcher, adjunct professor, pilot — which could raise questions about focus and commitment to a single-company PM role. The Intuit Staff PM tenure (3+ years, clear infrastructure scope, measurable outcomes) is the strongest signal of fit and will anchor the conversation. Erik will want to understand why Felix is pursuing an in-house PM role at Benchling after founding multiple startups, and whether the candidate can communicate infrastructure PM experience in accessible, non-jargon terms. The NeurIPS publication and deep AI/ML work are differentiators in a biotech AI context but Erik may not probe them technically — he'll care more that Felix can explain why Benchling specifically.

Questions they may ask (19)

categoryquestionwhyhow to prepare
resume_deep_dive Walk me through your time at Intuit as a Staff PM on Developer Frameworks and Platform Infrastructure. What was the scope of your ownership, and what does 675M engagements actually mean in practice? This is Felix's most directly relevant role to the Benchling JD. Erik will use this as the anchor question to assess whether the candidate can communicate infrastructure PM impact in plain language — a core recruiter screen for this role. Prepare a crisp 90-second narrative: team size, what you owned (ICE platform, SDK Starter Kits, MSaaS), the business problem each solved, and the 675M engagement metric contextualized (what is an engagement, why did it grow 275% YoY, what did you personally drive vs. what was organic).
resume_deep_dive You've been running two startups since September 2024 — Streamio AI and Fintellect AI — while also listing ongoing adjunct teaching. Why are you looking to return to an in-house PM role now, and how should I think about your bandwidth and commitment? Erik is a recruiter who has seen candidates with fragmented recent histories. The simultaneous founder + teacher + multiple-product-launch story from the last 8 months will be the first flag he needs to resolve before advancing the candidate. Be direct and honest: explain the strategic decision to pursue a high-impact in-house role, frame the founder experience as additive (0-to-1 product instincts, AI fluency, infrastructure hands-on), and address teaching as a part-time commitment that won't conflict. Avoid over-explaining.
resume_deep_dive You mention reducing developer onboarding from 2-3 weeks to minutes with the ICE Self-Service platform. How did you define and measure that outcome, and who did you have to convince to prioritize that work? The JD explicitly asks for a PM who can build business cases for infrastructure investment and make prioritization calls with senior stakeholders. This question tests whether Felix can demonstrate that skill with a concrete past example. Prepare the full story: what the baseline was, how you measured it (telemetry, surveys, time-to-first-deploy), who the skeptics were, and what the business case argument was. Quantify the $1M+ opex mitigation claim specifically.
resume_deep_dive You've listed a lot of technical projects — RL Workbench, aeval, AutoEval, BRAIN. For this PM role at Benchling, how do you see these projects as relevant, and are any of them ongoing commitments? Erik needs to assess whether the candidate's technical side projects are a distraction or a differentiator, and whether they represent ongoing time commitments that compete with a full-time role. Frame each project as a learning/credibility asset rather than an ongoing obligation. Be clear about which are complete vs. active. Tie the AI/ML depth to Benchling's stated mission of being an AI platform for biotech R&D.
technical_domain This role involves partnering on cloud economics — spend forecasting, cost optimization, vendor commitments. Can you walk me through a time you were directly involved in cloud cost decisions, and what your role was versus engineering's? The JD explicitly calls out cloud economics as a responsibility. Felix's Intuit experience (GCP-to-AWS migration, MSaaS, rSocket scaling) suggests exposure, but Erik will want to confirm the candidate can speak to this without overstating their technical role. Use the Mailchimp GCP-to-AWS migration or the rSocket throughput scaling as the anchor story. Be precise about what you owned (requirements, vendor coordination, business case) versus what engineering owned (architecture, implementation).
technical_domain How do you think about the difference between platform/infrastructure PM work and product PM work? What's harder about infra PM, and what do you find energizing about it? This is a standard recruiter screen for infra PM roles — they want to know the candidate has genuine affinity for the work, not just a resume line. Erik will use this to assess motivation and self-awareness. Articulate the specific challenges: invisible customers (internal engineers), hard-to-quantify impact, long time horizons, tension between reliability and velocity. Reference specific moments from Intuit or Splunk where you navigated these tensions.
technical_domain Benchling serves biotech scientists — not software engineers — as its primary end users, but this role is focused on the infrastructure underneath that product. How do you think about the relationship between internal engineering customers and the external scientists who ultimately depend on the platform? The JD calls out both internal engineering teams and external customers as discovery targets. Felix's Intuit experience is heavily internal-developer-facing, and Erik will want to know if the candidate can bridge to external scientific users. Acknowledge the two-layer customer model explicitly. Draw on the Intuit experience of serving both internal developers and end-product users (QuickBooks, TurboTax customers). Be honest about what you'd need to learn about biotech R&D workflows.
gap_transition You left Intuit in September 2024 and went directly into founding mode. What specifically about Benchling's infrastructure PM role made you decide this was the right opportunity to step back into a company versus continuing to build? Erik's job is to assess genuine motivation and reduce offer-decline or early-attrition risk. A candidate coming from founder mode needs a compelling, specific answer about why this company and this role — not just 'I want stability.' Research Benchling's infrastructure specifically — their scale (200K+ scientists, top 50 biopharma), their AI platform ambitions, and the specific infrastructure challenges implied by that scale. Connect your answer to genuine intellectual interest in the problem space, not just the job market.
gap_transition Your background spans biotech-adjacent AI (NeurIPS protein structure paper, BRAIN platform) but your PM career has been in fintech and enterprise software. How quickly do you think you could get up to speed on biotech R&D workflows, and what's your plan? Benchling is deeply domain-specific. Erik will want to know the candidate has thought about this gap and has a credible learning plan, not just confidence that their technical depth will carry them. Lean into the NeurIPS paper and Lawrence Berkeley Lab work as genuine biotech-adjacent credibility. Acknowledge the domain gap honestly and outline a specific learning plan: talk to scientists, read Benchling's public documentation, understand ELN/LIMS workflows.
behavioral_situational Tell me about a time you said no to a senior stakeholder on a prioritization decision. What was the ask, what was your reasoning, and what happened? The JD explicitly calls this out as a qualification: 'A track record of making real prioritization calls under pressure, not just facilitating consensus. You can describe a time you said no to a senior stakeholder.' Erik will almost certainly ask this verbatim or close to it. Prepare a specific story from Intuit or Splunk with a named stakeholder level (VP, CTO), a clear ask you declined, your reasoning (data, business case, opportunity cost), and the outcome. Avoid vague answers — this is a must-pass question.
behavioral_situational Describe a situation where you had to translate a complex infrastructure constraint into a business narrative for a non-technical executive audience. What was the constraint, how did you frame it, and what was the outcome? The JD requires bidirectional translation between technical and business stakeholders. Erik will use this to assess communication skills and executive presence, which are core recruiter evaluation criteria. Use the CTO-level Service Language Assessment from Intuit or the rSocket migration business case. Focus on the framing: what was the 'so what' for the executive, what did you leave out, and how did you handle pushback.
behavioral_situational Tell me about a time you had to coordinate across multiple engineering teams or organizations to deliver an infrastructure initiative. What made it hard, and how did you manage it? The JD calls out cross-org coordination and program management as explicit responsibilities. Felix's Intuit experience (Mailchimp migration, MSaaS Drift Detection, ICE across QuickBooks/TurboTax/Mint/Mailchimp/Credit Karma) provides material here. Pick one initiative with the most cross-team complexity. Map out the stakeholders, the conflict or misalignment, and what you specifically did to resolve it. Avoid making it sound like everything went smoothly.
behavioral_situational Give me an example of how you've used data to make a prioritization decision on an infrastructure or platform roadmap. What data did you have, what was missing, and how did you handle the uncertainty? The JD asks for outcome-focused roadmaps with defined metrics. Felix's resume mentions SQL/BigQuery telemetry work at Intuit and RICE frameworks at Splunk, which Erik may probe to assess analytical rigor. Use the Intuit telemetry/BigQuery work or the Splunk RICE framework story. Be specific about what metrics you tracked, what gaps existed in the data, and how you made the call under uncertainty.
role_specific_scenario Imagine you've just joined Benchling's infrastructure team. In your first 30 days, how would you go about understanding what the highest-priority infrastructure problems are? Who would you talk to, and what would you be trying to learn? This is a standard recruiter-level scenario question for PM roles that tests onboarding instincts, stakeholder awareness, and whether the candidate has a structured approach to discovery in an unfamiliar domain. Structure your answer around three discovery tracks: internal engineering teams (pain points, tech debt, reliability incidents), external customers (scale/performance needs surfaced through CSM or direct interviews), and business/finance stakeholders (cloud spend, cost optimization priorities). Reference your Intuit onboarding experience as a model.
role_specific_scenario The JD mentions defining metrics for infrastructure — reliability, cost, adoption, developer time saved. If you were setting the north star metrics for Benchling's infrastructure team in your first quarter, what would you propose and why? The JD explicitly lists this as a responsibility. Erik will use this to assess whether the candidate has genuine infrastructure PM instincts or is just pattern-matching to the job description. Propose a small set of metrics (3-5) with clear rationale: availability/SLA (reliability), cost per scientist or cost per API call (cloud economics), developer onboarding time or time-to-first-deploy (developer experience), and incident MTTR (operational health). Tie each to a business outcome.
motivation_fit Why Benchling specifically? What do you know about what we're building, and why does this problem space — biotech R&D infrastructure — matter to you? This is Erik's core motivation screen. As a recruiter who has been at Benchling for nearly 8 years, he has deep conviction about the mission and will quickly detect generic answers. Felix's biotech research background (NeurIPS, Lawrence Berkeley) gives him genuine material here. Connect your NeurIPS protein structure work and Lawrence Berkeley computational biology research to Benchling's mission explicitly. Reference specific Benchling customers (Moderna, Sanofi) or product areas. Demonstrate that you've used or researched the product.
motivation_fit This role is hybrid — 3 days in office in San Francisco. You're based in Oakland and currently running your own companies. How are you thinking about the transition to a structured in-office schedule, and what does your current work situation look like day-to-day? Erik is a logistics-aware recruiter who will want to confirm there are no practical blockers to the hybrid requirement and that the candidate's current founder commitments won't create conflicts. Be straightforward: Oakland to SF is a manageable commute, you're prepared for the hybrid schedule, and you've thought through how to wind down or background-mode the startup work. Don't be defensive — treat this as a practical logistics question.
unique_to_this_interviewer As part of Benchling's interview process, there's an AI-focused exercise or discussion. Can you walk me through how you're currently using AI tools in your day-to-day product work — not just what tools you use, but how they've changed how you work? The JD explicitly states: 'As part of our interview process, you'll complete a brief AI-focused exercise or discussion.' Erik, as the recruiter, will likely introduce or administer this component. Felix's AI depth is exceptional but he needs to translate it into PM workflow terms, not engineering terms. Prepare concrete examples of AI in PM workflows: using Claude/GPT for PRD drafting, customer interview synthesis, competitive analysis, or roadmap documentation. Reference your Vantage platform's AI interview prep tools as a product example. Keep it accessible — Erik is not technical.
unique_to_this_interviewer What questions do you have for me about the team, the role, or what success looks like in the first 6 months? Erik has been at Benchling for nearly 8 years and will expect thoughtful questions that demonstrate genuine research into the company and role. Weak questions here are a red flag for a recruiter who has seen thousands of candidates. Prepare 3-4 specific questions: ask about the infrastructure team's current biggest challenge, how the PM role interfaces with the engineering manager counterpart, what the previous PM in this role accomplished, and how Benchling measures PM success at the staff level.

Preparation priorities

  1. 1. Nail the 'why Benchling, why now' narrative — Erik has 8 years of Benchling conviction and will immediately detect generic motivation answers. Connect your NeurIPS/Lawrence Berkeley biotech research directly to Benchling's AI platform mission and prepare a specific, researched answer.
  2. 2. Prepare the 'said no to a senior stakeholder' story cold — the JD calls this out explicitly as a qualification, and Erik will almost certainly ask it. Have a specific, named-level story from Intuit or Splunk with a clear outcome ready.
  3. 3. Resolve the founder-to-in-house narrative proactively — the simultaneous Streamio + Fintellect + teaching story from the last 8 months is the biggest recruiter flag. Prepare a clear, confident explanation of why you're making this transition now and what you're doing with the startup work.
  4. 4. Translate infrastructure PM impact into plain language — Erik is not technical. Practice explaining the ICE platform, rSocket migration, and SDK Starter Kit work in terms a non-engineer can understand and find compelling. Avoid acronyms without definition.
  5. 5. Prepare for the AI-focused exercise — the JD explicitly flags this as part of the process. Prepare concrete examples of AI in your PM workflow (not just your engineering work) and be ready to discuss how AI tools have changed your approach to discovery, prioritization, or stakeholder communication.

⚠ Watch-outs