Katkat

Company

Generalmotors interview questions

5 practice questions in the style of Generalmotors's interviews, covering System Design, Software Engineering Fundamentals, Coding & Algorithms.

Questions5

0 easy4 medium1 hard

Your progress0/5

Generalmotors interview questions by the numbers

Last updated

Katkat has 5 Generalmotors interview questions. The largest topics are Software Engineering Fundamentals (40%), System Design (40%) and Coding & Algorithms (20%). By difficulty: 80% medium and 20% hard. The most common round is Technical Screen (80%). Frequent concepts include System Design, Algorithms, API Design and BFS.

Difficulty

  • Medium80% · 4
  • Hard20% · 1

Interview rounds

  • Technical Screen80% · 4
  • Onsite20% · 1

Roles

  • Software Engineer80% · 4
  • Machine Learning Engineer20% · 1

Frequent concepts

  • System Design40% · 2
  • Algorithms20% · 1
  • API Design20% · 1
  • BFS20% · 1
  • CI/CD20% · 1
  • Circuit Breaker20% · 1

Showing 1–5 of 5 results

  • Compare monolithic and service-based architectures and plan incremental extraction or consolidation around domain boundaries, data ownership, and measured goals.

    GeneralmotorsSoftware EngineerSystem DesignTechnical Screen
  • Tests your ability to architect an end-to-end reliability workflow combining resilient dependency handling, actionable telemetry, and safe continuous deployment with automated rollbacks.

    GeneralmotorsSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • This problem tests your ability to navigate a 2D grid and identify distinct connected components using graph traversal techniques like Depth-First Search (DFS) or Breadth-First Search (BFS).

    GeneralmotorsMachine Learning EngineerCoding & AlgorithmsTechnical Screen
  • Tests understanding of RESTful API design principles, HTTP semantics, robust error handling, and strategies for backwards-compatible contract evolution.

    GeneralmotorsSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • An open-ended design discussion about an application that calls three to five dependent services and must keep latency under 10 seconds and availability at 99% or better. It tests objective definitions, availability and tail-latency math, timeouts, retries, fallbacks, and adapting as requirements change.

    GeneralmotorsSoftware EngineerSystem DesignOnsite

Generalmotors interview experiences

All 2 →
  • Open-Ended System Design That Ran Fifteen Minutes OverGeneral Motors · Software Engineer · Onsite · Sep 2026

    The interview was scheduled for 45 minutes. The interviewer gave me a question that was roughly: there is an application that has to call three to five dependency services, and how do you guarantee a specific target for a specific service, for example access latency under 10 seconds and availability above 99%. It didn't feel like a normal design round. It felt like a very open-ended discussion ab…

  • Hiring Manager Chat Turned Technical, Then a Codility REST API Phone ScreenGeneral Motors · Software Engineer · Senior+ · Technical Screen · Aug 2026

    Earlier I had a call with the hiring manager. I expected the whole thing to be behavioral, but surprisingly it was almost entirely about technical decisions — things like how you'd go from a monolith to microservices, the tradeoffs between the two, and then how you'd go from microservices to a more modular architecture, and how to make those calls. About a week after that call, a recruiter reache…

More companies