Process
The interview was, of course, easy, but there were restrictions.
One of them was running code only once, which was frustrating.
He must have given three chances instead of one.
He is right, but how do I even know my code is running correctly the first time? I agree that I lost my mind during the interview, but I can't agree that a simple problem can be solved accurately on the first try. There might be a mistake, and debugging is also a part of the job to find faults in your code.
Questions
Implement a Stack using a Queue.
Was this helpful?
Interview Statistics
The following metrics were computed from 1 interview experience for the GitHub Full Stack Develoer role in India.
Success Rate
GitHub's interview process for their Full Stack Develoer roles in India is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having very negative feelings for GitHub's Full Stack Develoer interview process in India.
GitHub Work Experiences
- 1.0Bad Upper ManagementSenior Software Engineer • Current EmployeeToronto, Ontario, CanadaOctober 24, 2025Pros: - Salary and benefits are good - RemoteCons: - Upper management reports directly into Microsoft in the absence of a CEO. - This leads to a lot of thrash, long hours, and often burnout in team members.
- 5.0Great Culture, Low PaySoftware Engineer • Former EmployeeVirginia Beach, Virginia, United StatesOctober 20, 2025Pros: Good culture, flexible because remote.Cons: Doesn't pay as much as other big tech.
- 4.0Great Oman Work, Needs ManagementWeb Developer • Current EmployeeOman, OmanOctober 5, 2025Pros: Great place to work in Oman.Cons: Stressful, but time management is needed.
GitHub Interview Questions
