It’s something that comes hard to senior developers, because we’re all aware that every result is a team win. What I’m looking for in a principal engineer is someone who turns good teams into great teams who steers the organization away from disastrous mistakes who enables the business to accomplish things that, without them, would not have been done.
#Principal software engineer duties how to#
The challenge I have interviewing people for very senior engineering roles is how to tell the difference between somebody who was nearby when some interesting work got done, and somebody who made something interesting happen. In the past year, I have seen less than 5 job posting for a staff engineer. What we have tried as a company, what we haven't, why we built some things the way we did, how things work currently, how the politics works and the trust I have built. A lot of the value that I add now is because of the historical knowledge I have. I never expected this to be such a large part of my job, and how much value comes from it.īut I am also at this weird point where I am not sure if the title of "staff/principle" can be transferred to another company. I enjoy the soft work I do, a lot of emotional labor for other developers, soft sells for tech/feature work around the company, process strategy and such. Questions about technical feasibility, architectural discussions and planning, long term strategic planning, and lots of one offs from other developers. I'm a Staff engineer and of my 40 hour week about 10-15 of those hours are interviews, meetings, and answering questions.
0 kommentar(er)
