Dr. Carol Langlois: How to Tackle Imposter Syndrome at Work

In this first-ever episode of Women Driving Impact, author and former VP of Hackbright Academy Dr. Carol Langlois shares how connecting women with one another is driving real, positive change for tech companies. Brought to you by Kintone, a cloud-based, collaborative app building workspace to accelerate innovation and problem-solving at organizations.

https://podcasts.apple.com/us/podcast/dr-carol-langlois-how-to-tackle-imposter-syndrome-at-work/id1456561728?i=1000432130160

unnamed.jpg

Impostor Syndrome and Women in Tech

The term Impostor Syndrome gets tossed around a lot these days.  I thought I’d share with you the origins of this concept, what it really means and how to gauge if you exhibit any Impostor Syndrome characteristics.

The Origins of IP

53d2a8dfa8a0a693e8e87c5cfeaa04b2.jpg

IP (Impostor Phenomenon) was coined by Pauline Rose Clance, Ph. D in the late 70’s after she strangely experienced feeling like a fraud amongst her peer group in grad school, but couldn’t explain why.  She thought that she would fail exams even though she was well prepared, she felt other students around her were smarter than her and that she was passing her classes based on luck and was really just a “fraud” in school.

Later in life when she was teaching at a University, she realized that a lot of her female students had similar thoughts and feelings that she had when she was in grad school. Here she began her research on this topic and the originals of Impostor Phenomenon began.

Impostor syndrome (also known as impostor phenomenon or fraud syndrome or the imposter experience) is a concept describing high-achieving individuals who are marked by an inability to internalize their accomplishments and a persistent fear of being exposed as a "fraud". Despite external evidence of their competence, those exhibiting the syndrome remain convinced that they are frauds and do not deserve the success they have achieved. Proof of success is dismissed as luck, timing, or as a result of deceiving others into thinking they are more intelligent and competent than they believe themselves to be. Some studies suggest that impostor syndrome is particularly common among high-achieving women.[2]

Psychologists hypothesis that Impostor Syndrome is most common among high achieving women.  Interestingly, many women experience it for the first time while in graduate school.  (A very intense and high stress experience.)

It’s not surprising that we see Impostor Syndrome among women at coding bootcamps since bootcamps are (in many ways) similar to graduate school.

  • The expectations are higher

  • The lessons move very quickly

  • There is a lot of work outside the classroom

  • You need deep focus & discipline to succeed

  • You get very little sleep

  • It's a highly competitive environment.

Further research also shows that IP can be even more pervasive among women of color from marginalized populations. The research regarding Impostor Syndrome has traditionally highlighted groups who are “excelling in areas that were not always readily accessible to them”.[2]

This would certainly be applicable to women in tech.  (A culture dominated my males where female credibility can be tested on a constant basis.)  We hear stories of female software engines being the only female on their team, sometimes second guessed by their bosses, and even asked if a project was in fact “their own work”.   This is a high stakes environment where women are not always expected to necessarily succeed. Knowing more about IP and how it works can be helpful in understanding your own thoughts and views regarding your own success.

Here are a few sample questions from Dr. Clance's  Impostor Phenomenon scale. 

  1. I have often succeeded on a test or task even though I was afraid that I would not do well before I undertook the task.

         (not at all true)    (rarely)    (sometimes)   (often)   (very true)

       2. I can give the impression that I’m more competent than I really am.

        (not at all true)    (rarely)    (sometimes)   (often)   (very true)

       3. I avoid evaluations if possible and have a dread of others evaluating me.

        (not at all true)    (rarely)    (sometimes)   (often)   (very true)

*Sample questions may not be representative of the entire 20-item scale. To access FULL scale permission, please contact Dr. Clance (drpaulinerose@comcast.net).  

When Should I Introduce my Child to Code?” 

unknown1.jpg

Introducing Kids to Code.

As a former VP at Hackbright Academy, (the leading coding school for women) people always ask, “What is the best age to introduce my child to code?”  My answer.… “As soon as possible!”  The same goes for all the STEM sciences (Science, Tech, Engineering and Math.)   It’s never to early to introduce a child to something new. The next question they ask is always– How?

Every child is different, but why not expose them to “all things science” early on in a fun way.  There are: science museums, science based board games and video games, science based TV shows, experiments you can watch on Youtube, great tutorials by Khan academy, coding camps for kids, and the list goes on.  The earlier any child is exposed to something new, the more it opens their eyes to possibility. It makes them curious about the world.  First hand exposure is always a great tool and it provides a safe environment for children to ask questions if they are a bit shy.

The other day I passed a dad and daughter on the street.  They were crouched down on the sidewalk looking at something. (I’d say the daughter was about 7 years old.) Once I got closer, I could see that they were inspecting an acorn.  A very large and lonely acorn that seemed out of place on such a busy city street.  Where did it come from? The dad was talking about what an acorn is, what it does, the shell, how it will sprout, etc. He was also taking the time to answer all his daughter’s questions. It was a wonderful exchange and teachable moment that they were both clearly enjoying. He didn’t rush by the acorn on the sidewalk, he stopped and took notice of his daughter’s curiosity.  He used the opportunity to teach her about nature.  This type of time and patience helps ignite curiously in kids. So, introduce your child to code (or any science) when you are ready to dive in and be part of the conversation with them. If they see that you are engaged and curious then they will be too.

If you need help identifying some great resources for your child, just reach out! 

Dr. Carol