Software Engineer Job Details | Fitch Group

Fitch Group is expanding its Chicago-based technology team, signaling a broader industry shift toward AI-integrated full-stack engineering. According to the firm’s current recruitment criteria, future software roles in financial services will prioritize proficiency in AI-assisted tools like GitHub Copilot and the Model Context Protocol (MCP) to accelerate the delivery of credit and risk insights.

How is AI changing the software engineering workflow?

AI-assisted development is moving from a luxury to a core requirement. Fitch Group’s inclusion of GitHub Copilot and Microsoft Copilot in its “good fit” criteria reflects a trend where engineers act more as architects and reviewers than manual coders. This shift reduces the time spent on boilerplate code, allowing developers to focus on complex business logic and system security.

The mention of Model Context Protocol (MCP) points to a new frontier: standardized ways for AI models to access data sources. This allows an AI to interact directly with a company’s internal databases or APIs without custom-built connectors for every task. According to documentation from MCP, this framework enables a more seamless exchange of information between LLMs and local data environments.

Why is GitOps becoming the standard for financial services?

Financial institutions require strict audit trails and high availability. Fitch Group’s emphasis on ArgoCD and Kubernetes (EKS) highlights the industry’s move toward GitOps. In a GitOps model, the Git repository is the single source of truth for infrastructure. If a production environment drifts from its desired state, tools like ArgoCD automatically synchronize it back to the version-controlled configuration.

This approach eliminates the “it works on my machine” problem. By utilizing Amazon EKS for container orchestration, firms can scale microservices independently. This is critical for credit rating agencies that handle fluctuating loads of data during major market events. You can read more about cloud-native scaling in our previous analysis.

What role does the “Full-Stack” developer play in modern data architecture?

The demand for “T-shaped” engineers—those with deep expertise in one area and broad knowledge across others—is rising. Fitch Group’s requirement for Java/Spring Boot on the backend and React on the frontend, coupled with NoSQL databases like MongoDB, shows a preference for decoupled architectures. This allows a frontend to update its UI without requiring a full backend redeploy.

Integrating Content Management Systems (CMS) like Contentful further separates content from presentation. This “headless” approach allows financial data to be pushed to websites, mobile apps, and internal dashboards simultaneously via APIs. It transforms the website from a static page into a dynamic data application.

How does DevSecOps impact the development lifecycle?

Security is no longer a final step before release; it’s integrated into the CI/CD pipeline. Fitch Group’s focus on “DevSecOps” means that automated unit, integration, and visual regression tests are triggered the moment code is committed. This prevents security vulnerabilities from reaching production, a necessity for firms handling sensitive financial ratings.

Industry data suggests that shifting security “left”—moving it earlier in the development process—significantly reduces the cost of fixing bugs. When security checks are automated in the pipeline, developers get immediate feedback, reducing the friction between the engineering and security teams.

Frequently Asked Questions