Live data from Hacker News

My thoughts about the Principal role

galiglobal.com

111–120 of 124 posts

Re: My thoughts about the Principal role

#111

Earlier quoted context omitted.

It's still quite strange to me that we're at a point in tech where technical skill becomes a penalty. This is not to say that non-technical skills are not important and often more important, but for both myself and friends "getting paid well" and "working on hard problems" have become conflicting goals. There was a brief while, at the beginning of our current tech boom where strong technical skills were extremely val…

This is generally the way things go. That it wasn’t true at some point is the anomaly. The generalized version is that anything widely desirable about a job other than money acts to push down wages. For example, if a position is widely respected, well most people like to be respected so wages are going to be less than if it wasn’t widely respected. Similarly, if there’s a lot of people that enjoy spending time with c…

After leading a team for about a year and a half, I see why managers get paid more. Simply, it's less fun, especially for someone who likes to solve hard technical problems.

I think I'm okay at leading a team but moving me to a staff engineer position would be better for me and the company and I think my leader knows this. The experience has been enlightening and I have a lot more respect for non-technical managers now.

Re: My thoughts about the Principal role

#112
post #108

Earlier quoted context omitted.

> You end up being a hub for the larger team, helping everyone do their jobs. This is 70% of my job as a Sr Staff Engineer and I love it. But yes, it does take a certain temperament to enjoy it or find it satisfying. I like collaboration and pairing and helping other ICs grow their careers. And I love teaching, which this role allows me to do in abundance in all sorts of ways. Sure, I enjoy sustained technical work a…

> I think there is still a bit of a perception that IC levels higher than Senior are about "Senior but with more interesting technical problems". This is largely false. Anyone know of a career path where this is actually the case? Lately it seems like everywhere I turn it's meetings and PowerPoint. Ideally I'd like to keep working on harder and harder engineering problems until I die of old age.

Work on small teams doing hard things. Best if the team is mostly experienced people, too.

Big companies may work on harder problems, but usually with bigger teams and you end up doing a lot more communication.

Re: My thoughts about the Principal role

#113
“If after one year, you can't leave a team without impact, you've failed in your work.”

A top managerial professor I knew defined a manager’s role to be exactly this. Principal or manager or whatever you are called doesn’t matter in the end, since once you go beyond “senior” level positions your role largely should be facilitating, empowering, and advocating for the members of your team. In reality, these roles unfortunately deteriorate into countless meetings with other managers and political struggles within a strong current of corporate compromises. Ignoring the latter part usually results in bad outcomes for one’s career at this level.

In my opinion, a true, technical principal role only works when there is another very capable person that fulfills the role of shielding the principal from the inevitable political, hierarchical forces that will head their way particularly from the sales and marketing departments.

Re: My thoughts about the Principal role

#114
post #113

“If after one year, you can't leave a team without impact, you've failed in your work.” A top managerial professor I knew defined a manager’s role to be exactly this. Principal or manager or whatever you are called doesn’t matter in the end, since once you go beyond “senior” level positions your role largely should be facilitating, empowering, and advocating for the members of your team. In reality, these roles unfor…

> In reality, these roles unfortunately deteriorate into countless meetings with other managers and political struggles within a strong current of corporate compromises.

It is unfortunate that talented programmers turn their backs on leadership roles requiring inter-personal skills, propagating the stereotypes that prevent programers from progressing in their careers.

> In my opinion, a true, technical principal role only works when there is another very capable person that fulfills the role of shielding the principal from the inevitable political, hierarchical forces that will head their way particularly from the sales and marketing departments.

Needing such "adult supervision" is harmful for programming profession in the long run.

Re: My thoughts about the Principal role

#115
post #113

“If after one year, you can't leave a team without impact, you've failed in your work.” A top managerial professor I knew defined a manager’s role to be exactly this. Principal or manager or whatever you are called doesn’t matter in the end, since once you go beyond “senior” level positions your role largely should be facilitating, empowering, and advocating for the members of your team. In reality, these roles unfor…

> In reality, these roles unfortunately deteriorate into countless meetings with other managers and political struggles within a strong current of corporate compromises. It is unfortunate that talented programmers turn their backs on leadership roles requiring inter-personal skills, propagating the stereotypes that prevent programers from progressing in their careers. > In my opinion, a true, technical principal role…

This is not about who is the “adult” … it’s about creating an environment for success given the expectations of the job.

