How I would solve the Facebook iOS App Design Interview (2023)


David Seek

12 min read

How I would solve the Facebook iOS App Design Interview (1)

Last week, a reader contacted me to explain issues he was facing in his recent interview with Facebook. During the System Design challenge, he was asked to design a Mobile Application. Unlike the traditional System Design interview, this one focuses specifically on the architecture of the mobile application, and then moves into its many different details.

Since that reader has been part of a mobile application team, and his view point was rather limited, he did not have enough exposure to fully plan an application, and to help him prepare for such an interview. That's why we're going to explore exactly that in this article.


When sitting in an interview and being asked to "design Instagram", it's the first and most crucial step to ask clarifying questions. What part of the app do we need to concentrate on? We can't possibly design the whole application within 20 minutes - typically the amount of time dedicated for the actual design part. The remainder is reserved for questions from the interviewers, as well as yours.

Typically, interviewers want you to concentrate on a challenging and complex part of the application, like the "news feed", or the "instant chat".

A few examples of clarifying questions are:

  • What part of the app should I design? Authentication? Feed? User profiles? Messaging? Post comments? Application nowadays serve a multitude of purposes with an infinite amount of features.
  • (If for example a messenger app) What kind of attachments will the design support? If we don't have to worry about images, then we don't have to worry so much about caching. If we have to support map locations, do we need to worry about map performance? We need to ask the interviewer all kinds of questions to demonstrate our understanding of scalability.
  • Do I need to design uploading functionalities as well, or just the data output? For example, for a new feed, it's possible that creating feed items is also part of the design. Although, it typically isn't.
  • (If you're as familiar with it as I am) Is it okay to assume a Firebase backend so I can demonstrate my strengths best with my past experience? Just ask the interviewer if it's okay if you demonstrate an example utilizing an industry standard method you're best familiar with.
  • (If some kind of social media feed) What kind of feed items? Facebook, for example, supports tons of different types of elements. Everyone of them might deserve its own microsystem and so we need to define the focus.

For this article, we're going to create an Application Design for the "Instagram Home Feed"–so images and their meta-data. In an interview scenario, we're now expected to lead the open conversation. We're expected to explain what we will need to concentrate on, such as what aspects of modern application design influences our decisions.

(Video) Big-tech senior iOS dev system design interview prep: Design the Facebook feed | Live Dev Mentoring

Whether we interviewing for Amazon, Facebook, JP Morgan, Snapchat, TikTok or for startups, the basic and most common requirements overlap for all applications.

  • Scalability. We need to write an application that will be able to serve countless users, and handle an excessive amount of content all over the world.
  • Security. The application needs to at least match the high industry security standard in terms of authentication, networking and data storage.
  • High Velocity Development. Arguably as part of scalability, we need to support many users, as well as, many engineers. We need to lay out the foundation for a scalable code architecture that can support thousands of commits a day, without major disruption through merge conflicts.
  • Separation of Concerns. The design should demonstrate your seniority and understanding of code architecture in terms of clean code. Write services and managers that are easily interchangeable and are concerned about only themselves.


Once we know exactly what kind of functionality we have to develop, we will need to start the sketching process. We will start the design from the very lowest to the most top layer of the application. Starting from the AppDelegate, to the UIViewController.

How I would solve the Facebook iOS App Design Interview (2)

During an interview, you are required to sketch elements like above on a white board or some digital version thereof. I've created the sketch with Whimsical. Don't worry about making it beautiful. The purpose is to support your verbal arguments with a visual aid.

Using the sketch, we want to demonstrate how we separate different layers, as well as concerns. We've created dedicated ...Manager classes and MicroServices for specific requirements and functionalities, so we can exchange them without breaking anything.

In an interview scenario, you are sketching one component, and then you're explaining the ideas of it on the fly. The following list explains the purpose of each element, like I'd explain it on the fly as well.

  • NetworkingManager - Responsible for all requests that go outside of the application. Firebase, as part of an SDK, with its own wrapper of network operations would be left out of the following, but with a networking manager, the idea is to wrap all operations that interact with the internet. So all kinds of Alamofire or URLSession operations and tasks. Another example could be a delegate method to the AppDelegate that could cause some kind of UI banner, notifying the user of missing network connection, and kicking off some kind of offline mode.
  • DatabaseManager - Responsible for taking in database requests and returning states to potentially notify the user of issues. The advantage of wrapping database operations inside a wrapper class, is best demonstrated here. We could replace Firebase with AWS, without the rest of the application being affected at all. Only one class needs to be adjusted.
  • UserManager - Responsible for all auth related operations. Logging In. Logging Out. Provides some kind of observable API to make sure the app switches state when the auth state changes. A class best implemented in a LandingController class. When the auth state switches from user to nil, LoginViewController gets presented, and once logged in, FeedViewController.
  • AppDelegate - Instances for most managers are created, and passed down the view hierarchy using dependency injection. A NetworkingManagerProtocol could then have its delegate in the AppDelegate, and state changes could be kept and processed from there, creating visual indicators for the user.
  • FeedManager - Responsible for getting feed items. Has dependency on the DatabaseManager, and wraps everything needed from database to feed list. Casting database items to FeedItem objects, as well as caching, and handling errors and states. Providing APIs for its consumers. For example the FeedListViewController.
  • ImageManager - Provides a one-stop API to get images based on a URL parameter. It wraps the ImageLoader, and provides APIs like getImage(forURL) and uploadImage(forElement,image) and handles everything from loading, caching, all the way to error handling.
  • ImageLoader - Not exposed to consumers of the ImageManager, but a private dependency or initiation within, the loader itself has a dependency on the NetworkingManager. Remember: All networking requests are meant to go through one dedicated API.
  • ImageCache - Dependency of the ImageLoader. Provides an API to cache and retrieve images into and from the memory cache. Controlled using an LRU. A least recently used object queue.
  • UIViewController - It's important to mention to the interviewer that the view controller's only concern is to present elements to the view, and define view specific attributes. The remainder of the business logic is handled by prior defined API wrappers, the ...Managers classes.

Next, during the interview, we're typically asked to design a few example APIs, for parts of the sketched design, based on the interviewer's choice. Many interviewers like to talk about image loading and caching.

enum Image { // 1 case image(UIImage) case thumbnail(UIImage)}enum LoaderResult { // 2 case success(Image) case failure(Error)}class ImageLoader { // 3 func getImage(from url: String, onLoad: @escaping ((LoaderResult) -> Void))}
  1. Image enum, to demonstrate that we will have thumbnails for reduced perceived latency of the user. Demonstrates that performance is important to us.
  2. Result enum, to demonstrate that we write clean code and define secure types, and understand how to structure code well. Those are all important aspects of scalability.
  3. Dedicated ImageLoader, that demonstrates "separation of concerns". Having a clear, one-stop service to handle all "image loading" requirements. A clear defined API for future consumers.

With above in place, we have demonstrated that we understand how to generally structure a mobile application and are no strangers to the separation of concerns. We've also shown that we understand that writing dedicated APIs to avoid having to change countless consumers when underlying technologies change, increases "sprint predictability". This is an important part of the agile development cycle.

As an example, if we need to fix a bug related to image caching, we know exactly where to look. Only one part of the whole application handles image caching related activities, and once the bug in our ImageCache is fixed, the whole application's image caching is fixed. We will not have to perform some kind of static analysis to find all lines of code, that potentially individually handle caching.


Scalability comes in all kinds of equally important facets. Before we even reach the phone, we need to make sure our system is scalable. Vertically, by scaling up, as well as horizontally, by scaling out. We want to be able to support millions of users within the United States, as well as across the world.

During the System Design interview, we need to be aware of concept like regional server farms and networks, with load balancers and caching layers. When designing the Application Architecture, we need to think about similar concepts and ideas.

(Video) Mock iOS Facebook Interview 2020 - Software Engineer

We need to cache data locally, so hundreds of millions of requests are not unnecessarily overloading the backend system. We also need to define an application architecture that supports adding new functionality and fixing bugs by countless engineers, while supporting an extraordinary "speed to customer".

Examples include, the DatabaseManager must utilize some kind of a pagination or cursor controlled approach. A whole user's feed does not need to be downloaded all at once. We'd download 30 items at a time, while pre-rendering 20 for a low latency, and continuing with the "next page" when scrolling.

Another common measure to support a high scale of users and requests, is throttling. A 3-second limit on the "pull-to-refresh" action, could decrease unnecessary load on the backend. It always depends on the specific environment of the given application, and how often a manual user refresh is desired, needed or required.

Firebase uses an observable. The view refreshes without manual request. But the Firebase instance could be some kind of pre-computed, REDIS kind of database. The refresh pull could kick off a new pre-computation, to include more recent posts.

A last measure worth mentioning, within the context of a short article, is caching. For a news feed, we wouldn't want to run the expensive execution of downloading an image multiple times just because the users scrolls the feed up and down. The image is downloaded once, and then stored in a memory cache. That decreases network operations, and perceived latency for the user.

All of the above are thoughts you need to describe out loud to the interviewer, and you need to understand the underlying concepts to a point where you are able to debate the pros and cons.


Security is a huge topic, which is why I'm dedicating a whole, upcoming article just to the topic of "securely storing API keys". However, for now, I'm going to provide a few "buzzwords" you should use to prepare for the interview, as well as for future research.

During the interview, it's perfectly acceptable to say that we are not security experts. There's a whole profession specialized and highly educated around the whole topic of network and data security. Regardless, we are still, and rightfully so, expected to have a basic understanding of potential risks, as well as industry best practices.

In my personal example, I would simply be open and disclaim that most of my experience has been with Firebase, where authenticating users, storing tokens, and performing further security measures has mostly been outsourced to the Firebase SDK, and therefore I've had little exposure to custom implementations.

Most interviewers will then move to a different topic, to provide a better opportunity to shine. Always remember: the interviewer wants you to succeed.

(Video) My Design Interview Process at Facebook. Did I get it?

Of course, when interviewing for smaller companies and startups, they might need for us to be very proficient in security measures. If we're unable to satisfy that requirement, then it's in the mutual best interest to part ways. We can pursue other opportunities, and that company will find someone better qualified for their needs.

In most big companies, on the other hand, specialists are concerned with security, and those companies are primarily looking for generalists, or of course, for some specialists in areas like ReactNative or AR.

To name a few examples of best practice concepts:

  • We won't store sensitive information in the UserDefaults, as that storage does not enjoy higher encryption, and is therefore not safe against exploitation.
  • One trick to safely secure API keys is to utilize a private CloudKit database. This is potentially vulnerable against "man in the middle" attacks. But every idea in security can be countered with a "but".
  • A good practice to securely store Secrets, is to utilize a .xcconfig configuration file, ignore the file using a .gitignore, and reference the Secrets within the configuration file in code. That way, you're not exposing Secrets in your repository.


There are many different caching mechanisms and ideas. For example, it's common to cache images in memory. A messaging application is more efficient when retrieving images from memory rather than downloading it every time.

In our interview example, the FeedManager downloads feed items utilizing the DatabaseManager. That manager will have an internal cache implementation using, for example, CoreData. But the underlying technology is not exposed. That's the "separation of concerns".

As an additional example, to display a user profile, we need to download information to display it. Once downloaded, the cache will now have this information. We can display the profile instantly when requested. And while presenting the new controller, a request updates the information. Update the UI, and update the cache.

An inevitable follow-up question is typically how to handle how much data is stored in the cache. An Instagram feed contains hundreds, if not thousands, of feed items. Storing all of them would blow up even a hard disk storage, very fast.

To handle this kind of threshold, we'd typically implement an LRU, a Least Recently Used object queue. The FeedManager would download new feed items and the LRU stores the new items and kicks out the least recently used item.

The predicate for such an operation could, of course, be customized. For example, kicking out items that are supposed to be at the most bottom of a potential feed, as opposed to the most top items.

Offline Support

Naturally, given what users nowadays are able to expect from any kind of successful application, we'll most likely be asked to have some kind of idea how to support an offline mode.

(Video) System Design Interview - App Store - Apple Engineer (10+ Yrs) Interviews Senior Engineer (4+ Yrs)

In the Instagram example, we would need to make sure that user authentication and the stored user model supports offline availability. Furthermore, we should be displaying the feed items the user saw last.

Based on the caching mechanisms discussed before, we are already very far along in planning offline support.

In the past I've implemented a custom Offline Database of a Firestore as following.

class DatabaseManager { // 1 private let offlineDatabase = OfflineDatabase() // 2 private let onlineDatabase = OnlineDatabase() // 3 public func query(_ path: QueryPath, onLoad: @escaping (DatabaseResult) -> Void) { // 4 offlineDatabase.observe(path) { result in // 5 onLoad(result) } onlineDatabase.query(path) { result in // 6, forQueryAt: path) } } public func store(_ payload: Payload, forQueryAt path: QueryPath) {, forQueryAt: path { scheduler in // 7 } }}private class OfflineDatabase { public func observe(_ path: QueryPath, onComplete: @escaping (DatabaseResult) -> Void) public func store(_ payload: Payload, forQueryAt path: QueryPath, onStore: ((SchedulerResults) -> Void)? = nil)}
  1. As always, we want to demonstrate that we'll write clean and well-structured code, with separation of concerns. We will have a dedicated model for all database related tasks.
  2. We'll have a dedicated OfflineDatabase
  3. And a dedicated OnlineDatabase
  4. A query function that takes a QueryPath, some type of structure we specify as a prerequisite. We would communicate to the interviewer that we'd plan on having such types, but we will not be expected to implement every one of them.
  5. The idea is to observe the offline database and forward the information to the closure, down to the consumers.
  6. Then, we're using the online database, to update the offline database. And since in #5 above, we said that we're observing on the offline database, new information will automatically be forwarded to the consumers.
  7. Any kind of uploading functionality has not been set as requirement for this interview, but we provide a stub to demonstrate that the upload functionality will also be handled in this wrapper.

I hope that the concepts and ideas explained above will give you more of an understanding of how I would tackle the application design interview. I'm not saying that my way is the only way, or even the best way, but I'm offering my thoughts to help you get your own ideas.

It's important to understand that the points mentioned above are explained and discussed on a surface level. There is so much more to say. It's unlikely, however, that any interviewer will want you to go much deeper into details of any of them; and I don't want to have articles that take two hours to read.

The goal of the exercise–the interview challenge–is to find out if you have a clear and accurate overall understanding of how to write a solid, secure, and scalable application that follows coding best practices.

New article 🎉☺️

This one has been sitting on draft for a while. I'm talking about my past, my career and how I got into FAANG.

Less technical, and more personal.
Retweet and like for reach highly appreciated 🥰

(Video) Guide to Meta / Facebook Product Designer App critique (App Crit) interview

— David Seek (@DavidSeek) February 2, 2021

Sign up now for more.

Success! Copied the link to your clipboard. Thank you for sharing.


How do I prepare for a product design interview on Facebook? ›

Here are the four preparation steps we recommend, to help you get an offer as a Facebook product designer.
  1. 3.1 Learn about Facebook's culture. Most candidates fail to do this. ...
  2. 3.2 Practice by yourself. ...
  3. 3.3 Practice with peers. ...
  4. 3.4 Practice with ex-interviewers.
21 Jul 2022

How important is system design interview in Facebook? ›

The system design interview is a necessary hurdle as you advance in your career as a software engineer. System design interviews assess your design skills by asking you to build a scalable system.

Does Facebook ASK system design questions? ›

One of the many rounds of the Facebook interview process is the system design interview. A system design interview will require you to design a high-level architecture for a software system. In the simplest terms, the purpose of every system design will be to solve a problem.

How do you solve low level design problems? ›

How to solve LLD problems in the Interview
  1. Clarify the problem by asking the relevant questions. ...
  2. Define the Core Classes ( and Objects )
  3. Establish the relationships between the classes / objects by observing the interactions among the classes / objects.
  4. Try to fulfill all the requirements by defining the methods.
4 Sept 2020

How many rounds of interview does Facebook have? ›

Facebook's recruitment process consists of four main parts: resume screening, phone screenings, on-site interviews, and hiring committee reviews. While each part of the hiring process has its own value, the most difficult and decisive parts are phone screenings (1-2 rounds), and on-site interviews (4-5 rounds).

How do you pass a product design interview? ›

How to prepare for a Product design interview?
  1. Take a holistic approach and make an impression. ...
  2. Start with a better portfolio. ...
  3. Treat LinkedIn like it's your resume. ...
  4. The phone or video conference interview. ...
  5. Before onsites. ...
  6. On the day. ...
  7. Some of my favorite questions and what i'm looking for.

How many times can you fail Facebook interview? ›

Facebook: 1 year (from first interview and same job -- no restriction for different job) Apple: 6 months Cool-off period if fail onsite. Max number of attempts: None.

Is it difficult to get Facebook interview? ›

Getting a job at Facebook / meta isn't easy. For starters you are going to have to make it through multiple rounds of interview, with multiple different people.

What is full loop interview at Facebook? ›

The loop is several interviews back-to-back on the same day, usually with a lunch break. Instead of coding in a text editor, you will likely be asked to write code on a whiteboard. And of course there will be time to ask the interviewer anything you want. These traits are not all we look for, nor all we care about.

What design pattern does Facebook use? ›

Flux is the application architecture that Facebook uses for building client-side web applications. It complements React's composable view components by utilizing a unidirectional data flow. It's more of a pattern rather than a formal framework, and you can start using Flux immediately without a lot of new code.

How will you design Facebook? ›

Basic Design
  1. Each user will have a profile.
  2. There will be a list of friends in each user profile.
  3. Each user will have their own homepage where his posts will be visible. A user can like any post of their friend and that likes will reflect on the actual message shared by his. friend.

What are the elements of design used in Facebook? ›

Facebook Design Principles
  • Universal. Our mission is to make the entire world more open, and this means reaching every corner, every person. ...
  • Human. Users return to our site to be surrounded by friends and other people near to them. ...
  • Clean. ...
  • Consistent. ...
  • Useful. ...
  • Fast. ...
  • Transparent.

How do you identify a problem in design? ›

Some useful techniques for understanding the problem include the Five Whys, Fishbone Diagrams, and problem visualization exercises. Name – Give the problem a name. This gives everyone working on the project a common reference point. Make the name memorable, or even funny to keep it top of mind.

What are the common problems while designing? ›

5 Challenges Designers Face
  • Working With Tight Deadlines. Some people work well under pressure, while others struggle. ...
  • Balance of Design & Function. ...
  • Balance of Client Needs & Personal Design Preferences. ...
  • Staying Relevant & Gaining Skills Constantly. ...
  • Being Unique.
24 May 2019

Does Facebook call Rejection? ›

Yes, usually a recruiter will call back. Facebook, from my experience, has been particularly friendly and forthcoming so feel free to ask your recruiter about what you can improve on, and if you can re-apply in 6 months or a year.

How long does it take for Facebook to hire you? ›

A “hire" or “no hire" decision is made shortly after we receive feedback from the interviewers. On average it usually takes about 90 days from when a role opens to when an offer is received and accepted.

What happens after Facebook interview? ›

After your interviews, you'll hear from your recruiter to review how your interviews went and discuss any next steps.

What are the 5 steps in product design? ›

Product Design Process: 5 Steps
  • Step 1: Target Market Research. ...
  • Step 2: Initial Concept Design. ...
  • Step 3: Sketches, Drawings, and more Sketches! ...
  • Step 4: Prototyping. ...
  • Step 5: Consumer Feedback.
13 May 2022

What are the 4 product design process? ›

We utilize the Double Diamond product design process with four phases: Discover, Define, Develop, and Deliver. The product design process starts with the product discovery phase.

How can I fail an interview quickly? ›

Interview Mistakes to Avoid During the Interview
  1. You're Late to Arrive. ...
  2. You Pretend You Know an Answer That You Don't. ...
  3. Too Much Name Dropping. ...
  4. You're Too Rehearsed. ...
  5. You Have No Questions Prepared, Especially at the End of the Interview. ...
  6. You Use Too Much Jargon. ...
  7. You Let a Small Mistake Derail You.

Can I reapply after failed interview? ›

The job market is much the same. And one common question that job seekers have is: Is it okay to reapply for a position with a company after being rejected? The answer, in short, is: Yes! A rejection shouldn't deter you from giving it another go, even when it comes to a company that previously rejected you.

What should I study for a Facebook interview? ›

Coding Questions: Facebook interview questions focus on generalist knowledge on algorithms, data structures, and time complexity. They also test on architecture and system design (even entry level). Hiring Levels: Facebook normally hires at level E3 for entry level software roles with E9 behind the height of levels.

Does Facebook negotiate salary? ›

Although Facebook is typically only moderately flexible on base salary, I prefer to begin by negotiating base salary to see how flexible they are in the other components. By pushing on base salary—even knowing they aren't very flexible—we give them an opportunity to show where they are the most flexible.

What does Facebook look for when hiring? ›

They're looking for candidates that will challenge the status quo. They communicate to employees that you can't achieve greatness without making some mistakes along the way. Armed with the knowledge that they won't be penalized for their failures, employees feel empowered to make courageous decisions.

What is Apple's acceptance rate? ›

Apple conducts one of the most difficult technical interviews for software engineers. Given the 1% acceptance rate, even experienced engineers who excel in their current roles struggle to get an Apple interview.

How can you tell a fake interview? ›

Signs of online interview scams
  1. The job is too good to be true. ...
  2. You can't find the company's information online. ...
  3. The interviewer's email correspondence is unprofessional. ...
  4. Emails don't include contact information about the company. ...
  5. The job requirements and description are vague. ...
  6. The interview takes place via instant chat.

What are the 3 rounds of interview? ›

3 Rounds of Interview

This type of interview may include an HR round, technical round and a final discussion round.

Is 3 rounds of interview normal? ›

Having three to four interviews just for an entry-level position may frustrate candidates but the number is sufficient for a more senior role. In the event where more than four or five rounds of interviews are required, it is best to provide a justification.

Which design pattern is best for iOS? ›

Top 3 Structural Design Patterns Types for iOS App Development
  • Facade Design Pattern.
  • Adapter Pattern.
  • Decorator Design Pattern.
23 Dec 2021

What are the famous design patterns used in iOS? ›

The following are some of the commonly used iOS design patterns in swift.
  • Builder.
  • Facade.
  • MVC.
  • Singleton.
  • Template Method.
  • Decorator.
  • Viper.
  • MVVM.
13 Jan 2022

What are the 3 design patterns? ›

Design Patterns are categorized mainly into three categories: Creational Design Pattern, Structural Design Pattern, and Behavioral Design Pattern.

What are the 5 easy steps to create a Facebook page? ›

To create a Facebook page:
  1. Click the drop-down arrow on the toolbar, then select Create Page.
  2. Choose either Business or Brand or Community or Public Figure as your Page category.
  3. Enter a Page Name and Category, then click Continue.
  4. Upload a profile picture and a cover photo for your Page.
  5. The Facebook page will appear.

What is Facebook ad design? ›

A great Facebook ad design helps you attract attention and tell a story. Each of these tips can help you do that, but it's your job to put them together in the best way possible for your product or service. If you want some inspiration, check out our free Facebook ad templates that can help you get started.

How long did it take to design Facebook? ›

How long did it take to create Facebook? According to Zuckerberg's interview with Business Insider in 2016, it took him only two weeks to develop the initial version of Facebook — just two weeks to build a platform that would later host billions of users around the world and dominate the internet.

What are 3 of Facebook's top features? ›

Facebook has quite a lot of features but its main features are the Newsfeed where the user see contents from his Facebook friends and pages he follows; Messenger for messaging; Timeline where it shows the user's information and content posted or shared; the Wall, a space for the user's content; and Events where user ...

What are the 5 main design factors? ›

To help you on your way, we've put together a list of 7 important factors to be aware of when designing a product.
  • MATERIALS. ...

What are 3 features of Facebook? ›

Facebook structure
  • News Feed.
  • Friends.
  • Wall.
  • Timeline.
  • Likes and Reactions.
  • Comments.
  • Messages and inbox.
  • Notifications.

What are 4 common design errors? ›

Here is the list of the most typical mistakes when designing the product:
  • Not understand the importance of Usability.
  • Failing to understand user needs.
  • To design based on assumptions. Fail to test the design.
  • Not contribute to trends.
  • Afraid of data. Ignoring software automation.
24 May 2020

What is the biggest problem in design? ›

Unlocking design's diversity problem

Integrating design into a company's values is increasingly critical for success. Even with these wins, design's biggest threat is its lack of diversity.

What are the 3 keys to a good design? ›

Share: There are a lot of components that go into a design. To best communicate visually, the three main principles of design to consider are typography, hierarchy and color.

What makes a design successful? ›

Good design is a concept defined by industrial designer Dieter Rams's principles: It makes a product useful and understandable, is innovative, aesthetic, unobtrusive, honest, long-lasting, thorough to the last detail, environmentally friendly, and involves as little design as possible. Designers strive for good design.

How can I make my eyes better for design? ›

There are ways you can better develop your eye for design and we've rounded up some suggestions for how to begin.
  1. Step 1: Observe Trends. The best place to start when honing your eye for design is, well, right where you're standing. ...
  2. Step 2: Refer to the Greats. ...
  3. Step 3: Immerse Yourself. ...
  4. Step 4: Practice Makes Progress.
17 Jul 2019

What is a design problem example? ›

For example, a design problem statement may be, “New mums need a way to feel connected to a support group because they spend a large amount of time alone with their babies and end up feeling isolated and lonely.” These mums have a deep-rooted desire to know they're not alone, and a new product might help them ...

How do you solve design patterns? ›

How Design Patterns Solve Design Problems
  1. Finding Appropriate Objects. ...
  2. Determining Object Granularity. ...
  3. Specifying Object Interfaces. ...
  4. Specifying Object Implementations. ...
  5. Putting Reuse Mechanisms to Work. ...
  6. Relating Run-Time and Compile-Time Structures. ...
  7. Designing for Change.

How do I ace the Product Manager interview on Facebook? ›

Here are some of the most important things you can do to win the Facebook product manager interview:
  1. Learn everything there is to know about Facebook. ...
  2. Practice problem discovery. ...
  3. Prepare for Leadership and Drive questions. ...
  4. Practice discovering goal-relevant metrics. ...
  5. Learn how to discover pain points.

Is Facebook pm interview hard? ›

PM interviews are really challenging. The questions are difficult, specific to Facebook (Meta), and cover a wide range of topics. The good news is that the right preparation can make a big difference and help you land a Product Manager job at Facebook.

What is a product designer at Facebook? ›

Product Designers ensure our products. and features are valuable for people, easy to use and of the highest level of. craft and execution.

How long does Facebook interview process take? ›

Overall, expect the Facebook interview process to span four to eight weeks and approximately seven interviews. Interview processes do change periodically, so if your experience does not follow this exact path it's not a negative indicator.

Is it easy to get hired at Facebook? ›

Landing a job at Facebook is challenging. Facebook is one of the most iconic tech companies to work for in modern history, so its standards are high. You must also consider the competition as many highly-skilled individuals are applying to work at Facebook.

How can I pass the final interview? ›

Here are tips to give you the edge you need to pass the final interview;
  1. Prepare Like it's Your First. ...
  2. Don't Let Your Guard Down. ...
  3. Keep it Professional Even if it's a Casual Setting. ...
  4. Be ready to Discuss Salary. ...
  5. Reiterate Your Desire to Join the Team.
4 Feb 2022

Is product design a stressful job? ›

Problem-Solving Is Challenging

This is no easy task! Even experienced designers encounter head-scratching, stress-inducing design problems that can take weeks to solve. Then, after they finally solve a tough problem, three more problems appear! Patience is mandatory in such an intricate line of work.

Which country is best for product design? ›

Best countries to study product design
  • Product Design in UK.
  • Product Design in USA.
  • Product Design in Ireland.
  • Product Design in Belgium.
  • Product Design in Australia.
  • Product Design in Canada.
  • Product Design in Sweden.
  • Product Design in Italy.

What is the role of product design? ›

Product Designers are responsible for coming up with new product designs that meet the needs and wants of consumers. They will have many duties, such as creating design concepts, drawing ideas to determine which one is best suited for the product, and communicating their plans effectively so engineers can execute them.


1. Steam Friends List App - iOS Systems Design Interview
(Andrey Tech)
2. UX Interviews at Google, Apple, Facebook...(8 Types of UX Interviews You Need to Know)
3. System Design Mock Interview: Design Facebook Messenger
4. Facebook iOS Interview Question (Meta - Swift) – 2022
(iOS Academy)
5. iOS Engineer System Design Interview - What to expect, Interview Questions & Tips.
6. Facebook System Design | Instagram System Design | System Design Interview Question
Top Articles
Latest Posts
Article information

Author: Foster Heidenreich CPA

Last Updated: 2023/04/03

Views: 5910

Rating: 4.6 / 5 (76 voted)

Reviews: 91% of readers found this page helpful

Author information

Name: Foster Heidenreich CPA

Birthday: 1995-01-14

Address: 55021 Usha Garden, North Larisa, DE 19209

Phone: +6812240846623

Job: Corporate Healthcare Strategist

Hobby: Singing, Listening to music, Rafting, LARPing, Gardening, Quilting, Rappelling

Introduction: My name is Foster Heidenreich CPA, I am a delightful, quaint, glorious, quaint, faithful, enchanting, fine person who loves writing and wants to share my knowledge and understanding with you.