<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[The Product Design Interview - Medium]]></title>
        <description><![CDATA[Exports from my interview memory bank and excerpts from the book - Medium]]></description>
        <link>https://medium.com/the-product-design-interview?source=rss----6ea50094d8f---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>The Product Design Interview - Medium</title>
            <link>https://medium.com/the-product-design-interview?source=rss----6ea50094d8f---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 07:14:21 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/the-product-design-interview" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[What to expect in a product design interview]]></title>
            <link>https://medium.com/the-product-design-interview/what-to-expect-in-a-product-design-interview-e70a8b44567?source=rss----6ea50094d8f---4</link>
            <guid isPermaLink="false">https://medium.com/p/e70a8b44567</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[interview-preparation]]></category>
            <category><![CDATA[interview-tips]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Nishtha H. Dalal]]></dc:creator>
            <pubDate>Sat, 15 May 2021 15:46:27 GMT</pubDate>
            <atom:updated>2021-05-15T16:05:19.320Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ICgdiTJEAj1ePm20QfcB1Q.png" /></figure><p><em>Excerpts from </em><a href="https://nishthadalal.com/the-product-design-interview"><em>The Product Design Interview</em></a><em> — waitlist for the book is now open, extras available for download.</em></p><h3><strong>Recruiter Screen</strong></h3><p><em>30 minutes — 45 minutes</em></p><p>This round usually lasts about 30 minutes and is the initial screener. You can expect to speak with a general recruiter if it’s a smaller company or a recruiter who works with the product team in general, specific to the design organization or if the company is really big some smaller design teams or sub-organizations have team-specific recruiters. In general the recruiter will ask you questions to see if you fit the job description.</p><p>Preparation: Read through job description, research the recruiter, team and role you applied for.</p><h3><strong>Design screen</strong></h3><p><em>30 minutes — 1 hour</em></p><p>This round takes a few different forms — it could either be a casual conversation with the hiring manager or a designer on the team. The call itself will focus on who you are as a designer, your design experience and contributions, and your design process. Some interviewers may do an informal portfolio review by talking through a recent project or walking through a case study on your portfolio. You may also have a conversation about your career goals and your ideal next role in this round. You will have some time to ask the interviewer questions about the role, what they’re looking for and anything else on your mind.</p><p>Preparation: Design process, abridged recent project walkthrough, questions for the interviewer.</p><h3><strong>Design challenge</strong></h3><p><em>5–10 hours</em></p><p>This is a step some companies add in either after the recruiter screen or before the full onsite round. You could defer doing the challenge to later in the process by talking to the recruiter or hiring team about specific concerns, but for some this may not be an option to ensure they pursue all possible interview options. Companies and recruiting teams will tell you to spend about 5 hours on it but unfortunately it may take closer to 8–10 hours. The issue here is that if you spent the prescribed amount of time, there’s no guarantee other candidates won’t spend longer so it’s in your best interest to first set up expectations on the contents of the deliverable, fidelity of the designs, etc. before jumping into the challenge itself. Once you have that information you can time-box yourself and focus on the most important parts that the hiring team wants signal on e.g. interaction design, visual design, or something else.</p><p>Preparation: Follow-up questions about the challenge, UI Kits for wireframes, dedicated focus time.</p><h3><strong>Onsite interview</strong></h3><p><em>5–8 hours</em></p><p>In normal times this would be either over one full day or two half-days spent at the company office with different members of the team, getting a quick peek into office culture, informal lunches, and an office tour. In the remote world this would be a series of video calls with panels and interviewers.</p><p>Preparation: Good sleep, positive and confident mindset, granola bars and water.</p><h3><strong>Portfolio review</strong></h3><p><em>45 minutes — 1.5 hours</em></p><p>A typical onsite interview will kick off with a portfolio review where you will share a few of your proudest design projects in a formal presentation to the interview panel. Most interviewers from the rest of your day will be present in this round and it will help them get context of your work, background and set them up to ask you relevant questions in the breakout interviews. The recruiting team will help you prepare this presentation by telling you what the team likes to see — e.g. how many projects to include, how long to spend on each, what skills and process steps to focus on (e.g. final designs, research, explorations and iterations, etc.). The panel will ask you questions either during your presentation, between projects, or at the very end. They may reserve some questions for the one on one conversations.</p><p>Preparation: Compiled deck with chosen projects, timed practice sessions, peer review of deck</p><h3>App Critique</h3><p><em>45 minutes — 1 hour</em></p><p>Some companies will have a round focused on how you analyze and critique products that are out in the real world. You’re expected to co-select an app with your interviewer who will most likely be a designer. Once you choose the app you go through the product together and talk about what’s working well, what you would do differently, think critically about how the design team landed on the flows and product that is currently live, speculate as to what success looks like for the design and product teams, and whether they’ve achieved it.</p><p>Preparation: Practice sessions individually or with a peer</p><h3><strong>Problem solving</strong></h3><p><em>45 minutes — 1 hour</em></p><p>This round has a few different names — white-boarding, problem solving, collaboration exercise, design exercise. The format itself can vary slightly based on the type of prompt you are given but you can typically expect to spend about an hour with designers and sometimes product managers solving a problem on a whiteboard (or collaborative tool for remote interviews) and sketching out possible solutions. Prompts for this round can range from elevator button designs or driverless car designs to specific UX flows like optimizing booking / purchase completion on a website.</p><p>Preparation: Practice for prompts on the spectrum of broad design problems to specific UX design flows, structure for how you’ll approach the prompt, familiarity with the remote collaboration tool for remote interviews.</p><h3><strong>One on one conversations</strong></h3><p><em>30–45 minutes each</em></p><p>You can expect a series of 1:1 conversations with key members of your immediate team. If you’re interviewing for a specific role you’ll most likely meet with your future Product Manager, Engineering Lead, UX Researcher, and a few designers you would work closely with if you were to join. In addition to this you can expect another 1:1 conversation with your hiring manager. The primary goal of the cross-functional conversations is to get a sense of your working style, collaboration skills, and how you’d approach tough situations with each of your stakeholders. In each session you’ll also have a few minutes to ask questions.</p><p>Preparation: Think about how you work with research, product, and engineering. Background information on the team, questions specific to each area of practice.</p><blockquote>Excerpts from <a href="https://nishthadalal.com/the-product-design-interview">The Product Design Interview</a> — waitlist for the book is now open, extras available for download.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e70a8b44567" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-product-design-interview/what-to-expect-in-a-product-design-interview-e70a8b44567">What to expect in a product design interview</a> was originally published in <a href="https://medium.com/the-product-design-interview">The Product Design Interview</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Spotify Product Design Interview]]></title>
            <link>https://medium.com/the-product-design-interview/spotify-product-design-interview-a598488c5f00?source=rss----6ea50094d8f---4</link>
            <guid isPermaLink="false">https://medium.com/p/a598488c5f00</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[spotify]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[interview]]></category>
            <dc:creator><![CDATA[Nishtha H. Dalal]]></dc:creator>
            <pubDate>Sat, 15 May 2021 15:33:57 GMT</pubDate>
            <atom:updated>2021-03-24T13:37:38.940Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DHQpDaB6t69ripfINYoSKA.png" /></figure><p>An extra from <a href="https://nishthadalal.com/the-product-design-interview">The Product Design Interview</a> book</p><p>A few years ago I found myself wanting a different type of design role — one that had a bigger team yet allowed me to have a significant impact to the entire product. I interviewed and landed offers at some of the most coveted design teams like Spotify and Flatiron Health. For Spotify, I felt like though the team was big it was <em>too</em> big for me: I felt I wouldn’t be able to have a significant impact on the product itself. Nonetheless, it was an elaborate interview process that gave me insight into the inner-workings of the design team and product leadership at Spotify and it gave me a sense of accomplishment when I got the offer call. Here, I’ll break down the process and give a <a href="https://nishthadalal.com/the-product-design-interview/p/extras-spotify-interview">preview of the detailed guide I wrote</a> on how to prepare for this day-long interview.</p><p>The process itself speaks volumes to how Spotify works a little differently than most design teams. There’s no take-home design challenges, the whiteboarding round is treated a little differently to give candidates space to do individual work, and the 1:1 conversations are focused on <em>you</em> getting your questions answered just as much as the team getting to know you.</p><h4>What you can expect in the interview loop:</h4><ol><li><strong>Recruiter screen</strong></li><li><strong>Background Phone Screen — Virtual<br></strong>45 min · 1 interviewer</li></ol><p><strong>Onsite Interview Loop</strong></p><ol><li><strong>Portfolio Review with Design Team<br></strong>1 hour · 4–8 interviewers</li><li><strong>One on one conversations<br></strong>4–5 hours · 1 interviewer each<br>• Hiring manager<br>• Product Manager<br>• Product Insights: UX Researcher or Data Scientist<br>• Tech — Engineer or Engineering Manager or Tech Lead</li><li><strong>Lunch<br></strong>45 minutes · 1–2 buddies / informal</li><li><strong>Design exercise: planning<br></strong>30 minutes 2 interviewers</li><li><strong>Design exercise: individual work<br></strong>1 hour · alone</li><li><strong>Design exercise: review<br></strong>30 minutes · 2 interviewers</li></ol><h3><strong>Recruiter screen</strong></h3><p>Spotify has embedded recruiters for every product design team within a certain pillar — e.g. the Ads team will have their own design recruiter who works with the hiring managers and teams to identify specific needs and experience they’re looking for. Prepare for a highly specific recruiter screen digging into your background and past projects to find experience relevant to the role. Tailor your responses based on what the team is looking for and the job description, draw parallels where possible to the work you’ve done and the team’s product area.</p><p>Sometimes, in addition to your portfolio, the recruiter may request a copy of your portfolio/deck before or after their call with you. They share this with the hiring team to get an initial read on your skills.</p><p>As always, share timelines about other interviews or offers with the recruiter to help expedite the process. The recruiter will typically take your information back to the hiring manager or a senior designer on the team, who will do your next round: the phone screen.</p><h3><strong>General advice</strong></h3><p>Perhaps the most grueling on-site of the big name Product Design interviews, the Spotify on-site lasts a full day (9am — 5:30pm). In my opinion, the only way to get through this sane and victorious is to pretend you work there for a day. Try to shake off and forget any interview vibes. You’re given a sprawling room (in the WTC office) so settle in and tell yourself it’s your office and you have a meeting-heavy day.</p><p>Of course, it’s never a good idea to be overconfident and give off that “you already want to hire me” energy, when I say pretend you work there I mean approach it like a high-productivity day.</p><p>The team is also very mindful of giving you breathing room so if you need five minutes just ask for it, if you need coffee or a quick bite go for that too.</p><p>Research your interviewers ahead of time so you know who you’ll be talking to, and prepare questions for each practice (design, engineering, data, product management, and UXR) and write them down on a notepad if needed since they’re sprinkled all across your day.</p><blockquote><a href="https://nishthadalal.com/the-product-design-interview/p/extras-spotify-interview">Get the complete 9-page Spotify Product Design Interview Guide here</a> and sign up for the waitlist for my upcoming book <a href="https://nishthadalal.com/the-product-design-interview">The Product Design Interview</a> 📚</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a598488c5f00" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-product-design-interview/spotify-product-design-interview-a598488c5f00">Spotify Product Design Interview</a> was originally published in <a href="https://medium.com/the-product-design-interview">The Product Design Interview</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Facebook Product Design Interview:
