Senior Mainframe Software Engineer; Hogan API, Java, Boot, DevOps

At U.S. Bank, we’re on a journey to do our best. Helping the customers and businesses we serve to make better and smarter financial decisions and enabling the communities we support to grow and succeed. We believe it takes all of us to bring our shared ambition to life, and each person is unique in their potential. A career with U.S. Bank gives you a wide, ever-growing range of opportunities to discover what makes you thrive at every stage of your career.

Try new things, learn new skills and discover what you excel at—all from Day One.

This position will be responsible for the system development for the Hogan API application, using ISTIO Gateway, Kubernetes, Spring Boot, Java, Postgres, Z-connect, Datadog and Vulnerability resolution. Supporting NHID process. PCI and PAN compliance. Working directly with Hogan ODS and PAS creating the channel front-end API’s.

The candidate is a self‑motivated individual who can collaborate with a team and across the organization. The candidate takes responsibility of the software artifacts produced adhering to U.S. Bank standards in order to ensure minimal impact to the customer experience. The candidate will be adept with the agile software development lifecycle and Dev Ops principles.

• Consistently writes production-ready code that is easily testable, easily understood by other developers and accounts for edge cases and errors.
• Consistently considers best practice when designing services/APIs in accordance to agreed best practices and standards. Regularly designs code that fits with the overall architecture.
• Proficient at using systematic debugging to diagnose all issues located to a single service. Uses systematic debugging to diagnose cross service issues and is adept at using a range of tools to detect when there is an incident and raises this with stakeholders in a timely manner.
• Takes ownership of incidents which fall in their domain and may be involved in the resolution of an incident or aid others on resolving incidents.
• Understands and knows when to use different data structures. Understands when algorithms should be applied and the associated complexities. Helps others build their understanding of the applied algorithm and suggests improvements.
• Consistently creates reasonable sized code reviews that contain descriptions of changes and testing conducted. Assesses other code reviews with the lens of quality and value - code quality, acceptance criteria, business logic, test coverage and aligned to overall architecture. Highlights any issues with a code review that might result in release complications. Proactive in evaluating code reviews in the team and resolving open code reviews in a timely manner.
• Understands their team's testing approach and uses quality metrics to identify gaps. Works with their team to recommend solutions that are in accordance with accepted testing frameworks and the testing pyramid.
• Approaches engineering work with a security lens and actively looks for vulnerabilities both in the code and when providing code reviews. Has a holistic view on how the applications across more than one context integrate with each other. Is aware of the organization’s monitoring philosophy and skilled with the monitoring tools. Helps tune and change the monitoring on their team accordingly.
• Develops techniques on effective coaching strategies for different individuals. Seeks out mentoring opportunities specifically to increase knowledge in parts of the system that is not well understood. Supports and advocates others and provides tools to help them grow their understanding a technical topic.
• Actively participates and understands Scrum while developing a point of view on an effective software delivery process.
• Reviews tasks critically and ensures they are appropriately prioritized and sized for continuous integration and incremental delivery. Anticipates and communicates blockers, delays before they require escalation.
• Creates project proposals and designs that have considerable impact or touch multiple systems. Technical designs are clear, well thought out, and considers dependencies, failure states, maintainability, testability, and ease of support.
• Keeps business context in mind when proposing architectural decisions. Also considers scalability, reliability and performance of systems/contexts affected when defining technical designs.