I'm not sure what others experiences are but for me it's mostly the same but also different in some ways than in the past. The biggest change is that there's more structure in some key places.
For instance there are a few PMs now for very involved projects, and we have engineering managers to make sure we're getting along ok and not falling between the cracks (turns out 100+ people reporting to one person can be tricky), but still remains enormously open.
Most decisions are made in the open (if they legally can be), there's almost always a Pull Request with discussion around it if you want to either take part or just see how that decision came around. The culture is pretty allergic to anything closed. People frequently ask for a URL if they're curious how a decision was made. This makes it much easier to not feel left out as a remote employee (which something like 60% are).
As an engineer I can largely still choose what I work on much in the same way as before: if there's a project spinning up and I want to work on that project and that team wants me and my team is cool with me going I can totally go work on it.
I've actually been encouraged to work on other things lately to get more perspective on the product and work with new people. I don't feel pigeonholed like I have in some other places.
Teams mostly self organize into structures that best work for them. Some teams look fairly traditional. Some use scrum. Some use some other agile methods. Some use nothing. Some work closely with a PM. etc. Use what makes you happy and what makes you productive. Different projects have different needs.
Things may shift around as growth happens (and they have), but largely I feel like the principles have stayed intact. Still the best place I've ever worked.
Some LinkedIn job titles from current GitHub employees:
* VP, Business Development & Services
* Head of Technology Partnerships
* CIO
* VP, HR
* Vice President, Strategy
* Vice President, Marketing
* VP Communications
* Director of Outreach
* Director of Sales
See also: http://www.nytimes.com/2012/09/09/technology/valve-a-video-g... - "The few employees who’ve put titles on business cards do so to satisfy outsiders apprehensive about working with people without labels. The same applies to Gabe Newell, one of Valve’s founders."
(no idea whether this is the case here...)
One of my former colleagues had this sort of experience at one job, where his job title was "programmer" (you got this title if you were a programmer; there weren't any others available). He was finding it sometimes difficult to get people to return emails, presumably because he didn't sound important enough. Apparently the last straw was being roundly ignored in a particular meeting with one external company! A swift title upgrade (no changes in responsibility...) fixed all of this.
For instance there are a few PMs now for very involved projects, and we have engineering managers to make sure we're getting along ok and not falling between the cracks (turns out 100+ people reporting to one person can be tricky), but still remains enormously open.
Most decisions are made in the open (if they legally can be), there's almost always a Pull Request with discussion around it if you want to either take part or just see how that decision came around. The culture is pretty allergic to anything closed. People frequently ask for a URL if they're curious how a decision was made. This makes it much easier to not feel left out as a remote employee (which something like 60% are).
As an engineer I can largely still choose what I work on much in the same way as before: if there's a project spinning up and I want to work on that project and that team wants me and my team is cool with me going I can totally go work on it.
I've actually been encouraged to work on other things lately to get more perspective on the product and work with new people. I don't feel pigeonholed like I have in some other places.
Teams mostly self organize into structures that best work for them. Some teams look fairly traditional. Some use scrum. Some use some other agile methods. Some use nothing. Some work closely with a PM. etc. Use what makes you happy and what makes you productive. Different projects have different needs.
Things may shift around as growth happens (and they have), but largely I feel like the principles have stayed intact. Still the best place I've ever worked.