> That really makes no sense at all. How transferrable is the experience of an embedded developer to web development ? Or game development to enterprise applica

> That really makes no sense at all. How transferrable is the experience of an embedded developer to web development ? Or game development to enterprise applications ? Why would you even look at stuff that far outside your specialism? That's like saying because I'm a consultant orthopedic surgeon I can be a consultant psychiatrist. As your career progresses you will be more restricted in the fields you can enter without beginning a new career. And yet even in these way-out examples you gave there will be transferrable experience. Data driven design from game development; memory efficiency approaches from embedded? (I know nothing about it). It won't make you senior because you're way outside your field, but that experience is valuable. > You say you can give estimates for time and funding and yet you don't know the library landscape and what work needs to be done vs. what can be handled by the platform/libraries ? How do you think a manager does it? They talk with their team. A senior developer is no different except having more technical expertise than many managers. You seem to take a very indivdualistic view of the role of senior developer. > You mentor people about best practices yet you don't have real world experience with the particular tech stack ? I said "JavaScript framework" you broadened that to "tech stack". I don't need to know the ins and outs of React hooks - there's a reason I have developers in my team who are programming that stuff and not me. I was writing vanilla JS, then KnockoutJS, then Angular 2 so the principles are familiar even if I'm not mid-level in my expertise with React 18. Mentoring is a lot broader than "teaching how to program framework X". It's about developing skills, helping them figure out career progression, and advice and guidance. Tech is the least important part of mentoring - they can go get training for that. I detest the phrase "transferrable skills" but they are central to mentoring. > Which is to say I've hopped a lot of stacks and technologies between jobs and side projects. Yes. Why didn't you stick with something?