I applied for a C++ Software Developer position in May and successfully passed the interview process by the end of June. The process itself was pretty much generic: a technical phone interview, followed by three technical on-site interviews, and then, if you passed those steps, an HR interview. You can read about this process in many reviews online; the HR interview is fairly standard across companies. Therefore, I'd like to focus on the technical questions asked.

Please refer to the "Interview Questions" section for the first five. As Glassdoor does not allow more entries there, I will describe the subsequent questions below.

First On-Site Interview:

• Implement a thread-safe cache for objects that are expensive to copy. This cache should provide lookup, insert, and delete operations. Essentially, you need to combine std::unordered_map, std::mutex, and std::shared_ptr into a single class. std::shared_ptr ensures that threads do not hold pointers to deleted objects, while unordered_map and mutex are straightforward. I was also told that read-write locks or atomic variables could be used for synchronization, depending on usage patterns.

Second On-Site Interview:

• On-site 1: Two standard brain teasers were presented: boxes with wrong labels and searching for a coin that is heavier than others. These were easy.
• On-site 2: How to detect if a singly linked list has a loop. This is a standard slow/fast runner problem, described in every programming book.

Third On-Site Interview:

There were no direct questions. Instead, it was a conversation about profiling applications on UNIX systems to understand memory allocation patterns, space-time trade-offs, overriding malloc/free, and similar topics. I suspect this was intended to fill time while waiting for the HR person, so your experience may vary.

The day after, I had a video conference with New York, which was another friendly chat with no questions. I received an offer shortly after. Frankly speaking, I spent more time waiting for visa and background check results than preparing for and passing the interview itself.

I suggest using "Elements of Programming Interviews: The Insiders' Guide" for your preparation. It covers all the topics needed to answer their general coding questions. Good luck!

Phone interview 1: Remove duplicates from an unsorted singly linked list.

Phone interview 2: Tell whether there is anything wrong with the code you see.

Phone interview 3: Tell what's the output of the program you see.

First on site 1: A question about C++ templates.

First on site 2: A question about bitwise operations.