Impostor Syndrome for CS Students and Junior Developers: What Helps

Impostor syndrome in tech: when you feel like everyone else belongs except you

You got into a computer science programme, or you landed your first developer job, and somewhere along the way a quiet voice started saying: they made a mistake letting you in. Your classmates seem to understand pointers on the first try. The senior engineer in your team fixes in ten minutes what took you a whole day. On LinkedIn, people your age are posting about Google internships and open source contributions while you are still trying to get your React app to deploy.

If that sounds familiar, you are not broken and you are not alone. What you are describing has a name, a long research history, and, more usefully, some practical ways out. This post explains what impostor feelings are, why they are so common in tech, and what actually helps when you are a CS student or a junior developer in Lahore, Pune, Dhaka, Nairobi or anywhere else.

What impostor syndrome actually is

The idea comes from a 1978 paper by two psychologists, Pauline Rose Clance and Suzanne Imes, called The Imposter Phenomenon in High Achieving Women (published in Psychotherapy: Theory, Research and Practice, 1978). They worked with women who had degrees, awards and good jobs, yet were convinced they were not really intelligent and had fooled everyone. Their successes, in their own minds, were down to luck, charm or a mistake in the selection process.

Three things are worth knowing about that original idea:

• They called it a phenomenon, not a syndrome. It is not a medical diagnosis. You will not find "impostor syndrome" in the manuals doctors use. It is a pattern of thinking and feeling.
• It is about high achievers. The people who feel like frauds are usually the ones who have done well enough to be somewhere they fear they do not belong.
• It is not only women. Later research found it across genders and ages. A 2020 systematic review in the Journal of General Internal Medicine found reported rates between 9% and 82%, depending heavily on how it was measured, with particularly high rates among ethnic minority groups (Bravata et al., 2020). The same review linked impostor feelings with anxiety, depression and burnout, which is why it is worth taking seriously rather than laughing off.

The common pattern looks like this: you get a task, you feel anxious that you will be found out, you either over-prepare or put it off, you do fine, and then you explain the success away. "The exam was easy." "The interviewer was kind." "Anyone could have built that." The success does not land, so the next task feels just as scary. That loop is the thing to break.

Why it is so common in tech

Software is almost designed to produce impostor feelings. A few reasons:

The field is enormous and keeps moving. Nobody knows all of web development, let alone all of computing. Senior engineers google basic syntax every day. But as a student you do not see that; you only see the confident answer in class or the polished project on GitHub.

You compare your inside with other people's outside. On LinkedIn you see offer letters, never the 40 rejections before them. In class you hear the one student who answers every question, not the 30 who are as lost as you. Social media turns this into a constant highlight reel, and a highlight reel is a terrible benchmark.

Feedback in tech is blunt and frequent. Compilers fail, tests go red, code reviews come back with twenty comments. If you treat every red test as a verdict on your worth, you will feel like a fraud several times a day.

Many people start from behind. If you studied in Urdu, Hindi or Bangla medium, came from a small city, did not have a laptop until university, or are the first in your family to study computing, you may genuinely be catching up on things others learnt earlier. That is a gap in exposure, not ability, but impostor feelings blur the two.

The job market is tight. When junior roles are scarce, rejections pile up, and it is easy to read each one as proof that you were never good enough. Usually it is proof that there were 800 applicants for two roles.

Impostor feelings or a real skill gap?

This is the question that helps most, so be honest with yourself. Sometimes the voice is lying. Sometimes it is pointing, clumsily, at something real.

A real gap has a fix: a course, a project, a question to a senior. An impostor feeling does not go away with more study; you can learn ten frameworks and still feel like a fraud. The trick is to turn the vague feeling into a specific gap where you can, and to stop arguing with the rest.

Practical ways out

None of these is a magic switch. They are habits, and they work slowly, the way going to the gym works slowly.

1. Keep an evidence file

Your brain is very good at remembering mistakes and very bad at remembering wins. So write the wins down. Keep a simple note (Notion, Google Docs, a notebook) and add one line every time you:

• fixed a bug, even a small one
• explained something to a classmate
• got a pull request merged or a positive comment in review
• finished a course module or a project milestone
• did something that scared you, like asking a question in class

After a month, read it. The point is not to feel amazing; it is to give the rational part of your brain some data to argue with. Many engineers keep a "brag document" for performance reviews for exactly this reason.

2. Name the thought, then check it

Cognitive behavioural therapy (CBT) has a simple technique that works well here. When the voice says "I am going to be found out", write the thought down and ask three questions:

1. What is the evidence for this?
2. What is the evidence against it?
3. What would I say to a friend who told me this?

You are not trying to replace the thought with a fake positive one ("I am the best developer in the world"). You are trying to replace it with an accurate one: "I am new, I am slower than seniors at this, and I am improving." Accurate thoughts are much easier to believe.

3. Talk about it with people you trust

