← CIBC Interview Insights

CIBC·Software Engineer·Recruiter / HR Screen·Junior

Junior
Jun 2026

Summary

Behavioral round at CIBC for their tech rotational program, all HR, no technical stuff at all. Pretty standard set of questions but the conflict one tripped me up more than I expected.

Questions Asked (4)

Q1

Tell me about a time you had to pick up a new skill quickly. What was your approach and how did it go?

Adaptability & Ambiguity
Author's notes

Went with a story from a course project where I had to learn a framework in like two weeks.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Use the STAR method to tell a concise story about a specific time you had to learn a new skill quickly. Focus on your learning process, the actions you took, and the measurable outcome, while highlighting how you managed ambiguity and delivered results.

Pro tip: Choose a skill that is directly relevant to the role or CIBC's tech stack (e.g., a new programming language, framework, or domain like banking). Quantify the outcome to show impact, and briefly mention what you learned from the experience to demonstrate growth.

1. Set the Context

Briefly describe the situation: what new skill was needed, why it was urgent, and what was at stake. Keep it concise to focus on your actions.

2. Explain Your Learning Approach

Detail the steps you took to learn quickly: e.g., breaking down the skill, using official docs, tutorials, mentors, or hands-on practice. Show resourcefulness and prioritization.

3. Highlight Application and Challenges

Describe how you applied the new skill in a real task or project. Mention any obstacles you overcame and how you adapted your approach.

4. Share the Outcome

State the results: what you achieved, how it benefited the team or project, and any metrics (e.g., time saved, bugs reduced, feature delivered).

5. Reflect and Connect

Summarize what you learned and how it has made you more adaptable. Relate it to the role or CIBC's values, showing you can handle future challenges.

Key Points to Mention

  • A specific, relevant skill (e.g., a new programming language, framework, or domain knowledge)
  • Your structured learning process (e.g., online courses, documentation, pair programming, prototyping)
  • Time pressure or ambiguity and how you prioritized
  • Collaboration with others (e.g., asking mentors, knowledge sharing)
  • Measurable outcome (e.g., delivered feature on time, improved performance, reduced errors)
  • Lesson learned or how you've applied this adaptability since

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

Q2

Walk me through an internship project you worked on, including your role, the decisions you made, and what the impact was.

Stakeholder ManagementCross-functional Alignment
Author's notes

This one I was ready for.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Choose an internship project that clearly demonstrates your technical contributions and collaboration with stakeholders. Structure your answer using the STAR method, emphasizing your specific role, key decisions, and measurable impact. Highlight how you aligned cross-functional teams and managed stakeholder expectations to deliver results.

Pro tip: Quantify your impact with metrics (e.g., reduced processing time by 30%) and mention how you incorporated feedback from non-technical stakeholders to ensure the solution met business needs.

1. Set the Context

Briefly describe the project, its goals, and the team structure, including your role and the stakeholders involved.

2. Explain Your Role and Actions

Detail your specific responsibilities and the key technical decisions you made, such as choosing a framework or designing an API.

3. Highlight Cross-Functional Collaboration

Describe how you worked with other teams (e.g., product, QA, business analysts) to gather requirements, resolve issues, and align on deliverables.

4. Discuss Challenges and Solutions

Mention any obstacles (e.g., conflicting priorities, technical constraints) and how you navigated them through communication and compromise.

5. Quantify the Impact

Conclude with the project's outcomes, using metrics (e.g., time saved, bugs reduced, user adoption) and how it benefited the business or users.

Key Points to Mention

  • Specific technical skills used (e.g., Python, React, SQL) and how they contributed to the project.
  • Examples of stakeholder management, such as regular updates, demos, or feedback sessions.
  • Cross-functional alignment: how you ensured different teams were on the same page.
  • Key decisions you made and their rationale (e.g., choosing a library, optimizing a query).
  • Measurable impact (e.g., reduced load time by 40%, increased test coverage to 90%).
  • Lessons learned and how they apply to future software engineering roles.

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

