Sollicitatievragen bij albelli

The first step was a phone call with the recruiter. That was smooth and went well. The second step was a .Net API API. The requirements in the document was clear for me. I have done the task with the bonus points. I also added Azure CI/CD and deployed the API on Azure. After 2 weeks, the recruiter sent me a rejection email saying to me that the assignment does not need our requirements. I scheduled a Feedback meeting with her and I was shocked! She was reading from a document that the tech team has sent. She listed the pros they found on the assignment like (validation, IoC, Authentication, Testing) and the cons were(Duplicate validation, Separate of Concerns, and Code is not out of the box)). I had built the API with the best practices (DDD, TDD, Docker, CI/CD, Swagger) and am not sure what they are talking about. I could not have any argument with the recruiter on my code as she did not know much about engineering. It was a waste of time and work that I did for actually nothing. I hope the one responsible on checking the assignment is to have sense and give why a candidate is rejected although he was done with the assignment with all the bonus points.

1- recruiter interview (voice call) talked about previous experience and leadership experience. some questions about different situations and how I handle them. 2- take-home code challenge with 1 week time to complete. 3- technical interview which we talked about the code I wrote and how we could make it more efficient. with the team's help and hints. 4- cultural/team fit interview which will take place in a couple of days.

first phone call was pretty standard, nothing to high light second IW, was a technical assessment, an API that does the required in the document they sent you, nothing to highlight the third interview, the phone call with the other developers have some serious red flags, for starters you can explain what you did and they wanted you to quote the documentation in why you did X or Y, like me memorizing the documentation won't prove that I know how to implement something, it seems these guys are still in 1999 where you had to memorize the programming bugs, if I need to double check something I will just open the documentation and read it, I don't need to memorize it and even less for an interview, sorry that is just a bad practice a couple days later they sent me an email saying that I was rejected because I didn't understand the concepts I just implemented, bad experience, I sent an email to the recruiter of what distilled in the interview and so far I was ignored, I never got a reply back

First you meet with a recruiter where you speak about practical stuff. Then you meet a team lead and another designer, where they tell you more about how they work. I did not move forward after the second step.

Phone interviews followed by meeting in office. Pretty standard procedure with the usual steps where you are interview with different angles. Not a lot of positive impressions about the company from anyone I spoke to.

I applied with a CV and cover letter, then I received an email arranging for a phone call interview, which lasted about 30 minutes. I was informed that there would be two more interviews after that

The process was really fast, I heard back really quickly after applying, the interviews were scheduled within a few days after I applied, the questions were reasonably difficult, and they came back with their decision quickly too.

After a long time, I was contacted by phone. It was a quick conversation. After that, they sent a technical test project. I was not approved on this step. Even after spending many hours working on this technical test, they refused to give even any simple feedback and the HR do not answer any e-mail after that.

A waste of time. You need to do an exercise and then you have a 90 minutes interview. I had the interview with 4 or 5 kids. Questions about the architect design, design patterns, microservices, DDD? Not even one. This was a waste of time. 4 kids asking the questions of the school and if you do not respond as they know, for them probably is not correct. I remember 1 question that was about memory out of exception, I gave 3 examples and they "and more?", they wanted to listen to what they want to listen only (probably what they know only). To finish, after spending many hours working on this technical test and then a 90 minutes interview. I received generic feedback. I asked them for a reason, is the minimum after waste all of this time and do a free application, and HR do not answer any e-mail after that. This company just wants free training for their employees nothing more. Do not apply, or just ask for the max value and good luck. This was the worst interview ever.

I've talked to the recruiter and dev team. After the interview with the team, I was trying to contact the recruiter and his email was not working. Nobody gave me feedback. Wasting time.