Відео

how did it go?

Thanks Edward! Let us know if there's anything you want us to cover as well!

Thanks Wicks!

Hi Chris, good question! While you may not need to draw out a flow chart in general, it's best to let the interviewer understand the user flow, even if that is just in words as you're drawing a few connected screens. Arguably, many apps can be a single view with dynamic widgets, but showing when and how those widgets sequence based on user action and intent will help show that you are thinking about the overall user experience and not just focusing on the UI.

Hi Mikhail, great question! We are working on some things on our side to offer services to practice this later in the year, but for the meantime, I would advise trying to grab a mentor on a site like www.adplist.org/ to help you!

Glad it was helpful!

Thanks John! I actually learned that from someone I was interviewing. He did an awesome job pausing and recapping and it made a big impact! It made it much easier for me to understand his train of thought and removed a lot of the inferring and ambiguity, so even if he wasn't able to go as far, I understood his thinking and what he would do.

​@@BoldUX That brings up another question, in the context of a timed interview of say < 1 hour. Would you be looking for someone who didn't get as deep/far but walked you through it perfectly where you are in complete alignment/understanding, or someone who was able to finish and build out the solution to completion on the board, but now leaves you with a bunch of questions that you need extra time to dig or follow up.

Great question! I'm normally looking for both someone who can break down the initial problem to something manageable and show some solution to the problem. I'd lean more on someone who has a solid approach to the solution but maybe didn't have time to fully sketch it out than some one who sketched out a solution but didn't break it down or explain it. That being said, if they didn't show any ability to execute, that's a major red flag as well. If there's 1 hour of time to whiteboard, the breakdown and approach to the problem as well as weighing potential solutions could be 65-75% of the time with the remaining pieces being executing on an idea. Typically, if they have broken the idea down, it's pretty simple to sketch a solution, so doesn't take much time. You normally see more junior designers start quickly and start uncovering issues as they sketch, which pushes them back toward weighing solutions and evaluating the problem and requirements.

Thanks Scott!

Thanks for the kinds words!

🤣 That one was too much of a layup to not comment on

Good question! Normally, I see culture fit from 2 different angles: how the candidate feels like they fit into the team or product and how the interviewer sees the candidate fitting into the company or team. As a candidate, I would advise you spend time interviewing the people on the team about the culture and product and try to gauge our personal interest in the product and team members. See how easy it is to talk to them, how open they are to ideas, etc. as you talk, especially during whiteboards or brainstorming type interview tasks. From the company side, I tend to want to lessen this idea as I think companies use bias in the interview process which leads to less diversity in thinking. If the candidate expresses clear interest in another space or disinterest in yours, it may be best to guide them to another team within your company or another role, because passion, excitement, and intrigue into an area or piece of the process will lead to better design and a more successful candidate when hired.

Glad it was helpful!

Thanks for watching Manny!

Glad you enjoyed it

Much appreciated

Thanks for the positive vibes! We'd love to know any other topics you're interested in as well so we can speak about them!