payever Fullstack Engineer Interview Questions
& Process

The interview process had two main steps: a brief non-technical chat and a technical test. The initial conversation, under 15 minutes, was pleasant and covered all job details except salary. The technical part was the challenge. Despite applying for a full-stack role and expecting a test on MongoDB and Angular skills, I was given a backend test using NestJS and RabbitMQ. As a senior NodeJS developer, I'm comfortable with JavaScript but needed more time to learn the unfamiliar framework. This could have been avoided if they had disclosed the test technologies beforehand. The test was scheduled for a Monday, preventing weekend work, which was inconvenient as I have a current job. I did my best to complete the test given the time constraints. The results were expected within 24 hours but took a week. I was informed I failed without any specific feedback on the test, despite completing it. It seems I was deemed technically unfit due to a surprise technology test, even though I could learn and implement it adequately. No one from the technical team communicated with me directly. To add to the frustration, despite an email suggesting a second chance if the test wasn't satisfactory, the selection process was closed for me a week after the test. The entire technical process was frustrating and difficult. Compared to my current role as a full-stack developer at IBM, the difference in how companies treat professionals is significant.

So the interview process was pretty thorough, with different evaluation steps. First, I applied online with my resume and cover letter. Then, they reviewed my application and set up an initial interview with me over Telegram, where we talked about my experience and interest. After that, I got invited to do a practical test to check my technical skills, which was also given through a link on Telegram. They were available to help if I needed anything during the test.

For the interview, there was a live coding exercise using either Angular or Node. It was kinda tough because it had you work on a task within a limited time. This might be hard for Fullstack Developers who don't have the right skills or experience.