cswork / libraryOpen practice workspace

Interview guides · DENSO

DENSO Software Engineer Interview Guide

DENSO Software Engineer interview guide: reported rounds, questions and how candidates describe the process.

The 60-second brief

As a Software Engineer at DENSO, you will operate at the intersection of cutting-edge automotive technology, embedded real-time systems, industrial automation, and smart manufacturing. DENSO is one of the world's largest automotive technology suppliers, developing critical components and system software that power millions of vehicles globally. From powertrain control and thermal management to advanced driver assistance systems (ADAS), vision inspection tools, and automated testing hardware, the software engineered here directly impacts driver safety, vehicle efficiency, and manufacturing precision. In this role, your code will directly interface with sophisticated electronic control units (ECUs), high-speed communication buses, automated test fixtures, and human-machine interface (HMI) systems.

This guide is scoped to a Software Engineer candidate at DENSO.

Focus areas

  • Java
  • Data Structures
  • Algorithms

The DENSO interview process

DENSO candidates report 5 rounds over 4-6 weeks. The stages below are what candidates describe, not a published process.

HR Phone Screening

Initial phone screening to evaluate candidate's background and fit for the role.

What to demonstrate

  • Initial phone screening to evaluate candidate's background and fit for the role
  • Depth in Java

How to prepare

  • Be able to walk your CV end to end in two minutes, and say why this company specifically.
  • Have your salary expectations, notice period and location constraints ready, and ask for the rest of the loop in writing.

Online Assessment

Candidates may take an online aptitude and technical assessment exam.

What to demonstrate

  • Candidates may take an online aptitude and technical assessment exam
  • Depth in Java

How to prepare

  • Answer aloud and timed: What are standard pointer operations in C, and how do you prevent memory leaks in embedded environments?
  • Answer aloud and timed: What is object-oriented programming, and how do polymorphism and encapsulation benefit software modularity?

Technical Panel Interviews

Interviews with regional department heads and senior software leads, focusing on technical capabilities.

What to demonstrate

  • Interviews with regional department heads and senior software leads
  • Focusing on technical capabilities

How to prepare

  • Answer aloud and timed: Write a function to reverse a linked list or manipulate array structures efficiently.
  • Answer aloud and timed: How do control logic loops operate on programmable logic controllers (PLCs) or embedded microcontrollers?

Project Presentation

Candidates present prior engineering projects and defend technical decisions.

What to demonstrate

  • Candidates present prior engineering projects and defend technical decisions
  • Depth in Java

How to prepare

  • Answer aloud and timed: What methodologies do you use for hardware-in-the-loop (HIL) testing and automated vision inspection?
  • Answer aloud and timed: Describe how communication protocols like CAN or LIN operate within an automotive electronic control unit network.

Onsite Interviews

Interviews at major facilities with facility tours and team meetings to assess cultural alignment.

What to demonstrate

  • Interviews at major facilities with facility tours and team meetings to assess cultural alignment
  • Depth in Java

How to prepare

  • Answer aloud and timed: How do you design automated test scripts to validate software functionality against strict physical tolerance limits?
  • Answer aloud and timed: What approach do you take when troubleshooting a failing sensor reading or corrupted data transmission on a test bench?

Where candidates lose points

Know your resume inside and out

Interviewers frequently ask detailed questions about specific projects, languages, and technical tools listed on your resume. Be ready to explain your exact individual contribution to every project you cite.

Structure your behavioral answers with STAR

Use the STAR method (Situation, Task, Action, Result) when answering behavioral questions. Focus heavily on the concrete actions you took and the quantifiable results you achieved.

Tests that assert on the implementation rather than the behaviour

Assert on what a caller can observe, not on the number of internal calls or the shape of a private field. A test that breaks on every refactor but still passes when the answer is wrong costs more than it protects.

Questions & practice

Explain the difference between process and thread execution, and how shared memory is synchronized in C++.

Medium · Core Software Development & OOP Concepts

Approach

  1. Say what the runtime actually does before reasoning about the code.
  2. Name what is shared across threads and what owns each piece of state.
  3. Identify the window where an invariant is briefly untrue.
  4. Distinguish a value from a reference to it, and say which one you handed out.

Follow-up

  • What happens if two callers reach this at the same time?
  • Where could this allocate more than you expect?

