
embedUR systems Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 375 interview experiences · FREE TO READ
Which role are you interviewing for?
18 roles · 375 reportsCandidate interview experiences
First-hand accounts from people who interviewed at embedUR systems.
Software Development Engineer and Quality Engineer
My interview with EmbedUR had six stages. First up was an Aptitude Test with 45 questions in 45 minutes, covering logic, analysis, and general smarts. I got about 60% right, and it felt pretty moderate. Then came Technical Group Discussion 1 (Technical GD 1), where the panel threw out open-ended tech questions, and you raised your hand if you knew the answer. It was all about how much tech knowledge you had, if you were confident, and could explain things well. If you did good in that first tech chat, you moved on to Technical Group Discussion 2 (Technical GD 2). This one dug deeper into core computer science stuff, expecting a solid grasp of the basics. After that, there was a one-on-one Technical Interview. This chat was mostly about my resume, looking at my projects, tech skills, and what I learned in school. The last part was the HR Interview, checking my communication, personality, goals, and if I'd fit in.
- Could you explain what TCP and UDP are?
- Can you describe the three-way handshake process?
- What do you understand by page faults?
Fresher
It was a technical group discussion (GD). The HR conducted a stream-wise GD where they asked questions related to your specific engineering branch. Both your microphone and video were required to be on. Try to answer the questions with explanations.
- What are flip flops?
- What are losses in a transformer?
Software Developer
So the campus recruitment thing had four rounds. First was an online assessment with aptitude and logic questions to see how I solve problems. Then there were two technical group discussions, the first one was on core subjects and pretty easy, just to check basics. The second GD was similar but harder, from easy to medium, to see if I knew the subjects better. The last round was a face-to-face interview, covering both technical and HR stuff. They asked about my projects, my background, and general HR questions, plus some medium to hard technical questions to check my problem-solving and technical skills. It was a good process, got tougher as it went on, to check technical knowledge, analytical skills, and how I communicate.
- Could you walk me through one of your academic projects, detailing the problem it addressed, the tech stack you employed, and the results you obtained?
Network Engineer
It was more of like a Technical GD where they focused more on DSA questions like detecting a loop in a linked list (fast pointer & slow pointer) and OS questions like what is demand paging and segmentation.
- Can you explain Bubble sort and memory allocation in C?
- Do you know how to detect a loop in a linked list using the fast and slow pointer method?
- What is demand paging?
embedUR systems Interview Questions
Quoted word for word from embedUR systems interview reports.
“What is the difference between a latch and a flip flop?”
Read reports →“Which type of DC motor operates at a constant speed?”
Read reports →“Do you know the Linux command for checking disk size?”
Read reports →“Regarding a motor that runs at a constant speed, which motor is self-starting and why?”
Read reports →“What is the difference between a structure and a union?”
Read report →“What is the use of the ALE pin in an 8051 microcontroller?”
Read report →“Is pass by value or pass by reference more efficient?”
Read report →“Describe how to insert an element into the middle of a doubly linked list.”
Read report →“Can you explain what pinch off is and when it occurs?”
Read report →Formats, difficulty and experience
Across all 375 embedUR systems interview reports.