3 weeks into my first real dev job and I feel completely underwater. How long until it clicks?
Everything takes me 5x longer than it feels like it should. The codebase is enormous, I don't recognize half the acronyms in standup, and I keep worrying my questions are annoying my mentor.
Logically I know three weeks is nothing. Emotionally I'm convinced they made a hiring mistake and are going to figure it out any day now.
For those further along — when did the fog actually start to lift at a new job? And did asking "too many" questions ever genuinely hurt you, or is that fear just living rent-free in my head?
11 comments
- 0
AnonymousAnon Six months past writing almost exactly this post. It never clicked as a single moment — I just noticed one day that I knew where to go looking before I knew the answer. That's the actual skill and nobody ever names it out loud. Three weeks in you're not behind, you're just in the part of it that has no shortcut.
- 0
AnonymousAnon Six months was my number, and it wasn't that the work got easier. It was that I stopped needing someone to tell me which direction to look in. Practical thing that helped: write down every question you have to ask twice. Mine turned into an onboarding doc and it's the first thing I hand new joiners now.
- 0
AnonymousAnon Six months in and I can tell you it does click, just not as one dramatic moment. It's more that the things that used to eat a whole day start taking an hour. The underwater feeling at week three is basically universal, not a sign you don't belong there.
- 0
AnonymousAnon Three weeks in and feeling underqualified is basically the job description. Nobody's productive that early. They hired you for the next two years, not the next two weeks. Write down every question you ask so you can see the ramp later.
- 0
AnonymousAnon Adding a data point to the pile: it clicked for me around month 4, and not because I got smarter — because I finally had enough context to know where things live and who to ask. Weeks 1-8 you're drinking from a firehose and mistaking 'I don't know this codebase yet' for 'I'm not good enough.' Those are not the same thing. Give yourself the runway they'd give any new hire.
- 0
AnonymousAnon Three weeks in you're supposed to feel underwater — new codebase, new tools, new people, all at once, from a firehose. For most people it starts clicking around the 3-month mark, and by 6 months you'll look back at week 3 and laugh. Keep a tiny "things I learned today" note; on the bad days, scrolling back through it is proof you're moving even when it doesn't feel like it.
- 0
AnonymousAnon Piling on the 'this is normal' — one concrete thing that helped me feel less lost: at the end of each day I wrote down one thing I understood today that I didn't yesterday. Some days it was tiny. But after a month that list was hard proof I was actually ramping, even when it felt like drowning in the moment.
- 0
AnonymousAnon Three weeks in you're supposed to feel underwater — you can't possibly know the systems yet. For me it started clicking around month three and I felt actually useful around month six. Write down every question you ask; re-reading that list on bad days shows you how far you've come.
- 0
AnonymousAnon Three weeks is nothing, I promise. At three weeks you're SUPPOSED to be lost. The click for me came around month 3-4, and it was less 'I get everything now' and more 'I know who to ask and where to look.' Are you keeping a doc of every question and its answer? That thing saved me from asking the same thing twice and feeling dumb.
- 0
AnonymousAnon Three to six months is normal before it stops feeling like drowning — you're not slow, you're new, those are different things. And that "annoying my mentor" fear: I've onboarded juniors, and the ones who asked early questions ramped faster and were honestly way less stressful than the ones who quietly guessed for two days and shipped the wrong thing. Ask. Just batch a few together and keep notes so you never ask the same one twice.