Passa al contenutoPassa al piè di pagina
  • Lavori
  • Aziende
  • Stipendi
  • Per le aziende

      Migliora la tua carriera

      Scopri le tue potenzialità di guadagno, trova lavori da sogno e condividi approfondimenti su lavoro e vita privata in forma anonima.

      employer cover photo
      employer logo
      employer logo

      GitHub

      Questa è la tua azienda?

      Circa
      Recensioni
      Stipendi e benefit
      Lavori
      Colloqui
      Colloqui
      Ricerche correlate: Recensioni su GitHub | Offerte di lavoro di GitHub | Stipendi di GitHub | Benefit di GitHub
      Colloqui di GitHubColloqui per Technical Support presso GitHubColloquio di GitHub


      Glassdoor

      • Chi siamo
      • Contattaci

      Aziende

      • Account Business gratuito
      • Spazio per le aziende
      • Blog per le aziende

      Informazioni

      • Aiuto
      • Linee guida
      • Condizioni d'uso
      • Privacy e scelte pubblicitarie
      • Non vendere né condividere le mie informazioni
      • Strumento per l'accettazione dei cookie

      Lavora con noi

      • Inserzionisti
      • Carriere
      Scarica l'app

      • Cerca:
      • Aziende
      • Lavori
      • Località

      Copyright © 2008-2026. Glassdoor LLC. "Glassdoor," "Worklife Pro," "Bowls" e il relativo logo sono marchi registrati di Glassdoor LLC.

      Aziende seguite

      Non lasciarti sfuggire opportunità e informazioni privilegiate seguendo le aziende dove vorresti lavorare.

      Ricerche di lavoro

      Ricevi suggerimenti e aggiornamenti personalizzati avviando le tue ricerche.

      Colloquio per Technical Support

      25 lug 2015
      Candidato anonimo a colloquio
      San Francisco, CA
      Nessuna offerta
      Esperienza positiva
      Colloquio nella media

      Candidatura

      Ho presentato la mia candidatura online. La procedura ha richiesto una settimana. Ho sostenuto un colloquio presso GitHub (San Francisco, CA) nel mese di giu 2015

      Colloquio

      The pre-interview questions were basic "tell us about yourself" and "why do you want to work for Github". The actual interview involved answering a series of five demo support tickets. These tickets ranged from basic troubleshooting to more complex scenarios involving explaining policies to users. The questions should feel natural to anyone who has experience working in support for a similar software company. Interview was done online.

      Domande di colloquio [1]

      Domanda 1

      Hello support! My business has an internal Git server used for deployments. We have an internal Git server and we also use GitHub. For workflow purposes, how do I sync my repository to GitHub and and the internal Git server?
      Rispondi alla domanda
      34

      Altre recensioni di colloqui per Technical Support presso GitHub

      Colloquio per Technical Support

      23 ott 2018
      Candidato anonimo a colloquio
      Remote, OR
      Nessuna offerta
      Esperienza negativa
      Colloquio facile

      Candidatura

      Ho presentato la mia candidatura online. Ho sostenuto un colloquio presso GitHub (Remote, OR) nel mese di ott 2018

      Colloquio

      First and only time I ever hope to post on Glassdoor. I have been left mortified from this experience, not from not getting the job, but just how bad my experience was with the company’s “talent acquisition” member. The first Zoom call video started late and actually wasn’t a video call after all as she called via her mobile on the move. Apart from “tell me about yourself”, there wasn’t one more single question asked at their end in the whole interview. I put a lot of time into my personalised cover letter which was very clear that it was not read at their end. I ended up asking some questions to try and form a connection, since the “talent acquisition” member couldn’t really answer these basic company questions, that move didn’t really work very well. After her spiel about how amazing their support team is etc etc she said she would move me onto the next steps. I genuinely felt like the care factor was zero, when she mentioned they used ZenDesk, I tried to explain in a non-arrogant way that I had closed over 10,000 tickets on ZD with a near perfect satisfaction level. And also that I had won global awards for sales and support with my current company, I honestly felt like my comment went down like a fat kid on a light sea-saw. Overall she spoke 90% of the time, asked one question and genuinely didn’t care and wanted to hang up the Zoom call. The next step was to reply some questions via email, I’m not sure why you didn’t just ask those on the first call whilst we were talking? And to also reply to three support questions, this is where I must have gone wrong. I checked for spelling, structure and grammar twice so I didn’t think I went too wrong there, so it must have been down to the technicalities in my responses. In my experience in hiring for techical support, this isn’t looked at that hard early days in the interview process, unless you are really off the mark. I must admit it was really late (as I wanted to get this back quickly) and I wasn’t in the mood to learn GitHub too extensively at this point in time so I just thought I would get the responses in as quickly as I was able and I would concentrate on making the other areas of the response good (non-technical side). With my current company I checked over 20 ZD responses from the GitHub support team with my developers I am friendly with and I thought I was at least on par with the structure, style and tone that they replied with. The GitHub answers were generally very short and I couldn’t see any customer success tactics to write home about in any of the 20 replies I went through, the developers commented that their support was just standard in their experience so I wasn’t petrified about getting a few things wrong. I submitted my responses back to them. What happens next is what really got me down. A week later (which is pretty quick) I got an automated email reply, probably generated from TextExpander saying that you are not moving forward. Mainly because of your crap support responses that you sent us. Drummed down in a corporate equivalent to that last sentence, which was even more offensive to me. If I just spoke to a robot at the start I would have been so much happier and better off. You are honestly making the cut at this point off these theee support responses? Mortified is a strong word, but for someone who believes so strongly in customer success with humans and knows what it takes, I have lost a little faith in humanity. I am posting this one and only Glassdoor human review in response to the robotic, arragont and care factor of zero I recieved from GitHub.

      Domande di colloquio [1]

      Domanda 1

      Tell me about yourself?
      1 risposta
      13

      Colloquio per Technical Support

      1 apr 2016
      Dipendente anonimo
      San Francisco, CA
      Offerta accettata
      Esperienza positiva
      Colloquio difficile

      Candidatura

      Ho presentato la mia candidatura online. La procedura ha richiesto 2 mesi. Ho sostenuto un colloquio presso GitHub (San Francisco, CA) nel mese di mar 2016

      Colloquio

      1. Online application. I also sent a follow up message to the appropriate recruiter via LinkedIn. 2. Five mock support tickets and a few questions (e.g., tell me about a time you helped someone) to answer via email. 3. Video interview w/ my now manager. 4. Pairing w/ a current technical support specialist, where we answered another five tickets together (well, mostly I did, with his help when needed). 5. Full day interview: 5 hours, 11 people total, including one more pairing (only three tickets this time). This is done on site in San Francisco or remote via video call, depending on how you plan to work. Each session had a topic (e.g., working remotely, troubleshooting, diversity). It took about a week to hear back from them between each step in the process. In the end, it was exactly 2 months from the day I submitted my online application to the day I received my offer via phone call. I was surprised that there were only a few behavioral interview questions ("tell me about a time when...") throughout the process. Also, I was certain I bombed the first pairing but they definitely seem much more interested in seeing your process than that you actually get to the right answer. I was told that all their recent hires have had beginner level knowledge of Git.

      Domande di colloquio [1]

      Domanda 1

      What would you do if you urgently needed information from someone working in a drastically different timezone (who was almost certainly asleep)? (They asked me this a few different times in slightly different ways.)
      1 risposta
      35

      Le migliori aziende per "stipendio e benefit" vicino a te

      avatar
      Amazon
      3.7★Stipendio e benefit
      avatar
      Google
      4.5★Stipendio e benefit
      avatar
      HENNGE
      3.8★Stipendio e benefit
      avatar
      xneelo
      3.8★Stipendio e benefit