Software Engineer – Enterprise Claims Build Automation & Release Engineering (Gradle, Maven)

Being good neighbors – helping people, investing in our communities, and making the world a better place – is who we are at State Farm. It is at the core of how we operate and the reason for our success. Come join a #1 team and do some good! Grow Your Skills, Grow Your Potential Responsibilities As a Software Engineer / Lead Software Engineer in Enterprise Technology (ET) Claims, you will join the Enterprise Claim System (ECS) Build team, the team that owns CI/CD pipeline infrastructure, build automation, and release engineering for one of State Farm's largest and most complex applications. ECS spans 40+ product modules across concurrent release streams, compiled and deployed through scheduled full-system builds orchestrated by both a legacy Jenkins cluster and an evolving GitLab CI platform. You will drive the modernization of this ecosystem, migrating Jenkins jobs to GitLab CI pipelines (with GitHub on the long-term horizon), evolving builds from Ant/Maven toward Gradle, and building the shared tooling and automation that keeps hundreds of Claims developers productive.

Design, implement, and maintain GitLab CI pipelines that compile, package, and validate a large-scale Java application across multiple concurrent release streams using shared AWS runners and custom Docker images. Migrate and retire legacy Jenkins jobs by re-implementing them as modular, reusable GitLab CI pipelines using shared templates and source libraries. Build and maintain developer-facing utilities such as tagging tools, merge validation, code search, build comparison/diff, version reporting, and code metrics, all delivered as pipeline-triggered automation. Develop and evolve internal dashboards that provide release teams and developers real-time visibility into build health, queue times, and deployment status. Manage shared build infrastructure: custom container images, artifact repository integration (JFrog Artifactory), credential management, multi-environment deployment orchestration, and runner configuration. Automate release operations: branch/tag management across multi-stream releases, version management, configuration-only builds, and externalized configuration. Drive long-term modernization: evaluate and implement Gradle as a replacement for Ant and Maven build scripts; prepare for eventual migration from GitLab to GitHub, aligned with enterprise technology direction.

Required Strong engineering fundamentals (design, secure coding, testing, maintainability) with experience delivering and supporting production build/release systems at scale. Hands-on CI/CD pipeline development: writing pipeline definitions, designing multi-stage workflows, working with shared runners, and managing pipeline-as-code patterns (not just triggering builds). Proficiency in shell scripting (Bash) for build automation, comfortable writing scripts that interact with Git, REST APIs, and orchestrate multi-step build processes. Solid Git workflows: branching strategies, tagging conventions, multi-stream release management, and merge validation. Unix/Linux command-line fluency; experience with Docker container images for CI environments. Strong ownership, collaboration, and communication; comfortable working across teams and navigating ambiguity. Desired Experience with Gradle (Kotlin or Groovy DSL), particularly migrating large Java projects from Ant or Maven. GitLab CI advanced patterns: parent-child pipelines, shared templates/includes, dynamic variable generation, custom runner configuration, container registry management. Apache Ant and/or Maven deep knowledge (for maintaining the current estate while migrating forward). Artifact repository management (JFrog Artifactory or similar): promotion strategies, credential management, retention policies. Python scripting for build automation and reporting. GitHub Actions experience (future-state target). Cloud platforms (AWS): understanding of compute runners, region selection, and