If you are a star candidate with plenty of experience under your belt and are ready to impress us with a personal open-source project on Github, we want to give you a chance to do so!
We will carefully evaluate your work, and if it meets our engineering standards, we will make you skip the Take Home Assignment and get you straight to the ‣, where you will be able to showcase your skills while talking about something that you’re deeply passionate about!
This option should ideally be taken by exceptional candidates with a strong open-source track record.
If you are such a candidate, we understand that a Take Home Assignment would feel pretty meaningless, and we are happy to evaluate your technical abilities via other routes.
In our hiring history, we encountered very few candidates like that, and one of them was Rehan (who’s now a Chef 🧑🍳!).
His project ‣ should give you a feeling for what we would like to see if you are invited to take this option.
First and foremost, your project should solve a real world problem and be production ready.
No forks accepted and the project must be public so that we can see that the vast majority of the commits came from you.
Relevance: The project must align with the role you are applying for and must demonstrate skills that are directly applicable to our tech stack and industries.
If you wrote your own smartwatch OS, we could all agree that’s well impressive, but we are a Cloud based (AWS/Azure) Data&AI consultancy, so that would unfortunately not be relevant.
Accepted languages: Python, Typescript, Scala, Java.
Complexity: We will assess whether the project's complexity matches the level of work expected at our clients. We won’t be looking for toy projects, but something that solves a real-world problem.
Readability: We look for clear, readable code. Are variable names meaningful and is the code well-structured with appropriate use of functions, classes, and modules?
Consistency: We look for consistent coding styles, such as indentation, naming conventions, and comment styles. Is a clear coding standard followed?
Documentation: We evaluate project-level documentation, code comments and docstrings. Are they helpful, comprehensive and informative?