- What is the biggest challenge users face with the product?
- Are there any significant drop off points in the experience?
- What are some features users are expecting or inquire about?
- How much of things built come from designs?
- What areas of the product do you feel need design support?
- How much of the product does design typically touch?
- How do you conduct design reviews?
- What does your frontend/component library look like?
- Are there areas of product debt that you're interested in tackling early?
- How do you do design requests?
- How do you source new features?
- What do you use to track product events?
- How do you validate tests?
- What are low-hanging features left to work on?
- What are larger features to be developed in coming year?
- What are the uncharted areas?
- How do you balance feature development between core roadmap, product maintenance, user request and internal tools?
- Where are you looking for a product designer to make a majority of contributions?
- What all design and organizational tools do you use on the team?
- What engineering or product tools are you required to use?
- Describe the teams and design process?
- How do you balance between marketing, product and research?
- What will be the primary concern of the role in the near term?
- What areas of the product require the most attention?
- What is the culture of standups and grits?
- How much is the design team budgeted to grow in the next year?
- Audience: Legal professionals and operations
- Mission: To deliver better software to a technologically underserved profession
- Core Values: Trust, Integrity and Initiative
- Product Leads: Diana Hasan, VP of Product
- Tech Stack: React, Postgres, Amplitude…