Scientific Systems Analyst

Day-to-day tends to involve working with research teams to understand their computing needs, evaluating scientific software and systems, supporting deployments, troubleshooting issues, and documenting workflows. The role sits between IT and science — close enough to research to understand the work, technical enough to evaluate tools effectively.

Coordination tends to happen with researchers, IT teams, software vendors, and research leadership. The hardest part is often the gap between what researchers want and what IT infrastructure supports cleanly — research workloads often push systems in ways general IT doesn't encounter.

People who tend to thrive here are scientifically curious, technically grounded, and patient with the unique demands of research computing. If you want pure development or get frustrated with niche workloads, the focus can wear. If you find satisfaction in being the person who actually makes scientific teams more productive through better systems, the role can be quietly central to research output — and the work tends to be intellectually engaging.