Travailler chez DigitalOcean |

Présentation de DigitalOcean

New York, NY (États-Unis)
Entre 201 et 500 employés
Entreprise non cotée en bourse
Services informatiques
Entre 100 et 500 millions $ (CAD) par an

Avis sur DigitalOcean

Tendances des évaluationsTendances des évaluations
Approuvent le PDG
(aucune image)
Mark Templeton
8 Évaluations
  • Utile (1)

    « Awesome remote culture and people »

    • Équilibre travail/vie privée
    • Culture et valeurs
    • Opportunités de carrière
    • Rémunération et avantages
    • Dirigeants
    Employé actuel - Senior Software Engineer
    Employé actuel - Senior Software Engineer
    Point de vue positif
    Approuve le PDG

    Je travaille chez DigitalOcean à plein temps (Moins d'un an)


    * Amazing remote culture and laser-sharp focus on making that work
    * Highly-skilled group of people who take their jobs seriously
    * Really interesting at-scale problems to solve across the entire tech stack
    * Current management is very open and honest about the challenges, no visible "head in sand" moments so far
    * I like a company that knows at which inflection points in growth changes in management are required. From what I can see, DO has no problem making those calls


    * Rapid growth (both in head count and in product offering) have created a degree of instability and disorganization, particularly at the process level
    * The tech stack is very much in flux at the moment, with layers of legacy, experimentation, and modern sitting atop (and within) one-another; it's chaotic
    * I struggle to think of anything else worthwhile that would warrant memorializing in perpetuity. So far it's been a pretty great place to work

    Conseils à la direction

    Management sets the tone for the company, and Mark's optimistic yet open approach to communication has been fantastic to experience. Keep doing that at all levels, even when it's painful, embarrassing, frustrating or infuriating. Honesty is respect.

    Keep listening to the folks in the trenches. So far it seems that everyone wants to build the best bug-free, performant thing they can for the customers. PRSS is a great initiative, showing the team that their pains are both as important as, and synonymous with, the customer's pains. It only really works when both sides of the equation are satisfied.

Voir les 71 avis

Entretiens chez DigitalOcean



Obtenir un entretien

Obtenir un entretien




  1. Utile (1)  

    Entretien de Software Engineer

    Candidat à l'entretien anonyme
    Pas d’offre d’emploi
    Expérience neutre
    Difficulté moyenne


    J'ai postulé en ligne. Le processus a pris 4 semaines. J'ai passé une entrevue à DigitalOcean en avril 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.

    Questions d'entretien d'embauche

    • Coding assignment to write an application to demonstrate understanding of network protocols and data structure, with the following constrains:
      1. Any programming language of my choice; preferably Go or Ruby. I picked Go.
      2. My code must pass the provided integration test harness.
      3. Restricted to standard libraries of the chosen programming language. IOW, no 3rd party frameworks or helper libraries.
      4. Bonus features: Include a Dockerfile. Document design rationale.   1 réponse
Voir les 131 entretiens d'embauche

Prix et distinctions de DigitalOcean

Faites-nous savoir s'il nous manque toute reconnaissance du milieu de travail ou de l'industrie – Ajouter des prix

Vous travaillez chez DigitalOcean ? Partagez vos expériences

  • Star
  • Star
  • Star
  • Star
  • Star
Cliquez pour noter