What are standard pointer operations in C, and how do you prevent memory leaks in embedded environments?

Medium · Core Software Development & OOP Concepts

Approach

  1. Say what the runtime actually does before reasoning about the code.
  2. Name what is shared across threads and what owns each piece of state.
  3. Identify the window where an invariant is briefly untrue.
  4. Distinguish a value from a reference to it, and say which one you handed out.

Follow-up

  • What happens if two callers reach this at the same time?
  • Where could this allocate more than you expect?

Write a function to reverse a linked list or manipulate array structures efficiently.

Medium · Core Software Development & OOP Concepts

Approach

  1. Restate the input: its shape, its size, and what is guaranteed about it.
  2. Name the brute-force solution and its complexity before improving on it.
  3. Choose the data structure from the access pattern, not from familiarity.
  4. State the target complexity and say which constraint rules the naive version out.

Follow-up

  • How does this change if the input no longer fits in memory?
  • What is the worst case, and how likely is it on real data?

Replace offset paging on the resource feed with keyset

Easy · keyset pagination · composite index · sort order

resource holds resource_id, tenant_id, owner_user_id, title, body_ref, version, status ('draft','active','archived','deleted'), created_at, updated_at, deleted_at, with an index on (tenant_id, status, updated_at DESC, resource_id DESC). The listing endpoint returns active resources for one tenant, newest update first, 50 per page, today with LIMIT 50 OFFSET n. Tenants reach page 400 and rows are created while they read. Write the keyset query, define what the cursor carries and how it is encoded, and say which part of the index each predicate uses. Assume PostgreSQL 16.

Approach

  1. Name the two failures separately. OFFSET 20000 makes the server produce and discard 20,000 rows, so page cost grows with depth rather than with page size. Independently, any write that changes how many rows sort above the offset moves the window between two fetches, and the direction decides which anomaly you get: an insert lands at the head of updated_at DESC and pushes already-returned rows down past the boundary, so they are returned a second time; a delete above the offset, or a row whose updated_at is bumped above the cursor, pulls rows up and one is never returned at all. Nothing in the response reveals either.
  2. Write the seek: WHERE tenant_id = $1 AND status = 'active' AND (updated_at, resource_id) < ($2, $3) ORDER BY updated_at DESC, resource_id DESC LIMIT 50. The row-value comparison is one index range rather than a disjunction, and both columns are NOT NULL, which is what makes that comparison well defined.
  3. Map each predicate onto the index: tenant_id and status are equality on the leading columns, (updated_at, resource_id) is the range, and the ORDER BY matches the index order so no Sort node appears and the scan stops after 50 rows. The DESC in the definition only matters for mixed directions — a plain ascending btree on the same columns is read backwards for this query.
  4. Put both sort columns in the cursor and nothing the client can tamper with into another tenant: base64 of (updated_at, resource_id), validated server-side, with tenant_id taken from the principal.

Follow-up

  • The client asks for 'jump to page 400'. What do you offer instead, and what does the honest version cost?
  • Sort order becomes user-selectable across four columns. How many indexes is that, and which would you refuse to add?

Stop tag and share joins from fanning out a page

Medium · join fan-out · semi-joins · many-to-many

resource_tag is (resource_id, tag_id) with PK (resource_id, tag_id); resource_share is (resource_id, shared_with_user_id, permission). The tagged-and-shared listing inner-joins resource to both, filters tenant_id, tag_id = ANY($2) and shared_with_user_id = $3, orders by updated_at DESC and takes 50. Pages come back with fewer than 50 distinct resources and the total in the header is far too high. Explain the row multiplication, rewrite both the page query and the count query so each is correct, and name the index each one needs. PostgreSQL 16.