Impostor feelings depend on the belief that everyone else is fine. The fastest way to break that belief is to say it out loud to a few people. When you tell a classmate "honestly, I felt completely lost in that algorithms lecture", the most common answer is "oh thank God, me too". Seniors will often tell you they still feel it. That does not make the feeling go away, but it changes what it means: it is a normal part of learning something hard, not proof that you are uniquely bad.

4. Ask questions earlier

Junior developers often stay stuck for hours because asking feels like admitting they are frauds. A useful rule many teams use: try on your own for a set time (say 30 to 60 minutes), write down what you tried, then ask. That way you are not helpless and you are not wasting a day. Asking a good, specific question is a skill senior engineers respect.

5. Change your comparison

Comparing yourself with the top 1% on LinkedIn is like comparing your morning jog with an Olympic sprinter. Compare yourself with yourself six months ago instead. Can you do things now that you could not then? That is the only comparison that tells you anything useful. If social media keeps pulling you into comparison, it is reasonable to mute accounts, limit the app, or check it once a day instead of all day.

6. Be kinder to yourself, on purpose

This sounds soft, but there is good research behind it. Psychologist Kristin Neff's work on self-compassion, and studies like Breines and Chen's 2012 experiments, suggest that people who respond to failure with understanding rather than harsh self-criticism are actually more motivated to improve, not less. Being hard on yourself feels productive, but mostly it makes you avoid the hard things. The free exercises on Self-Compassion.org are a good place to start.

7. Do the scary thing in small doses

Confidence usually follows action, not the other way round. If you wait until you feel ready to answer in class, apply for an internship or open a pull request on an open source project, you may wait for years. Pick the smallest version: one question this week, one application, one small pull request fixing a typo in documentation. Each one is a piece of evidence for your file.

For junior developers in their first job

If you have just started work, a few extra things help:

• Remember why you were hired. Your company did not hire you to know everything. They hired you to learn quickly and become useful. Nobody expects a junior to design the architecture.
• Ask your manager what good looks like. "What would make you say my first three months went well?" turns a vague fear into clear goals.
• Write things down. A personal log of what you learnt each day doubles as your evidence file and makes you better at your job.
• Find a buddy. Another junior who started at the same time, or a slightly more senior engineer, makes the first year much less lonely.

When it is more than impostor feelings

Impostor feelings are common and usually manageable. But if the self-doubt has turned into feeling low most days, losing interest in things you used to enjoy, not sleeping, or thinking that you are worthless or that things are hopeless, that is more than a confidence issue. Please talk to someone: a university counsellor, a doctor, or a mental health professional. The Looking after your mental health roadmap explains how to find help, and if you are ever thinking about harming yourself, use Find A Helpline or your local emergency services straight away. Sefism is not a medical service, and a good professional is worth far more than any blog post.

Build it step by step on Sefism

I built the Building real confidence roadmap for exactly this: impostor feelings, negative self-talk, comparison on LinkedIn and social media, collecting evidence and small wins, and speaking up in class and at work. It is a set of short stages with reflection checks and small actions rather than theory.

Useful companions:

• Self-Compassion.org for Kristin Neff's free exercises
• Ivan Joseph's talk on the skill of self-confidence, a short, practical watch
• Mindset by Carol Dweck, on treating ability as something you grow
• The Speaking and being heard roadmap if your doubts are loudest when you have to talk in class or meetings

My honest read

Almost every good engineer I know has felt like a fraud at some point, and many still do on new projects. The difference is not that they stopped feeling it. It is that they stopped letting it make their decisions. Keep your evidence, ask your questions, compare yourself with last year's you, and keep doing the slightly scary next thing.

FAQ

Is impostor syndrome a mental illness?

No. Clance and Imes described it as a phenomenon, a pattern of thoughts and feelings, not a diagnosis. It can sit alongside anxiety or depression, so if you feel low most of the time, talk to a professional.

Why do I feel like a fraud even when I get good grades?

Because impostor feelings explain success away as luck or easy marking. Keeping a written record of what you did, and checking your thoughts against that evidence, helps the success actually register.

Do senior developers get impostor syndrome?

Yes, often, especially when they move to a new team, a new technology or a bigger role. The field is too big for anyone to know everything.

How do I stop comparing myself to others on LinkedIn?

Remember you are seeing highlights only, limit how often you check, mute accounts that consistently make you feel worse, and compare yourself with where you were six months ago instead.

What is the fastest way to feel more confident as a CS student?

There is no fast way, but the most reliable one is small, regular action: ask one question in class, finish one small project, open one pull request, and write each one down.

Ask your own question

If your situation is different from the ones above, browse the career questions library first; someone has probably asked something close. If not, members can ask Tauseef a question and get a written answer. Create your free Sefism account to save roadmaps and track your progress.

Stay in touch

• LinkedIn: where I share roadmaps, career advice and honest takes on hiring. Follow, or message me.
• X (Twitter): short practical thoughts on engineering and careers.
• Instagram: quick tips and a more personal side.
• Sefism Discord: find peers who are on the same path and happy to talk.
• Sefism on YouTube: walkthroughs and talks.

Cover photo by Chirayu Trivedi on Unsplash.