---
# System prepended metadata

title: Interview Questions

---

# Interview Questions

Round 1 - Done

Round 2 - In Progress


# Second Round Questions

## Get to know

I've been giving a quick intro on myself and then asking for a quick intro as well.

## Behavioral questions
Purpose: guage team values and communiction style. Asess for growth and self-awareness.

- What do you look for in a team environment and how do you promote this?
- What is your approach to proposing a new idea for a project? Have you ever had to persuade or encourage your co-workers to approach a task differently?
- Can you remember a time you and a team member disagreed and how you resolved it?
- What is your strategy for integrating working independently and with others?
- What have you found effective in your communication style and what are you currently experimenting with/improving?


## PM questions

Purpose: Understand thought process around product choices.

- Why are you interested in product? (I actually asked this spontaneously because Kyler didn't have prior product experience.)
 - What's your process for prioritizing different features to add?
- How do you incorporate feedback from different teams? Especially when there are conflicting angles and timescales that are all worth considering.
- At Govrn, we try to take a contributor-focused approach in our product as opposed to a purely dao-focused approach.  What are your thoughts on this?
- What do you see as the role of a PM?
    - How should the PM work with the developmment team to create a successful relationship?
- What do you think contributes to an intuitive product?
- What's the highest leverage or most important part of the product process in your opinion?  If there was one thing you wanted to be known for when it comes to product, what would that be?
    - Now walk me through the process of how you incorpoorate that into your daily work habits.
- What does a good user story or technical docs have?  Walk me through the specifics.

Use Case:
- You work on factory line that has 10 people work across 5 different stations (2 people per station)
- You need to design something for the workers to use if they needed to do an emergency stop of the production line.
    - The emergency stop can only occur if all 5 stations confirm a shut down.

*What to look for*
- For this to exist, each station needs a way to trigger this, be notified when someone pushed the button, etc.  So to start, at a minimum there needs to be a button for instance.
- Does the PM start by interviewing tthe workers at each station?  Do they take in the differences of the work they're doing?  Do they go ahead and build the full thing at once?  Break it up into smaller pieces.

## Engineer questions

I'm not sure what problem solving questions I would ask the engineering candidates since Keating has more in depth questions to ask for this and potentially a take home algorithm?

## Questions for me

I've been leaving the end of interviews for question time about Govrn/role/etc.

# Coordination Asks 


Asks: 
- portfolios/twitter linked in the hackmd
- A better way to run product manager part of the interview
- It would be helpful to know if I'm the first or second person to interview in the second round so I can read the other person's notes or ask the second person to ask anything I've missed.
    - e.g. Interviewed Kyler today and still have no sense what his product abilities are.
- Should I be asking engineers technical questions? I think Keating may have that covered?
    - In which case, I imagine I won't use the entire hour

   



## PM Roles and Responsibilites

Currently we're looking to hire for a traditional PM Role, the normal tasks you'll be asked to do are:
1. Pulling in observations from CBCE team and user feedback to generate new ideas
2. Create first stage of one pager documentation for the team to review on what we build next
3. Managing the backlog
4. Working with the Devs and Designers to push the product specs through the product lifecycle
5. Prioritize what gets built next
6. Work with dev team to answer any questions they have
7. Plan out the feature releases and own the changelog
8. Once a feature is deployed, run user feedback sessions to understand what is and isn't working.

### Traits
We are currently prioritizing someone that:
- Can operate as a convergent thinker:  we have a lot of threads moving at once and we need someone to balance us out by bringing us back to the page.
- Focused on Shipping:  Generating new ideas isn't our problem, we need someone that can ignore the noise and ship out work

