If you’re looking for tips on how to get started with a Geektrust coding challenge, what we look for in a coding solution etc.., you’re at the right place.
Our coding challenges are a bit offbeat from the usual coding tests. And this is intentional. We’re trying to understand how you would write code in the real world and not whether you can do a quick solution to get it to pass.
The majority of us at Geektrust have been developers and spent a decade or more at ThoughtWorks, and we’ve designed our coding challenges to understand your approach to solving a problem.
So here’s how we suggest you get started:
- Read the coding problem well and understand clearly what the expected input/output is.
- Sketch out a domain model in your head/paper with a modular structure.
- Write tests and keep evolving your solution. In parallel, list out dependencies and targets to be executed in a build file
- Refactor and make your code simpler, while running your unit tests.
- Create a README with all assumptions, dependencies and sample I/O
You can read here in detail what we look for in your code –> https://www.geektrust.in/how-we-evaluate. There are more links that help you understand how to write code that we like, and the companies we work with like.
If you need help, do join our Slack channel and we’ll be happy to help you out. Look forward to seeing you there.