Working on something that millions of people use and still mostly like.
More time and effort go to padding resumes with questionable rewrites, “leadership,” and AI functionality than is spent thinking about the health of GitHub and its users as a platform.
Stop chasing dollars and pretending large language models are good at everything at the expense of user experience and platform stability. Let's actually make GitHub better.
I applied for a Senior Software Engineer role, and they immediately sent me into a take-home coding exercise. The task was to implement an HTTP service for storing and accessing data. I completed it quite easily, including some additional unit tests
There are many good intentions behind GitHub's process. They don't fall for the LeetCode-style interviews that you see everywhere now. They've opted for a real-world problem instead, which is a lot more interesting and fun to work on. Unfortunately,
I applied online and after about one week, I received an email with the following steps: 1. **Code assignment.** It was pretty easy; they give you five hours, but it took less time to do a good job. 2. Three days after I submitted the code assign
I applied for a Senior Software Engineer role, and they immediately sent me into a take-home coding exercise. The task was to implement an HTTP service for storing and accessing data. I completed it quite easily, including some additional unit tests
There are many good intentions behind GitHub's process. They don't fall for the LeetCode-style interviews that you see everywhere now. They've opted for a real-world problem instead, which is a lot more interesting and fun to work on. Unfortunately,
I applied online and after about one week, I received an email with the following steps: 1. **Code assignment.** It was pretty easy; they give you five hours, but it took less time to do a good job. 2. Three days after I submitted the code assign