D
Deutsche TelekomSoftware Engineer
Updated May 26, 2026

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.
Build my free plan
Hot & recentNewest first
5 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.
6 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 they were interested in my profile for a frontend role. I responded promptly and was excited to move forward, but after that initial outreach there was complete silence. I kept following up for about two weeks, and there was no acknowledgement—nothing even as basic as a status update—just silence.

That same theme of poor communication showed up elsewhere for me too: I felt the HR side didn’t answer my questions and never got back to me after the interview. The process felt like it wasted my time rather than being a serious, well-run funnel. By contrast, I also had a smoother HR-involved day where the first conversation with HR felt relaxed and standard—questions about my background, education, and what was on my CV. The second round then moved into team leads and technical questions tied to past projects and the technologies involved, and at least that portion felt coherent and respectful.

Unlock every Software Engineer interview experience

Real Software Engineer interview experiences
  • Difficulty, sentiment and outcomes
  • New reports added every week
See all experiences
Share your 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.

ProfessionalismSupportive environmentInterview dynamics

Logistics & Scheduling

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.

OutcomeReflectionPreparation