Approach

  1. Do the arithmetic against the predicates that are actually there. An inner join emits one row per matching child row, and both joins are filtered: tag_id = ANY($2) admits only the requested tags, shared_with_user_id = $3 admits one user's share rows. So a resource holding three of the requested tags and shared with $3 once yields three rows, not one — the multiplier is its count of matching tags times its share rows for that single user, and that second factor is 1 unless the table admits duplicate (resource_id, shared_with_user_id) pairs. LIMIT 50 then limits rows rather than resources, and COUNT(*) counts pairs — the header is the product, not the population.
  2. Reject DISTINCT as the fix. It deduplicates after the product has been built, so the planner must materialise and sort the fanned-out set before the LIMIT can apply, and it leaves any SUM or AVG in the same select list wrong.
  3. Rewrite both filters as semi-joins, keeping resource as the only row source: AND EXISTS (SELECT 1 FROM resource_tag rt WHERE rt.resource_id = r.resource_id AND rt.tag_id = ANY($2)) and the same shape against resource_share. A semi-join stops at the first match per resource and preserves the driving index order, so ORDER BY updated_at DESC, resource_id DESC LIMIT 50 still stops after 50 rows.
  4. Count with the same predicates and no join at all: SELECT count(*) FROM resource r WHERE r.tenant_id = $1 AND r.status = 'active' AND EXISTS (...) AND EXISTS (...). Nothing multiplies a resource, so the number is the population.

Follow-up

  • The filter changes from 'any of these tags' to 'all of these tags'. Rewrite it and state what it costs relative to the ANY form.
  • A resource can be shared with the same user twice under different permissions. Does your count change, and should it?

How would you design a class in Java to manage dynamic objects with specific member functions and constraints?

Medium · Core Software Development & OOP Concepts

Approach

  1. Fix the scope first: who calls this, how often, and what they do when it fails.
  2. Name the read and write paths separately; they rarely have the same bottleneck.
  3. Choose a partition key and say what query it makes expensive.
  4. State the consistency you need, and where you are willing to be stale.

Follow-up

  • What breaks first when traffic grows ten times?
  • How does this behave when that dependency is down for an hour?

What is object-oriented programming, and how do polymorphism and encapsulation benefit software modularity?

Medium · Core Software Development & OOP Concepts

Approach

  1. Clarify what is being asked and what a complete answer contains.
  2. State your assumptions explicitly before working the problem.
  3. Say what you would check first and why it is the highest-information step.
  4. Work from the requirement backwards to the design.

Follow-up

  • What assumption would you test first?
  • How would you know your answer was wrong?

How do control logic loops operate on programmable logic controllers (PLCs) or embedded microcontrollers?

Medium · Controls, Testing & Hardware Integration

Approach

  1. Say who the caller is and what they do when the call fails halfway.
  2. Define the identity of a request so a retry cannot double-apply it.
  3. Separate accepted, pending, failed and confirmed; they are different facts.
  4. Design the error taxonomy before the success shape; callers branch on it.

Follow-up

  • What happens if the caller retries after a timeout?
  • How does a client discover it is on an old version of this contract?

What methodologies do you use for hardware-in-the-loop (HIL) testing and automated vision inspection?

Medium · Controls, Testing & Hardware Integration

Approach

  1. Say who the caller is and what they do when the call fails halfway.
  2. Define the identity of a request so a retry cannot double-apply it.
  3. Separate accepted, pending, failed and confirmed; they are different facts.
  4. Design the error taxonomy before the success shape; callers branch on it.

Follow-up

  • What happens if the caller retries after a timeout?
  • How does a client discover it is on an old version of this contract?

Describe how communication protocols like CAN or LIN operate within an automotive electronic control unit netw

Medium · Controls, Testing & Hardware Integration

Describe how communication protocols like CAN or LIN operate within an automotive electronic control unit network.

Approach

  1. Say who the caller is and what they do when the call fails halfway.
  2. Define the identity of a request so a retry cannot double-apply it.
  3. Separate accepted, pending, failed and confirmed; they are different facts.
  4. Design the error taxonomy before the success shape; callers branch on it.

Follow-up

  • What happens if the caller retries after a timeout?
  • How does a client discover it is on an old version of this contract?

How do you design automated test scripts to validate software functionality against strict physical tolerance

Medium · Controls, Testing & Hardware Integration

How do you design automated test scripts to validate software functionality against strict physical tolerance limits?

Approach

  1. Fix the scope first: who calls this, how often, and what they do when it fails.
  2. Name the read and write paths separately; they rarely have the same bottleneck.
  3. Choose a partition key and say what query it makes expensive.
  4. State the consistency you need, and where you are willing to be stale.

Follow-up

  • What breaks first when traffic grows ten times?
  • How does this behave when that dependency is down for an hour?

