Because you are comparing your inside, full of confusion, with their outside, which only shows the finished answer. Feeling slow next to stronger engineers is what learning quickly feels like. Treat the gap as information, not a verdict, and use it: watch how they think, ask better questions, and measure yourself against last month rather than against them.
What people tell me
I recently joined a team, or started working on a project with engineers far more experienced than me. In meetings they talk about things I have never heard of, they find bugs in minutes that would take me days, and they review my code with comments I do not fully understand. I have started to feel stupid and I avoid asking questions because I do not want them to see how little I know. I wonder whether I am in the wrong place.
A composite of the messages behind this question, with personal details left out.
Key takeaways
- Being the least experienced person in the room is the fastest place to learn, even though it feels like the worst.
- Stronger engineers usually are not smarter. They have seen more failures and recognise patterns you have not met yet.
- Write down every term you do not understand and look them up that evening. The list shrinks faster than you expect.
- Ask questions that show your thinking, not just your confusion.
- Compare yourself with who you were a month ago, not with someone who has ten more years of mistakes behind them.
You are seeing the answer, not the work
When a senior engineer finds a bug in five minutes, you see the five minutes. You do not see the dozens of similar bugs they fought for days, years ago, which is exactly why this one took five minutes. Experience in software is mostly pattern recognition. They are not solving the problem from scratch. They are remembering.
Meanwhile you see all of your own confusion in full detail. You are comparing your messy inside with their polished outside, and nobody wins that comparison.
I have felt this in every new team I joined, including after many years in the industry. The feeling does not mean you are in the wrong place. Often it means you are in exactly the right place.
Feeling stupid is not the same as being stupid
Here is a test I give people. Ask yourself:
- Do I understand things this week that confused me a month ago?
- Are my review comments getting smaller or more specific?
- Can I now finish some tasks without asking anyone?
If the answer to any of these is yes, you are learning at a healthy speed. The feeling of being slow is simply what fast learning feels like from the inside, because you are constantly at the edge of what you know.
If the answer to all of them is no after two or three months, that is worth attention, but it is a signal to change how you learn, not a verdict on your ability.
Turn the gap into a curriculum
The engineers around you are the best learning resource you will ever have, and they are free. Use them deliberately:
- Keep an unknowns list. Every time you hear a term, tool or idea you do not know, write it down. Spend twenty minutes each evening on two or three items. Within a month the meetings sound very different.
- Read their pull requests. Not just yours. Look at how they name things, how they split changes, what they test, and what they write in the description.
- Study their review comments on your code. Group them. If three comments are about error handling, that is your next topic.
- Watch them debug. Ask if you can sit in, or share a screen, when they investigate an issue. Notice what they check first. That order is the skill.
How to ask without feeling exposed
Most people who feel stupid stop asking questions, which makes the problem worse. The fix is not to ask fewer questions. It is to ask better ones.
Compare these two messages:
I do not understand how the payment service works.
I am tracing how a refund reaches the payment service. I can see the request leave the orders API, but I cannot find where it is consumed. Is it through the queue, and if so, where should I look?
The second one shows effort, narrows the problem, and takes the senior engineer thirty seconds to answer. Experienced engineers are almost always happy to answer questions like that, and they quietly note that you are someone who tries first.
What stronger engineers notice about you
It rarely occurs to people in your position, but the seniors are not judging you on how much you know. They know you are new. What they notice is:
| They notice | They do not care much about |
|---|---|
| Whether you try before asking | Whether you already knew the tool |
| Whether you repeat the same mistake | Whether you made the mistake once |
| Whether you communicate when stuck | How long a new area takes you at first |
| Whether you follow through | Whether you asked a basic question |
Most of the left column is behaviour, and all of it is within your control from day one.
Protecting your confidence while you grow
A few habits help:
- Keep a weekly wins note. Three lines every Friday: what you shipped, what you learned, what you understood that you did not before. On bad days, read it.
- Pick one area to own. It could be a small module, the test setup, or documentation for onboarding. Becoming the person who knows one thing well changes how you feel in the room.
- Stop reading silence as judgement. A senior engineer who does not reply quickly is busy, not disappointed.
- Talk about it with someone outside the team. A peer or mentor can remind you that everyone goes through this.
When it might be a real mismatch
Occasionally, the gap is too large for the support available: you are the only junior, nobody reviews your code, and questions go unanswered for days. That is a team problem rather than a you problem. Raise it with your manager as a request, for example asking for a regular pairing session or a clearer onboarding path. If nothing changes over a few months, it is reasonable to look for a team that invests in growing people.
If you are still stuck
Read What Actually Changes in Your First Two Years as an Engineer and The Habits That Make an Engineer Worth Routing Work Through. You might also find the question on feeling not good enough for tech useful. If you want someone to look at your specific situation, join Sefism and, as a member, book a 1:1 session.
Was this answer helpful?
Read next
- What Actually Changes in Your First Two Years as an EngineerInterviews test the small part of the job that is easy to test, and the rest is learned on site. Reading code as the main skill, how to ask a question that costs nothing, why small shipped changes beat large ones in progress, using code review as the fastest teaching you will get, and the four things that actually get people promoted, three of which are not about writing code.
- The Habits That Make an Engineer Worth Routing Work ThroughEvery team has one or two engineers other people route work through, and what they have in common is not raw technical strength. It is that when something is given to them it comes back, and when it will not, you hear about it early. Fifteen habits that build that reputation, none of which require a title or permission.
Your situation is not quite this one?
Members get written answers to their own questions, a roadmap built for them and feedback on their projects. Early access is open to X and Instagram followers and university students. Prefer to talk? A free call works too.