Deutsche Bahn logo

Deutsche Bahn Software Engineer Interview Questions
& Process

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

Based on 7 interview experiences · FREE TO READ

1.9 Rounds average
Average Typical difficulty
57.1% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Deutsche Bahn.

Showing 3 of 7
Deutsche Bahn logo
Deutsche Bahn

Software Engineer

Engineering · more than a year ago

Entry Average Positive experience No offer 3 rounds
Interview process
Recruiter call Technical screen Presentation
Interview formats
Behavioral Technical Presentation

It was a relaxed vibe. Everyone introduced themselves first. Then there were technical questions, and finally, I had to present a project from my studies. Fair follow-up questions were asked, and they also gave an outlook on the next steps if successful.

Confirmed questions1 question
  • Tell me about your biggest success so far, whether personal or professional.
Deutsche Bahn logo
Deutsche Bahn

Software Engineer

Engineering · more than a year ago

Entry Average Neutral experience Decline offer 1 round
Interview process
Recruiter call Onsite
Interview formats
Behavioral Technical Presentation

After applying through the online system, I received a call inviting me for an in-person interview. During the call, I could ask initial questions about the Bundesbank and we discussed general topics like the salary range. The whole process from application to interview took about 3 weeks. The interview panel included HR, the disability representative, my potential boss, and others from the department. The conversation was professional yet friendly. Besides questions about my background and motivation, there were also in-depth questions about my technical knowledge. Additionally, I had to develop and explain a solution strategy for a hypothetical scenario, which involved drawing diagrams on a whiteboard. They didn't ask typical brain teaser questions like measuring a plane without a ruler or why tennis balls have felt. Instead, the questions were directly relevant to the tasks I'd be doing in the job.

Confirmed questions3 questions
  • What do you identify as the primary risks in IT operations, and what attack scenarios are common in your view?
  • What are the available methods for protection against these threats?
  • How would you approach developing and presenting a solution for a hypothetical situation?
Deutsche Bahn logo
Deutsche Bahn

Software Developer

Engineering

Entry Average Negative experience No offer 3 rounds
Interview process
Recruiter call Take home Presentation
Interview formats
Behavioral Technical Presentation

The interview was conducted by a recruiter on short notice (3 days after applying), likely to check details not apparent from the resume, such as personal projects. Notes were passed to department heads for the next round decision. The next stage involves a task with a presentation, followed by another interview if successful.

Confirmed questions2 questions
  • What programming errors have you encountered in past projects and how did you resolve them?
  • Do you code in your free time?

Deutsche Bahn Software Engineer Interview Questions

Quoted word for word from Deutsche Bahn interview reports.

What are the available methods for protection against these threats?

Read reports

Can you explain methods for reducing bundle size in web development?

Read reports

What do you identify as the primary risks in IT operations, and what attack scenarios are common in your view?

Read reports

Which framework would you recommend for a given problem scenario x?

Read report

Tell me about development tasks in the field of electronics.

Read report

Which parts of our stack are you already familiar with?

Read report

How would you approach developing and presenting a solution for a hypothetical situation?

Read report

Formats, difficulty and experience

Across all 7 Deutsche Bahn interview reports.

Interview formats

Behavioral 40%
Technical 33.3%
Presentation 20%
Coding 6.7%

Interview difficulty

Easy 28.6%
Average 71.4%
Difficult 0%

Candidate experience

Positive 57.1%
Neutral 28.6%
Negative 14.3%