Q3

Describe a conflict you had with a teammate or manager. How did you resolve it and what did you take away from it?

Conflict Resolution
Author's notes

Harder than I thought it would be.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Choose a real, low-stakes conflict where you and the other person disagreed on a technical or process decision. Use the STAR method to describe the situation, your actions to resolve it, and the positive outcome. Emphasize collaboration, active listening, and what you learned about working with others.

Pro tip: Avoid blaming the other person; instead, show how you sought to understand their perspective and found a mutually beneficial solution. Mention that you followed up to ensure the relationship remained strong.

1. Set the context

Briefly describe the project, your role, and the nature of the conflict (e.g., disagreement over code architecture, deadlines, or priorities). Keep it concise and neutral.

2. Explain the conflict

State the opposing viewpoints without assigning blame. Focus on the issue, not personalities, and show that you understood the other person's perspective.

3. Describe your actions

Detail the steps you took to resolve the conflict, such as scheduling a one-on-one, actively listening, proposing a compromise, or escalating appropriately. Highlight your communication and problem-solving skills.

4. Share the outcome

Explain how the conflict was resolved and the positive result for the team or project. Mention if the relationship improved or if you delivered successfully.

5. Reflect on takeaways

Summarize what you learned and how you've applied that lesson in subsequent situations. Show growth and self-awareness.

Key Points to Mention

  • Active listening and empathy for the other person's perspective
  • Focus on the problem, not the person
  • Collaboration and compromise to find a win-win solution
  • Professional communication and emotional intelligence
  • Positive outcome for the team or project
  • Personal growth and application of the lesson learned

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

Q4

Tell me about a time you were working against a tight deadline. How did you decide what to prioritize and what trade-offs did you end up making?

Roadmap PrioritizationAdaptability & Ambiguity
Author's notes

Solid story here, used a capstone project crunch.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Use the STAR method to describe a specific project with a tight deadline, focusing on how you assessed urgency, impact, and dependencies to prioritize tasks. Highlight the trade-offs you made (e.g., scope reduction, technical debt, testing depth) and the outcome, emphasizing communication with stakeholders and lessons learned.

Pro tip: Quantify the impact of your prioritization and trade-offs (e.g., 'delivered core features 2 days early, allowing time for critical bug fixes') to demonstrate business acumen. Also, mention how you documented technical debt for future sprints, showing you balance short-term delivery with long-term code health.

1. Set the Context

Briefly describe the project, the tight deadline, and why it was critical (e.g., regulatory requirement, client demo, production incident).

2. Assess and Prioritize

Explain how you evaluated tasks based on impact, urgency, and dependencies. Mention any frameworks (e.g., MoSCoW, Eisenhower Matrix) or tools (e.g., Jira, Trello) you used.

3. Decide Trade-offs

Describe the trade-offs you made, such as reducing scope, deferring non-critical features, or accepting temporary technical debt. Explain your rationale.

4. Execute and Communicate

Detail how you communicated decisions to stakeholders, adjusted plans as needed, and kept the team aligned to meet the deadline.

5. Reflect on Outcome

Share the results (e.g., met deadline, positive feedback) and what you learned, including how you addressed any trade-offs post-deadline.

Key Points to Mention

  • Use of prioritization frameworks (e.g., MoSCoW, impact/effort matrix) to make objective decisions.
  • Specific trade-offs: reducing scope, deferring features, or accepting technical debt with a plan to address later.
  • Communication with stakeholders: keeping them informed, managing expectations, and negotiating deadline or scope.
  • Collaboration with team: delegating tasks, pair programming, or swarming on critical issues.
  • Quantifiable outcome: meeting the deadline, delivering key functionality, or achieving business impact.
  • Post-mortem or lessons learned: how you prevented similar issues or improved processes.

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