Software Engineer II - Backend, Python AI/ML
JPMorgan Chase & Co.Match Score
Against your primary resumeLogin to See Your Match Score
Create a free account or log in to unlock your CV match score across:
Protocol Intelligence
Data-driven signals on your job's competitivenessTier-1 brand, common backend title, and mid-level (2+ years) experience amplify competition.
Backend engineering skills are broadly transferable across industries despite payments context.
2+ years requirement plus mandatory backend and AI-assisted tooling experience enforces moderate filtering.
Job Description
Structured overview of role & requirementsAbout This Role
Design, develop, and troubleshoot software components for secure, stable, scalable Payments Technology products.
Write high-quality code using Python or other programming languages with limited guidance, leveraging enterprise-authorized AI coding assist tools and validating outputs.
Contribute to application development by analyzing large data sets and applying software development life cycle methodologies including CI/CD, resiliency, and security.
Minimum Requirements
2+ years of applied software engineering experience with formal training or certification.
Hands-on experience in system design, application development, testing, and operational stability in a corporate environment.
Experience with one or more modern programming languages and database querying languages, and use of enterprise-authorized AI-assisted software development tools.
Work Experience Required: 2+ years; Location constraints implied for India/NAMR/APAC/LATAM/Hong Kong but not explicitly detailed as mandatory in JD.
Ideal Candidate Profile
Experienced in full software development life cycle within Agile methodologies with CI/CD and security focus.
Familiar with AI-assisted coding tools and responsible AI use in engineering workflows including data sensitivity and secure handling.
Experience or exposure to Java 17+, microservices on AWS Kubernetes or ECS, Terraform scripting, and relational databases like Oracle or PostgreSQL preferred but not mandatory.