Perguntas frequentes de entrevistas da empresa ATHENAWORKS
Os usuários do Glassdoor classificaram sua experiência com o processo de entrevista da empresa ATHENAWORKS como 100% positiva, com nível de dificuldade 3,5 de 5 (5 indicando o nível máximo de dificuldade). Os candidatos que passaram por entrevistas para os cargos de Mid-Senior Front End Developer e Senior Full Stack Developer classificaram o processo como o mais difícil de todos. Já as entrevistas para os cargos de Mid-Senior Front End Developer e Senior Full Stack Developer foram classificadas como as mais fáceis.
O processo de contratação da empresa ATHENAWORKS leva, em média, 14 dias, com base em 2 entrevistas fornecidas por usuários de todos os cargos. O processo de contratação dos candidatos ao cargo de Mid-Senior Front End Developer foi o mais rápido (em média, 14 dias). Já o processo de contratação do cargo de Mid-Senior Front End Developer foi o mais lento (em média, 14 dias).
Candidatei-me por meio de recrutador(a). Fui entrevistado pela ATHENAWORKS em out. de 2025
Entrevista
A entrevista técnica foi conduzida por dois devs da equipe deles, e foi dividida em perguntas e desafios técnicos. Considerei as perguntas adequadas para o escopo da vaga (Fullstack) mas o desafio técnico achei inadequado, pois era um problema de média complexidade, que envolvia pesquisa, e eles queriam que fosse feito na hora, sem levar em conta o tempo reduzido.
Perguntas de entrevista [1]
Pergunta 1
Como é controlado o acesso a um bucket no S3 da AWS.
Candidatei-me online. O processo levou 2 semanas. Fiz uma entrevista na empresa ATHENAWORKS (São Paulo, SP).
Entrevista
The interview process was a very positive experience overall. From my perspective, the team was very human-centered and genuinely attentive to what I had to share. The first stage was a conversation with someone from HR. It was a friendly talk where they asked general questions about my background, past experiences, and career goals. After that, I had a technical interview with one of the engineers from AthenaWorks. Unfortunately, I experienced some internet connectivity issues during the call, which disrupted my performance and impacted the outcome. I didn’t move forward to the next stages, mainly due to the connection issues that disrupted the interview. But how do I know that? A few days after the interview, they got back to me to let me know they had decided not to proceed. I asked for feedback so I could improve, and they were very transparent and constructive in their response. They not only highlighted the points I could work on but also pointed out some strengths they had noticed during the interview. They even mentioned that they would reach out again if another opportunity opened up, so I could retake the technical assessment — since the issues I faced were mostly out of my control. If I had passed that round, the next phase would have been technical interviews with the client. From what I was told, this would start with a system design and general technical interview, followed by an asynchronous technical assessment. After that, there would be a follow-up call with the dev team to present and explain my solution — and possibly work on new features through a pair programming session. That said, I believe the exact structure of the client-side interviews may vary depending on the specific client.
Perguntas de entrevista [1]
Pergunta 1
They asked me some interesting questions about how I use AI in my work — specifically, how I leverage it to improve my development process.
Candidatei-me por meio de recrutador(a). O processo levou 2 semanas. Fui entrevistado pela ATHENAWORKS em fev. de 2022
Entrevista
Interviewer was very friendly and in general everything was cool. They contacted me the next day to give me the results from my interview and how to move forward with them.
Perguntas de entrevista [1]
Pergunta 1
What is a difference between patch and put http request?