Deutsche Telekom Software Engineer Interview Experiences 2026
Real, anonymous reports from people who interviewed for Software Engineer at Deutsche Telekom, newest first and distilled into what to expect across the loop.
Get your personalized Deutsche Telekom Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
My first round was short and almost breezy. It lasted about 30 minutes and started with me introducing myself, then they walked me through what work they did there and what equipment they used. The only technical thing that really stood out was how they asked about my experience with lab equipment. Overall, it felt straightforward and not stressful, more like an early fit check than a deep technical assessment.
A different time, the format felt like an in-person, three-round flow. I went through multiple sessions where the second round leaned heavily technical, and the final round shifted toward a more managerial conversation. I ended up being asked about linked lists and a mix of topics spanning databases and backend building blocks—things like MySQL, reverse proxy, trees, BST, and also MongoDB and Redis. Even though it was more covered than that first short call, the experience still felt approachable because the questions were clearly structured into rounds.
3 months ago
Average Negative Košice
One hiring path I experienced felt professional during the actual conversation, but the process soured right after. After speaking with a team under the broader Deutsche Telekom group, I got post-interview feedback that didn’t match what I had already discussed. The feedback pointed to ServiceNow and “large organization” experience as reasons not to move forward, even though ServiceNow never came up during the job discussion and I had already said I’d used it before. I also mentioned prior work at a big multinational tech company, so the rationale didn’t feel aligned.
What made it frustrating wasn’t only the rejection—it was the sense that the feedback was vague or inaccurate. It left me unsure whether the real issue was technical fit, culture fit, or something else entirely. In a separate application, the bitterness came from communication itself: my application just stayed stuck in an “in process” state for a full month with no meaningful updates, even after follow-ups. That kind of silence was hard to reconcile with how large and reputable the company seemed.
4 months ago
Easy Negative India
I had one experience that started with good momentum but quickly turned into nothing. I was directly reached out to by someone in recruiting who said …
10 months ago
Average Positive India
The process I went through felt balanced—neither too easy nor overly punishing—and it moved quickly. One experience lasted about a month end to end, b…
11 months ago
Average Positive Hungary
After a recruiter prescreen, my process turned into two interviews that felt like a step up. The recruiter call was mainly about general fit and align…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Interview Structure & Rounds
The interview process typically consists of multiple rounds, often starting with an HR conversation, followed by technical interviews that may include coding challenges and project discussions. Candidates can expect a mix of foundational topics and deeper dives into their past work, generally structured to assess both technical skills and cultural fit.
HR roundTechnical interviewsProject discussion
Technical Focus & Topics
Candidates should prepare for a strong emphasis on core technical concepts, including data structures, algorithms, and specific programming languages like Java and C#. Expect questions that assess both theoretical knowledge and practical application, often with follow-ups to clarify understanding.
Data structuresJavaAlgorithms
Communication & Feedback
While some candidates experienced clear and timely communication throughout the process, others reported significant delays and vague feedback post-interview, which can lead to frustration and uncertainty about their performance. It's advisable to seek clarity on expectations and follow up if communication lapses occur.
CommunicationFeedbackFollow-up
Candidate Experience & Atmosphere
The overall atmosphere during interviews is generally described as professional and supportive, though some candidates encountered negative experiences with interviewers who appeared disengaged or overly strict. Candidates should be prepared for varying dynamics and maintain a positive approach regardless of the interview tone.
Candidates noted that the scheduling and logistics of the interview process were often well-organized, with clear communication regarding interview times and follow-ups. This aspect can significantly enhance the overall experience, making it feel more manageable and respectful of candidates' time.
SchedulingLogisticsOrganization
Outcome & Reflection
Candidates reported mixed outcomes, with some not receiving offers despite feeling the interviews were fair and structured. Reflecting on the experience, many emphasized the importance of preparation and understanding the company's culture, as well as the need for clear communication throughout the process.