These coding exercises are meant to help Spiff gain insight into how you would tackle actual feature requests by the product team. The exercises are relatively simple, but you are encouraged to treat them as if you were working on the Spiff codebase. This means applying the same attention to code quality, tests, pull requests, commits, etc as you normally would. Quality is valued above quantity.
- Clone the repo (don't fork) - This is your start time
- Point the remote origin to a new repo under your account
- Retreive dependencies:
yarn, and start the dev server:yarn start. The app should open on http://localhost:3000 - This will take you to an index that lists the exercises. For each exercise:
- click the exercise link from the index page
- v1:
- review v1 specs
- create a new branch off of master
- complete the
Solutioncomponent for the exercise (the ProgressBar exercise is found in ProgressBar.js) - create a pull request on your repo when finished
- v2:
- review v2 specs
- create a new branch off of v1
- build on v1 to meet v2 requirements
- create a pull request on your repo when finished
- The last commit is your end time
- Send a link to your repo to casey@spiff.com
- Try to limit your total time to 3.5 hours. If you feel like you need more time to adequately demonstrate your ability and thought process, please do. There are likely more steps than you can complete in 3.5 hours
- Testing: write unit tests where you can and don't worry about component tests
- Place css and test files beside the component they relate to (same directory)
- Feel free to use any non-human resources you like: StackOverflow, Google, reference code on Github, etc
- If you run out of time, please add a few quick comments explaining what you would have done if you had more time. The same is true if instructions were unclear or if you have any other thoughts
Thank you for taking the time to complete this coding assessment! Don't stress too much about any one thing, we evaluate the exercises holistically.