Site Reliability Engineer Interview Experience - Germany
Process
It took pretty long for the first response to my application. I didn't expect an answer anymore.
- 30 min chat with the hiring manager
- 30 min chat with the team manager
After the first two chats, they decided to hand out a coding challenge that initially felt pretty simple to me, but there were some issues to tackle with scaling and performance. The challenge had to be solved within four hours during the following week.
They reviewed the challenge and scheduled two technical and one behavioral interview.
- Behavioral (Amazon style)
- General technical discussion
- Discussion about my challenge solution
There was no live coding session in LeetCode style.
I received a very satisfying offer that was contingent on a background check.
Questions
What would you do if the requests increase drastically? How would you scale the service? How would you know that you have to scale the service?
Was this helpful?
Interview Statistics
The following metrics were computed from 1 interview experience for the DigitalOcean Site Reliability Engineer role in Germany.
Success Rate
DigitalOcean's interview process for their Site Reliability Engineer roles in Germany is incredibly easy as the vast majority of engineers get an offer after going through it.
Experience Rating
Candidates reported having very negative feelings for DigitalOcean's Site Reliability Engineer interview process in Germany.
DigitalOcean Work Experiences
- 3.0123Jr. Software Engineer • Current EmployeeIstanbul, TurkeyApril 4, 2025Pros: The benefits include a good salary and flexible working hours.Cons: Hard work and work at the weekend.
- 3.0fire the rest of the c-suiteSenior Software Engineer I • Current EmployeeSeattle, WashingtonSeptember 17, 2023Pros: The work life balance is great and my team works really hard to protect that.Cons: This is a deeply technical company run by a C-suite that has zero product vision. We haven't built a substantially new product in years with our only new releases being through acquisitions or white-labeling other company's products. For example: before recently acquiring Paperspace for its GPU compute platform, we had multiple aborted attempts to build our own GPU product that were always abandoned as soon as the current crypto or AI hype cycle waned. And now that we have Paperspace, that's being run by our M&A division instead of product or engineering and there's no plan from leadership on how to integrate their wildly-incompatible tech stack. The C-suite is a bunch of clowns LARPing as successful tech execs as they drive this company into the ground. At least the board is finally starting to fire them though.
- 2.0Make DO great againSoftware Engineer • Current EmployeeHyderābād, IndiaSeptember 27, 2026Pros: They offer decent pay and benefits. The senior engineers are really good, and helpful.Cons: 1. There is a poor work-life balance because some Indian managers expect you to work on weekends without offering a comp-off, or they make false promises of one later. 2. The company seems to have grown allergic to remote work. It’s sad to see a company that grew to $1B by being remote-first move away from the very culture that helped make it successful.
