Good Pay, Toxic Leadership
Good Pay, Toxic Leadership
Competitive salary and benefits.
Great engineers.
Remote infrastructure is good.
Many teams to switch out of if needed.
Good managers are extremely hard to come by.
Leadership is not diverse and is toxic.
Constantly switching guidelines and expectations.
Poses as diverse, but isn't really diverse.
Works with ICE, Home Depot, and Chick-fil-A.
Doesn't care about the health of people.
Additional Ratings
Was this helpful?
GitHub Interview Questions
GitHub Interview Experiences
Senior Software Engineer
I applied online. The process took 2 months. The interview process took over two months, with long stretches of silence between rounds and poor communication from the recruiter. While I was excited about the role and the team seemed strong, the logi
Senior Software Engineer
I recently applied for a senior role, and a recruiter reached out asking me to complete a coding exercise. I had 5 hours from the moment I started it. It was a simple exercise that asked me to create basic HTTP services for uploading and downloading
Senior Software Engineer
There were two engineers. It was a LeetCode problem, followed by a questions and answer session on scalability and security. LeetCode-style coding problem (live coding, algorithm/data structures). Q&A discussion focused on scalability and security
Senior Software Engineer
Austin, Texas, United StatesJanuary 21, 2026I applied online. The process took 2 months. The interview process took over two months, with long stretches of silence between rounds and poor communication from the recruiter. While I was excited about the role and the team seemed strong, the logi
Senior Software Engineer
United StatesJanuary 1, 2021I recently applied for a senior role, and a recruiter reached out asking me to complete a coding exercise. I had 5 hours from the moment I started it. It was a simple exercise that asked me to create basic HTTP services for uploading and downloading
Senior Software Engineer
New York, New York, United StatesMarch 1, 2025There were two engineers. It was a LeetCode problem, followed by a questions and answer session on scalability and security. LeetCode-style coding problem (live coding, algorithm/data structures). Q&A discussion focused on scalability and security
