https://github.com/mcmakler/frontend-code-challenge
Example interview test for frontend candidates. https://www.mcmakler.de
https://github.com/mcmakler/frontend-code-challenge
Last synced: 12 days ago
JSON representation
Example interview test for frontend candidates. https://www.mcmakler.de
- Host: GitHub
- URL: https://github.com/mcmakler/frontend-code-challenge
- Owner: mcmakler
- License: mit
- Created: 2017-11-27T10:53:00.000Z (over 7 years ago)
- Default Branch: master
- Last Pushed: 2018-02-18T12:06:50.000Z (over 7 years ago)
- Last Synced: 2024-11-18T00:37:20.098Z (6 months ago)
- Language: JavaScript
- Size: 2.12 MB
- Stars: 21
- Watchers: 6
- Forks: 65
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
- awesome-recruitment-tests - McMakler - Create a layout based on the given screen and consume our public API to retrieve a list of advertisements. (HTML & CSS)
README
# Front-End Interview Test
This is a simple front-end code challenge created to serve two purposes:
1. Show off your skills,
1. Give us a better understanding of your skills.## The Task
The programming challenge exists in 2 parts:
* Part A: HTML + CSS
* Part B: Javascript### PART A: HTML + CSS

* Create a layout based on the given screen (fe_test_example_screen.png).
* Style the layout consistently and beautifully, adhering as closely to the design as possible.
* **NOTE:** You are free to use any preprocessor you wish, or write raw CSS. *Bonus points for an explanation of your choice.*### PART B: Javascript
* Consume our public API @ https://api.mcmakler.de/v1/advertisements to retrieve a list of advertisements of vacant apartments.
* Display the first 10 advertisements in the HTML + CSS layout created in step A, sticking to the layout, placing data where it fits.
* **NOTE:** You are free to use any framework you wish, or do it VanillaJS style. *Brief explanation of your choice.*## Additional Instructions
* Fork this repository
* After you're done, provide us the link to your repository.
* Leave comments where you were not sure how to properly proceed.
* Implementations without a README will be automatically rejected.
* No pull requests
* ES6 and above## Bonus Points
* Tests
* Clean code!
* Knowledge of application flow.
* Knowledge of modern best practices/coding patterns.
* Demonstration of good state management.
* Usage of frameworks/supersets.
* Pixel perfection.
* Componential thinking.
* Usage of linters.
* Git hooks.
* Usage of Material Design concepts