520c200dd6
|
||
|---|---|---|
| .. | ||
| testdata | ||
| README.MD | ||
| amount.go | ||
| amount_test.go | ||
| analyzer.go | ||
| analyzer_test.go | ||
| errors.go | ||
| go.mod | ||
| go.sum | ||
| transaction.go | ||
| transaction_test.go | ||
README.MD
Welcome to the Digits Go Work Sample!
At Digits, we care deeply about who joins our team, so congrats on making it to this round in the process!
One of our goals as we continue the conversation is to learn more about how you think about and solve technical problems, so that we can get a sense of what it will be like working together day-to-day. That's what we're going to focus on here.
First things first: If you have prior experience with go, please only spend 3 hours on this. If you are new to go, please allow yourself 4 hours.
We've designed it so there is more work here than it's possible for anyone to finish in 3 (or 4) hours, so don't worry about it. We're looking for quality of engineering, not quantity of engineering. Seriously :)
And, of course, feel free to use any resources you would in your normal day-to-day work experience: Google, StackOverflow, etc.
Please take the time to format your code using gofmt (trivial to do if you are using VSCode). If you are new to go, this is a great resource to get some pointers.
Without further ado, here's a quick intro to the basics...
Setting Up...
Make sure you have Go installed. You'll need at least 1.13.
Then, head on over to analyzer_test.go where the instructions continue...
When your 3 hours are up, follow the instructions at the bottom of this README to submit your work sample, along with a few written-response questions. Happy coding!!
If You're Totally Stuck :-(
If the instructions above don't work for any reason, or you get hopelessly stuck while coding, don't stress! Send us a note at hello@digits.com and we'll help get you sorted!
When Your 3 Hours Are Up :-)
Pencils down! We know how tempting it is to keep going, so we really appreciate you sticking to the time limit :)
To submit your work sample, Zip up this directory (everything except the .build sub-directory) and email it back to us along with your written responses to these questions:
- How would you evaluate your work? What went well? What would you do differently?
- What was the biggest insight you gained, or thing you learned, while working on this?
- If you were to add another test challenge to this, what would it be? Why?
Thanks again for taking the time to complete this, and we're really looking forward to continuing the conversation!
Happy coding!!
—Team Digits