El proceso duró 2 semanas. Acudí a una entrevista en CloudLinux en ene 2018
Entrevista
After an introductory talk I was given a Codility task to do within a week. I managed to complete it with the score 50% while the minimum required for that position was 75%. They offered me to take another shot at the same task. This time I was absolutely ready, but the platform scored me at miserable 37% which was insane.
I may not be a "ninja" or "Jedi" of Python, but I can't imagine myself not being able to accomplish the same task on the second attempt.
So I wrote the person I spoke with earlier expressing my disagreement with the score and asking their colleagues to evaluate my code, but the response was dead cold: "There is no and cannot be an error. Try again in 6 months".
I saw that the hiring process at CloudLinux was unprofessional. They slow on responding and doesn't seem to care about hiring anybody. Getting Codility to select the "right" Python developers is as ridiculous as running candidates through a dance contest. But you can't do nothing about it other than blacklist this company and never return.
Envié una solicitud electrónica. El proceso duró 3 días. Acudí a una entrevista en CloudLinux en ago 2024
Entrevista
Applying is a waste of time. They don't review applications seriously. You apply with a perfect fit to all the requirements and bonus requirements, waste your time writing cover letters, but it is clear they don't review applications seriously or interview seriously.
Envié una solicitud electrónica. El proceso duró 2 semanas. Acudí a una entrevista en CloudLinux (San Petersburgo, ) en nov 2018
Entrevista
As always at the initial step of the process I was asked what salary I would expect. I replied - no problem from their side. Then I was invited to take an online test consisting of 3 tasks. I was given 2 hours and 30 minutes to complete them. The first task was an ICPC-like one with a long description (but in fact not that difficult). In the second task I needed to spot a bug in an existing impl of another ICPC-task. And the last one was more practical: I was asked to calculate some statistics based on a time series data. My overall score was 72% (make some stupid mistakes in the last one). Then after 3-4 we arranged a technical interview. It took ~2 hours and was boring: interviewer red the questions from the list and mostly replied: ok, the next one. I also was asked to write some code: fibonacci, decorators, generators. Also there was a shell-scripting session. That was it. Then after a couple of days the hr reached me out and said than everyone showed green light and she wanted to skype me and discuss my offer details. The arrangement took 2 more days. Finally, she said that based on the feedback they could offer me only N (what is quite less than I expected and said in the beginning). That was just a waste of time.
Preguntas de entrevista [2]
Pregunta 1
does `==` do deep comparison for containers in python by default?