Part 3]]></title>
            <link>https://medium.com/the-product-design-interview/facebook-product-design-interview-part-3-df46b9771a5b?source=rss----6ea50094d8f---4</link>
            <guid isPermaLink="false">https://medium.com/p/df46b9771a5b</guid>
            <dc:creator><![CDATA[Nishtha H. Dalal]]></dc:creator>
            <pubDate>Sat, 15 May 2021 15:32:55 GMT</pubDate>
            <atom:updated>2021-01-14T21:23:32.572Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Weh9zLNfOFnk6CnSqvzK5A.png" /></figure><p>Continued from <a href="https://medium.com/@nishthaHD/facebook-product-design-interview-part-2-6abfad6a426d">Part 2</a> · An extra from <a href="https://nishthadalal.com/the-product-design-interview">The Product Design Interview</a> book</p><p>Just when I was recovering and reflecting on the Past Work call, 45 minutes later, I had the second interview — as Facebook calls it, “The Critique Work Call”. The interview was set up with Product Design Manager at Facebook, a fancy title that is bound to bring about some nervousness.</p><p>I had been preparing for this part of the interview for weeks by this point, so much so, that I found myself constantly critiquing apps that I happened to use in those weeks. I had pointers ready for some of the most popular apps such as<em> Facebook, Groups, Twitter, Google Inbox, Google Maps, Apple Maps, Uber, Yelp, Apple Calendar</em>, to name a few. When I ran out of popular apps, I would go to the App Store and download a few from the Top Charts and practice on those.</p><p>A great resource for this is Julie Zhou’s <a href="https://medium.com/the-year-of-the-looking-glass/how-to-do-a-product-critique-98b657050638">How to do a Product Critique</a>. Being the Director of Product Design at Facebook, I felt like there was no better advice to follow, especially for this interview. Other posts by her such as, <a href="https://medium.com/the-year-of-the-looking-glass/the-death-of-users-and-product-design-a857f1ad2f3b">The Death of “Users” and “Product Design”</a>, and 7 <a href="https://medium.com/the-year-of-the-looking-glass/7-reasons-to-no-hire-a-product-designer-part-i-95cf34a851af">Reasons to No-Hire a Product Designer</a> are great resources for understanding the process too. Her blog had become my bible for a few days, trying to soak in as much of her wisdom as I could. With Julie Zhou’s expert advice on my side, and tons of practice with critiquing, I was ready for the last and final part of the process.</p><h4>The Critique Work Call</h4><p>The idea is to critique an app/product together with the interviewer, so they can have a better understanding of your insight into a product. The recruiter had discussed the process of this call with me, and later emailed me a few pointers about the same. I was told that the interviewer will provide an app to chat about, and they tend to sample popular apps so I should be familiar. However, she said if I am unfamiliar, I should alert the interviewer and he/she might decide to change it. One of the most important pieces of advice she gave me was:</p><p><strong><em>It’s important to touch on product thinking, interaction, and visual design in your critique</em></strong></p><p>She further elaborated that this interview is a chance for the interviewer to see how you evaluate and provide feedback. Facebook is extremely feedback driven, so the ability to communicate feedback effectively is important to them. Lastly, she recommended I should chat via a land line or have an extra phone/tablet handy, since it’s hard to juggle chatting while walking through an app.</p><p>Not knowing the app was the most nerve wracking part of this, and to maintain a structured approach even when you are caught off guard with the app can be very difficult. At the same time, if your answer seems unstructured, it reflects poorly on your thinking skills, and your overall approach to design. Keeping this in mind, I tried to come up with several universal structures that could work for any app, touching upon the three areas that the recruiter had mentioned, as well as the pointers I got from all the reading I did about product critique. I finally settled on this one:</p><ol><li>Focal point</li><li>How well does it achieve the goal/focal point</li><li>Thinking, interaction, and visual design</li><li>Compare to competitors</li></ol><p>For the third part, I decided to do a page-by-page approach, as it would be much easier for the interviewer to follow, and would allow for a more free-flowing discussion.</p><p>The interview was in two, obvious parts — Introductions, and the App Critique.</p><p><strong>Introductions</strong></p><p>The Product Design Manager called me at the scheduled time, and the introductions were pretty customary — I was asked about my past experience, some of the classes I have taken and a kind complement that my resume was “impressive”. When the manager started to introduce himself, giving me a background, I was reminded again how I lucked out with my recruiter. The manager mentioned that he went to the same college as me, had lived for a long time in the same city, and we digressed a little to discuss the co-incidence.</p><p>I believe the recruiters try to pair you up with interviewers with whom you have a lot in common with, which helps especially for this interview, as it’s meant to be a semi-formal discussion and mostly subjective. This “match”, or so to speak, I think, enables a comfortable conversation, and with a higher chance that the manager is receptive to your ideas, your odds of doing well increase drastically.</p><p>He then went on to explaining his role at Facebook, and as it turned out, both my interviewers were working on the same team and product.</p><p>After discussing my past work briefly, the manager proceeded to explaining the format of the phone call. He explained that we would select an app, I could choose either an iOS, Android, or Windows platform. To my surprise, he said I could choose the app, and said it would have to be one that is</p><blockquote>“Targeted to a large audience in terms of demographics, something universal, like Google Maps, Twitter, Yelp…”</blockquote><p>I stopped listening at Yelp, and rejoiced for a moment, because it was one of the apps I had prepared for the earlier day. He continued to give a few more examples, and lastly, before I chose, I was told</p><blockquote>“But there’s one catch, you are not allowed to choose a Facebook app, so Facebook itself, Messenger, Groups, Instagram, etc. are off limits”</blockquote><p>I told the manager that’s fair enough, and I understand why they would have that rule, and proceeded to choose the app. I asked if we could discuss Yelp on iOS, but I made sure the manager did not have any other app in mind. While I was prepared for Yelp, I did not want it to seem as though I was fixated on it, but rather open to whatever app we would end up choosing. He agreed to Yelp, and before we started the critique portion of the interview, he reemphasized what the recruiter had told me, focus on the thought process, design thinking, and organized approach.</p><p>I asked him if he had a preference for a specific approach he would like for the discussion, when he mentioned he would prefer we discuss the app a little before, then page-by-page, and finally discuss the design as a whole. He explained that it would be easier to follow for both of us, and would cover all aspects he was looking for, and with that, we proceeded to the next part.</p><p><strong>App Critique</strong></p><p>The manager alerted me when he had the app up, and I did the same, and he mentioned</p><blockquote>“I personally love the app, I’m actually a heavy user, but to be honest, I have never written a review”</blockquote><p>This made me a tad nervous. Being a Product Design Manager, I was pretty sure he had already critiqued the app in his mind, and I was afraid if the bar had automatically been raised just by choosing this app.</p><p>I was first asked how I viewed Yelp, when I started discussing Yelp, the product. I established it’s focal point is to discover local businesses based on crowd-sourced reviews and ratings, although a large part of the emphasis has always been placed on discovery of restaurants, bars and other eateries. We went on to discussing some of the most compelling features of the product, and how it helps attain the goal of allowing its users to make an informed decision, discover and share opinons about local businesses. We also discussed the transformation and shift towards visuals that Yelp has gone through with their latest iOS app update, more fitting to the new design paradigm. I got affirmatives like “Absolutely”, and “I agree”.</p><p>After the summary portion we jumped right into the app. Since we went page-by-page, I have broken it down by just that, with the pages that we discussed in detail.</p><p><strong>Nearby</strong></p><p>One of the compelling features of Yelp is the discovery aspect, and the nearby option caters well to it, being the home screen of the app, if you may. We discussed the rationale behind having this as the landing page, I mentioned how I thought it was a great idea to get a quick glance at the image, rating, and all the information one would typically find in a search result, as well as the “must-try” which is unique to this page, to which he responded</p><blockquote>“I had never noticed that must-try in the corner, it’s great”</blockquote><p>We discussed in depth how the focus on visuals really comes through on this page, with larger images, and a card layout. We continued discussing the nearby page, and moved on to the list of categories we see an absolutely iOS6 style, making the entire portion feel like a misfit</p><blockquote>“Yes, it definitely looks like it doesn’t belong. How would you redo it”</blockquote><p>I suggested an icon approach, similar to those found on the corner of the list items in a smaller bar. Getting rid of the text, and shrinking it down to the height of one list item would be both utilizing the screen-space better, as well as keep the focus on the suggestions. The manager seemed to agree and said it was a great idea.</p><p>We moved on to the search and search results page, which was a great transition to the design discussion.</p><p><strong>Search</strong></p><p>The design shift from the nearby page quickly fades in the Search page, and we had a long discussion as to whether it was the best way to display the results. Some of the things I pointed out about the screen was that it was too cluttered, with a font-size that would oftentimes make you squint, the search bar jumping up and down when you switch from the Nearby page, and the entire search screen was seemingly following the iOS6 design guidelines. We discussed some of these inconsistencies, the manager mostly agreeing to my arguments. I was asked for a suggestion for the search results, where I suggested</p><blockquote>I feel like with the changing trends and the more recent iOS design paradigm, a more visual format would provide a greater user experience. With only 6 results fitting to a screen<strong> </strong>on the iPhone 6, the list items could well be <strong>made cards with an image </strong>and the same information</blockquote><p>The manager, to my surprise, responded with</p><blockquote>“You’re right! Now that you say it, that is a great approach to the list”</blockquote><p>Other inconsistencies on the page that we discussed were the search bar itself, which was both inconsistent within the app, as well as with the OS. The buttons being bordered and the back button were not complying with the new OS guidelines.</p><p>We moved on to a brief discussion about the new center button on the bottom navigation, and I mentioned it’s a great way to keep focus on the point of the app, allowing the users to have instant access to what makes Yelp the product it is — reviews, and pictures. We also discussed the additional check-in option and the shift towards social sharing.</p><p><strong>Business Page</strong></p><p>The last page we critiqued in detail was the business page, with a lot of similar points emerging about design inconsistencies, and how to better display the information. Some of the questions I was asked were</p><blockquote>Do you think having the write a review, check in options on the business page is repetitive?<br>Would you move around the order?<br>Do you think the drag to see pictures feature is hidden and should be made more obvious?</blockquote><p>I discussed these in detail, most of which the manager seemed to agree with me on. One of the key discussions we had about the business page was when I was asked to suggest a change to the way the reviews were displayed. I suggested bringing in the idea of cards into this page too, having a horizontal scrollable area that could fit more cards per screen, with larger fonts, allowing for better usability. I explained a common use case for this, imagining someone commuting (walking, driving, in a train) wanting to make a decision. Having these cards would let them flip through quickly, as well get the information they were looking for faster, with better readability.</p><blockquote>“I never thought of that, that’s a great suggestion”</blockquote><p>After that, we discussed other features briefly, I mentioned the monocle feature which I believed was extremely buried, and could definitely be a unique selling point for Yelp, at which point the manager paused to make a quick note of it.</p><p>We transitioned into discussing Yelp as a whole, its competitors, how FourSquare is coming up rapidly and can pose some serious competition, and things that are unique to Yelp. He asked me what I think of the overall product, when I said</p><blockquote>Yelp essentially nailed the chicken-egg problem, and it’s popular due to its popularity — more people use Yelp because more people use Yelp</blockquote><p>He exclaimed at that thought, saying</p><blockquote>“Absolutely! That’s a great way to put it, and very accurate”</blockquote><p>He then summarized our app critique, we both agreed that in terms of design, there was definitely room for change, and maybe a potential feature for credibility of the reviews, as we discussed the controversy surrounding paid reviews.</p><p>The manager pointed out that we were running out of time, as it had already exceeded the scheduled interview slot of 45 minutes by 15 minutes or so. He finally asked me<strong><em> Why Facebook? </em></strong>It’s important, again, to make sure you’re touching on the larger picture, and realizing just how big of an impact you would be making being a part of Facebook. My answer revolved around the fact that Facebook is a part of people’s daily lives, and doing Product Design at Facebook would mean playing a role in these lives. Upon listening to my answer he said</p><blockquote>Absolutely! You nailed that one right in the head.</blockquote><p>With that, I wrapped up the intense three-part Product Design Interview process.</p><p><strong>Takeaways from the App Critique Call</strong></p><p>Some of the things that I noticed about the third part of the interview were</p><ol><li>It’s very important to <strong>break away from the overtly formal conversation</strong>, keep it professional, but allow for a discussion. Make sure you pause in between, and look for the pointers and prompts that the manager gives you. They want to ensure that not only have you prepared, but also have the design-thinking embedded in you, so don’t go off on a rant without letting them ask you questions.</li><li><strong>The interview is very subjective</strong>, to my luck, the manager seemed very receptive to my suggestions, and more importantly, gave me feedback on the same. It might sometimes be harder to decode what the interviewer is thinking so be prepared for that</li><li>Always have a suggestion, and if not, you should have a pretty good answer for why not. It’s the same point — designers are meant to design, and true designers will always <strong>find room for improvement</strong></li><li>Keep the product in mind, and make sure all your suggestions and critique <strong>circle back to the product as a whole</strong>, not just superficially. Time and again, during the interview, I noticed the manager was impressed and would especially discuss in depth when I suggested something that I said would “better cater to the product”, or “helps attain the goal”</li></ol><h3>More interview advice &amp; company-specific guides in <a href="https://nishthadalal.com/the-product-design-interview">The Product Design Interview</a> book.</h3><h4>A Redesign of the Yelp iOS App based on this critique can be found <a href="https://medium.com/@nishthaHD/redesigning-yelp-863782b75179">here</a></h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=df46b9771a5b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-product-design-interview/facebook-product-design-interview-part-3-df46b9771a5b">Facebook Product Design Interview:
