An initial conversation occurred with HR, followed by a technical interview offering choices in frontend, backend, or full-stack focus, allowing candidates to showcase their strengths. The interview went well, leading to a discussion on software architecture with an architect and a final meeting with a project delivery team member to understand the company's projects. Based on the positive outcomes of the test and the conversations, it seemed likely that an offer would follow. However, the follow-up call brought vague feedback, citing concerns about being 'too senior' for the role, insufficient budget, and a requested salary that was considered too high — despite it being within the range listed in the job description...

You will get a call from an HR person to talk about the company and have an idea what you will be working on., Then I call with the team to have more technical discussion. Finally you will have the call to do the coding or let’s call it a day of work simulation where they get to test your knowledge. Which I screwed it up because I was already thinking of refusing any offer in the future. In the last part if you’re a newly graduate it’s okay but if you’re more experienced developer you will feel offended by their coding test, they are definitely missing the point of having a coding challenge. The last test will give you an idea that the company is not very high tech and a lot of legacy code. I know someone worked there and the company doesn’t seem to be a good working company if you sit fiiiit the culture. And yes it’s only when I did the test I knew it’s only too good to be true