jobsearch v0.0.1

← benchling / Product Manager, Infrastructure

interviewer_questions / art_siFtVaRFGiY

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 Sun Microsystems, giving him a strong pattern-matching instinct for what 'good' looks like in product roles at growth-stage tech companies. As a recruiter rather than a hiring manager or technical leader, his interview focus will center on motivation/fit, communication clarity, career narrative coherence, and whether the candidate maps cleanly to the role's stated qualifications. He will not probe deep technical architecture but will screen hard on role alignment, culture fit, and whether the candidate can articulate their story compellingly to a non-technical audience.

My profile through their lens

From Erik's recruiter perspective, Felix presents as an unusually technical PM candidate — NeurIPS publication, hands-on AI/ML builds, and 12+ years spanning IBM engineering through Staff PM at Intuit — which is a strong signal for a role requiring infrastructure credibility. However, the resume is dense and founder-heavy since 2024, which a recruiter will want to understand: is this a candidate returning to a PM role after a startup detour, or someone who prefers founding? Erik will also notice the breadth of industries (fintech, real estate, biotech-adjacent research) and want to understand why Benchling specifically. The Intuit Staff PM role with 675M+ engagements and developer platform ownership is the clearest analog to this role and will anchor the conversation. Erik may also flag the gap between Felix's most recent W-2 role (Sept 2024) and now, and will want a clean narrative around the founder period.

Questions they may ask (20)

