I saw a Systems Engineer position at their website more than one year ago. Seemed interesting so I applied. No news at all. Months later got an email from one recruiter from an recruiting agency, offering me the same position: Ok let's go ahead. Days later the recruiter tells me that they are not interested on me, because I've been already in process with them. - "What? I've never talked or been in contact with them." - "Sorry man, it is the client decision." Several months later I receive an email from Social Point HR: - "We want to interview you for a Systems Engineer position". - "Ok, let's go ahead!" I had an Skype interview with HR: She tells me on the chat that she's in a meeting that is taking longer than expected to complete. In fact, the reason is that the meeting started late. How about having the interview in... 45 minutes. I wonder what could happen if things were in the other way: me having to postpone the interview 45 min for whatever the reason... Ok ok,.. no problem. See you in 45 min. 45 min later the interview starts. After some introductory words, she fires the first question: - "Explain me what have you been doing in the last year." I explain to she my last year at my current employer. She fires again, and this time the shot comes from my back: - "Ok. Do you have experience developing in Java?" - "What? I'm not a developer. And this is a Systems Engineer role. I have some knowledge about Java, and I've developed some applications for personal interest, but I'm far to consider myself a professional Java developer. And honestly, if you're looking for someone to cover both roles efficiently, believe me: it is going to be really difficult to find it." - "We know, but our current sysadmins are doing this kind of job, and we want to hire another individual with the same capabilities, even knowing that it is hard to find." Some nice words finishing the interview from their side , and that's all. I think it is one of the weirdest and unprofessional recruiting processes I've had in my 31 years professional career, and believe me: I've done dozens of them. Guys at Social Point: developers are developers. They build the product you are selling. Sysadmin are sysadmins. They build, monitor and keep up the infrastructure your products live on, and also the infrastructure that your developers and QA team need to do their work, not to mention the deployment pipelines among other things. Dev or QA taking care of that, means that they are not doing their work: build the product that your company sells. Not to mention DBAs: it is quite common to consider that a sysadmin can do the work of a DBA. A sysadmin can do SOME database management, but if your are doing serious business, believe me: HIRE DBAs.