Travailler chez |

Présentation de

Paris (France)
De 51 à 200 employés
Entreprise non cotée en bourse
Solutions logicielles et réseau d'entreprise
Ne sait pas / non applicable

Red Hat, Salesforce, Acquia is an idea-to-cloud application platform that simplifies cloud infrastructures.

We give developers the tools they need to experiment, innovate, get rapid feedback and deliver better-quality features with speed and confidence thanks to our unique ... En savoir plus

Mission: We believe developers should concern themselves with features and code quality, not servers and tooling and that Cloud infrastructures can be simplified.

Our mission is to help you move fast without breaking things.

All software deserve ... En savoir plus

Avis des employés

  • « Entreprise exceptionnelle »

    • Équilibre travail/vie privée
    • Culture et valeurs
    • Opportunités de carrière
    • Rémunération et avantages
    • Dirigeants
    Ancien employé - Employé anonyme - Grenoble (France)
    Ancien employé - Employé anonyme - Grenoble (France)
    Point de vue positif
    Approuve le PDG

    J'ai travaillé chez à temps plein (Plus d'un an)


    En 10 ans de carrière il s'agit de l'entreprise la plus humaine pour laquelle j'ai travaillé. Les dirigeants sont éclairés et compréhensifs, le full télétravail pour tous les employés fonctionne très bien, et l'on y côtoie des gens intelligents et originaux. La rémunération est aussi très bonne.


    L'obligation de partager une chambre avec un collègue lors des réunions d'équipe.

    Conseils à la direction

    Continuer comme ça !

Voir les 21 avis

Entretiens chez



Obtenir un entretien

Obtenir un entretien




  1. Utile (3)  

    Entretien de DevOps/SRE

    Candidat à l'entretien anonyme - Toronto, ON
    Aucune offre d'embauche
    Expérience négative
    Difficulté moyenne


    J'ai postulé en ligne. Le processus a pris +4 semaines. J'ai passé un entretien à (Toronto, ON) en septembre 2018.


    The process started out great. I enjoyed the discussion with the recruiter and it was helpful.

    That was followed by the technical screen which was, IMO, amateurish. As described by someone else, it was a multiple choice python quiz. Be careful to press the right button, as the [BIG RED BUTTON] is equivalent to "I don't know". (I hit the wrong button several times by mistake.)

    I was actually surprised when I learned that I was going to the next steps as Python isn't my strongest language and I thought I'd flunked it for sure.

    The next interview with a team member was technical, uneventful and went well.

    The third interview was to be with a technical leader. We had a difficult time communicating over the link to unfortunately. The audio was terrible, video was impossible. I finally called in via telephone and we made arrangements to meet another time. (I later found with traceroute that a router upstream was dropping a significant number of packets.)

    About ten minutes into the time scheduled for our next meeting, I sent an email asking where he was and received an email from them saying "I had an emergency and I am not able to attend our talk. I'll will contact you shortly."

    I did NOT hear from them "shortly". I sent several emails over several days, finally CC'ing the recruiter. The recruiter apologized and set up the next appointment for about a week later.

    The time for the next appointment came and went with nobody showing up. No email this time explaining why. I sent off an email after about 15 minutes of waiting (roughly 3:15pm their time in Paris). The recruiter sent me an email the next day; apparently another "emergency" happened and the interviewer couldn't make it (or even communicate that fact). The recruiter apologized saying "We will put on hold our recruitment process as we need to improve our process here."


    I did hear back from the interviewer with an apology several days later (interview on Tuesday, apology on Friday), but then suggesting that it was my fault. "..your internet connection was horrible and we weren't really able to communicate."

    I think the failure to communicate originated at their end.. I can certainly understand "emergencies", but not their failure to communicate -- and then to try to blame it on me? Come on..

    It's a shame. It looks like an interesting company otherwise, but communication is an important part of a remote first company and it appears that they don't understand that..

    Questions d'entretien d'embauche

Voir les 20 entretiens d'embauche

Actualités de l'entreprise

  • is number 26 of the best small places to work in Austin, Texas in 2019!

  • 87% of France based Platformers say this is a great place to work!

Tout afficherTout afficher

Prix et distinctions de

  • Best Horizontal Cloud Solution in Europe, Eurocloud, 2015
  • Pass French Tech, BPI, 2018
Voir plus

Vous travaillez chez ? Partagez vos expériences
  • Star
  • Star
  • Star
  • Star
  • Star
Cliquez pour noter