Part 3</a> was originally published in <a href="https://medium.com/the-product-design-interview">The Product Design Interview</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Facebook Product Design Interview:
Part 2]]></title>
            <link>https://medium.com/the-product-design-interview/facebook-product-design-interview-part-2-6abfad6a426d?source=rss----6ea50094d8f---4</link>
            <guid isPermaLink="false">https://medium.com/p/6abfad6a426d</guid>
            <dc:creator><![CDATA[Nishtha H. Dalal]]></dc:creator>
            <pubDate>Sat, 15 May 2021 15:31:40 GMT</pubDate>
            <atom:updated>2021-01-14T21:22:43.367Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s2_fY8z4x6x3d67HaIYpOQ.png" /></figure><p>Continued from <a href="https://medium.com/@nishthaHD/facebook-product-design-interview-part-1-3e5befe33a33">Part 1</a> · An extra from <a href="https://nishthadalal.com/the-product-design-interview">The Product Design Interview</a> book</p><p>I was lucky enough to have my interviews scheduled within two weeks of the phone screen. I was told 3 days in advance, and had both interviews scheduled for the same day, with a 45 minute gap between the two. I had all my research in by this point, updated my portfolio, and added some additional content like usability studies and other documents produced for a design-centered project. I had discussion pointers for each project, and ranked them in order of preference. I was all set for this, and with very little room for uncertainty pertaining to the questions that might come up, there was a scarce chance for an element of surprise, or being caught off-guard. Thankfully I wasn&#39;t.</p><h4>The Past Work Call</h4><p>The first of the two interviews is usually expected to be with a <strong><em>product designer </em></strong>where you will discuss your past work in depth. The designer will ask about your role in every project, especially in regards to group projects. You are expected to explain any constraints or prompts that go with your project. The interview is scheduled to last 45 <strong>minutes</strong>, but it can go longer.</p><p>It is key to be as intentional as possible in your descriptions and emphasize the importance and seriousness placed in the design process. <strong><em>Do not let it seem as though you take the process lightly. </em></strong>It is also important to have a structured, well thought out answer. Jumping from point A to F and back to B shows poor train of thought, lack of ability to follow a process in general, and worst of all, unpreparedness.</p><p>Having being told the format of the interview and what to expect, the interviewee is expected to give a stellar performance, knowing the content, and your ability to follow the design process must shine through. More often than not, the interviewer, who is a product designer, has been doing this for a long time, and it’s hard to fool them about whether you actually had a design process or made it up later.</p><p>An outline I made and followed religiously was:</p><ol><li>Concept of the product and why</li><li>Design goals and concept</li><li>Obstacles and fulfilling the design concept</li><li>What I would do differently</li></ol><p>This covered all the aspects that the designer thinks are important, based on what I was told by the recruiter, as well as read from other interviewees experiences. The order allows for a complete walk through of the project in terms of its evolution, as well as the design process.</p><p>The interview was, again, broken down into three parts, but since the point of the call was to discuss your past work, two out of the three parts were extremely similar in terms of the questions and discussion</p><p><strong>Introductions &amp; Format</strong></p><p>Of course, there were introductions in the beginning, and a small discussion about the designer’s role at Facebook. I was asked about my past experiences from my resume, education, and to explain a little about any design classes I have taken. The designer told me a little bit about what she does, which was rather interesting. She worked on the Ads team, and talked a little about her recent projects at Facebook, and finally moved on to explaining the format of the interview.</p><p>She summarized it much like the recruiter had</p><blockquote>“We will be discussing two, or three of your projects from your portfolio in detail. Try to walk me through the entire design process for each of these”</blockquote><p>At this point, even though I had a rehearsed format, I asked her if she had a specific format in mind. She emphasized that she would like to hear the process as it took place, focusing on the decisions, and:</p><blockquote>“…chronologically would be the best way to go, but if you have another structure, I’m open to that”</blockquote><p>I then asked her if she had a preference as to which of my projects she would like to hear about, when she said she had none, and I went with my top two choices.</p><p><strong>Product &amp; Design Concept</strong></p><p>The questions and format for both projects were extremely similar. I started out explaining the concept of the entire project before discussing the design concept. I felt like it was important to show that you think of a product holistically, and would allow for a complete walk through of the project in terms of its evolution, as well as the design process.</p><p>As it turned out, I was right. While I was explaining the concept of the project, for each of them, the interviewer discussed my choice of target audience. The first product that I discussed was a health tracking app, for which she asked me</p><blockquote>“Why did you think that this product would appeal to this demographic?”<br>“Did you do any research to determine the target audience?”</blockquote><p>For the second product, which was a college class scheduler, the target audience was very obvious.</p><p>For both products, I covered the rationale of the product, and the problem I was trying to solve with each of these. It seemed as though the designer was interested in why the product was created, and asked a few more questions to better understand each problem. After this, I started discussing the design goals and concept.</p><p>A large part of explaining my design goals was focused on the concept of the product and the gap it was trying to fill. The designer noticed this, and started asking questions such as</p><blockquote>“Was this layout chosen for visual appeal, or to simplify the process for the users?”<br>“Why did you choose a larger font?”</blockquote><p>Acknowledging these aspects in your design goals shows a user-centered approach, not only to the design, but also to the product as a whole. You must emphasize your effort and ability to create a design that focuses and caters to the product, and not the other way around.</p><p>Discussing the design concept and goals also helps the designer follow through, and shows how well and religiously you <strong><em>follow the design process. </em></strong>Skipping this part usually gives the impression that you just jumped in and created something, without making any design or product considerations. Furthermore, it will allow the designer to see if your final product reflects these goals, and your ability to transform a concept into a substantial design.</p><p><strong>Obstacles and Fulfilling Design Goals</strong></p><p>No design ever goes through as planned, and every designer will attest this. It’s how you deal with these obstacles that the interviewer wants to see. Your ability to tackle a problem and come up with a solution that does not compromise the user-experience is what Facebook looks for.</p><p>As I went through the HCI practicum project, some of the questions I was asked were about the process itself, in an attempt to see how well it was thought out. One of the projects I discussed had a participatory design session, and the questions she asked were primarily about how I decided who would participate, the prompts for the session, and how the session was run. Others were more design specific and point blank</p><blockquote>Why did you go with the list approach?<br>Did you decide it should look like this, or was this something the users suggested?<br>How did the users respond to ____?</blockquote><p>To stumble on these answers is when the designer can tell that you faked the process. This is what the recruiters mean when they say <strong><em>know your work.</em></strong></p><p><strong>Future Changes &amp; Flaws</strong></p><p>Lastly, point out your flaws. This doesn&#39;t mean hate on your own design and put it down in every way possible, because after all, if it sucked that much, why is it on your portfolio in the first place?</p><p>At the same time, saying there is nothing I would do differently is an instant turn off for multiple reasons. It shows ego, arrogance, and mostly, it’s a marker for a non-designer. A key trait of a designer is to recognize room for change and improvement. Critique your design, talk about things you would want to add, change, and most importantly, provide a rationale for why.</p><p>For most of the things that I said I would do differently, I was always asked</p><blockquote>“Why? Why do you think that’s a problem?”<br>“How do you think this will help the product?”</blockquote><p>For the first project I had discussed, it was an iOS app design, to which I suggested a complete visual redesign to ensure it matches the new iOS design paradigm. I was asked a series of questions related to these suggestions</p><blockquote>“Why wasn&#39;t it done in the first place?”</blockquote><p>to which my answer was that iOS7 was still in beta at the time, and with no clear design guidelines at the time, I had to follow my instincts, and do a lot of guesswork. The designer agreed with a</p><blockquote>“that’s a fair point you make”</blockquote><p>This was followed up with, why would you want a design that matches iOS7 guidelines completely when there are plenty of apps that follow their own design guidelines. My answer referred back to the design goals and target audience who would be best comfortable with nativity, and the designer seemed impressed, remarked, “that’s right, the users come first”. The bottom-line is</p><blockquote>Don’t suggest a change unless you know why</blockquote><p>Saying I would make the buttons rounded, or change the color scheme are superficial answers that clearly have no thought put into it. Find something that adds to the product, meets its goals better, improves user-experience, and provide a well thought out reason as to why you didn&#39;t do it in the first place.</p><p>The phone call went longer than expected, having discussed two projects in full detail. The conversation was free flowing, with questions from the interviewer, impressed remarks, and agreement when explained my rationales for certain decisions. With less variation in her tone, it was hard to tell if the interviewer was truly impressed, or if it was just something she was saying passively. Aside from that, it was a positive experience, mostly because I was prepared for the questions that were going to come my way.</p><blockquote><strong><em>Continue to </em></strong><a href="https://medium.com/@nishthaHD/facebook-product-design-interview-part-3-df46b9771a5b"><strong><em>Part 3</em></strong></a></blockquote><h4>More interview advice &amp; company-specific guides in <a href="https://nishthadalal.com/the-product-design-interview">The Product Design Interview</a> book.</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6abfad6a426d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-product-design-interview/facebook-product-design-interview-part-2-6abfad6a426d">Facebook Product Design Interview:
