> While Charity has deep experience in the domains of infrastructure & operations, databases, and backend engineering, I come originally from design, frontend, and product engineering, and I take a particular joy in collaborating with product management and ux design.
I had trouble figuring what they actually did, and what they currently do in their VP role. There's a lot of lip service, but it's not entirely clear what the person now spends most of their days doing.
Even the quote "coming from design, frontend and product engineering" doesn't tell me much (I'm also exactly that; I work on projects from doing sketches to Figma layouts to building front-end/mid-end in Sveltekit, build APIs in FastAPI, etc. etc.) — what did they excel at to get the VP job, and what do they miss the most about being in the trenches to... doing what they do now?
There's a ton of words on here but I don't really know what it says.
There's a few steps removed from the trenches to VPE. Check out "The Manager's Path" book for an overview of the different expectations of a current day smaller-than FAANG-like companies and the path of an engineer going up through management.
I had a similar impression. I also thought as you move into executive leadership things get much more strategic and you're rarely the one executing. But they list out lots of tactical experience and qualities that they say make them a good VP.
Its just HR PR forced on the poor dude. I'm a tech adjacent poor but I've seen many been forced to write something and it's always kind of like this. A bunch of people in the company will write a piece or two like this so something recent comes up in searches during campus recruiting. It serves two purposes, just the right amount of ass kissing and gassing up potential recruits.
I had trouble figuring what they actually did, and what they currently do in their VP role. There's a lot of lip service, but it's not entirely clear what the person now spends most of their days doing.
Even the quote "coming from design, frontend and product engineering" doesn't tell me much (I'm also exactly that; I work on projects from doing sketches to Figma layouts to building front-end/mid-end in Sveltekit, build APIs in FastAPI, etc. etc.) — what did they excel at to get the VP job, and what do they miss the most about being in the trenches to... doing what they do now?
There's a ton of words on here but I don't really know what it says.