Technical roles like a true principal at a high level require deep concentration and focus … being interrupted every 15-30 minutes to attend a meeting, answer a phone call, strategize a political response, respond to a slack message, handle complaints from critical clients, attend budget meetings, create reports, etc. is not the right environment.

Re: My thoughts about the Principal role

#116
post #27

I have personally not found the staff/principal level very enjoyable or satisfying. You end up being a hub for the larger team, helping everyone do their jobs. I'm not just referring to the coders. It's very draining and I resent that the industry classifies this type of work as technical IC work. A small subset of these higher "IC" roles do get to focus on technical IC work, but for most people a staff/principal rol…

> You end up being a hub for the larger team, helping everyone do their jobs. This is 70% of my job as a Sr Staff Engineer and I love it. But yes, it does take a certain temperament to enjoy it or find it satisfying. I like collaboration and pairing and helping other ICs grow their careers. And I love teaching, which this role allows me to do in abundance in all sorts of ways. Sure, I enjoy sustained technical work a…

> I think there is still a bit of a perception that IC levels higher than Senior are about "Senior but with more interesting technical problems". This is largely false. In most organizations those roles are about empowering other people. You can see this if you read the stories Will Larson's new book, Staff Engineer: Leadership Beyond the Management Track.

I think that's _one_ way to do it, but it defeats the purpose of having an IC path. It's basically "ship code while being a lite-manager". There's space for more types of staff+ engineers than "manager-lite" versions of the role.

I'm in a semi rebellion with exactly the description you provide, because I find it's short-sighted. We need to allow these roles to be anywhere along the spectrum from manager-like to purely technical. The best description I found of these more senior roles is that they give you license to build the role you wish to have. Kind of like being a tenure professor.

Here's my own self-defined role definition: focus on exploration and research along with mentoring my peers into becoming the next version of themselves. On the other hand, I have no interest in managing the day to day process; it gets in the way of my primary goals.

Re: My thoughts about the Principal role

#117
post #83

Earlier quoted context omitted.

Thanks for the reply! If you had it to do over again, would you chose to go into the area that you’re especially interested in and sacrifice ever getting the high FAANG comp? Or do you feel that having that savings invested has given you the long term security to feel comfortable, but perhaps if you’d made ~80% less over your career you’d be less satisfied?

That’s something I think about often. Sometimes I do wish I had plunged towards passions, but I know a lot of people who burned out by doing that. I think my path was probably a good one; it really is very psychologically nice to not worry at all about money and be able to advance my career in any direction I want now without feeling like I am being selfish, or neglecting my responsibilities as a father, or whatever.…

> I also certainly learned a lot at Amazon (although the thing I learned most was “how to be effective inside Amazon,” which isn’t a particularly great skill in the long run!).

Can you speak more to this? Why is being effective inside Amazon different from being effective at any other large organization?

Re: My thoughts about the Principal role

#118
post #43

Earlier quoted context omitted.

Have you been able to maintain a similar level of compensation? I started my career in scientific computing, and was paid a pittance compared to what a PE is paid at a big tech company. I’m wondering if moving to scientific computing is a luxury afforded by putting in time at AWS.

The sibling comment pretty much nailed it. I saved well over 75% of my income as a PE and have more than enough money accumulated, so I'm not worried. My wife works as well, and even though we're in a pretty expensive area (Seattle) and have a child, we're very comfortable. I get paid $110,000 per year, and have great benefits. It feels like plenty to me, even though I don't save nearly as much anymore. I agree it's…

[deleted]

Re: My thoughts about the Principal role

#119
post #43

Earlier quoted context omitted.

Have you been able to maintain a similar level of compensation? I started my career in scientific computing, and was paid a pittance compared to what a PE is paid at a big tech company. I’m wondering if moving to scientific computing is a luxury afforded by putting in time at AWS.

If one started at Amazon before 2016 or so, and put in a full 4 years to get 100% of their new hire stock vesting, they’d easily have more than $1 million just in stock. That plus all your other savings from the time you put in can make relaxing in a lower paid role for the next N years until you’re ready to retire an attractive proposition.

Yes, that is exactly my point.

On the other hand, if you spend your early career as a researcher making five digits a year in the Midwest, then move to SV in middle age to increase your earnings, you probably won’t ever catch up and be able to live very comfortably given the cost of housing.

This is just a possible counterpoint, learned the hard way, to the common advice to “pursue your passion.” My advice to those who have the option: make some money first, then pursue your passion.

Post reply on HN