How I Managed Impostor Syndrome in My First Year as a Software Engineer
I recall beginning my first job with a fantastic organization. It was a very fantastic opportunity for me to work on a real-world project that will influence millions, or perhaps thousands, of users. I recall that I had spent some time studying, attending tutorials, and getting ready to present myself as outstanding and smart. But I came to understand that during the first few weeks of my employment, I had a constant sense of not being prepared and good enough.
These feelings might even appear as fears about being a self-taught developer (not having a structured learning experience ); not having a degree in computer science; running out of time to study a code; not fully comprehending some concepts before commencing your first task; also having realized that my coworkers performed significantly more quickly than I did; panicking that you might lose your job if you aren’t keeping up; or even starting to wonder how to keep track of the countless checks on your few code submission.
If not handled appropriately, imposter syndrome is very real and can negatively affect confidence
Having worked in the field for a while, I took some time to reflect on my journey so far and realized that these sensations are pretty typical. The reality is, that whenever I begin a new project or job, Imposter syndrome starts knocking on my mind.
My conclusion is that It is simply another of those things that will eventually vanish.
If at any point in your career, but especially in the beginning, you felt this way. Here’s some advice that I utilize whenever I feel this way:
- Never be too harsh on yourself.
It wasn’t by accident that you got the position in the first place; it meant you were deserving of it. Remember that your employer selected you to work for them and that you are therefore just as valuable as everyone else around you. There may be a number of skills you need to develop, but the one you always had got you the first job. Perfectionism may be a sign of a positive desire to give your finest effort. The idea is to avoid becoming sentimental about the situation as it is to the point you begin to distrust your current ability. Everyone wants to perform at their best when it matters most, free from the burden of moving in a loop when working on a task, but you must also be willing to give your time to grow.
Trust me, it can take some time to gain confidence in anything you’re doing for the first time, but we can all achieve it by achieving one small triumph at a time. As a result, whenever I’m given new, difficult work to do, I reflect on my past accomplishments and how I’ve handled similar challenges effectively. I feel better and more confident because of that.
Here are a few encouraging statements. I constantly state whether I feel that way frequently or always.
- I always find the right code for the program.
- Every day, writing innovative code is easier and easier for me.
- I get great ideas with little effort.
- My creativity flows from me like a river.
- I have always been very intelligent
- I am naturally innovative and creative
- I trust my own ability to solve problems
- I always investigate all possible solutions
- I am naturally enthusiastic about what I do
- I see myself as an extraordinary engineer
2. Ask other engineers questions
When I finally found the courage to approach other engineers and solicit their help or advice, I noticed that things started improving. I was able to see how other people approach issues and arrive at solutions. It’s not expected that everyone has all the information. You can ask for help. — Every senior you work with was once a junior.
“Grown-ups don’t look like grown-ups on the inside either. Outside, they’re big and thoughtless and they always know what they’re doing. Inside, they look just like they always have. Like they did when they were your age. Truth is, there aren’t any grown-ups. Not one, in the whole wide world.”
When I started talking to other developers and mentors about the difficulties I experienced at various times, I realized I was not the only one going through this and that someone else, who today appeared to be so successful, had also gone through the same thing.
Seniors who were always willing to assist me with my inquiries helped me overcome my anxieties and doubts when I was faced with roadblocks. Even when I wasn’t sure if I was right or wrong, they were there to answer my questions.
Finally, I was careful to take notes during this process to ensure that I learned from the responses and would not ask the same questions later.
3. Work on a side project related to your present role.
In the long run, overcoming imposter syndrome may be possible with the help of this strategy, especially for confidence building. I attempted to integrate all the technologies into a side project that was in line with my company’s area. Once I identified the technologies involved in the job I was working on ( for example, a fintech, eCommerce, or logistics domain), I commence a side project.
When I had a challenge with a task, I realized that the expertise I had gained from utilizing it in my side project could be applied to the current task. This allowed me to get a better grasp of a specific usage and scenario. I reached a point at work when I was no longer coding on the side project; instead, I was just strengthening my mastery of concepts I had already covered.
“Imposter Syndrome is like the boogie man: Open the closet, turn on the lights, look around, and you see that nothing is there.
Scott Roberts — Github Security Engineer
For reading, I’m grateful. If imposter syndrome is something you are experiencing or have experienced in the past, I hope this post will be very helpful and encouraging.
Appreciate, clap, share, and follow. I sincerely appreciate it.
