Scale Engineer

Software Engineer II

Software EngineerL2Medium

This interview process is designed to assess candidates for the Software Engineer II (L2) position at Indeed. It evaluates technical proficiency, problem-solving skills, collaboration abilities, and cultural fit.

Rounds·3

Timeline·~14d

Experience·2 - 5 yrs

Comp band·US$110000 - US$140000

Interview time·150 min

Evaluation

What they measure.

  • Problem-solving approach
  • Code quality and efficiency
  • Understanding of data structures and algorithms
  • System design principles
  • Communication skills
  • Collaboration and teamwork
  • Cultural fit with Indeed's values

Preparation

How to prepare.

Tips

  1. Review core computer science fundamentals, including data structures, algorithms, and operating systems.
  2. Practice coding problems focusing on time and space complexity.
  3. Study system design principles and common architectural patterns.
  4. Prepare for behavioral questions by reflecting on past experiences using the STAR method.
  5. Research Indeed's products, culture, and recent news.
  6. Prepare questions to ask the interviewer about the role, team, and company.

Study plan

Fig · Study plan — 04 phases

01 / 04
01

Phase 01 of 04

Data Structures and Algorithms

Weeks 1-2: Data Structures & Algorithms fundamentals. Practice coding.

Weeks 1-2: Focus on fundamental data structures (arrays, linked lists, trees, graphs, hash tables) and algorithms (sorting, searching, dynamic programming, graph traversal). Practice coding problems related to these topics on platforms like LeetCode.

Questions

Commonly asked.

  • How would you design a system to handle real-time notifications for millions of users?
  • Given an array of integers, find the contiguous subarray with the largest sum.
  • Describe a time you had to deal with a difficult stakeholder. How did you manage the situation?
  • Explain the difference between a process and a thread.
  • How would you optimize a slow-performing database query?
  • Tell me about a project you are particularly proud of and your role in it.

Locations

Regional differences.

Fig · Regions — 02 locations

01 / 02

Location

San Francisco

Interview focus

System DesignDistributed SystemsScalability

Common questions

  • How would you design a URL shortener service?
  • Explain the CAP theorem and its implications for distributed systems.
  • Describe a challenging technical problem you solved and how you approached it.

Tips

  • Be prepared to discuss large-scale systems and their design considerations.
  • Familiarize yourself with common distributed system patterns.
  • Practice explaining complex technical concepts clearly and concisely.

Rounds

Round-by-round.

Expand a step for evaluation criteria, sample questions, and prep notes.

Med

Technical Interview - Coding · 45 min · Software Engineer (Peer)

This round focuses on your ability to solve coding problems. You will be given one or two coding challenges and asked to implement a solution. The interviewer will assess your problem-solving approach, coding style, and understanding of fundamental computer science concepts. Expect questions related to data structures, algorithms, and their practical application.

What they look for

A systematic approach to problem-solvingClean, readable, and efficient codeAbility to identify and apply appropriate data structures and algorithmsUnderstanding of time and space complexity

Evaluation

  • Problem-solving skills
  • Coding proficiency
  • Understanding of data structures and algorithms
  • Code clarity and efficiency

Sample questions

  • Given a binary tree, invert the tree.

    Data StructuresAlgorithmsTreesRecursion

  • Find the first non-repeating character in a string.

    Data StructuresAlgorithmsStringsHash Tables

Prep for this round

  1. 01Practice coding problems on platforms like LeetCode, HackerRank, or Coderbyte.
  2. 02Focus on understanding the time and space complexity of your solutions.
  3. 03Be prepared to explain your thought process clearly as you code.
  4. 04Practice writing code on a whiteboard or in a shared editor.

Common rejection reasons

  • ×Inability to articulate thought process
  • ×Poorly structured code
  • ×Incorrect or inefficient algorithm implementation
  • ×Lack of understanding of fundamental concepts

DSA

Coding questions at Indeed.

Frequently reported on Indeed loops

View all at Indeed

Other guides

More at Indeed.