Skip to content

Course home

Research methods and techniques

Research methods and techniques

EasyMediumHard
123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225
Question 198

Why do junior software developers report higher levels of "imposter syndrome" in daily stand-up meetings?

Studies show a persistent gap in self-assessed competence among software engineers during agile development ceremonies. Analysis of data from the Tech Careers Cohort Survey showed a 22-point gap in reported confidence regarding technical contribution during daily stand-ups between junior developers (under 2 years of experience) and mid-level developers, which narrows by only 5 points after another year of employment.

Why does this confidence gap exist?

One reason is the high-visibility nature of agile framework practices. The principle of social comparison suggests that daily, public verbal updates make individuals highly sensitive to peer evaluation. When junior developers hear senior colleagues describe highly complex tasks, they are less likely to envision themselves as capable contributors.

Another factor is self-perception. Multiple self-report surveys have shown that:

  • junior developers tend to rate their programming proficiency as significantly lower than their peers, even when working on identical tasks
  • when objective code-quality metrics and ticket-completion rates are analyzed, junior developers perform almost identically to mid-level developers in terms of bug rates and delivery speed
  • junior developers are highly likely to select the "unsure of my approach" option on self-assessment surveys, even when their code passes all automated tests first time.

This suggests that junior developers’ lower self-reported scores are driven by a lack of confidence (imposter syndrome) rather than a lack of competence.

A 2022 study by the Munich Software Institute revealed a strong correlation between psychological safety indicators within engineering teams and junior developers' self-reported confidence. Tech companies ranking highest in psychological safety displayed the smallest disparity in self-efficacy scores.

(Source: Adapted from a contemporary social science magazine article)


One methodological issue raised in this article is the validity of research using self-report.

With reference to the article:

a.

Explain one strength of using self-report for this type of research.

[2]
b.

Explain one weakness of using self-report for this type of research.

[2]
Markscheme

Research methods and techniques Questions

  1. A Level
  2. /Psychology
  3. /Research methods and techniques

644 exam-style questions on OCR A Level Psychology Research methods and techniques. Each one has a worked solution and a mark scheme showing where the marks go.

Question bank