Balancing Technical Breadth and Depth

•

#SystemsEngineerChallenges SE_Day4/5 : 𝗧𝗲𝗰𝗵𝗻𝗶𝗰𝗮𝗹 𝗕𝗿𝗲𝗮𝗱𝘁𝗵 𝘃𝘀 𝗗𝗲𝗽𝘁𝗵 -- the 𝗧-𝗦𝗵𝗮𝗽𝗲𝗱 𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿 Systems engineers often struggle to balance: 👇

• Broad technical knowledge across many domains, ranging from software and hardware and electronics to networking and cybersecurity, to quality and manufacturing, operation and retirement. • Sufficient depth to make informed, decisive choices in complex situations

As an engineer aptly described, it’s akin to a "𝙢𝙞𝙡𝙚 𝙬𝙞𝙙𝙚/𝙞𝙣𝙘𝙝 𝙙𝙚𝙚𝙥 𝙟𝙤𝙗." This duality requires continuous learning and adaptation, as technological advancements and industry demands constantly evolve.

Maintaining this equilibrium of breadth and depth is an ongoing challenge, necessitating not only technical acumen but also strategic foresight and a willingness to delve deeper when critical decisions arise.

Unfortunately though, most job postings I see require a very specialised set of skills and call that Systems Engineering. Like it is a discipline expertise. A Software Engineer is an "I-Shaped" profile, an expert going deep in the detail of their discipline.

And I see jobs requiring only creating some diagrams for the Architecture and they call it MBSE. Or writing some requirements and they call that Requirements Engineering. And the role Systems Engineering? ...

Or worse, they trow in all buzzwords they can think of related to Systems Engineering. Which makes it sound like 3 full-time jobs in one ... 𝗜'𝗺 𝘀𝘂𝗿𝗲 𝘄𝗲 𝗰𝗮𝗻 𝗱𝗼 𝗯𝗲𝘁𝘁𝗲𝗿! 👇

More clarity and more education is needed for Systems Engineering! For candidates to know what to expect and how to plan careers. And companies to create realistic and clear positions. 𝙒𝙝𝙖𝙩'𝙨 𝙮𝙤𝙪𝙧 𝙚𝙭𝙥𝙚𝙧𝙞𝙚𝙣𝙘𝙚 𝙤𝙣 𝙩𝙝𝙞𝙨? 𝙒𝙝𝙖𝙩 𝙙𝙤 𝙔𝙊𝙐 𝙏𝙝𝙞𝙣𝙠?