💻
Guidelines of Coding test
CADDi's hiring process for some positions requires you to take a coding test. This guideline describes the points we look for in the coding test and the questions we frequently receive.
Outline
What we look for in a Coding TestFrequently Asked Questions and Answers
Time required for each position
What we look for in a Coding Test
Through the Coding Test, we focus on whether we can have the image that we can “work
together to promote development”, rather than checking your knowledge of algorithms or speed
of response.
In addition to whether a certain percentage of test cases are answered correctly, we also check
the code quality (readability, etc.). We would be happy if you could submit your answer from the
perspective of “If you were us, would you want to work with the person who wrote this code?”
Even if not all test cases are answered correctly, we are looking to see how correct the approach is. We expect you to submit a certain level of code quality, rather than submitting the fastest possible solution.
Frequently Asked Questions and Answers
Time required for each position
Since we place more emphasis on code quality (readability, etc.) than on speed of response, we
have set a generous time limit.
For your reference, the following is the average time required by past examinees.
| Roles | Time Limit | Average time required |
| Backend Engineer | 120min | About 110min |
| Frontend Engineer | 150min | About 135min |
| ・Machine Learning Engineer ・MLOps Engineer ・Data Engineer | 90min | - |
| Engineering Manager | 300min | About 180min |
| ・Backend Engineer/English（Workflow Engine） ・SRE | 150min | About 130mi |
| Backend / Full-stack (Fluent English Required） | 105min | About 105min |