Worldline logo

Worldline C++ Developer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 5 interview experiences · FREE TO READ

3.2 Rounds average
Average Typical difficulty
60% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Worldline.

Showing 3 of 5
Worldline logo
Worldline

C++ Developer

Engineering · a year ago

Mid Easy Positive experience Accept offer 2 rounds
Interview process
Technical screen Technical screen
Interview formats
Technical

Had two interview rounds, both technical, with the team lead and manager. They asked simple questions on C++, OOP, SQL, DBMS, and Linux. It was an easy process overall. The difficulty can change based on the project.

Confirmed questions1 question
  • Questions related to DBMS were asked.
Worldline logo
Worldline

C++ Developer

Engineering · a year ago

Mid Average Negative experience No offer 3 rounds
Interview process
Technical screen Technical screen Technical screen Recruiter call
Interview formats
Technical Technical Technical Behavioral

It was a complete waste of time. They conducted three interview rounds, all of which I passed. The only thing left was an HR discussion. After the discussion, the HR asked me to wait for 2-3 days, and then they just ghosted me.

Confirmed questions1 question
  • Find the maximum number of occurrences.
Worldline logo
Worldline

C++ Developer

Engineering · more than a year ago

Entry Difficult Negative experience No offer 3 rounds
Interview process
Recruiter call Technical screen Onsite Offer
Interview formats
Behavioral Technical Coding

My experience with the company was quite negative. The interview process was pretty standard: first a phone call, then two Skype interviews (one with team leaders from different parts of Europe, and another one which was the C++ test), followed by an in-person interview. To be direct, I was outright lied to. When I arrived at their offices, I was told it would be a formality, just to see me in person to give me an offer. Then, once I got to the office, I was almost insulted. The HR guy basically told me the C++ test went poorly and doubted if my Bachelor's thesis was actually done in C++. He also expressed concern about my 'compromise with the company' simply because I'm pursuing a part-time Masters, which I had already explained I was committed to both my current job and studies. I ended up doing another C++ test on-site, supposedly 'to see if this one would go better,' which was different. They presented a project they were working on, but it wouldn't compile when running a unitary test. I was supposed to find the error. Naturally, I couldn't find it, as it's unreasonable to expect someone to find an error in a large C++ project within 2 minutes, especially for an entry-level position. This seemed pretty weak. Afterward, I asked the HR guy about the test results to know if I was proceeding. He mentioned he was trying to manage that alongside the current stage and that a colleague would call soon to discuss contract matters. I interpreted this as them playing games, likely because they had another candidate and were keeping me as a backup. This is just my theory, but given the bad vibes, I decided to withdraw my application.

Confirmed questions2 questions
  • What are your career aspirations for the next 5 years?
  • Could you create a C++ class for basic operations, including its constructor and destructor?

Worldline C++ Developer Interview Questions

Quoted word for word from Worldline interview reports.

Could you create a C++ class for basic operations, including its constructor and destructor?

Read reports

Can you explain OOPs concepts in C++ and provide an example?

Read report

What are your career aspirations for the next 5 years?

Read report

What are your experiences with Github, Docker, System Design, and SQL?

Read report

Formats, difficulty and experience

Across all 5 Worldline interview reports.

Interview formats

Technical 58.3%
Behavioral 25%
Coding 16.7%

Interview difficulty

Easy 20%
Average 60%
Difficult 20%

Candidate experience

Positive 60%
Negative 40%