Software Engineer(Internship) applicants have rated the interview process at Millennium with 2.8 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 69% positive. To compare, the company-average is 44.9% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer(Internship) roles take an average of 22 days to get hired, when considering 16 user submitted interviews for this role. To compare, the hiring process at Millennium overall takes an average of 25 days.
Common stages of the interview process at Millennium as a Software Engineer(Internship) according to 16 Glassdoor interviews include:
One on one interview: 33%
Presentation: 24%
Personality test: 10%
Group panel interview: 10%
Phone interview: 10%
Drug test: 5%
Skills test: 5%
IQ intelligence test: 5%
Here are the most commonly searched roles for interview reports -
The interview contained 3 Leetcode style problems. I was asked to demonstrate how to make a GET request to an API endpoint that accepts a SQL query, retrieve the JSON response, and then parse the data to extract specific fields
Interview questions [1]
Question 1
How would you make a GET request with a SQL query that returns JSON, and then parse the JSON to extract certain information?
First they are asking about presenting yourself then they gave me a question of code then they asked about compilation about jit boxing unboxing classical theme of C and Java.
In initial interview asked about data types and some basic knowledge of programming, and my cv. no Leetcode yet. The interviewer was nice, and pretty knowledgeable about technology. Btw, avoid interviewing at multiple location! If you screwed up in any of them, you will be rejected automatically
First is cv application then is the hackerrank which is pretty hard and then a behavourial online assesment. Then if you pass that is the first technical interview which for me has a binary search question followed by a bfs question with a 2x2 grid which you should use dynamic programming