Software Engineer I applicants have rated the interview process at Indeed with 3.2 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 54% positive. To compare, the company-average is 49.6% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer I roles take an average of 21 days to get hired, when considering 176 user submitted interviews for this role. To compare, the hiring process at Indeed overall takes an average of 22 days.
Common stages of the interview process at Indeed as a Software Engineer I according to 176 Glassdoor interviews include:
One on one interview: 28%
Phone interview: 25%
Skills test: 18%
Presentation: 9%
Group panel interview: 9%
Background check: 3%
Personality test: 2%
Other: 2%
IQ intelligence test: 2%
Drug test: 2%
Here are the most commonly searched roles for interview reports -
Only did the 1st round. It was a medium Leetcode question. The interview was only for 30 min. Their compiler threw an unexpected error, which even the interviewers couldn't fix
I applied through an employee referral. The process took 1 week. I interviewed at Indeed (Anaheim, CA) in Nov 2024
Interview
My interview experience at Indeed began with a technical screening conducted by Karat. The first segment focused on conceptual knowledge, where I was able to choose two areas for questioning. I selected HTML/CSS and REST APIs. This portion was straightforward, featuring questions such as "What is the color of the `` tag?" when presented with HTML, and "How would you create an endpoint for a new inventory item?" regarding REST APIs. I felt this initial segment was appropriately aligned with a Software Engineer I role.
However, the interview then transitioned to a live coding section, which presented a significant leap in difficulty. I was tasked with solving LeetCode-style problems, aiming to complete at least two out of three within an hour. The initial problem was a greedy algorithm question, comparable to a LeetCode medium or harder, and I couldn't find a similar problem online, suggesting it might have been an original question. The stark contrast in difficulty between the conceptual and coding rounds was surprising; I genuinely wondered if there was a mix-up with questions intended for a more senior role. I spent the entire hour on the first problem and unfortunately couldn't pass all the test cases.
Terrible scheduling. Difficult company to deal with. Will not contact again. Pay was below industry average for the location. Misleading job description. Benefits below standard. Hope everyone avoids this place
In total, there were five interviews. Three of them were more technical and the other two or more about your background. The technical interviews were pretty standard simple to medium Leetcode questions.
Interview questions [1]
Question 1
I was asked about how we kept metrics in my previous job. When I told him that this was something we didn’t really do, he continued to harp on this question for the entirety of the interview, as if it was something that would be very difficult for me to learn.