Devsecops Engineer Interview Experience - New York, New York
Process
I applied online and received a response from a recruiter about two weeks later. They broke down the process and what was to be expected. They scheduled an initial interview with the manager of the team I would be working with. It was a fairly decent conversation with some questions surrounding my experience. I thought it went well, and the manager laid out the next steps.
The next step was an assessment, but a couple of days went by, and I reached back out to the team to see when I should expect it. They said I should be hearing back soon.
To my surprise, it wasn't an email regarding the assessment but an automated rejection email. This was a complete waste of my time, and I feel they could have at least had someone provide me with some feedback.
Don't bother wasting your time here.
Questions
What is the most recent project you've worked on?
Was this helpful?
Interview Statistics
The following metrics were computed from 1 interview experience for the GitHub Devsecops Engineer role in New York, New York.
Success Rate
GitHub's interview process for their Devsecops Engineer roles in New York, New York is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having very negative feelings for GitHub's Devsecops Engineer interview process in New York, New York.
GitHub Work Experiences
- 5.0Friendly Crew, Worth The WaitSoftware Engineer • Current EmployeeNew York, New York, United StatesJune 25, 2023Pros: Friendly crew, room for growth.Cons: Takes a while to onboard, but it's worth it.
- 3.0Staff Software Engineer at GitHubStaff Engineer • Current EmployeeNew York, New York, United StatesApril 5, 2023Pros: Work with some of the smartest people in this industry.Cons: Disorganized and disjointed leadership, high-stress incidents, and occasional long hours.
- 4.0They get a lot of things rightSeniour Software Engineer • Former EmployeeNew York, New York, United StatesFebruary 8, 2024Pros: They did a mob-programming session whilst I was there. 1:1 was also solid - this might be because I had a relatively good manager.Cons: There were a couple of good senior engineers that will be fun to work with. Some engineers will want to nitpick your PR to oblivion to show they know what they are doing, up to the point where they'd have to come back to apologize a couple of times for not reading what your actual PR does. This turned into an exhausting cycle.
GitHub Interview Questions
