Section 1 - Instruction

You've learned that competence and commitment are separate dimensions. Now let's practice identifying these signals in real engineering team situations.

Remember, competence shows in code quality and technical knowledge, while commitment appears in motivation and confidence around technical work.

Engagement Message

Ready to test your observation skills?

Section 2 - Practice

Type

Swipe Left or Right

Practice Question

Which behaviors indicate competence versus commitment? Swipe each behavior to match the correct dimension.

Labels

  • Left Label: Competence
  • Right Label: Commitment

Left Label Items

  • Writes efficient, maintainable code
  • Debugs complex issues quickly
  • Catches bugs during code reviews
  • Explains technical concepts clearly

Right Label Items

  • Volunteers for challenging technical problems
  • Stays late to perfect code quality
  • Proactively learns new technologies
  • Shows excitement about architecture discussions
Section 3 - Practice

Type

Multiple Choice

Practice Question

Sarah consistently delivers clean, well-tested code and helps teammates resolve technical blockers during standups. However, she frequently says "Just assign me whatever ticket is next" and rarely participates in sprint planning discussions or suggests technical improvements.

What does this pattern suggest about Sarah?

A. High competence, high commitment B. High competence, low commitment
C. Low competence, high commitment D. Low competence, low commitment

Suggested Answers

  • A
  • B - Correct
  • C
  • D
Section 4 - Practice
Sign up
Join the 1M+ learners on CodeSignal
Be a part of our community of 1M+ users who develop and demonstrate their skills on CodeSignal