
EFI Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 151 interview experiences · FREE TO READ
Which role are you interviewing for?
30 roles · 151 reportsCandidate interview experiences
First-hand accounts from people who interviewed at EFI.
Field Service Engineer
I had a great experience interviewing at EFI USA. The process was fast and organized, from the initial contact to the final offer. The interviewer was genuinely kind, professional, and made me feel at ease right away. I never felt like I was being interrogated; it was more of a conversation. Overall, a very positive experience.
- Can you walk me through your experience and background?
QA Automation Engineer
The interview process was pretty bad, and I really didn't like how the rejection happened at the hiring manager level. After two technical rounds with a week in between, they just said the candidate wasn't expert enough. Honestly, the questions they asked weren't even that challenging for the experience level, like anyone with basic knowledge could answer them. I'm not sure what level of expertise they were looking for. The hiring manager round was even worse, trying to bring down the candidate's confidence. Instead of trying to find the absolute best, they should just reject candidates at the technical stage so people don't get their hopes up and can move on to other companies instead of wasting time.
- Basic oops concepts
- Write a few programs
Quality Control Manager
Started with a recruiter screen, then a video call with the department head. Next was a 2.5-hour in-person interview with 5 team members, preceded by a 1-hour video call with a team member. The process concluded with a video call with the HR VP. I was informed I'd be contacted about a decision. Despite investing 4 hours and interacting with 8 people, there was no follow-up, and the position was filled.
- How do you handle conflict?
Principal Engineer
The interview process began with a recruiter call, followed by scheduling an in-person interview. The in-person interview wasn't strictly necessary and could have been virtual. The interviewer seemed knowledgeable but unprepared, under the impression that I had already completed a phone or virtual interview round. He was surprised to learn this was my first interview with EFI. It started with basic C++ questions, then moved into understanding background processes, which I attempted to explain. His questioning style was also suboptimal, often posing questions in a 'is it like this or that' manner. Overall, it was a very unpleasant interview experience; I felt like quitting midway. It lasted over an hour and fifteen minutes, after which I was told to leave.
- Could you explain the difference between a copy constructor and an overloaded assignment operator?
- What is the difference between malloc and new?
- Tell me about some synchronization questions.
EFI Interview Questions
Quoted word for word from EFI interview reports.
“Write a C function to get the size of a structure without using the sizeof() operator.”
Read reports →“For a given sentence, can you sort the letters within each word alphabetically?”
Read reports →“How do you find duplicate elements in an array in the most efficient way?”
Read reports →“What is the difference between a process and a thread?”
Read reports →“Can you write a C++ program to find the factorial of a number?”
Read report →“Could you explain the difference between a copy constructor and an overloaded assignment operator?”
Read report →“How do you extract a value from a cell in a web table?”
Read report →“Can you explain how to print a number in words?”
Read report →“Can you describe how to search for a word within a large file?”
Read report →Formats, difficulty and experience
Across all 151 EFI interview reports.