Want to get hired at Chase- Candidate Experience page?
Lead Software Engineer QA Lead
Chase- Candidate Experience page
Bengaluru, Karnataka, IndiaOn Site
Original Job Summary
Overview
As a Lead Software Engineer QA Lead at JPMorgan Chase, you will be part of the Commercial and Investment Bank - Payments Technology team. You will develop robust, secure technology solutions in an agile environment, ensuring operational stability and high performance.
Job Responsibilities
Your primary responsibilities include:
- Design, develop, and troubleshoot creative software solutions.
- Develop secure, high-quality production code and review team code.
- Automate recurring issues for improved operational stability.
- Lead evaluation sessions with vendors and internal teams.
- Drive communities of practice for new and leading-edge technologies.
Required Qualifications
This role requires:
- At least 5 years of applied experience in software engineering.
- Advanced skills in Selenium, Java, Cucumber, and Appium for test automation.
- Expertise in the full software development life cycle with agile methodologies, CI/CD and security.
- Practical cloud native experience and in-depth knowledge of financial IT systems.
Key skills/competency
Selenium, Java, Cucumber, Appium, CI/CD, Agile, Cloud, Automation, Software Development, Financial Services
How to Get Hired at Chase- Candidate Experience page
🎯 Tips for Getting Hired
- Customize your resume: Highlight agile, automation, and cloud skills.
- Prepare technical examples: Demonstrate Selenium and Java projects.
- Research Chase's culture: Study their mission and values online.
- Practice behavioral questions: Reflect past team leadership experiences.
📝 Interview Preparation Advice
Technical Preparation
circle
Review Selenium and Java coding challenges.
circle
Practice automation framework implementation scenarios.
circle
Study cloud native architecture fundamentals.
circle
Brush up on CI/CD pipeline integrations.
Behavioral Questions
circle
Describe a past leadership challenge.
circle
Explain teamwork in agile projects.
circle
Discuss handling code review conflicts.
circle
Share experience with vendor evaluations.