Software Developer applicants have rated the interview process at Globant with 2 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 50% positive. To compare, the company-average is 63.8% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Developer roles take an average of 11 days to get hired, when considering 2 user submitted interviews for this role. To compare, the hiring process at Globant overall takes an average of 44 days.
Common stages of the interview process at Globant as a Software Developer according to 2 Glassdoor interviews include:
Skills test: 33%
Phone interview: 33%
One on one interview: 33%
Here are the most commonly searched roles for interview reports -
Foi feita apenas equiparação de cargos quando uma empresa foi fundida. Não teve uma entrevista formal, apenas alinhar quem ainda não se enquadrava em um 'nível' da globant para poder gerar a equiparação salarial
Interview questions [1]
Question 1
ALinhamento de cargos entre as empresas pós fusçao
After the initial interview (with a very kind HR representative) I was invited to a technical one. I received an email saying how long the interview would be (1 hour) and what was expected, all very professional. But when I entered the meeting the interviewer didn't know my name and didn't have my resume beforehand (he wasn't prepared for the interview at all). He also asked me to share screen with a code editor, something that hadn't been mentioned in the email I received so I didn't have a proper environment ready. It was also evident the interviewer was searching for questions online and reading them to me, even including 2 questions that weren't related to my profile. Also, when I wasn't able to reply correctly or I stated I didn't know something, the interviewer didn't answer, just skipped to the next question (I'm sorry, but I'm more used to people holding a conversation and at least exchanging opinions so the interview can also be a learning experience, not just someone taking notes with no comments at all). The technical interview was supposed to last 1 hour but it lasted 2. After the first hour I was feeling a bit drained already but then it was the time for live coding, the most stressing part of the process. I solved the first problem within 2 minutes and was given a second problem, which was harder. I made sure I understood the requirements and the interviewer agreed with my understanding, but after 40 minutes the interviewer said my code wasn't doing what was required, so I clarified the requirements again and it turns out I had got it wrong (even when I precisely asked about it and he had told me I was right in my understanding). Also, during my coding experienced I asked several times about a specific method I didn't remember (I wasn't sure about the exact syntax) and the interviewer didn't even answer (I could overhear him speaking to someone else, so it was clear he wasn't even paying attention to me). Then he suggested I added some code that clearly didn't work, so I said so but since he insisted I added it just to satisfy him and show it didn't work, and proceeded to do what actually DID work. Very absolutely unprofessional.
Interview questions [1]
Question 1
Definición de property, de context manager, generador, decorador, GIL, self. Diferencia entre pop y delete en listas. Diferencia entre operador == y operador is. Diferencia entre método de clase y estático. Herencia múltiple. Patrones de diseño. Definición de REST.
It was exciting for me, I felt very comfortable. The interview depends on the seniority you want to apply. English is important and Knowledge of technology such as programming language and devtools is essential.
Interview questions [1]
Question 1
Lambdas Maven Java features Spring Boot starter Explain about what would it be the solution of a problem? Devtools