In this code challenge, you'll demonstrate your programming abilities by building a data-driven, component-based application. We expect the challenge to take you about four to six hours.
Two projects are available – Vue and React. If you haven't used either framework, and you're most experienced with Angular, we suggest using Vue.
Clone, bootstrap and start a project:
$ git clone [email protected]:TechniqueSoftware/frontend-challenge.git
$ # cd into desired project
$ npm install
$ npm start
An app should now be running on your machine. Templating, babel and hot-reloading have been included.
The product team would like you to create a dashboard for health clubs and studios. This dashboard will help club owners determine when they should run promotions for membership agreements. The success of a promotion relies on check-in volume and the popularity of a membership agreement.
Implement the following features. Your app should look nice and feature basic accessibility, however, functionality is the highest priority. Use the wireframe below as a guide.
- Many widgets can be added to the dashboard. Each widget contains:
- A select input for selecting a location
- A stat of the busiest day of the week (Sunday, Monday, etc.) for the selected location
- A stat of the most popular agreement for the selected location
- A stat of the most popular agreement on the busiest day of the week for the selected location
- Note: If there's a tie for any stat, show both/all results
- Widgets can be removed from the dashboard
- A date range input allows users to filter the data to use for statistics for any given time period (inclusive, so start time should be at 00:00 and end time should be 23:59)
To develop the dashboard, request data from an API for one of our mock clients.
GET locationsGET locations/{locationId}/member-checkinsGET locations/{locationId}/member-agreements- The API is under https://code-challenge-api.club-os.com/api
Our engineering team uses testing to prevent bugs and fuel a culture of confidence and trust. There are many things that can be tested, but we'd like you to focus on the following.
- Test statistic logic
- Test major components
- Tests should be runnable by:
$ npm test
Lastly, the engineering team will need your evaluation on how the feature will scale over time. Take notes on scaling issues or edge cases the feature might run into over its lifetime, and send your notes with you code challenge. A few bullet points will do.
We can't guarantee equal availability for all candidates during the code challenge. To be fair, no questions will be answered. If you have a question, please send it with your submission.
Here are some resources we'd use to complete the code challenge. Feel free to use others!
- Jest: Testing platform
- Enzyme: React testing utility
- Moment.js: Parse and display time
- Tachyons or Bootstrap: Layout and design
- React’s notes on accessibility
- Google's notes on accessibility
When you've completed the code challenge, remove the node_modules directory, zip the project and attach it in a response to the code challenge email. Include your evaluation notes, and if you'd like, tell us about your code or how you think the challenge went!
What are we looking for in your submission? We'll be evaluating submissions in this order:
- Functional application
- Clear, well written and structured code
- Passing tests
- Sensible design with accessibility features
- Evaluation of scalability
- Amount of criteria met