Re:Jonathan Blow – If AI Solved Coding, Why Is My Software S...
by dante54 on Sunday November 15, 2026 @02:09AM
(#50504727)
You just described my consulting gigs. I however specialize in data, so its a bit easier to get proofs. However, getting business requirements is a pain, conversely I almost entirely handle implementation albeit with some supervision from the aforementioned no to so technical managers.
But there's a more general kind of "systems analyst" that still survives (and is mostly what the BLS stats refer to): a person whose job is to map out the current business domain of a system (consisting of not just computers, but also people, infrastructure, institutions, etc.) and identify where it will need to be modified (but not necessarily how it will need to be modified) to make it capable of being put to use in a certain way for a given plan/mission.
Systems analysts in this sense tend to be one of the actual workhorse jobs inside "management consulting" firms and "think tanks." Governments, militaries, and large bureaucracies with many independent business units (think IBM) are their customers.
Systems analysis is sometimes done structurally over an entire organization: someone at a very high level has some new vision for an initiative, and hires these companies/think-tanks to help them determine how to "align" their organizational architecture with what a military might call a new "doctrine" or a company might call a new "paradigm." In these cases, the systems analyst performs the first step of that alignment: understanding "the system as it is today", and identifying what parts of it are already aligned vs. which parts will need to change. Their output is a report to the person driving the process.
But structural analysis is more often applied to specific strategic/business units, as the result of that strategic/business unit being chosen to execute a given strategic mission, as an enablement process to get that unit into the specific shape it needs to be in to execute that mission. In this case, there is likely an assigned "mission {planner, architect}" (who may also become the mission's director; or who may hire for such a director role and then depart to go plan the next mission.) The systems analyst works for/with the mission planner as their "eyes and ears", interacting with the business unit to gather information for the planner to use.
In both the structural and strategic cases, there are usually also one or more systems engineers who determine the "how" for implementation of these changes. (A mission planner is usually a very senior systems engineer themselves.)
However, unlike the systems analyst, who is considered more trustworthy to central leadership when they exist outside of the system they're analyzing (and so mostly work for external firms like think-tanks rather than for the orgs themselves), there's much less of a motivation to separate out systems engineering in that manner. So systems engineers (including mission planners!) tend to be regular [if high-paid] career employees of the central organization. These folks are frequently "general staff" in a military (with no real analogous term, AFAIK, for the equivalent people within a conglomerate's parent company.)
Due to their value coming in part from existing in separate firms that can negotiate on their behalf, systems analysts in this sense are well-paid indeed! But also worked hard, bounced around, and signing NDAs constantly. And possibly a bit bitter, in that they often see how things are broken with no chance to be part of the fix.