Toshiba logo

Toshiba Embedded Engineer Interview Questions
& Process

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

Based on 15 interview experiences · FREE TO READ

2.3 Rounds average
Average Typical difficulty
53.3% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Toshiba.

Showing 3 of 15
Toshiba logo
Toshiba

Embedded Software Engineer

Engineering · nearly a year ago

Mid Difficult Positive experience No offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Technical Coding Behavioral

So, the interview had an intro, then some C basics, reversing a linked list, a macro question for bit ranges, pointer arithmetic, and string questions. They really emphasized keeping the basics strong, like macros, pointers, and memory management. This role was specifically for driver development.

Confirmed questions2 questions
  • Can you reverse a linked list?
  • Write a macro to get a specific range of bits.
Toshiba logo
Toshiba

Embedded Software Engineer

Engineering · a year ago

Mid Difficult Neutral experience No offer 3 rounds
Interview process
Technical screen Technical screen Technical screen
Interview formats
Technical Coding Technical

So the interview process started with an online MCQ test, it had questions on analytics and C programming. After that, I had my first technical interview which was about 40 mins long. They asked me some basic C questions, gave me a couple of simple coding problems, and asked me to explain OOP concepts. Then I moved to the second technical interview, where I had to explain my project. They also threw in some harder C questions, like bitwise stuff, which I couldn't answer.

Confirmed questions2 questions
  • Questions regarding C, embedded C, and basic to advanced concepts.
  • Questions regarding C, embedded C, and basic to advanced concepts.
Toshiba logo
Toshiba

Embedded Software Engineer

Engineering

Entry Easy Positive experience No offer 3 rounds
Interview process
Technical screen Technical screen Technical screen
Interview formats
Technical Coding Behavioral

The interview process started with an online test that had 4 sections: Cognitive Aptitude (23 questions), Technical - Predict the output (13 questions), Analytical (4 questions with a 2 min limit), and Programming (1 for CSE and 2 for EC). The total time limit was 60 minutes, with no sectional limit except for analytical thinking. The aptitude section covered topics like profit and loss, directions, data interpretation, human relations, time and work, speed and distance, non-verbal reasoning, and percentages. There were no verbal or comprehension questions. The C snippets section focused on strings, for loops, printf, and switch case, with 13 snippets in total. The coding questions involved finding the sum of divisors of a number and finding the nth prime number. Round 2 was a Technical Interview where I was asked to introduce myself and explain my projects in detail. Then, they asked about C and C++ basics, focusing on strings, pointers, structures and unions, OOPs concepts, stacks, and queues. Since I mentioned Python, I was questioned about dictionaries and sets. There were also questions on bit manipulation and sorting algorithms. Round 3 was supposedly a Managerial Round, but it felt like another technical round initially. When I elaborated technically on project challenges, the interviewer asked me to avoid technical details. They reviewed my resume and asked questions based on it. General questions like "Why Toshiba?", "What do you do when demotivated?", and "What books do you read?" were asked, along with some puzzles. I was asked if I had questions, and I inquired about higher studies opportunities while working there, which I felt was a mistake that might have impacted my chances for the next round, the HR round, after which job and internship offers were given.

Confirmed questions2 questions
  • What is the difference between macros and constants?
  • Can you explain the difference between call by value and call by reference?

Toshiba Embedded Engineer Interview Questions

Quoted word for word from Toshiba interview reports.

Can you explain the difference between call by value and call by reference?

Read report

Formats, difficulty and experience

Across all 15 Toshiba interview reports.

Interview formats

Technical 40%
Coding 32.5%
Behavioral 25%
Other 2.5%

Interview difficulty

Easy 6.7%
Average 60%
Difficult 33.3%

Candidate experience

Positive 53.3%
Neutral 40%
Negative 6.7%