Computer Programmer Analyst

Most days mix requirements gathering, coding, and user support — meeting with business stakeholders to understand needs, designing technical solutions, writing or maintaining code (often in COBOL, Java, .NET, or specialized enterprise stacks), running tests, and supporting deployments. You're often working in insurance, banking, government, healthcare, or other enterprise IT settings, and the application portfolio — legacy systems, modern stack, hybrid — shapes the work.

What tends to be harder than people expect is how much of the role is communication and translation. Stakeholder requirements rarely arrive technically clean, translating business language into technical specs is its own craft, and legacy system maintenance can dominate weeks at a time. Enterprise IT pace and change-management discipline structure the work.

People who tend to thrive here are comfortable with both business stakeholders and code, patient with legacy systems, fluent in iteration, and quietly committed to systems that work. If you want pure engineering with no requirements work, dev roles offer that. If you like the bridge between business needs and the systems that meet them, the role offers durable demand at enterprises with significant legacy investment.