Part 2</a> was originally published in <a href="https://medium.com/the-product-design-interview">The Product Design Interview</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Facebook Product Design Interview: 
Part 1]]></title>
            <link>https://medium.com/the-product-design-interview/facebook-product-design-interview-part-1-3e5befe33a33?source=rss----6ea50094d8f---4</link>
            <guid isPermaLink="false">https://medium.com/p/3e5befe33a33</guid>
            <dc:creator><![CDATA[Nishtha H. Dalal]]></dc:creator>
            <pubDate>Sat, 15 May 2021 15:27:59 GMT</pubDate>
            <atom:updated>2021-01-14T21:21:50.409Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zBY2elPXB228_W7QYj8Yvw.png" /></figure><h3>Facebook Product Design Interview:<br>Part 1</h3><p>An extra from <a href="https://nishthadalal.com/the-product-design-interview">The Product Design Interview</a> book.</p><p>Only recently, I had the opportunity to interview for a product design internship position at Facebook. Like most, to me, this was the trajectory to the best thing that could happen to my career.</p><p>Sidenote: If you’re applying, one way to get design interviews by doing <a href="https://medium.com/@nishthaHD/quick-critiques-double-as-design-interview-magnets-661defed9669#.yq5p6urab">quick critiques</a></p><p>When I first got the email, I was extremely excited, but at the same time unbelievably nervous. I have always been a front-end developer, with some design experience, and none in design interviews. So I hit the Internet like no other, Google-ing, Glassdoor-ing, and Quora-ing, amongst various others, and found some help, but there could be more.</p><p>That being said, whatever guidance I did get from these few sources that I found was extremely helpful, so I hope I can give back to the rest of the community, and future interviewees via this post.</p><p>I’m going to walk through the journey of the entire interview process, from the recruiter call, all the way to the decision. The interview is in 3 parts, first one being the Recruiter Call, followed by a Past Work Call, and finally the App Critique Call. After much anticipation and anxiety, you will finally hear about the decision in about a week.</p><h4>The Recruiter Call</h4><p>The first step of the <strong><em>product design internship </em></strong>interview process is the recruiter call. Very similar to most, and identical to other Facebook phone screens, you will be contacted by a recruiter to set up a time, and have a phone conversation which is broken down into three parts:</p><p><strong>Introductions &amp; Timeframe</strong></p><p>I had a casual conversation with the recruiter, introducing myself, followed by a brief introduction by the recruiter as to what she does, how she manages interns, and her past experiences with interns. I was truly impressed by the last part. I might have hit the jackpot with this recruiter, who was overseeing 7 interns in the past summer, out of which 5 pitched to Mark Zuckerberg.</p><p>After this, we discussed the timeframe, when I am looking to get an offer, any other offers on the table, deadlines and the dates I am seeking an internship for. The recruiter seemed extremely flexible about this. She was initially under the impression that I was interviewing for the next summer, but when I told her I was actually looking to start within the next two months, she agreed to that instantly.</p><p>The call pivoted quickly after the formalities.</p><p><strong>Experience &amp; Why Facebook</strong></p><p>The recruiter jumped right into my resume, asking about my past experiences, how much design experience I have had and to explain some of the things I had done in the past.</p><p>It’s extremely important to stop yourself from discussing the non-design aspects in detail, as you can feel yourself losing the recruiter’s interest at that point. I slipped up into the front-end part for a minute or so, when she asked</p><blockquote>“What design considerations did you make while creating the UI spec”</blockquote><p>That got me right back on track, and I made a quick mental note to focus on the design. Another important thing to remember is to not blabber away, but try to have more of a conversation in this part. The recruiter will always have questions, so try not to go on with a saga, but leave room for questions in between. A free flowing conversation will leave more room for you to correct yourself, come back on track, and get cues as to what the recruiter is expecting to hear.</p><p>She asked me to walk through an entire project on my portfolio in terms of the product, concept, and design decisions I made.</p><p>Facebook places a great amount of importance into shipping products, having a rounded approach, and employees who’s goals are aligned to those of yours. After discussing past experience, some of the questions were whether you have taken a product from beginning to end, discussing that experience, working with teams, and finally the big one</p><blockquote>Why Facebook Product Design</blockquote><p>It’s important to have a good reason, not just “because it’s Facebook” or “because it would be great on my resumé”. Their goals have always been clear, impacting and changing lives, making a difference, delivering relevant news, focusing on communities, user-centered approach to design, amongst others. Find which one you <strong><em>share their passion</em></strong> with and you can’t go wrong.</p><p>Last but not least, have this answer ready:</p><blockquote>What team would you like to be a part of and why</blockquote><p>I had this one thought out already — Groups. Apart from the obvious reasons that there is a visible effort and focus that Facebook has placed on this area recently, it is something that goes back to their roots of community based social networking.</p><p><strong>Next Steps &amp; Interview Process</strong></p><p>By this point, the recruiter had already told me that they would definitely be moving forward with me. I was taken by surprise because in my research about these interviews, most people said that they heard via email about this.</p><p>She quickly went on to explaining the remaining process, which is two phone interviews, one about my past work and the other critiquing an unknown app. She mentioned the past work one would be similar to the walkthrough I did in this one, but with more projects. Some of the advice she gave me for the interviews was:</p><ol><li>Update your portfolio and know your work inside out</li><li>Choose the ones you want to discuss beforehand</li><li>Practice for the app critique interview as they are most likely popular apps</li><li>Have a preference ready because the interviewer might let you choose</li></ol><blockquote><strong><em>Continue to </em></strong><a href="https://medium.com/@nishthaHD/facebook-product-design-interview-part-2-6abfad6a426d"><strong><em>Part 2</em></strong></a></blockquote><h4>More interview advice &amp; company-specific guides in <a href="https://nishthadalal.com/the-product-design-interview">The Product Design Interview</a> book.</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3e5befe33a33" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-product-design-interview/facebook-product-design-interview-part-1-3e5befe33a33">Facebook Product Design Interview: 
Part 1</a> was originally published in <a href="https://medium.com/the-product-design-interview">The Product Design Interview</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>