My interview process was made up of 5 rounds: screening interview with a headhunter, a conversational technical interview, a take home assignment, a more in depth technical interview, a culture fit interview with the team, and a hiring manager interview. Communication throughout the interview process was clear and consistent. Contrary to some other reviews posted here, I had a very positive experience during all of my interview rounds, which is not common from my past interview experiences. While the priority of the interviews were to determine my technical skills and whether I would fit well into the role, it was often done in a conversational and respectful way. What really stood out were the people I talked to at each stage, which really speaks for the culture of the company. I would absolutely recommend anyone to apply to DKB code factory.

I am posting this review as an over note to the candidates who gives their whole effort in securing a new job. I have had an interview with the DKB recently and had a very disappointing experience. Even though the initial conversation went well, the very next was the coding challenge. The challenge itself tags that you need not have to spend more than 4 hours, but actually if you work it as an end to end use case, you need atleast 1.5 days to finish it off. I am stating this on the basis of the qualities you consider while coding. for example , defining a well good algorithm, structuring your code, writing end to end test as well as unit tests, managing performance optimization techniques, maintaining accessibility standards, writing CI/CD etc. Adding all these features to your exercise will cost you more than a day for sure. Even though you add all of these quality standards and submit a solution to them, their response will either be "not to the level for a senior role" - which I got as a review- or if its more than of a perfect structure, their response will be "too much AI coded. nothing to discuss more about the challenge" and these responses will reach out to you after they send a survey of interview to make sure that they are on safer side. I wanted to let , the recruiters, know that we as candidates spent our brain and energy for this challenge and we deserve at least a discussion call about the work we did. Or at least you should explain in challenge what is your expectation as crystal clear. You are writing in challenge that we do not expect a pixel perfect implementation and just wanted to know your problem approaching skills and believing that we do more than enough for the challenge and get a vague dump response from you. Here I doubt your credibility as well. My challenge was published in a public repo and its was cloned by more than 100 times by unique users within the next five days. I wonder how such a huge traffic can come to a repo which you state that is not upto the standard of a senior developer. Or I doubt if you trying to make candidates work for some of your applications feature for free of cost in the name challenge. Dear candidates, please be aware of such traps and secure your ideas carefully.