Indeed logo

Indeed Software Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 314 interview experiences · FREE TO READ

3.1 Rounds average
Average Typical difficulty
54.7% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Indeed.

Showing 3 of 314
Indeed logo
Indeed

Software Engineer

Engineering · more than a year ago

Senior Average Positive experience No offer 4 rounds
Interview process
Technical screen Technical screen Technical screen Phone screen
Interview formats
Coding Coding Coding Behavioral

It started with a screening by a third-party company, involving an easy/medium Hackerrank programming challenge. Then, there were a few rounds of easy/medium programming exercises with two engineers, one leading and the other observing. The final stage was a more casual, resume-based Q&A with two principal engineers. The interviewers were punctual, friendly, and supportive, and clearly knowledgeable in their field, offering hints and guidance on the programming exercises when needed.

Confirmed questions1 question
  • Could you implement a simulated thread pool executor using JavaScript?
Indeed logo
Indeed

Software Engineer

Engineering · more than a year ago

Mid Average Negative experience No offer 2 rounds
Interview process
Technical screen Onsite Panel Background check Offer
Interview formats
Technical Coding System Design Behavioral

The interview had two main parts. First, a Karat interview where I chose 3 topics and they asked questions, and I solved two coding problems. Second, an onsite interview with two whiteboard sessions. The first was a graph-based coding problem using DFS. I solved it quickly and discussed time complexity. The interviewer modified the graph to see if my solution still worked, which it did, though I made a small mistake in complexity calculation that I corrected. The second whiteboard session was system design for a company review system. I asked clarifying questions, did some calculations, and explained my technology choices. Afterwards, I asked for feedback, and the interviewer seemed positive. A couple of days later, HR told me the interview didn't go well and I wasn't proceeding. I asked for detailed feedback but got none. Then I got a rejection email, still no feedback. It's frustrating because so much time is invested, and it would be helpful to know where to improve.

Confirmed questions3 questions
  • Karat --- Graph based question
  • Onsite -- Round1 -- DFS based question
  • Round2 -- System Design for Review System where user can come and post a review about company
Indeed logo
Indeed

Software Engineer

Engineering · more than a year ago

Entry Average Positive experience Accept offer 5 rounds
Interview process
Recruiter call Technical screen Take home Onsite Background check Offer
Interview formats
Coding Technical Behavioral

The interview process was pretty clear and the recruiter laid it all out. First, there's a recruiter screen to see if you're a good fit. If they like you, you'll get a chance to do a Karat interview. This is basically a Leetcode-style coding test done virtually, but outsourced to Karat. You'll be in Karat's editor trying to solve harder problems in about 50 minutes. Try for 3, but at least nail 2. Karat sends Indeed a video of your interview and their thoughts. A cool thing is, if you mess up, you can retake it. If Indeed is happy with your Karat results, you'll do a virtual onsite. This is usually 4-5 interviews back-to-back with different people from different teams, with 2-3 interviewers each. My super day had two Indeed whiteboard sessions, a 'progex' where you build a program, and a resume deep dive. The whiteboard ones weren't too tough, the interviewer guided you a lot. The Progex was longer, like 105 minutes, and you had to build something work-related. They expect you to finish and pass all tests, but I ran out of time and my code didn't even compile. Just focus on writing clean code, and they'll still evaluate you. The resume review was a standard behavioral interview, looking for project or leadership experience. Make sure to talk a lot about your specific contributions to building software in teams.

Confirmed questions5 questions
  • For the progex, could you create a program to do a fuzzy search on job postings, identifying the top 10 most relevant postings for each search query based on keyword matches?
  • What are your thoughts on the runtime complexity for the fuzzy search implementation?
  • What potential improvements can you suggest for the fuzzy search program in the future?

Indeed Software Engineer Interview Questions

Quoted word for word from Indeed interview reports.

Given a list of iterators for K sorted streams, merge them and count only those numbers that appear in multiple streams.

Read reports

What are the duplicate words in a sentence? For example, given the sentence "The dog is the best", the output should be "the".

Read reports

Find the first duplicated word in a sentence, for example, in "cat dog monkey cat", the first duplicated word is cat.

Read reports

Build an autocomplete feature that suggests completions based on provided strings and the prefix of a search term.

Read reports

From a list of scrambled strings, like "strtrgcaba", can you find one word from a given list, say [birds, cat, baby, etc..]? If no words match, return null.

Read report

On an infinite chessboard, what is the optimal path for a knight to reach a goal square, given that some spaces might be blocked?

Read report

Can you provide a sorted list of unique integers that are common to two given sorted integer lists?

Read report

What is the sum of all values in a tree where a child's value is reduced to its parent's value if it's greater?

Read report

Can you reverse a URL string while ensuring that special characters like '&' are not tampered with?

Read report

Formats, difficulty and experience

Across all 314 Indeed interview reports.

Interview formats

Coding 39.8%
Technical 32.8%
Behavioral 17.5%
System Design 7.6%
Presentation 1.9%

Interview difficulty

Easy 12.1%
Average 59.2%
Difficult 28.7%

Candidate experience

Positive 54.7%
Negative 19%
Neutral 26.4%