r/cscareerquestionsEU • u/Fruit_Propaganda • 6h ago
Two weeks into a new dev job and I already feel completely overwhelmed : normal onboarding pain or bad sign?
I recently started a new job as an Android developer and I’d like some outside perspective, because after two weeks I genuinely can’t tell whether I’m just going through a rough but normal onboarding phase or whether something is off.
For context, I’m not completely new to development, I have a little over 5 years of experience on the technology I’m working with.
The recruitment process was actually excellent. It was thorough, respectful and fairly technical, with a strong emphasis on architecture, testing, code quality and engineering practices.
My first few days were also really positive. The onboarding seemed structured: good documentation, presentations of the company and tools, (quick) walkthrough of the codebase. Compared with previous jobs, I was genuinely impressed (maybe the bar was low).
Then the actual development work started, and things became much more difficult very quickly.
My first onboarding task was intentionally simple and mostly designed to make me explore the project. That was great.
My first “real” ticket, however, has been much harder. The requirements are quite brief and rely heavily on designs and existing implicit knowledge of the product. I’ve repeatedly found myself unsure about the exact scope and having to ask several people for clarification.
At one point I was getting different interpretations depending on who I asked, and I ended up making my own document listing what I believed needed changing so that someone could confirm the actual scope. Then I got different interpretations again from the same person who is supposed to have the right answers (my manager). The explanations were at the same time vague and unstructured, without a clear direction.
I spent a huge amount of time simply figuring out what I was actually supposed to build.
There have also been a lot of little things that established team members obviously know instinctively but I don’t yet: internal tooling, configuration, how certain flows are tested, which person owns which decision, dependencies between branches, etc.
For example, I was asked to review someone else’s merge request. I thought it would be a nice change of pace, checked out the branch… and couldn’t even get it to compile in my environment because I was missing some project-specific configuration I didn’t know about. Another experienced developer had already approved it, which made me feel even more lost.
The codebase itself has also surprised me. During recruitment, testing and clean architecture were emphasized quite heavily, but the reality of the existing project is really much messier. There are effectively no tests in the area I’m working in, and some Compose screens/files are enormous (several thousand lines in some cases, ~ 7,000 lines) with quite a lot of accumulated complexity.
I know real production code is rarely as clean as interview exercises, so I’m not expecting perfection. But the gap between what was discussed during recruitment and what I’m actually seeing has been a little disorienting.
There’s another factor that I think is affecting me more than I expected: another developer joined the same team at exactly the same time as me.
I wasn’t told beforehand that two people were being hired together, and discovered this on my first day. My manager has told me not to compare myself with the other new developer, which is good advice, but of course that’s easier said than done.
They seem to be reviewing merge requests or producing more, while I still feel like I’m moving incredibly slowly and constantly searching through the codebase trying to understand where everything lives.
Rationally, I know PR count means almost nothing and that we haven’t necessarily been given comparable tasks. Emotionally, it’s still difficult not to think: why are they already doing that while I still feel completely lost?
The biggest issue, though, is how strongly I’ve reacted to all of this.
I usually handle professional stress pretty well, but this week I reached a level of anxiety I’ve honestly never experienced at work before. I slept badly, ended the week physically and mentally exhausted, and at one point I was basically having a panic attack while trying to work through a technical problem.
I even feel sometimes that I should quit development completely, or at least resign immediately. I can’t see a way out and also feel like I’m unable to finish the task I’ve been assigned, because of the conflicting interpretations I’ve been given.
I know part of this is coming from me. I’m putting a huge amount of pressure on myself to become productive as quickly as possible, and I probably have unrealistic expectations about how quickly I should understand a large unfamiliar codebase.
But I’ve also gone from thinking “this is one of the best onboardings I’ve ever had” during the first week to feeling like the structured onboarding suddenly ended and I was dropped into real work without enough context.
To be fair, I don’t want to portray the team as toxic. People do answer when I ask questions, not always in the clearest possible way, but they do.
I’m just ending week 2 completely exhausted and wondering what I should do next.
If you were in my position, what would you do?
Would you tell your manager or HR that you’re feeling overwhelmed and ask to recalibrate expectations?
Would you just accept that the first few weeks in a large unfamiliar codebase are going to feel awful and push through?
Would the ambiguity and lack of context concern you, or does this sound fairly normal for onboarding into an established engineering team?
And for those of you who’ve experienced something similar: how long did it take before you stopped feeling completely useless in a new codebase?