What approach do you take when troubleshooting a failing sensor reading or corrupted data transmission on a te

Medium · Controls, Testing & Hardware Integration

What approach do you take when troubleshooting a failing sensor reading or corrupted data transmission on a test bench?

Approach

  1. Establish what changed and when, before forming any theory.
  2. Pick a bisection that eliminates candidates whichever way it turns out.
  3. Check the instrumentation before believing the symptom.
  4. Separate the trigger from the cause; the deploy is rarely the bug.

Follow-up

  • What would you look at first, and what would it rule out?
  • How would you tell a cause from a coincidence here?

Suggested practice checklist

Built from the rounds and topics DENSO candidates report.

Day 1 — Map the DENSO loop

  • Write out the reported sequence: HR Phone Screening, Online Assessment, Technical Panel Interviews, Project Presentation, Onsite Interviews.
  • For each round, write one sentence on what it is judging, from the description above, and mark the one you are least ready for.

Deliverable: A one-page map of the 5 reported rounds, with the weakest marked.

Day 2 — Work Java

  • Spend the session on Java, which DENSO candidates report being tested on.
  • Write one worked example in Java and time yourself on it.

Deliverable: One timed worked example in Java.

Day 3 — Work Data Structures

  • Spend the session on Data Structures, which DENSO candidates report being tested on.
  • Write one worked example in Data Structures and time yourself on it.

Deliverable: One timed worked example in Data Structures.

Day 4 — Work Algorithms

  • Spend the session on Algorithms, which DENSO candidates report being tested on.
  • Write one worked example in Algorithms and time yourself on it.

Deliverable: One timed worked example in Algorithms.

Day 5 — Answer out loud: Core Software Development & OOP Concepts

  • Answer aloud, timed: Explain the difference between process and thread execution, and how shared memory is synchronized in C++.
  • Answer aloud, timed: How would you design a class in Java to manage dynamic objects with specific member functions and constraints?

Deliverable: Spoken answers to 2 reported Core Software Development & OOP Concepts question(s), under time.

Day 6 — Answer out loud: Controls, Testing & Hardware Integration

  • Answer aloud, timed: How do control logic loops operate on programmable logic controllers (PLCs) or embedded microcontrollers?
  • Answer aloud, timed: What methodologies do you use for hardware-in-the-loop (HIL) testing and automated vision inspection?

Deliverable: Spoken answers to 2 reported Controls, Testing & Hardware Integration question(s), under time.

Day 7 — Answer out loud: Behavioral & Team Collaboration

  • Answer aloud, timed: Describe a challenging engineering project you worked on and how you overcame technical roadblocks.
  • Answer aloud, timed: How do you handle working in a multi-disciplinary panel setting with cross-functional engineering leads?

Deliverable: Spoken answers to 2 reported Behavioral & Team Collaboration question(s), under time.

Behavioural preparation

Behavioural rounds judge the decision you made and what it cost.

Describe a challenging engineering project you worked on and how you overcame technical roadblocks.

Medium · Behavioral & Team Collaboration

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. Name the disagreement and how you resolved it with evidence.

Follow-up

  • What would you do differently if you ran that again?
  • How did you know your change caused the improvement?

How do you handle working in a multi-disciplinary panel setting with cross-functional engineering leads?

Medium · Behavioral & Team Collaboration

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. Name the disagreement and how you resolved it with evidence.

Follow-up

  • What would you do differently if you ran that again?
  • How did you know your change caused the improvement?

Tell me about a time when you had to explain a complex technical bug to a non-technical manager or client.

Medium · Behavioral & Team Collaboration

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. Name the disagreement and how you resolved it with evidence.

Follow-up

  • What would you do differently if you ran that again?
  • How did you know your change caused the improvement?

How do you prioritize tasks and ensure safety and quality standards when facing tight production deadlines?

Medium · Behavioral & Team Collaboration

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. Name the disagreement and how you resolved it with evidence.

Follow-up

  • What would you do differently if you ran that again?
  • How did you know your change caused the improvement?

Do you prefer working independently or in collaborative team environments, and why?

Medium · Behavioral & Team Collaboration

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. Name the disagreement and how you resolved it with evidence.

Follow-up

  • What would you do differently if you ran that again?
  • How did you know your change caused the improvement?