The process consists of 5 steps. In the first step, after the HR phone interview, you are expected to introduce yourself to the Head of Engineering and HR, describe the projects you have worked on and the technologies you have used. As you talk, technical questions may be asked. In the HR part, you are asked questions that are commonly asked in HR interviews. In the next step, you do a case study or online coding exercise. You are given a week to complete the case study. The case study I received was not difficult, but you are expected to use an extensible manner and design patterns when writing the code. This code is reviewed, and then you interview with two technical employees based on the code you wrote. Those who participated in the technical interview did not know what the work was about. You explain what you did, and at the end, you are asked where you would improve it if you wanted to, and you are expected to code. After this stage, you take an English exam. In the final step, you have a final interview with the HR business partner and two people from the relevant team, where you are asked a series of questions about both technical and team dynamics, as well as classic questions about what you expect from the team. If there are any notes taken during the review of the previous case study, they are asked. The people interviewing seem to have a serious ego problem; they act as if you know nothing because you don't work at Trendyol. Prepare yourself for this; during the interview, this condescending attitude may irritate you. Any kind of question can be asked, even simple Java questions.
In the final interview, I was asked questions like, “How would you handle this situation?” based on various scenarios. After saying that there was no single correct answer to these questions, I was rejected. I didn't understand why, as the whole process had gone very well. They are obsessed with the culture of feedback; if you come up with a few magic phrases, you can pass most stages. In the final interview, I was asked questions like, “How would you handle this situation?” based on various scenarios. After saying that there was no single correct answer to these questions, I was rejected. I didn't understand why, as the whole process had gone very well. They are obsessed with the culture of feedback; if you come up with a few magic phrases, you can pass most stages. Design patterns and SOLID principles are important, yes, but Trendyol is obsessed with them. If you can't explain even the smallest thing in your code or say, “I broke this principle for this reason,” they may not find it sufficient.
NOTE: Try not to make a single mistake. They say things like “it's just a simple mistake, what matters is that the person is aware of it,” but these small notes they take can lead to your rejection. This is important: if they see even a small flaw somewhere, you get rejected.
NOTE: The test must definitely achieve high coverage in all stages of testing. The types of tests and what is used when writing these tests are definitely asked. Like smoke test, integration test etc.etc. even if you did not write them do know what are they in simple way.
NOTE: You can pass a case study without getting a negative grade using a simple technique. Deliberately do some things poorly and mention it, so you can point them to what you did poorly, and of course, know the better way beforehand and code it.
