Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Task 1: Debugging
Directions
We've created a product dashboard template with a graph displaying products' popularity levels and a simple text search. However, some features were left out or built with bugs to test your debugging skills. Your task is to restore the app's functionalities as portrayed in the example solution above.
When coming up with solutions, assume the backend layer was built by another developer and is not open to changes. The design and feature requirements, however, are open to changes and you may feel free to make any tasteful design adjustments.
Overall requests
It is not a requirement of this interview for you to create the perfect component, or to fix all the allocated bugs; the task is designed to reveal the way you approach tasks and Please ensure to think out loud throughout the tasks to reveal your thought process to us. The use of AI and web searches is permitted as long as you can explain why you've accepted the AI responses.
Task 2: Creating a component
Directions
Your task is to create a reusable EmptyState component that resembles the image above (credit: MongoDB). The EmptyState is typically used on error pages, empty search results, and/or other empty list / table states or error states.
Your component should apply best practices and reference existing components in terms of patterns and code styles. To get started, install all dependencies and run
yarn storybook, or the equivalent using another package manager. Build the component and create a Storybook file that best showcases the component you've created. We have created a component directory for you insrc/components/EmptyState.The task is opinionated around our stack on purpose. We would like to gauge how quickly you can adapt to the usage of our component library. If the patterns used are very unfamiliar, you may simply use
<div>s and other raw HTML elements. Our component library is a wrapper around ChakraUI's v2 and other component-specific libraries.