payever Interview Questions
& Process

The hiring process moved super quickly. Got a LinkedIn message and then a technical test pretty soon after. The test was tough but definitely related to the actual job. My chat with the tech lead was straight to the point, focusing on architecture and code quality instead of typical interview stuff. I liked how upfront they were about company goals and how fast I got feedback after each step. Just a heads-up, the tech test has a short deadline, so be ready to drop everything to tackle it. It would be cool if they gave a quick rundown of the team setup on the first call.

The interview process at Payever is pretty fast and has several steps. You'll probably start with a quick call from HR or a recruiter to go over your background, experience, and what you expect from the job. Then, there's usually a skills test or technical assessment, which is standard. If it's a technical role, you'll get coding problems or a case study. For other roles, it might be more marketing or business-related tasks. After that, if you make the cut, you'll have interviews with team leads or managers. These focus on your tech skills, how you solve problems, your past work, and if you're a good fit for the company culture. Some people also mentioned doing a trial work period or a 'remote working day' to see how you actually do the work. People say it's fast but can be a lot, with detailed tasks and sometimes mixed communication. A lot of reviews point out that they really care about practical skills, so be ready to show you can do the work before they offer you the job.

The test was challenging but appropriate for the role, which includes a 3-6 month training period, indicating it's for developers with potential rather than experienced professionals. I had issues with the recruitment process: 1. Requiring a paid software that needs a Company Account for download, making it unusable without one (unless on Linux), which is a significant disadvantage. 2. Refusal to assist with technical difficulties, even for issues caused by their setup, stating it would be 'unfair'. Any technical problem seems to lead to automatic failure. 3. Despite the test's complexity, failure results in a simple rejection without detailed feedback on performance, which is disappointing given the effort involved.

Got contacted on LinkedIn first. Then had a 15 min Zoom call with HR. After that, they wanted me to do a technical task. They initially offered me an IT Project Manager role, but during the interviews, they realized I was a better fit for IT Security Manager and changed it. We scheduled the technical task, meant to start at 8am with 5 hours allocated. On the day it was supposed to happen, nobody contacted me or sent the task. Apparently, there was a 'technical problem', so we rescheduled. When I finally did the task, I noticed it was still titled 'IT Project Manager Task'. It didn't include anything about cybersecurity or security. It was basically stuff a dev or IT Project Manager would do, so my actual skills weren't tested.