4 ms·
The key here is Principal. 40 plus is considered fine and good for Architects/Managers and people in leadership positions. Try to get a senior engineer or below
by namelessoracle 5y ago
The key here is Principal. 40 plus is considered fine and good for Architects/Managers and people in leadership positions. Try to get a senior engineer or below job where you are expected to be grinding out code instead.
- brandall10 5y agoI was a senior at my last 4 roles - IOW, I was a Sr. dev turning 40, and didn't get another higher level role until turning 43. But yes, I have that experience in my background. I had my first principal role back when I was 32 (but prior to switching away from .NET development) and 2 other lead roles in my 30s.
- throw4765433 5y agoI think the stack is important. I know a lot of older Java and .Net developers that are hired to grind out code.
- brandall10 5y agoSo we're just going to move the goal posts then? Yes, having desirable skills is a given. We have a bunch of .NET devs (our BE is .NET) and the average age of these folks probably right around 40, because in general they're going to be older devs who do that.
- pjmlp 5y agoAbout the same age as the one you are replying to, usually the best way to work around that is consulting, where you are expected to be business analyst, architect, devops and coder in one package. Granted, not everyone enjoys doing it, and it comes with lots of politics as baggage as well.