Dynatrace logo

Dynatrace Software Engineer Interview Questions
& Process

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

Based on 50 interview experiences · FREE TO READ

2.5 Rounds average
Average Typical difficulty
68% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Dynatrace.

Showing 3 of 50
Dynatrace logo
Dynatrace

Software Engineer Intern

Engineering · nearly a year ago

Intern Average Positive experience Accept offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Technical Behavioral

The interview process was quite smooth and definitely manageable if you're comfortable with programming. Because of my GitHub profile, I didn't encounter a ton of technical questions. Instead, we mostly discussed what I've worked on, the rationale behind my decisions, and what I'm hoping to work on and learn going forward.

Confirmed questions1 question
  • What are your reasons for choosing or not choosing React?
Dynatrace logo
Dynatrace

Software Engineer

Engineering · nearly a year ago

Senior Average Negative experience No offer 4 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite Background check Offer
Interview formats
Behavioral Technical Coding

So I went through the whole thing, recruiter and hiring manager both said it was fully remote, then got dinged at the end cause of my location even though they said I did great. Took about a month. Started with a quick recruiter chat, then a 1-hour chat with the hiring manager and the team's lead engineer, which had some easy tech questions. After that, a 2-hour technical session with two engineers, including live coding and some Q&A, which actually finished early. I thought that was it, but they wanted me to meet a director in Gdansk for an hour. That meeting was short, like 20-30 mins, mostly about how often I could come to the Gdansk office. I was like maybe every 3 months, and they agreed to that, and I said I'd come for company events too. But then, despite them saying it was remote and the team being in different offices, I got a rejection call saying location was the issue.

Confirmed questions1 question
  • Can you explain what a DaemonSet is and also what a StatefulSet is?
Dynatrace logo
Dynatrace

Software Engineer

Engineering · a year ago

Mid Average Positive experience No offer 3 rounds
Interview process
Recruiter call Phone screen Onsite
Interview formats
Technical Behavioral

It's a three-round process. First, there's a short phone call that's just a preliminary screening to see if you're interested and qualified. Then, a personal interview, which was online for me and lasted two hours. Finally, a technical round with team members where we also discussed experiences and debugged code on paper.

Confirmed questions2 questions
  • Subject-specific questions (C++, Linux)
  • How did you handle difficulties?

Dynatrace Software Engineer Interview Questions

Quoted word for word from Dynatrace interview reports.

How can you form the largest possible number from a given number by removing a single digit '5'?

Read reports

Could you tell me the byte length of an Integer across different languages?

Read reports

What are two factors that impact the performance of machine learning algorithms?

Read report

Can you explain Java's primitive data types and why they are beneficial?

Read report

Can you explain what a DaemonSet is and also what a StatefulSet is?

Read report

What's the point of object-oriented programming, and when might it not be the best approach?

Read report

Can you explain the distinction between threads and processes?

Read report

Formats, difficulty and experience

Across all 50 Dynatrace interview reports.

Interview formats

Technical 39.3%
Behavioral 30.8%
Coding 23.1%
Presentation 4.3%
Other 0.9%

Interview difficulty

Easy 14%
Average 66%
Difficult 20%

Candidate experience

Positive 68%
Neutral 10%
Negative 22%