Section 1 - Instruction

You've learned that psychological safety is crucial for high-performing teams. Now let's practice recognizing the signs that indicate whether your team feels safe to speak up.

These signals often appear in subtle behaviors and team dynamics.

Engagement Message

What signs of psychological safety have you noticed in your engineering team?

Section 2 - Practice

Type

Sort Into Boxes

Practice Question

Sort these team behaviors into the correct psychological safety categories.

Labels

  • First Box Label: High Safety
  • Second Box Label: Low Safety

First Box Items

  • questions approach
  • admits code gaps
  • flags bugs early

Second Box Items

  • hides failures
  • silent in reviews
  • avoids complexity
Section 3 - Practice

Type

Fill In The Blanks

Markdown With Blanks

Fill in the blanks to identify psychological safety indicators.

When engineers regularly say "I don't understand this system" or "I think there's a bug here," this indicates [[blank:high]] psychological safety.

When team members only speak up when directly asked and avoid volunteering technical concerns, this indicates [[blank:low]] psychological safety.

Suggested Answers

  • high
  • low
Section 4 - Practice

Type

Multiple Choice

Practice Question

Which scenario demonstrates the highest psychological safety?

A. Engineers wait for the tech lead to propose solutions first B. Someone questions a potential performance issue in the lead's design C. Everyone quickly approves the architecture to avoid conflict D. People only speak when they're certain the code is perfect

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