categoryquestionwhyhow to prepare
resume_deep_dive Walk me through your time at Intuit as a Staff PM on Developer Frameworks and Platform Infrastructure — what did you own end-to-end, and what was the biggest prioritization call you made? This is the most directly relevant role on the resume to the Benchling JD. Erik will use this as the anchor for the entire screen — it demonstrates infrastructure PM experience, developer-facing platform work, and scale. He needs to confirm the candidate can articulate it clearly to a non-technical audience. Prepare a crisp 2-minute narrative: what the platform was, who the customers were (internal devs), what you owned, and one specific prioritization call where you said no to something. Quantify impact (675M engagements, 2-3 week to minutes onboarding) without going too deep technically.
resume_deep_dive You've been running two AI startups since September 2024. What prompted you to step back from Staff PM at Intuit, and what are you looking for in returning to a PM role now? Erik will flag the Sept 2024 departure as a potential risk signal — is this candidate committed to a PM role or will they leave again to found something? This is a standard recruiter screen for candidates with recent founder stints. Prepare an honest, forward-looking answer: what you learned founding, why a PM role at a company like Benchling is the right next chapter, and why now. Avoid making it sound like the startups failed — frame them as intentional learning that makes you a better infrastructure PM.
resume_deep_dive Your resume spans IBM engineering, Kaiser SOA, Splunk search orchestration, Intuit developer platforms, and now AI startups. How do you connect those dots into a coherent PM story for this infrastructure role? Recruiters at growth-stage companies like Benchling look for narrative coherence. Erik has seen hundreds of PM resumes and will want to understand the through-line, especially given the breadth of Felix's background. Craft a 60-second career narrative that threads: engineering foundation → enterprise infrastructure PM → developer platform scale → AI-native builder. Land on why infrastructure PM at a biotech AI platform is the logical next step, not a lateral move.
resume_deep_dive You mention teaching at De Anza College since 2018 alongside full-time roles. How do you manage that alongside demanding PM work, and what does it signal about how you operate? Erik will notice this unusual ongoing commitment and may probe it as either a scheduling concern or a character signal. It's been concurrent with Intuit Staff PM and the founder period. Frame it positively: it keeps you sharp on fundamentals, forces you to explain complex concepts simply (a core PM skill), and reflects a commitment to community. Clarify it's manageable (evening/weekend courses) and hasn't impacted professional performance.
technical_domain At Intuit, you scaled ICE from 6K to 50K TPS via rSocket migration. Without getting into the weeds, how did you as a PM contribute to that decision — what was your role versus engineering's role? The Benchling JD explicitly states the PM is 'not expected to be a systems architect' but must make 'crisp trade-off calls.' Erik will want to confirm Felix understands the PM/engineering boundary and can articulate his contribution without overclaiming technical ownership. Be precise: your role was defining the business case (latency SLA, cost, developer experience), aligning stakeholders on the why, and holding engineering accountable to outcomes — not designing the rSocket protocol. Have a clear answer for 'what would have happened if you hadn't pushed for this?'
technical_domain Benchling's infrastructure PM will need to partner on cloud economics — spend forecasting, cost optimization, vendor commitments. Do you have experience translating infrastructure investment into a business case for non-technical executives? The JD calls out cloud economics as a specific responsibility. Felix's Intuit experience (GCP-to-AWS migration, $1M+ opex mitigation) and Splunk work are relevant, but Erik will want to hear Felix frame it in business terms, not technical ones. Prepare a specific example: the ICE Self-Service platform reducing onboarding from weeks to minutes and mitigating $1M+ opex is perfect. Practice translating it into a business narrative: 'Here's what it cost, here's what it saved, here's how I made the case to leadership.'
technical_domain You've built developer SDKs and platform tooling at Intuit. How do you think about measuring the success of infrastructure investments where the 'customer' is an internal engineering team rather than an end user? Benchling's infra PM must 'define the handful of metrics that matter' for reliability, cost, adoption, and developer time saved. This tests whether Felix can translate internal platform work into outcome-based metrics, a core JD requirement. Use the Intuit DevPortal/ICE example: developer onboarding time, TPS throughput, engagement growth, and opex savings. Be ready to discuss leading vs. lagging indicators and how you'd set up a metrics framework for an infra team.
gap_transition You've been a founder for the past 9 months. How do you think about the shift from setting your own direction entirely to operating within a company's existing roadmap and organizational constraints? This is a classic recruiter concern for returning founders. Erik has seen candidates struggle with this transition at Asana and Benchling. He needs confidence that Felix won't chafe at organizational structure. Acknowledge the difference honestly, then pivot to what you're excited about: the leverage of a large engineering team, the depth of customer relationships, the ability to focus. Reference your Intuit experience as evidence you thrive in structured environments.
gap_transition Benchling is a biotech R&D platform — your background is in fintech, enterprise software, and AI. What have you done to get up to speed on the biotech domain, and how quickly do you think you could be credible with Benchling's scientific customers? Erik will flag the biotech domain gap. Benchling's customers are scientists at Sanofi, Moderna, and academic labs — Felix has no direct biotech PM experience. This is a real gap the recruiter will probe. Be honest about the gap but demonstrate curiosity: reference any adjacent work (BRAIN protein structure prediction, Lawrence Berkeley Lab RNA/DNA analysis, NeurIPS paper) as evidence of scientific fluency. Emphasize that infrastructure PM is more about engineering pain than domain science, and that you've learned new domains quickly before (Kaiser healthcare, Splunk security).
gap_transition Your most recent Staff PM role was at a company with 10,000+ employees. Benchling is smaller and faster-moving. How do you think about operating in a company at that stage? Erik has recruited for both Asana (growth stage) and Benchling (scale-up). He'll want to assess whether Felix is comfortable with the ambiguity and pace of a company that's not yet at Intuit's scale. Reference your founder experience as evidence of comfort with ambiguity, and your Splunk experience (smaller than Intuit) as a bridge. Emphasize that you prefer environments where you can see the direct impact of your decisions.
behavioral_situational Tell me about a time you said no to a senior stakeholder on a prioritization call. What was the situation, what was your reasoning, and what happened? The JD explicitly calls out '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 ask this verbatim or close to it — it's a stated qualification. Prepare a specific STAR story from Intuit or Splunk. The Service Language Assessment presented to the CTO is a strong candidate — you had data, you made a recommendation, and presumably had to defend it. Be specific about who you said no to and what the outcome was.
behavioral_situational Describe a time you had to coordinate across multiple engineering teams with competing priorities. How did you keep the infrastructure roadmap moving without direct authority over those teams? The JD calls out 'coordinate across orgs' and 'program management is required.' Felix's Intuit experience coordinating across 20 mobile apps and 30+ SKUs is directly relevant, but Erik will want a behavioral story, not a resume summary. Use the Mailchimp GCP-to-AWS migration or the MSaaS Drift Detection program as your story — both required cross-team coordination without direct authority. Focus on how you built alignment, not just what you shipped.
behavioral_situational Tell me about a time you had to translate a complex infrastructure constraint into a business narrative for a non-technical audience. How did you frame it, and did it land? The JD requires 'comfort translating technical constraints into business narrative.' Erik will probe this because it's a core differentiator between infrastructure PMs who get stuck in engineering and those who can influence the business. The $1M+ opex mitigation story from Intuit ICE Self-Service is ideal. Practice telling it in 90 seconds: what the constraint was, what it meant for the business in plain language, and how you got buy-in.
behavioral_situational Give me an example of a time you had to make a product decision under incomplete information. What was your process, and how did you know when you had enough to move? The JD states the PM must 'make crisp trade-off calls under incomplete information.' This is a standard behavioral probe for PM roles, and Erik will use it to assess decision-making maturity. Use the Splunk Scheduler Service delivery (June–Oct 2019, ~4 months) as your story — fast delivery under uncertainty. Or use a founder decision from Streamio/Fintellect where you had to ship without full data. Focus on your decision framework, not just the outcome.
role_specific_scenario Imagine you're 60 days into the role at Benchling. You've done discovery with the infrastructure engineering team and identified 8 potential roadmap items. How do you decide what goes on the roadmap and what doesn't? This is a role-play on the core JD responsibility: 'own prioritization and roadmap.' Erik will use this to assess whether Felix has a structured approach to infra PM prioritization and can communicate it clearly. Reference your RICE framework experience from Splunk and your telemetry/usage data work at Intuit. Walk through a lightweight framework: business impact, engineering cost, reliability risk, customer pain signal. Be explicit that you'd validate with both engineering and business stakeholders before locking anything.
role_specific_scenario Benchling's infrastructure serves 200,000+ scientists at companies like Sanofi and Moderna. If a major reliability incident occurred and you needed to communicate the impact and resolution plan to both engineering and executive stakeholders, how would you approach that? The JD calls out 'report on outcomes' and reliability as a key metric. This scenario tests whether Felix can operate as the connective tissue between engineering and business during high-stakes moments. Draw on the Kaiser Splunk Logging-as-a-Service experience (1.7TB daily, 200+ enterprise customers) — you've managed high-stakes infrastructure with real customer impact. Prepare a clear framework: immediate triage communication, root cause timeline, business impact quantification, and remediation roadmap.
motivation_fit Why Benchling specifically? There are a lot of infrastructure PM roles at AI companies right now — what makes this one the right fit for where you want to go? This is Erik's core recruiter question. He needs to know Felix isn't spray-applying to every AI PM role and that there's a genuine pull toward Benchling's mission and stage. After 8 years at Benchling, Erik is a culture carrier and will probe for authentic motivation. Connect your scientific background (UC Berkeley Computational Engineering, BRAIN protein structure prediction, Lawrence Berkeley Lab) to Benchling's mission of accelerating biotech R&D. Be specific: 'I've worked on protein structure prediction since 2004 — the idea of building infrastructure that helps scientists do that work faster is genuinely compelling to me.'
motivation_fit Benchling emphasizes AI fluency as a core expectation for every employee. How are you using AI in your day-to-day work today, and how would you bring that into this PM role? The JD explicitly states 'AI fluency is the foundation we build on' and that the interview process includes 'a brief AI-focused exercise or discussion.' Erik will ask this as a standard screen for all candidates. Felix's background here is exceptionally strong. This is your strongest card — play it confidently but don't overwhelm. Lead with practical PM applications: using AI for customer discovery synthesis, PRD drafting, metric analysis. Then briefly reference your RL workbench and aeval platform as evidence of deep AI fluency. Keep it grounded in 'how I'd use it in this role' not just 'look at what I've built.'
unique_to_this_interviewer What do you know about Benchling's culture and how teams work together, and what questions do you have for me about what it's actually like to work here day-to-day? Erik has been at Benchling for nearly 8 years — he is the institutional memory on culture. Recruiters at this tenure level appreciate candidates who ask thoughtful questions about culture, not just the role. This also signals genuine interest. Prepare 2-3 specific questions for Erik: ask about how the infrastructure team interfaces with product teams, what the onboarding experience looks like for PMs, and what separates the PMs who thrive at Benchling from those who don't. Avoid asking about compensation or benefits in this screen.
unique_to_this_interviewer You've been recruiting for Benchling's product teams for nearly 8 years. What does the profile of a successful PM at Benchling look like, and how do you think about what makes someone a strong fit for the infrastructure PM role specifically? This is a strategic question that turns the interview into a dialogue. Erik will appreciate the meta-awareness, and his answer will give Felix real signal about what the hiring team is actually looking for beyond the JD. Ask this toward the end of the conversation after you've demonstrated strong answers. Listen carefully — Erik's answer will tell you what to emphasize in subsequent interviews with the hiring manager and engineering team.

