Key Insights for Your 1-Hour Interview

Based on this conversation, here are the areas to focus on:

1. Technical Collaboration (25 minutes)

Deep dive opportunities:

• The Craft Talent Hub project - She spent 1.5 years building a talent marketplace with engineers. Get specifics:
  • How did she communicate product requirements?
  • What was her role vs. the engineers in making technical decisions?
  • How did she handle disagreements about technical approach?
  • What would she have done differently?
• Data structure collaboration - She seemed excited about your mention of the "Qwestly Profile" data model. Test her ability to:
  • Think systematically about data architecture
  • Communicate technical concepts clearly
  • Partner with engineering on product decisions

2. Growth Mindset & Adaptability Assessment (25 minutes)

Red flags to explore:

• She mentioned being "allergic to operating inefficiently" after seeing operational issues at the search firm
• How does she handle ambiguity vs. wanting efficient processes?
• Can she be scrappy when needed, or does she expect mature systems?

Questions to ask:

• "Tell me about a time you had to work with broken or inefficient systems - how did you adapt?"
• "At a startup, we often have to choose between speed and perfection. How do you think about those tradeoffs?"

3. Product Vision vs. Execution (10 minutes)

She clearly has domain expertise, but can she think strategically about product evolution?

Recommended Questions for Your 1-Hour

Technical Partnership:

1. "Walk me through how you worked with engineers on the Craft Talent Hub - what was your process for defining requirements?"
2. "If you disagreed with a technical decision the engineering team made, how would you handle it?"
3. Based on what you know about our product, what do you think are the data model challenges compared to typicall Applicant Tracking System?
4. "Looking at our current data model challenges, how would you approach collaborating with me to solve them?"

Growth/Adaptability:

1. "You mentioned being allergic to inefficiency - how do you balance that with startup scrappiness?"
2. "What's an example of when you had to learn something completely outside your wheelhouse?"
3. "How comfortable are you with ambiguous role definitions that evolve monthly?"

Product Thinking:

1. "What's the biggest risk you see in our approach to building this marketplace?"
2. "If you could design the ideal recruiting data model from scratch, what would it look like?"

Things That Stood Out

🟢 She brings immediate value - 1,400 candidate database, VC relationships, domain expertise 🟢 Product mindset - Got excited about data structures and technical problems 🟡 Efficiency focus - Could be great or could clash with startup chaos 🟡 Role expectations - Need to ensure she's truly ready for startup ambiguity

Overall, this intro call set you up perfectly for a focused technical assessment. She seems genuinely excited about the problem and has relevant experience collaborating with engineering teams. Your 1-hour should focus on validating that she can be a true technical partner, not just a domain expert.

---