Technical screening questions
Ask for one example per question and listen for specifics.
- How do you manage memory in modern C++? A good answer: RAII and smart pointers instead of raw new and delete.
- What is move semantics? A good answer: Transferring resources to avoid copies.
- How do you avoid data races? A good answer: Mutexes, atomics and ownership design.
- How do you find a memory leak? A good answer: Sanitizers or Valgrind.
- Which C++ standard do you use? A good answer: C++11, 14, 17 or 20 and specific features.
Quick screening questions
Use these when you have only a few minutes.
- Which C++ standard do you work in day to day?
- How do you prevent data races?
- Describe a memory or performance bug you tracked down.
What separates the levels
Match the level to the requirement before you submit.
- Junior: fixes bugs and implements small features.
- Mid: owns components.
- Senior: designs systems and performance strategy.
Red flags
Any of these is a reason to probe further.
- C-style code in a modern C++ role.
- Cannot explain RAII.
- No debugging tools experience.
Tools you should hear mentioned
A C++ developer with real experience usually names several of these without prompting.
- Modern C++
- STL and templates
- CMake
- GDB or debuggers
- Valgrind or sanitizers
- Boost
Run the call well
Ask for the last project first, then dig into the second or third question. Take notes on versions, team size and outcomes, and record them with the submission so the vendor’s later technical interview does not surprise you.
Frequently asked questions
How long should a C++ developer screening call take?
Fifteen to twenty minutes is enough to cover the project, three technical questions and availability, rate and work authorization.
Do recruiters need to know the technology?
Working vocabulary is enough. Use the sourcing guide for the role and listen for specifics instead of judging technical depth yourself.