3. The goal of any interview is to get to know one another.
It’s important to remember:
You have as much of an opportunity to ask questions as the interviewer does
Expressing your interest and desire to learn about the job is critical
Preparation is very difficult to fake
GOAL
4. Here are some questions I would expect an A to ask:
What skillsets do you think someone needs to be successful in this role?
Where do you think I can make the largest immediate impact?
Who specifically should I also be talking with at your organization to get a better picture of the current state?
If you had the money to hire 10x people, where would you hire them to?
Assuming you would be my boss, how would I be able to make you successful?
Knowing your product and market, what do you feel is your competitive advantage when compared to (x)
Given the constraints of a startup, what recent, major successes have you had?
SHOW INTEREST
5. Having a coached response for what you’re bad at, is becoming a bad idea.
Having a coached response for what you’re good at is a great idea!
It is important to know what you’re passionate about
It is important to know how technology intersects with your passions
It is important to know what past work you are proud of
It is important to know your “secret sauce”
KNOW YOURSELF
6. Can this person differentiate between solving problems and building solutions?
Does this person understand how product/engineering interact and
problems/benefits of various approaches?
Is this person a constant learner?
Does this person have good customer empathy?
Does this person care about the products they’re leading?
WHAT I LOOK FOR
