Envié una solicitud electrónica. Acudí a una entrevista en T-Mobile en sept 2020
Entrevista
Good
- Throughout the process, I got an opportunity to meet with a lot of T-Mobile engineers. They all were genuinely nice.
- Initial interview process is really good. You are screened with an easy level of Leetcode style questions. Then you're in a half-day interview which among others involves a live coding session. The great aspect of this live coding session is, you don't need to complete the code but demonstrate your ability of the language, using tools, TDD, thought process and even Googling skills.
Bad
The whole interview process is pretty long. I spent around ten hours between multiple interviews. It would be nice if they fail fast.
Ugly
Like some other people have mentioned, in the end, I also got ghosted by my recruiter (talent scout). What frustrates me the most is I always got good feedback after or even during the interview. One of the interviewers even encouraged me to accept the offer. I guess at the end of the day I wasn't a good fit. Considering I spent around ten hours interviewing, an answer, even a generic rejection letter, is not a lot to ask for.
Preguntas de entrevista [1]
Pregunta 1
For a live coding session, you're given a set of questions around an hour before the interview.
Solicité el puesto a través de una agencia de empleo. Acudí a una entrevista en T-Mobile (Hyderabad) en oct 2025
Entrevista
Interviewers focused on the fundamental skills and how the candidate was trying to solve the problem rather than making it Q&A session. If we can provide our solutions with clarity it would be easy to crack.
Preguntas de entrevista [1]
Pregunta 1
Binary Search, Optimizing an API, How does your day looks like.
Envié una solicitud electrónica. El proceso duró 2 semanas. Acudí a una entrevista en T-Mobile (Frisco, TX) en sept 2025
Entrevista
Interview:
The interview process was straightforward. A couple of round of interviews, first one with 2 of their senior engineers, and second one with a HM. Despite doing well (answered all the questions asked) and hearing some positive feedback during the interview, I did not get pass the first round. One of the interviewer seemed to like me, he agreed with a lot of answer I said and we had a very positive and collaborative interaction. However, the other one ... not so much. He asked vague questions with a fixed answer in his mind, and when I did not say what he was looking for a couple of times, I lost some points on his scoresheet. I did eventually say what he was looking to hear but that apparently did not save me. Also, the interview was very technical until the final question. The second interviewer, who was not pleased throughout the interview, did a total shift from deep technical questions to a behavioral question for which I did not have an exact match for an answer. I think that hit the nail on the coffin.
Recruiter:
The recruiter was truly incompetent. Their communication was poor throughout the process, especially after my first interview. Did not get even a generic response about the status of my application.
Interviewers and Recruiters both could do a better job.
Preguntas de entrevista [1]
Pregunta 1
This was an Software Engineer AI role, so discussion about AI, data processing pipeline like ETL, resume related questions, and yes, one random behavioral question at the end which caught me offguard.
Technical interview was more question/answer style. No coding tests. This was more of a test center at the time than software development. It was basic intuition and how I could work with others and the depth of technical knowlege of coding, testing and data analytics
Preguntas de entrevista [1]
Pregunta 1
What was my experience with database interactions when it came to pulling large volumes of test results from database for business intelligence visualization
