SponsoredLaptop recommendation
Lenovo V15 G4 AMD Ryzen 5 7520U 15.6 inch FHD Laptop, AMD Graphics, 16GB DDR5 5500Mhz Ram, 512GB SSD NVMe, Windows 11, Dolby Audio, Arctic Grey, 1 Year Onsite Brand Warranty
₹49,650
77 people viewed this job today
Software Engineer I
Experience Required
Minimum 2 years
Employment Type
Full-time
Target Batch
Any
Role Category
Software Engineering
How to Apply
Apply on the company portal
Skills Recommended
PythonTornado web frameworkTypeScriptReactMachine LearningLLMsUI/UX designingModel Risk ManagementFinancial Services
About the job
Job Description
Software Engineer I
Mumbai, Maharashtra, India
Apply Now
Job Information
Job Identification
210742917
Job Category
Software Engineering
Business Unit
Corporate Sector
Posting Date
06/05/2026, 03:57 pm
Locations
Nirlon Knowledge Park, Western Express Highway, Goregaon (East), Mumbai, IN-MH, 400063, IN
Job Schedule
Full time
Job Description
Are you looking for an exciting opportunity to join a dynamic and growing team in a fast paced and challenging area? This is a unique opportunity for you to work in our team to partner with the Business to provide a comprehensive view.
As a Software Engineer I at JPMorgan Chase within the Model Risk Governance & Review (MRGR) team, you will be developing tools for MRGR Analytics to improve efficiency and reduce duplication of effort, including resource management and cost optimization tools. You will provide support for model reviewers and governance teams in building independent testing and efficiency tools. You will be delivering high-quality solutions by emphasizing the importance of data controls, testing, user experience and continuously seek input from users to align efforts with their objectives. Bring your expertise to JPMorgan Chase. As part of Risk Management and Compliance, you are at the center of keeping JPMorgan Chase strong and resilient.
The team is responsible for conducting independent model validation and model governance activities to help identify, measure, and mitigate Model Risk in the firm. Within MRGR, the Chief Operating Office (COO) supports model risk stakeholders in their review and governance activities, and drives certain governance activities itself, with responsibility for: product ownership, process engineering and software development for model risk technology and analytics; model risk reporting; administration of oversight committees; project management of the review and governance pipeline; coordination of regulatory/audit deliverables including capital stress testing exercises; and general business management. Within COO, MRGR Analytics provides technology solutions for MRGR and its clients, assisting them in performing their tasks more efficiently, accurately, and with better control. Majority of the solutions are built within Athena (JPMorganChase’s proprietary framework using Python language), Tableau and QlikView/QlikSense frameworks.
Job responsibilities
Develop tools to automate various tasks in the model governance and review lifecycle.
Build various dashboard reports to help manage the body of work that MRGR deals with.
Translate the existing business requirements in model risk management space into business applications using applied development work mostly in Python using in-house built Python framework.
Integrate Large Language Models (LLMs) into existing systems to enhance automation, reporting capabilities and decision-making processes.
Collaborate with cross-functional teams to identify opportunities for LLM integration and develop solutions that leverage LLM capabilities.
Build intelligent solutions to support the activities of MRGR staff.
Required qualifications, capabilities, and skills
A Bachelors or Masters degree in a Science, Technology, Engineering, or Mathematics discipline with significant exposure to computer programming.
Minimum 2 years of full stack application development.
Proficient in Python and knowledge of Tornado web framework / TypeScript / React required.
Good understanding of software architecture, object-oriented programming and design patterns.
Experience with integrating machine learning models, including LLMs, into enterprise applications.
Strong communication skills with the ability to interface with other functional areas in the firm on business requirements.
Risk and control mindset: ability to think critically, assess user needs and create design solutions to meet user needs.
Preferred qualifications, capabilities, and skills
Experience in working with large data sets.
Exposure to LLM integration and deployment in real-world applications.
Strong UI/UX designing skills.
Experience in model risk management or financial services space.
About Us
JPMorganChase, one of the oldest financial institutions, offers innovative financial solutions to millions of consumers, small businesses and many of the world’s most prominent corporate, institutional and government clients under the J.P. Morgan and Chase brands. Our history spans over 200 years and today we are a leader in investment banking, consumer and small business banking, commercial banking, financial transaction processing and asset management.
We recognize that our people are our strength and the diverse talents they bring to our global workforce are directly linked to our success. We are an equal opportunity employer and place a high value on diversity and inclusion at our company. We do not discriminate on the basis of any protected attribute, including race, religion, color, national origin, gender, sexual orientation, gender identity, gender expression, age, marital or veteran status, pregnancy or disability, or any other basis protected under applicable law. We also make reasonable accommodations for applicants’ and employees’ religious practices and beliefs, as well as mental health or physical disability needs. Visit our FAQs for more information about requesting an accommodation.
🎯 Why This Role Matters
As a Software Engineer I at JPMorganChase, you will be at the forefront of solving complex problems that impact millions of users. This is not just about writing code or executing tasks; it is about taking ownership of critical systems, collaborating with top-tier talent, and driving innovation. If you want a role that challenges you to grow rapidly and leaves a lasting impact on the industry, this is it.
⚡ Key Skills Needed
To stand out for this position, you need more than just the basics. Hiring managers for this Software Engineer I role are looking for:
- ✓ Strong foundational knowledge in core engineering principles.
- ✓ Ability to adapt quickly to the fast-paced environment at JPMorganChase.
- ✓ Proficiency in Python, Tornado web framework, TypeScript.
💡 Application Tips
- •Tailor your resume: Highlight specific projects or experiences that align directly with current initiatives at JPMorganChase.
- •Prepare for behavioral rounds: Be ready to discuss times you have handled failure, tight deadlines, or team conflicts.
- •Leverage the AI Assistant: Use the AI Assistant button above to evaluate your resume against this specific Software Engineer I description before applying.
Candidate Guide
More than a copied JD: use this page to prepare before you apply.
JPMorganChase is hiring for Software Engineer I in Nirlon Knowledge Park, Western Express Highway, Goregaon (East), Mumbai, IN-MH, 400063, IN. This page goes beyond the raw listing so students can understand what the role usually expects, how to prepare for screening, and how to apply more thoughtfully instead of forwarding a resume blindly.
PythonTornado web frameworkTypeScriptReactMachine LearningLLMsUIUX designing
Company overview
JPMorganChase appears on Campus to Career because the opportunity is relevant for students and early-career candidates who want a clearer view of real hiring demand. When evaluating any employer, students should look beyond the brand name and focus on work quality, reporting structure, product maturity, mentorship, and the kind of ownership the team is likely to trust a new hire with.
A fresher or internship role at JPMorganChase can be valuable when the candidate understands what the business is solving and how the team contributes to that larger outcome. Even before the interview, students should try to learn the company domain, customer type, pace of execution, and whether the role sits close to product, platform, support, data, or delivery.
What this role usually means in practice
Software Engineer I is likely not just a keyword match. In real hiring, titles often compress multiple expectations into one label. This means the student should read the listing as a signal of day-to-day problem solving, team collaboration, deadline discipline, and the ability to learn new workflows quickly.
The current role is listed as Full-time in Nirlon Knowledge Park, Western Express Highway, Goregaon (East), Mumbai, IN-MH, 400063, IN, with Minimum 2 years mentioned on the page. For freshers, the most useful interpretation is: what kind of output will the team expect in the first 30 to 90 days, and what proof can the candidate show that they are ready to deliver it?
- Understand the business problem the role supports
- Map your projects to likely day-to-day work
- Prepare one story about fast learning and one about ownership
Required skills and how to interpret them
The listing highlights skills such as Python, Tornado web framework, TypeScript, React, Machine Learning, LLMs, UI, UX designing. Students should not panic if they are not equally strong in every item. Companies often list an ideal stack, but interviewers usually look for transferable understanding, clarity of fundamentals, and a believable proof-of-work story.
A better preparation strategy is to sort skills into three buckets: already strong, interview-ready but shallow, and currently weak. This prevents overconfidence and also stops students from wasting time revising topics that are unlikely to matter during the first screening round.
- Be ready to explain where you used Python in a project, coursework, internship, or self-study build.
- Be ready to explain where you used Tornado web framework in a project, coursework, internship, or self-study build.
- Be ready to explain where you used TypeScript in a project, coursework, internship, or self-study build.
- Be ready to explain where you used React in a project, coursework, internship, or self-study build.
- Be ready to explain where you used Machine Learning in a project, coursework, internship, or self-study build.
- Be ready to explain where you used LLMs in a project, coursework, internship, or self-study build.
- Be ready to explain where you used UI in a project, coursework, internship, or self-study build.
- Be ready to explain where you used UX designing in a project, coursework, internship, or self-study build.
Eligibility and application readiness
Students should treat eligibility as more than just degree, batch, or marks. Real readiness also includes whether the resume supports the role clearly, whether your GitHub or portfolio can survive a quick recruiter scan, and whether your self-introduction makes logical sense for Software Engineer I.
If the listing mentions a batch requirement, relocation, internship-to-full-time path, or communication expectations, make sure those details are reflected consistently in your resume, application form, and outreach message. Consistency is a major trust signal in early-stage screening.
- Resume aligned to the role and keywords
- Portfolio or GitHub links working correctly
- Projects chosen based on role relevance, not just recency
- Clear answer prepared for “Why this role?”
Salary insight and offer evaluation
The listing does not clearly publish compensation, which is common for fresher and early-career openings. Candidates should use peer benchmarks, city cost, and recruiter conversations to understand likely salary range before final acceptance.
For freshers, salary should be interpreted together with learning quality, tech exposure, mentorship, workload, location, and conversion or growth path. A slightly smaller offer with stronger ownership and cleaner learning loops may outperform a bigger offer that provides weak role fit or no meaningful skill depth.
Interview preparation tips for this job
Candidates applying for Software Engineer I should prepare in layers. The first layer is role fit: why this company, why this role, and what proof supports your application. The second layer is technical or functional depth: the tools, concepts, or workflows most likely to appear in screening. The third layer is behavior and communication: clear explanations, honest ownership, and calm thinking when details are incomplete.
A strong practice method is to prepare a short project walk-through, a role-fit introduction, one debugging or challenge story, and a realistic answer to what you still want to learn. That combination usually performs better than memorizing long theoretical scripts.
- Review two strongest projects deeply, not ten projects weakly
- Prepare role-specific terminology and examples
- Practice concise answers for HR and recruiter rounds
- Revise fundamentals likely connected to the listed skills
Application strategy for better conversion
The best candidates do not just click apply. They adapt. Before submitting, update the top section of your resume, reorder projects if needed, and make sure your strongest evidence matches the narrative for Software Engineer I. If the company uses an external portal, take form fields seriously because ATS filters often read those signals separately from the PDF.
If the route is recruiter email or a direct apply link, use that path professionally. Submit complete information, avoid spammy follow-up, and if you choose to reach out on LinkedIn, mention the role, one or two fit points, and a respectful ask. The goal is to make your application easier to trust, not louder.