machine-coding-feedback

Please go through this document to get your machine coding code reviewed by workat.tech

Why Practice for Machine Coding Round?

• In companies like Flipkart, Uber, Swiggy, Ola, Cred, etc the first onsite round is the machine coding round.
• You’re given a design problem (like design a parking lot) with a set of requirements.
• Then you need to create a clean, modular and extensible coding solution for the same.
• The code is supposed to be written in a matter of 90 mins.
• After the round, you sit with an interviewer who goes through your code and tries to understand your design decisions and also tries to see if your code works for all the requirements.
• The interviewer may ask you to extend your solution based on some new requirement.
• It is a pretty crucial round since most of the people get eliminated in this round and it is completely different from what everyone generally practices for.

How to prepare?

Please go through our article on ‘How to prepare for machine coding round?’.

Setup

• Ensure that you’ve a github account. If you do not have one, check this page.
• Ensure that you’ve git set up locally on your Laptop/PC. If it is not set up, check this page.
• Go to machine-coding-feedback repository.
• Fork the repository. If you’re new to git, follow the steps mentioned in the fork section here
• Clone the repository in your local machine.If you’re new to git, follow the steps mentioned in the clone section here

Coding

• After the setup step, a new folder will be created in your laptop/PC with the name: machine-coding-feedback.
• Open that folder in an IDE of your choice and start coding.

Expectations

• Make sure that you have a working and demonstrable code
• Make sure that the code is functionally correct
• Code should be modular and readable
• Separation of concern should be addressed
• Please do not write everything in a single file
• Code should easily accommodate new requirements and minimal changes
• There should be a main method from where the code could be easily testable
• [Optional] Write unit tests, if possible
• No need to create a GUI

Submission

• After you’re done with coding, you need to commit and push your changes to github.
• You should push your changes to the master branch of your forked repository. If you’re new to git, follow the steps mentioned in the push local changes to remote section here
• Create a pull request to our master branch. If you’re new to git, follow the steps mentioned in the PR section here

Evaluation

• We’ll be reviewing everyone’s submission and try to provide feedback on how to improve through code review comments on GitHub.
• We also have some volunteers who will help with the review.
• Anyone can volunteer to review.