embedUR systems logo

embedUR systems Embedded Engineer Interview Questions
& Process

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

Based on 10 interview experiences · FREE TO READ

2.9 Rounds average
Average Typical difficulty
60% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at embedUR systems.

Showing 3 of 10
embedUR systems logo
embedUR systems

Embedded Software Engineer

Engineering · more than a year ago

Entry Easy Negative experience No offer 4 rounds
Interview process
Technical screen Technical screen Technical screen Group
Interview formats
Technical Presentation Technical Group

So, there's this company recruiting, offering 4.5 LPA for the first 6 months, then 5.5 LPA. There's a 2-year agreement, and raises only happen at the end of the second year. They are looking for candidates with above 7.5 CGPA from ECE, EEE, CSE, IT, and Mechatronics. The first round was a written test with 35 questions (6 on Theoretical Networking, 6 on Microprocessor, 16 on C Programming, and 3+2 on Apti and verbal) on an OMR sheet. They took the question paper back, and apparently, they use these 'dumb questions' every year. About 25% got through. The second round was an extempore where you pick your topic, and the interviewer just asked for the topic name, claiming they had enough experience to judge. Half were eliminated here. The third round was a face-to-face technical interview. They asked about C vs C++, mutex vs semaphore, who developed C, C++, and Java, C storage classes, and Linux commands. The interviewer didn't even look at the resume; only CGPA mattered. The final round was a group interview where they asked about malloc, calloc, realloc, and AVL trees, though the interviewer seemed clueless about AVL trees. I was rejected in the third round and was happy about it.

Confirmed questions4 questions
  • Can you explain malloc, calloc, and realloc?
  • Who were the developers of C, C++, and Java?
  • What is the difference between a mutex and a semaphore?
embedUR systems logo
embedUR systems

Embedded Software Engineer

Engineering

Entry Easy Positive experience No offer 6 rounds
Interview process
Technical screen Group Technical screen Technical screen Technical screen Onsite
Interview formats
Technical Group Technical Technical Technical Technical Behavioral

So, the first step was an aptitude test with numeric, technical, and basic C/C++ questions, worth 35 marks and pretty straightforward. After that, we had a group discussion (GD), but honestly, it felt like a formality because people were only moving to the next stage based on their aptitude scores. Then came two technical interviews that were super fast-paced, almost like rapid-fire. Most questions were easy, though a couple were a bit tricky. The final stage was an in-person interview at the EmbedUR office, combining technical and HR questions. Out of the 5 students who made it to the final round, I was one of them, but sadly, I didn't get selected in the end. Overall, it was a decent experience, though.

Confirmed questions5 questions
  • Can you explain the basics of MPMC?
  • Questions on Digital Electronics fundamentals
  • Fundamentals of EDC-PE
embedUR systems logo
embedUR systems

Embedded Software Engineer

Engineering

Entry Average Positive experience No offer 2 rounds
Interview process
Recruiter call Technical screen Phone screen
Interview formats
Technical Coding Behavioral

I applied through an academy and the interview process took only 2 hours. After that, they mentioned they had a long list of candidates to interview and would let me know my standing. If selected, there would be one more round to meet the manager. I declined!

Confirmed questions6 questions
  • Can you answer some basic C questions?
  • Please write a C program.
  • What does GCC stand for?

embedUR systems Embedded Engineer Interview Questions

Quoted word for word from embedUR systems interview reports.

Formats, difficulty and experience

Across all 10 embedUR systems interview reports.

Interview formats

Technical 62.1%
Group 13.8%
Behavioral 13.8%
Coding 6.9%
Presentation 3.4%

Interview difficulty

Easy 30%
Average 70%
Difficult 0%

Candidate experience

Positive 60%
Neutral 30%
Negative 10%