> Markdown version of [/videos/863-what-makes-a-great-software-engineer-challenging-our-assumptions-instead-of-talking-about-imposter-syndrome](https://www.wearedevelopers.com/videos/863-what-makes-a-great-software-engineer-challenging-our-assumptions-instead-of-talking-about-imposter-syndrome). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# What makes a great Software Engineer? Challenging our Assumptions Instead of Talking about Imposter Syndrome

Bad software isn't a technical problem; it's a communication problem. Stop treating imposter syndrome as an individual failing and start valuing empathy as a core engineering skill.

- **Speakers:** Irina Anastasiu
- **Event:** WeAreDevelopers LIVE
- **Published:** March 13, 2024
- **Duration:** 55:07
- **URL:** https://www.wearedevelopers.com/videos/863-what-makes-a-great-software-engineer-challenging-our-assumptions-instead-of-talking-about-imposter-syndrome

## Summary

The tech industry often equates technical ability with an obsession for obscure coding trivia, feeding imposter syndrome and driving diverse talent away from software engineering. Rather than treating imposter syndrome as an individual failing, challenging the underlying stereotype of the isolated, obsessive geek reveals that modern engineering requires a much broader spectrum of problem-solving capabilities. A narrow focus disproportionately harms women and pushes highly capable systems thinkers into product management or design roles where their core technical insights are lost. To build resilient products, engineering teams must embrace cognitive diversity beyond the traditional optimizer archetype, which strictly seeks a single correct technical answer. Using Basadur’s problem-solving framework, effective software development equally relies on generators who navigate ambiguity, conceptualizers who connect abstract ideas with business logic, and implementers who test assumptions in the real world. Acknowledging these diverse styles shifts the focus from dogmatic debates over microservices versus monoliths toward true creative problem-solving. Ultimately, bad software is not a technical problem; it is a communication problem. Recognizing empathy, cross-functional collaboration, and big-picture glue work as core technical skills prevents teams from blindly building elegant solutions for the wrong business use cases. By fixing the systemic bias rather than the individual, organizations can build inclusive engineering cultures that retain senior technical talent and foster high-performing, adaptable agile teams.

**Keywords:** imposter syndrome in tech, cognitive diversity in engineering, basadur problem solving framework, software engineering stereotypes, technical interview bias, agile team communication, engineering talent retention, glue work in software development, women in tech inclusion, cross-functional collaboration, architecture dogma pitfalls, engineering team dynamics, tech industry gender bias, inclusive engineering culture, developer problem solving archetypes

## Chapters

1. **Exploring the archetype of a good software engineer** (00:02) — Understanding the traits of a great software engineer requires looking beyond traditional coding skills.
1. **How the geek stereotype fuels imposter syndrome** (02:12) — The persistence of the obsessed coding introvert archetype makes feeling a sense of belonging difficult for others.
1. **Broadening the definition of technical problem solving** (07:12) — Valuing communication and conceptualization equally to purely technical abilities improves diversity and product quality.
1. **Navigating real world software architecture collaboration** (09:34) — Bad software is often a communication problem that requires defining actual business needs before implementation.
1. **Exploring Basadur problem solving styles and archetypes** (14:51) — Individuals possess distinct preferences for gaining and utilizing knowledge across four problem-solving quadrants.
1. **Applying problem solving archetypes to engineering teams** (17:42) — Combining different working styles like generators and optimizers creates more robust and well-rounded software solutions.
1. **Redefining technical competence beyond traditional framework trivia** (21:50) — True technical capability can be demonstrated by inventing dynamic concepts rather than relying on memorized jargon.
1. **Mapping team roles to problem solving archetypes** (24:55) — Plotting individual roles onto problem-solving quadrants helps visualize and appreciate cognitive diversity in the workplace.
1. **Reflecting on engineering motivations and undervalued strengths** (34:27) — Critical non-technical skills like empathy and communication often drive success but remain frequently overlooked in technical environments.
1. **Fostering inclusivity and networking for women in tech** (52:19) — Company initiatives and dedicated communities play a crucial role in supporting and retaining female engineers.

## Related Moments

- [Overcoming engineered biases to achieve equal technology representation](https://www.wearedevelopers.com/videos/549-keynote-hidden-histories) (from "KEYNOTE: Hidden Histories")
- [Debunking the stereotype of the introverted software engineer](https://www.wearedevelopers.com/videos/1494-breaking-the-ice-debunking-myths-between-recruiters-and-developers) (from "Breaking the Ice: Debunking Myths Between Recruiters and Developers")
- [Mitigating groupthink through diverse and inclusive software engineering teams](https://www.wearedevelopers.com/videos/43-algorithmic-bias-preventing-unfairness-in-your-algorithms) (from "Algorithmic Bias- Preventing Unfairness in your Algorithms")
- [Exploring the impact of diverse teams on engineering outcomes](https://www.wearedevelopers.com/videos/1760-inspiring-young-people-and-their-parents-to-become-programmers-cassandra-chin) (from "Inspiring Young People (and Their Parents) to Become Programmers - Cassandra Chin")
- [Overcoming imposter syndrome without immediate representation in tech communities](https://www.wearedevelopers.com/videos/533-the-power-of-the-community) (from "The power of the community")
- [Reframing imposter syndrome and cognitive dissonance in tech](https://www.wearedevelopers.com/videos/907-is-everything-difficult-or-is-it-just-me) (from "Is everything difficult, or is it just me?")

## Related Articles

- [Women in Tech: Navigating Career Transitions and Breaking Barriers](https://www.wearedevelopers.com/magazine/491-women-in-tech-navigating-career-transitions-and-breaking-barriers)
- [Top Characteristics of a Software Engineer](https://www.wearedevelopers.com/magazine/166-top-characteristics-of-a-software-engineer)
- [What is Software Engineering in the Age of AI?](https://www.wearedevelopers.com/magazine/640-what-is-software-engineering-in-the-age-of-ai)
- [Navigating the AI Shift](https://www.wearedevelopers.com/magazine/629-navigating-the-ai-shift)

## Related Jobs

- [Tribe Lead - ( Software) Engineering Centre of Excllence](https://www.wearedevelopers.com/jobs/ext/1475530-tribe-lead-software-engineering-centre-of-excllence) at **SD Worx**
- [Principal Software Engineer, Enterprise AI Platform](https://www.wearedevelopers.com/jobs/ext/1467292-principal-software-engineer-enterprise-ai-platform) at **GitHub**
- [Senior Engineer, Infrastructure Platform](https://www.wearedevelopers.com/jobs/ext/328836-senior-engineer-infrastructure-platform) at **Intercom, Inc.**
- [Principal Software Engineer, Database Infrastructure](https://www.wearedevelopers.com/jobs/ext/1465908-principal-software-engineer-database-infrastructure) at **GitHub**
- [Principal Software Engineer, Identity](https://www.wearedevelopers.com/jobs/ext/1469181-principal-software-engineer-identity) at **GitHub**
- [Staff Software Engineer, Database Infrastructure](https://www.wearedevelopers.com/jobs/ext/1470125-staff-software-engineer-database-infrastructure) at **GitHub**