
Qt Group Software 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
Candidate interview experiences
First-hand accounts from people who interviewed at Qt Group.
Software Engineer
It started with a 30-minute technical interview that had around 30 short questions. Because the job was about graphics programming, half were C++ and the others were general and Qt graphics related. Then, I had to do a test project, I could pick one of two options, both were about Qt graphics API and shaders. If I passed that, there were more interviews, technical and non-technical.
- Regarding C++ class hierarchies, in what order are constructors executed?
Senior Software Developer
I applied online and filled out the application form, which had basic info and a salary expectations question. After a month, HR emailed me. There were 3 stages: 1) HR screening with questions about me, my experience, current role, and salary expectations again. A few days later, I got invited to a technical interview. 2) The technical interview was a simple LeetCode task I solved in 10-15 min with the best complexity and answered a few C++ questions based on my code. It was scheduled for an hour, but I finished in 30 min. The interviewers seemed friendly. I got positive feedback and an invitation to the 'on-site' interview. The 'on-site' interview was 4-5 hours at the Qt office in Adlershof, with 4-5 parts: 1) Another technical coding interview (fixing bugs in a Qt framework app, 1 hour). 2) Another technical theoretical interview. 3) Lunch with the team. 4) Behavioral interview with HR and my manager. 5) A short presentation on a technical topic or my experience (optional, I skipped it). I fixed the Qt app, passed the theoretical part, but during the behavioral interview, they asked about my salary expectations again and if I was ready to negotiate. This was strange since I'd already passed all technical parts and my salary expectations were known from the application.
- What's the complexity of std::vector push_back?
- Explain the Linux process structure and the elf file format.
- Describe static and shared libs.
Software Engineer
The communication was polite and responses were quick. The interview itself was also fast-paced. It felt more like a school exam than a professional interview, making it hard to gauge how it relates to actual work. A downside was the mismatch between the job description and what was actually tested; they focused on unmentioned skills and ignored those listed as important. Ultimately, they proceeded with candidates who lacked the stated requirements but possessed the emphasized skills. The whole experience felt like a waste of time, and they should be clearer about their actual needs. On the plus side, it was definitely a speedy process.
- Questions covering basic programming knowledge, and some nit-picky ones.
- Questions that were to the point, and others asking for definitions of umbrella terms or obscure knowledge.
- Questions that are more typical of academic studies than daily work.
Qt Group Software Engineer Interview Questions
Quoted word for word from Qt Group interview reports.
“What's the complexity of std::vector push_back?”
Read reports →“Given a string, how would you reverse it in C?”
Read reports →“Regarding C++ class hierarchies, in what order are constructors executed?”
Read reports →“Can you reverse a linked list?”
Read reports →“What is the Q_OBJECT macro and what is its role in using QT features like signals-slots, qobject_cast, MetaObjects, and Parent Child representation? Explain how it interacts with the MOC compiler.”
Read report →“Describe static and shared libs.”
Read report →“Do methods within a class consume memory?”
Read report →“Explain the Linux process structure and the elf file format.”
Read report →“What about Qt frameworks?”
Read report →Formats, difficulty and experience
Across all 15 Qt Group interview reports.