Process
After submitting the application, I was contacted a few weeks later by HR. We discussed the role and the team. HR set up a pair of video interviews: one with a technical member of the team and one with the hiring manager.
Due to some technical difficulties with the scheduling software integration, the interviews were held in reverse order, one week apart. The day after the second interview, I was notified by HR that they had elected to go forward with a different candidate.
I had been told that following the two video interviews, there would be a group interview if I were chosen for that round.
The people were nice, and the discussions were engaging and interesting.
Questions
After providing a general description of the type and nature of the traffic on the site, I was asked what approach I would take to balance the risks versus the cost.
Was this helpful?
Interview Statistics
The following metrics were computed from 1 interview experience for the GitHub Security Operations Engineer role in United States.
Success Rate
GitHub's interview process for their Security Operations Engineer roles in the United States is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having very good feelings for GitHub's Security Operations Engineer interview process in United States.
GitHub Work Experiences
- 1.0It used to be a great companySoftware Engineer • Current EmployeeSan Francisco, California, United StatesAugust 26, 2022Pros: The benefits are incredible, and you can work from home. Yep, that covers the pros.Cons: Management can make or ruin a company. When I started, we had a great management team, so positive! There were all-hands meetings, and people were promoted and rewarded for hard work. Now, those people have all left. This new management team came in like Scar from The Lion King. There are far fewer promotions, and all-hands meetings are gone. This new CEO, Thomas Dohmke, lied to everyone, saying they were doubling the merit cycle rewards. In reality, he cut it in half. People are now just numbers. Hard work does not matter. They make you get peer reviews, but they carry no weight. Turnover is at an alarming rate and will continue. Worst of all, they punish you for moving. They will rip away 10-30% of your pay if you leave the Bay Area. This company has lost its way. I won't be shocked if it goes down in flames soon. Customer service is all gone. It's a shame. GitHub had something great here. It was the place to be and work. Now, it's just a job. I won't be here much longer and won't give notice. They don't deserve that respect. Please do not work here, you will regret it!
- 1.0Great in theory, not in practiceCustomer Reliability Engineer • Former EmployeeSeattle, Washington, United StatesMarch 19, 2025Pros: Coworkers are great, products are cool.Cons: Management can be a nightmare, and HR is awful. I have been prevented from getting necessary medical procedures by an abusive management chain.
- 4.0Good Team, Flexible But BusySoftware Engineer • Current EmployeeLondonderry County Borough, Northern Ireland, United KingdomOctober 6, 2024Pros: Good people and training, flexible.Cons: Heavy schedule sometimes; management can be decent.
GitHub Interview Questions
