Ik heb via een recruiter gesolliciteerd. Ik heb gesolliciteerd bij Spring Financial
Sollicitatiegesprek
After the first phone call, they asked me to submit an online assessment that included backend, frontend, and database access. Even though I implemented everything they requested and provided a clear README explaining how to start the application using Docker, I received an email saying I wouldn’t be moving forward. So far so good, it's part of the game. The problem was that they said they couldn’t provide any feedback because they had too many applications. I find that extremely disrespectful.
Sollicitatievragen [1]
Vraag 1
Submit an online assessment that included backend, frontend, and database access
Ik heb online gesolliciteerd. De procedure duurde 1 week. Ik heb gesolliciteerd bij Spring Financial (Vancouver, BC) in sep 2025
Sollicitatiegesprek
This is only about the initial screening call from a recruiter. Based on such a start - I have decided not to proceed.
The screening was mostly regular. It felt like the recruiter hadn't checked my resume at all, as after my usual intro presentation he mentioned that I might not be a match, as I was way more qualified than the job required.
But the negative rating is just because of a single question asked by the recruiter later: "What object-oriented patterns have you used ... for goals like increasing performance performance ...".
In my experience, questions about OOP basics could be relevant if two things are true:
- If the interviewee has next to no experience, so the only thing to check is the programming basics. But the interview was for a senior engineering position.
- If the interviewer knows programming basics - to understand the answer. As otherwise it is only possible to see if the answer contains some of the expected keywords. And I didn't have impression that the recruiter was knowledgeable.
Also - OOP has nothing to do with performance.
It could just be a tricky question - to see how an interviewee handles nonsense. But I did double-check with the recruiter and was told that it was a serious question provided by the hiring manager.
I did try to explain basics of OOP, but the recruiter didn't seem to be interested in that. I also tried to explain, unsuccessfully, that OOP had nothing to do with performance.
I do not expect recruiters or managers to be knowledgeable in technical stuff. But I do expect people to be aware of the limits of their knowledge. So this question meant to me both the recruiter and the hiring manager were incompetent. Not a great sign.
Sollicitatievragen [1]
Vraag 1
What object-oriented patterns have you used ... for goals like increasing performance performance ...