Engineering Systems Analyst
As an Engineering Systems Analyst, you analyze the technical systems engineering teams use to design, simulate, and validate their work — evaluating tools, recommending improvements, and supporting engineering productivity.
What it's like to be a Engineering Systems Analyst
A typical day tends to involve evaluating engineering software and systems, gathering requirements from engineering teams, troubleshooting tool issues, supporting tool deployments, and documenting workflows. The role sits between IT and engineering — close enough to engineering to understand their needs, technical enough to evaluate tools effectively.
Coordination tends to happen with engineers, IT teams, software vendors, and engineering leadership. The hardest part is usually getting engineers to actually adopt new tools or workflows — engineers tend to be conservative about disrupting their working environment, and a better tool that no one uses isn't actually better.
People who tend to thrive here are technically curious, patient with change management, and respectful of the engineering work they support. If you want to do engineering yourself or get frustrated with adoption challenges, the support nature can wear. If you find satisfaction in making engineering teams more productive through better tools and systems, the role can be quietly impactful across many engineering projects.
Where this role sits in the broader career landscape — and where it can take you.
Roles like this one sit within a broader occupational category. The numbers below reflect that full landscape — helpful for context, but your specific experience will depend on level, specialty, and where you work.
How this category is changing
Skills & Requirements
Navigate your career with clarity
Truest gives you tools to understand your strengths, explore roles that fit, and plan your next move.
Explore Truest career toolsTruest editorial: Fit check, role profile, things that vary, advancement analysis, lateral moves, interview questions.