Preparation priorities

  1. 1. Career narrative coherence: Prepare a tight 60-second story connecting IBM engineering → Kaiser/Splunk infrastructure PM → Intuit Staff PM → founder → Benchling. The founder period needs a clean forward-looking frame, not a defensive one.
  2. 2. Intuit ICE/DevPortal deep dive: This is your anchor story for infrastructure PM credibility. Prepare specific metrics (675M engagements, 6K→50K TPS, 2-3 weeks→minutes onboarding, $1M+ opex), one prioritization call where you said no, and one business narrative you built for non-technical stakeholders.
  3. 3. Biotech domain bridge: You have more scientific credibility than most PM candidates (BRAIN protein structure, Berkeley Computational Engineering, Lawrence Berkeley Lab) — connect it explicitly to Benchling's mission. Practice the 30-second version of why this domain resonates personally.
  4. 4. AI fluency demonstration: The JD explicitly requires an AI-focused discussion. Prepare a concise answer covering: (a) how you use AI in PM workflows today, (b) one concrete example from your founder work (aeval, RL workbench), and (c) how you'd apply it in this specific role. Don't over-engineer this — Erik wants practical fluency, not a research talk.
  5. 5. Behavioral stories inventory: Prepare STAR stories for: (1) saying no to a senior stakeholder, (2) cross-org coordination without authority, (3) translating technical constraints into business narrative, and (4) making a decision under incomplete information. These map directly to stated JD qualifications and Erik will probe at least 2-3 of them.

⚠ Watch-outs