Mission: Our mission is to simplify cloud computing so developers and their teams can spend more time building software that changes the world.
We’re always thinking of ways to make developers’ lives easier, including an intuitive interface and ...
I have been working at DigitalOcean full-time (Less than a year)
Clear career path, very open source friendly, great values, learning every day, the challenges are exciting
It's cold in NYC during winter, the HQ could have been somewhere warmer :D
Advice to Management
You are doing a great job ! The communication channel is clear, we receive a lot of information regarding what is going on, where we are going. It's perfect !
I applied online. The process took 4 weeks. I interviewed at DigitalOcean in April-2016.
I applied for one of DO's Software Engineer positions through their website earlier this year. HR got in touch with me a few days later. The preliminary HR screening was easy and friendly with a few "Tell me a bit about yourself", "Why are you considering DO?" questions. After that they sent me a coding exercise to work on.
The exercise itself isn't too difficult. I spent about two hours every evening on it, and got it completed within a week. I was very hopeful about it since I felt like my code satisfied all the given constrains, passed their test harness, demonstrated advance understanding of the Go programming language, provided good test coverage, and included the bonus features. The review process took a lot longer than expected. I did two follow-ups with HR after the second and third-and-half week marks. Another week passed after my last follow-up email (with no responses), then I was notified that they wouldn't move forward with me because although my code was good with good test coverage, the reviewers felt that I didn't show enough OO design and utilization of custom types. I was a bit disappointed for that being the only reason for the rejection of my application. While OO is a part of Go, it's not the only part. I demonstrated good understanding of key concepts like channels, wait group, signal handling, race detection, function closures, interfaces, composition and mocks (OO anyone?) in my code. From my experience with Go, unlike Java or Ruby, not everything needs to be a struct or a custom type. The builtin types of string, int, slices, map, channel and functions are usually sufficient for most coding, to avoid over-engineered code.
We are excited and proud to announce our new CEO, Mark Templeton. Read more about the next wave at DigitalOcean from Ben Uretsky:
Currents is back! ☁️ Get the latest insights on containers, serverless, workplace preparedness, and more from the developer community
Let us know if we're missing any workplace or industry recognition –