← JP Morgan Interview Insights

JP Morgan·Software Engineer·Onsite - Behavioral / Leadership·Intermediate

Intermediate
Jun 2026

Summary

Behavioral round at JP Morgan for a software engineer role. Pretty much all about past projects and how you worked with your team, so if you haven't thought through specific examples beforehand you'll feel the pressure fast.

Questions Asked (3)

Q1

Walk me through a past project you worked on and how you handled a specific challenge during it.

Adaptability & AmbiguityCross-functional Alignment
Author's notes

They kept asking follow-ups after every answer so having one vague project story wasn't going to cut it.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Select a project that demonstrates both technical depth and cross-functional collaboration, then use the STAR method to structure your story. Focus on a specific challenge where you had to adapt to ambiguity or align stakeholders, and highlight the measurable impact of your actions.

Pro tip: Emphasize how you navigated ambiguity and aligned cross-functional teams, as JP Morgan values engineers who can deliver results in complex, regulated environments. Quantify the outcome to show business impact.

1. Set the Context

Briefly describe the project, your role, and the team composition, including cross-functional partners. Keep it concise to save time for the challenge.

2. Define the Challenge

Clearly state the specific challenge, such as unclear requirements, tight deadline, or conflicting stakeholder priorities. Explain why it was difficult.

3. Describe Your Actions

Detail the steps you took to address the challenge, emphasizing how you adapted, communicated, and collaborated with others. Highlight any technical or process innovations.

4. Highlight the Outcome

Share the results, including quantifiable metrics (e.g., time saved, performance improvement) and any positive feedback from stakeholders.

5. Reflect and Learn

Summarize what you learned and how it has influenced your approach to similar situations since. Show growth and self-awareness.

Key Points to Mention

  • Cross-functional collaboration with product, design, or business stakeholders
  • Adaptability to changing requirements or ambiguous situations
  • Technical problem-solving and decision-making under constraints
  • Communication and alignment strategies (e.g., regular syncs, documentation)
  • Quantifiable impact on business or team metrics
  • Lessons learned and how you applied them in future projects

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.

Q2

Describe a time you had a conflict with a teammate and how you resolved it.

Conflict Resolution
Author's notes

Had a decent example ready but I undersold the resolution part.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Use the STAR method to structure your answer, focusing on a specific conflict and your role in resolving it. Emphasize collaboration, communication, and a positive outcome that benefited the team and project. Highlight how you maintained professionalism and contributed to a solution.

Pro tip: Show that you view conflict as an opportunity for improvement, not just a problem to solve. Mention how you sought to understand the other person's perspective and adapted your approach to reach a win-win solution.

1. Set the Scene

Briefly describe the project, your role, and the teammate involved. Provide enough context for the interviewer to understand the stakes and the nature of the conflict.

2. Explain the Conflict

Clearly state what the disagreement was about, focusing on the issue rather than personal attacks. Avoid blaming the teammate; instead, describe the differing perspectives or approaches.

3. Describe Your Actions

Detail the steps you took to resolve the conflict, such as initiating a private conversation, actively listening, and proposing compromises. Highlight your communication and problem-solving skills.

4. Share the Resolution

Explain how the conflict was resolved, emphasizing the collaborative effort and the positive outcome for the project and team dynamics.

5. Reflect and Learn

Conclude with what you learned from the experience and how it has improved your ability to handle similar situations in the future.

Key Points to Mention

  • Specific example with clear context (project, role, teammate)
  • Focus on the issue, not personal differences
  • Active listening and empathy to understand the teammate's perspective
  • Collaborative problem-solving and compromise
  • Positive outcome for the project and team relationship
  • Lesson learned and application to future situations

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.

Q3

Can you give an example of a time you shared knowledge with your team or helped a colleague grow?

Cross-functional Alignment
Author's notes

Easier than the conflict one for me.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Use the STAR method to describe a specific instance where you proactively shared knowledge or mentored a colleague, focusing on the actions you took and the positive outcomes for the individual and the team. Emphasize how this contributed to team success and alignment with business goals, especially in a financial services context.

Pro tip: Quantify the impact where possible (e.g., reduced onboarding time by 20%, increased team velocity) and highlight how your knowledge sharing improved cross-functional collaboration or code quality, which is highly valued at JP Morgan.

1. Set the Context

Briefly describe the situation: the team, the project, and the colleague's challenge or knowledge gap. Mention why sharing knowledge was important for the team's success.

2. Explain Your Approach

Detail the specific actions you took to share knowledge or help the colleague grow. This could include pair programming, creating documentation, conducting workshops, or one-on-one mentoring.

3. Highlight the Outcome

Describe the results of your efforts: how the colleague improved, how the team benefited, and any measurable impact (e.g., faster delivery, fewer bugs, improved collaboration).

4. Connect to Broader Impact

Relate the example to the role at JP Morgan: emphasize how knowledge sharing fosters cross-functional alignment, innovation, and a culture of continuous learning.

Key Points to Mention

  • Specific knowledge shared (e.g., new technology, best practices, domain expertise)
  • Method of sharing (e.g., pair programming, documentation, workshops, code reviews)
  • Colleague's growth and improved performance
  • Team or project outcomes (e.g., increased efficiency, better code quality)
  • Alignment with JP Morgan's values (e.g., collaboration, excellence, integrity)
  • Measurable results or recognition received

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.