This is a repository of take-home excercises for candidates applying to join the team at Weever Apps.
The goal of the exercise is for a candidate to complete one of the available problems before their final interview. The solution is then reviewed with the candidate and used as a discussion point in the hiring process.
Expect to take anywhere from 3 - 4 hours of your time. In general you’ll have a week to complete the assignment. We understand that your time is valuable and circumstances are different for everyone so we are open to discussing special arrangements on a case-by-case basis.
The requirements for each exercise are given informally. There may be amiguities or contradictions. We do our best to give them in a form similar to what you may expect on the job. Do your best to interpret the intention and present your solution. However if you’re really stuck feel free to contact your interviewer with your questions.
After you submit your code we will contact you with a follow-up interview. We like to talk about code and will walk through your submission with you. We want to hear about your design choices, what you thought about the specifications, trade-offs you may have made, etc. We’ll cover both the technical and social aspects of working at Weever.
Keep it simple.
We want to know how you approach problems and the kind of code you write to solve them. Our primary language is Javascript but feel free to use the language you are most comfortable with.
In code review we want you to walk us through your solution. You will be asked to explain your implementation choices, trade-offs, etc.
These exercises are just toy problems but treat them like production code that you would actually deploy.
You can submit your solution to us in the manner most convenient to you: tarball, zipfile, dropbox, repository… whatever works best.
Make sure to include a README with your submission. If there are any
tools or setup instructions we need to run your code document them
there. Also give us a high-level introduction to your solution: how to
run it, things to try out, describe the API a bit, etc.
Assume, however, that we will run your code in some kind of Unix-like operating system.
Help Robbie the Robot deliver presents.
See the robot.md for more details.
Parsing METAR reports.
See the metar.md for more details.
Already have a cool project to show us? Can think of a more interesting problem than the ones described above? Show us!
Just make sure it represents about 3 - 4 hours of effort and you can describe the specification or intended purpose clearly.
Some parts of the specification may be intentionally ambiguous and open-ended. Do your best to interpret the intention of the specification and make a call. We’d like to know the reasoning behind your decisions!
If something is contradictory or makes absolutely no sense feel free to let us know. We’ll try to clear it up.
Please contact us! We’re happy to make alternative arrangements.