It is well known tribal knowledge at Big$Corp that if you are a software engineer and want to grow, don't write software. Talk about it, make pictures of boxes with arrows going from all boxes to all boxes, write documents, flow charts, and pretend that once the "high level architecture documents" are done, the act of writing robust software is just like adding water, microwaving for two minutes and presto, you have a bowl of hot and spicy software ready. Lead, drive, delegate, hand off, steer, manage, communicate, coordinate, pathfind, spreadsheet, groundbreak, do proof-of-concepts, do demos, but whatever you do, do not actually write robust software from start to finish.