LendingClub·Product Manager·Technical Phone Screen·Intermediate

Intermediate

Jun 2026

Summary

Interviewed at LendingClub for what seemed like a product or engineering role touching autonomous systems. The content was pretty sparse so hard to say much beyond that one question came up about self-driving cars, which felt like it came out of nowhere for a fintech company.

Questions Asked (1)

How would you approach launching and testing a self-driving car?

Product StrategyA/B Testing & ExperimentationAdaptability & Ambiguity

Author's notes

Weird question for a lending company, right?

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by clarifying that while self-driving cars are outside LendingClub's domain, you'd apply a structured product management approach: define the problem, identify key metrics, and design a phased rollout with rigorous testing. Emphasize safety, regulatory compliance, and iterative learning through simulation and real-world pilots, mirroring how you'd de-risk any high-stakes product.

Pro tip: Acknowledge the unique safety and regulatory constraints of autonomous vehicles, and propose a staged approach that starts with geofenced, low-speed environments and gradually expands—showing you understand risk management and incremental value delivery.

1. Define Vision and Success Metrics

Articulate the product vision (e.g., safe, reliable autonomous mobility) and define clear success metrics such as safety incidents per mile, intervention rate, and customer satisfaction.

2. Conduct Feasibility and Risk Assessment

Evaluate technical, regulatory, and ethical risks. Identify constraints like sensor limitations, liability, and local laws, and prioritize use cases (e.g., highway driving vs. urban).

3. Design Phased Testing Strategy

Start with simulation and closed-course testing, then move to supervised real-world pilots in geofenced areas. Use A/B testing to compare algorithms or sensor configurations in controlled settings.

4. Iterate with Data and Feedback

Collect data from each phase, analyze failures, and iterate rapidly. Incorporate edge cases and continuously update models based on real-world performance.

5. Scale Gradually with Monitoring

Expand operational design domain (ODD) incrementally, ensuring safety and regulatory compliance at each step. Maintain robust monitoring and fallback systems.

Key Points to Mention

Safety as the top priority and non-negotiable metric
Regulatory and ethical considerations (e.g., NHTSA guidelines, liability)
Phased rollout: simulation → closed course → geofenced pilots → public roads
A/B testing and experimentation in controlled environments
Data-driven iteration and edge case handling
Cross-functional collaboration (engineering, legal, policy, UX)

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.