Tips for Coinbase Staff Product Design Portfolio Review

Samsung
23y2i74

Go to company page Samsung

23y2i74
Yesterday 5 Comments

I have my portfolio review coming up and was wondering if there is anything specific I should focus on for staff level. This is what the recruiter mentioned "We ask that you walk us through the problem you were solving, your range of explorations, and the solution you arrived at"

This seems general and very lean - Should I also include exp navigating organizational complexity, Cross Domain co-workings, stakeholders and tradeoffs, key challenges, etc... or is that something they will be looking for signals for later on in the process?

#design #interviews #ui/ux #coinbase

comments

Want to comment? LOG IN or SIGN UP
TOP 5 Comments
  • I would hope that anyone who is interviewing people for staff roles would want to see more than just product designs in a presentation. I would definitely recommend showing how you manage organizational challenges.
    Yesterday 2
    • How would you demonstrate this
      Yesterday
    • By presenting a project that was riddled with them but still successful thanks to your efforts.

      It can still be a design project (although it could be something else as well), but instead of focusing on how or why you designed a feature or product in a particular way, you focus on how you managed a redesign through a reorg or how you led the design of a feature set that involved 3 distinct areas that your team didn’t own or how you managed up to stop a nightmare HiPPO from ruining a project.
      Yesterday
  • Meta
    πŸ”Ή blue

    Go to company page Meta

    πŸ”Ή blue
    Yes you should. Dm for a review session
    Yesterday 1
    • Samsung
      23y2i74

      Go to company page Samsung

      23y2i74
      OP
      Do you have any tips for structure - This is my first time interviewing for staff level roles and not sure how to structure. I usually cherry pick projects but as a Staff Designer I have a handful of projects I led for the product area I own - How should I frame my experience owning a product area vs just deep diving into constituent projects. Currently my approach is to just take it up a level so outline from a highlevel

      - Business, User goals/needs as they pertain to the product area

      - My role and co-working (e.g cross functional partnerships, navigating organizational complexity, etc...)

      - Show the different projects explorations to move those metrics, (show some visuals)

      - Outcome/Results
      Yesterday