Junior Computer Programmer Analyst

Most days mix supervised analysis and coding with structured learning — sitting in on requirements meetings, supporting code work under direction, writing tests, helping with deployments, and learning the office's development and change-management workflows. You're often working in enterprise IT settings — insurance, banking, government, healthcare — and the application portfolio (legacy and modern) shapes early exposure.

What tends to be harder than people expect is the translation work required. Stakeholder requirements rarely arrive technically clean, and bridging business and technical language is a craft that develops over years. Mentorship quality and project mix shape early career growth, and enterprise change-management discipline structures how work moves through.

People who tend to thrive here are comfortable with both stakeholders and code, patient with iterative requirements, willing to learn from senior staff, and quietly committed to systems that meet real needs. If you want pure engineering with no requirements work, dev roles offer that. If you like building a career at the intersection of business needs and the systems that meet them, the role offers durable demand at enterprises with significant business systems.