|
|
|
|
|
by AndrewKemendo
2423 days ago
|
|
The list of "What does Strategic Engineering Work look like," looks a whole lot like basic management. Each of these things listed below are fundamentally organizational/resources/personnel issues and except for one have almost no relation to the work stream of an IC which would include actually writing new code, refactoring old code, debugging, etc...: - Tackling technical challenges that span multiple technical and organizational systems. - Researching and identifying the problems that could be worked on, a year or two from now - Ramping up strike teams to help build a thing. - Looking at the big picture including cultural, product and technical challenges, to help inform choices that would be best for the org, perhaps with a 2-5 year view. - Forming strategies, writing proposals and pitching them across the company, for new architecture, systems or approaches. - etc... Except for developing prototypes, assuming the senior engineer is actually doing that, that entire list are just foundational management/leadership tasks. |
|