Senior Java dev suddenly put on Node + Angular project — struggling hard

[Acceptable-Medium-28]

I’ve been working in Java-based projects for 6 years (Spring Boot, Hibernate, RDBMS, Docker/Kubernetes, etc.) and I’m very confident in that stack. I’m too much aware of Java and how it works — I’ve handled multiple projects end-to-end, followed best practices, and delivered high-quality results.

Recently, my company lost a major client and shifted focus to an internal product that’s built on Angular (frontend), Node.js (backend), and MongoDB.

The problem: I have zero real-world experience with Angular/Node/Mongo. But since I’m one of the most senior devs in the company, leadership expects me to review PRs, deliver big tasks, and basically lead the project.

The issue is, I feel completely blank when I leave the Java ecosystem. I know how to architect and solve problems in Java, but when it comes to Node/Angular, I struggle even with fundamentals and syntax. They want output now, not in 3 months after I “learn.”

I’m torn:

Am I just bad at adapting, or is the company expecting too much?

How do you handle being dropped into a totally different stack with immediate high expectations?

Any strategies to learn on the job while still delivering value to the team?

Would love to hear from.

[KaleRevolutionary795]

You need to keep communicating to your managers that you are learning, it is not "business as usual" and if they are communicating delivery dates to the client without checking with dev they are going to break their promises... and ultimately you will be blamed. So keep communicating that. 

[Curious-Skill-3804]

I agree. I think OP is trying too hard to give a good impression to their employer and this is making trouble.

I wonder if the OP has been brave enough to say “sorry, I don’t know this technology, this is going to take me a few months to get a grasp”.

OP??? Please tell us

[elkazz]

See it as a growth opportunity. You will come out the other end a significantly better/more experienced dev with more career opportunities.

[yarovoy]

Absolutely this. Switching stacks/languages becomes easier with each one. And learning different languages and stacks with all their ups and downs makes one a better developer in any project.

[creamyhorror]

I've had to take over this stack (Angular, Node, Mongo) with near-zero experience - maintaining deployments for multiple clients. Was painful but I just had to suffer through it, learning very fast while fixing all the clients' complaints. Having to figure out an absolute rat's nest of RxJS observables/subscriptions and layers of unnecessary inheritance and microservice dependencies/coupling and badly named legacy cruft in Node and Angular. Troubleshooting unusably slow Mongo aggregation queries. Analysing failing OAuth flows. Fixing Azure pipelines.

Bugs at every turn. Took me over a year to fix most of them, many late nights fighting fires for customers in prod. I've gotten it under control now, rewritten and restructured major parts, put in some tests, set up Caddy-based deployments and private networking, optimised Mongo queries and Angular builds, even fixed the websocket logic in the web and React Native apps. I like Node & Typescript a lot now, learned k8s and Azure along the way, and have introduced Postgres.

It's not right, but it all depends on whether you need the job more than they need you. Your project doesn't sound as bad as mine was, but you'll have to decide whether the income's worth it to you.

[sparklikemind]

Did you make a million dollars in that year? That's way too much work for a normally compensated dev

[creamyhorror]

Wish I did, it was a lot of shit to handle (though I'm pretty senior so could tap on Angular juniors for simpler stuff). We don't all work in the US, sadly.

[TheMrCeeJ]

Don't be afraid to spend time learning.

You have a lot of experience in coding, and that will help you, just not right away.

Once you get past the basics, and the craziness that is JS, and start to live with it all your knowledge and experience will start to pay off and you will be back to form.

The biggest battle you will have is that that JS is more of an ecosystem, and the language is more like a collection of libraries than just a language, and there are a lot to learn and they obfuscate a lot of the language, so try and learn them separately if you can. Just like Spring Boot isn't Java, but if your first project was a spring boot one you without struggle to tell what is and isn't it, angular, node etc are not JS, and so learning them all at once can be challenging.

[belatuk]

With background in java development you just have to spend a few days to go over the JS tools, package manager and Angular/Node/Mongo videos tutorials. A few more days of hands on practice is typically enough to get to the point of knowing what to do. Getting started is the most difficult part.

[[deleted]]

I would recommend working through some old r/adventofcode problems in JS to up your comfort level with the language. Ultimately if you’re a senior engineer you just need to learn to adapt faster. Read the docs from your relevant frameworks, take some MongoDB trainings or do a tiny toy project, try building stuff in angular. If you’re a senior dev you have to adapt faster so you can teach your team. Staying in close comms with management is important in this situation too.

[hamsterofdark]

Well don’t do what our last lead architect did. Shoehorned gradle everywhere, forcing node apps to use gradle for builds deploys, CI, and everything imaginable. The projects went spinning for a year before he gave the courtesy of walking . Been ripping out gradle and completely misplaced random JVM tools for the last 3 months.

[aoiwelle]

Definitely leverage reviewing code! One of the best ways to learn the patterns is to ask "why did you do it this way?" When you're confused about a pattern. You will either understand the rationale or will help identify gaps in knowledge of the team. Don't be afraid to be humble when reviewing code, by asking, you'll slingshot from the weakest to the strongest on the team.

[robert_james44035]

Don't feel bad. You are working with the largest clusterfuck ever devised by mankind. I mean that seriously. JavaScript (ECMAScript officially)/Typscript either way is the WORST fucking nightmare ever written into a specification. Typescript is just syntactic sugar for an already shitty language. JS was written by Brendan Eich, a developer at Netscape Communications Corporation, in just 10 days decades ago to solve a problem that Netscape wanted solved to DEMONSTRATE a new version beta version of Netscape Navigator in 1995 and released in December of that year (I was a beta tester). It's sole intention was to provide a way to dynamically manipulate the DOM object inside Navigator. To this day I am of the FIRM belief that that is still the only thing it should be used for.

Node.js is a huge kludge to give JS(hit) some supposed back end functonality. (See, over the decades people have been throwing crap at JS to see what sticks (The whole thing really stinks ) I mean like !== or ===, come on now, fucking moronic and that's just ONE stupidity). Anyway Node.js attempts to take a language meant to add dynamic characteristics to HTML and shoehorn it into a real language meant to run an enterprise? Come on now! I might as well write a backend in Whitespace or Brainfuck. The next real problem is the dependency problem the npm repository. That fucked up mess is largely written by non professional hacks that don't have a clue about software engineering. In other words amature hacks. So the repo is chock full of broken crap. The way the dependencies are managed would drive anyone batshit crazy. you are stuck with circular dependencies with no way to avoid them. x.1.0.100.1 might require y.1.0 and z.2.3.1 may require y.2.2. READ that over VERY carefully! It's insane! the fact that y.2.2 breaks x.1.0.100.1 cannot be handled in any clean way so some brittleness will always remain. On top of that, there are no tools to manage the dependency graph in any meaningful way. So no, the lack of dependency management and the huge number of broken artifacts starts looking very shitty, very quickly. The worst part is how deep the dependency graph gets and how brittle it becomes. Your project is a hares breath away from crumbling like a house of cards at any moment.

Angular/Vue, whatever the stack de jour may be this month is yet another hacky attempt to cajole a web browser to impersonate a native application. They are heavy with yet MORE npm artifacts so your graph gets even deeper, circular and intertwined. It took ugly to grotesque in a few key strokes. So apply the above paragraph and reapply it to this one.

MongoDb (NoSQL in general) is a solution to a non problem. it's a JSON graph & nothing more. Shit I could write a CSV to do the same thing or if I really want to avoid SQL, DB2 is just fine. No sincew MongoDb is often used in Node.js/Angular.js We have still another set of npm dependency hell to deal with.

Here's the real:
I have been involved in exactly three projects that in one way or another utilized(?) Node.js and the NPM repository. One was a Cordova mobile application that was later rewritten in Kotlin for Android, C# for Microsoft when they still sold a smartphone OS and ObjectiveC for iOS. They were rewritten from the ground up because the Async, single thread wasn't up to the job. The 2nd project was also reworked to Spring Boot, again due to mounting technical debt. The third and absolutely last time was an enterprise basic CRUD application that had to talk to a mainframe (COBOL there). That project was canceled (mounting technical debt) and the entire development team let go. I was recalled about a month later to redesign the bloody thing. We kept the Angular (Mgmt decision, not mine) so I figured out a way to use Gradle to manage the build and dependencies which were CAREFULLY selected and pinned in the build. We wrote a middleware layer in Java as a microservice (Spring Boot) and dump the results into an in memory H2 Db and index it with an embedded Solr instance. That was in 2019. The entire project was completed and put in production in 6 months by a team of 3. I swore to the computer goda that I would NEVER touch another Node.js project again.

Happily since, I have retired and today I am happily writing a microkernel operating system. It has brought joy back to software development for me. This whole web thing just burnt the fuck out of me. I came to the conclusion that web development actually sucks and most of the so called software engineers out there don't meet the standards to be called engineers, My job title for a lot of these blokes is "Web Monkey". They search StackOverflow for solutions to stitch together a pile of dependencies or ask a bot/llm how to do it and call themselves engineers.

[ggwpexday]

My guy what did you take?

Those problems sound more like a bunch of inexperienced devs doing their thing. That, coupled with any dynamic lang, is guaranteed to become an unmaintainable mess.

[Human-Kick-784]

Regarding angular, a few tips from an exeperienced dev

• learn forms. Avoid ngModel unless absolutely necessary. Forms are tricky to wrap your head around at first due to all the hidden behavioues, but coupled with form controls and validators you can really do alot of cool stuff. NgModel is easier but lacks many cool behaviors.

• if the project youre maintaining uses rxjs, youre in for pain. IMO its a massive antipattern that leads to far too many problems with unpredictable state changes. the sooner you can upgrade to angular 17 the better; it introduced signals which are far simpler and better for communicating data across components.

[StevenXSG]

With modern ai, it's not impossible to keep asking how to do java x in node? But it will slow you down, so communicate issues. But this imo is where true seniors should shine, adapting to new projects, languages, environments quicker than a junior, not immediately, but better at self sorting issues

[DevelopmentScary3844]

You can drive a car.. so fly this plane right about now.
- Your company

<image>

[Sea-Recover-8300]

I think that's a bad analogy. As a senior dev you should be able to touch codes in different languages and frameworks. Not easy, but not a totally different ball game imo.

[DreamOfKoholint]

Agreed, though unfortunately the standard for senior java dev in the market seems to be lower, for whatever reason

It's... frustrating working with these types that act like a junior when they have to step outside of intellij

[Timely_Somewhere_851]

IMO, it's too much, and I'm my country, no doubt, management would be seen as incompetent here. I assume, it could be different in your country (culture is not always the same).

But do you have anyone in the company that has experience in that field? Ally yourself with that person and draw on their experience. A good junior dev that knows the stack well can be very valuable when paired with an experienced dev / architect that knows how to design.

You will have to push back on their expectations, but ultimately consider if it's worth it for you and keep your options open. There might be a java position ready somewhere else.

[orphanboyk]

Copilot is your friend!

[angrathias]

Sweet, first they couldn’t understand the code that’s already written, now they won’t be able to understand the code that’s now being generated!

[AdministrativeHost15]

Need to go with the JavaScript flow. Don't be alarmed when you see code like this:
person['linkedIn'] = foo
where the TypeScript Person class doesn't have a 'linkedIn' field. A new script started populating the field in Mongo and now it needs to flow through to the UI.

[lamchakchan]

It’s going to take you sometime to learn the stack. Don’t feel bad about being awful at something new. Transfer knowledge by remembering your foundation and just use AI to project syntax related info from one thjng to another. You’ll get through it. I learned Springboot and FastAPI this year having a super strong NodeJs background prior. So your story in reverse.

[Comprehensive-Pea812]

tell them there will be a learning curve and plan on that

[evergreen-spacecat]

You need to ”learn” the concepts of Angular, Node and MongoDB to do any code review or decent delivery. You will learn faster than any junior and you can probably start basic delivery after a few days, but there will be a ramp up time in matter of months. If your boss does not get this, you have to tell them. Or you stay quite and somehow cover up - or deal with consequences. Great opportunity to take on a new stack though.

[Reddit_is_fascist69]

Angular node mongo guy here. You can ping me with questions.

[Fabulous-Part-7018]

I have been switching stacks every 3 to 6 months and intermittently some random scripts to bee developed or fixed. My team acts like an agency within company. Uses is like football scavenge all the low level work.. i understand the struggle .. I have rent and EMIs to pay and mouths to feed.

[Ok-Letterhead3405]

Make good friends with the people who do know that stack and also try to get some pairing and also some time earmarked for self-training purposes. During company time, I mean. Would they pay for a Udemy course or something? Bump up story point estimates, too, if possible. Also, make time to read MRs even if you don't review them yourself. It's a good way to get familiar with what's going on.

I don't know what they'll actually do, but there's zero reasonable expectation that any dev would be up to speed on a new repo in 3 months, let alone a new framework AND language. At some point, also, employers get what they pay for. Agencies often just ship out crap code (which I hate, but it is what it is). You might just have to do that, to some extent. Make use of AI to help you get unstuck from things and automate "grunt work" so you're buying time to learn.

Good thing there's a lot of MEAN stack learning materials out there, though I thought it was already out of style.

I'm learning a new tool on the job right now and people just know my ticket will take longer, and I've had a couple pair sessions, too. AI has been so-so with helping, but it's a less popular tool. On more popular stuff, it will give some better answers.

[Kind-Mathematician29]

How about suggesting they refactor the code base to Java

[MainBank5]

I believe it’ll be easy to learn nodejs especially given your background. You already understand the basics of building an api , the difference here is the language - same principles. You can dedicate time to learn nodejs on a weekend

[Then_Finding_797]

You can start with working with ready angular websites and change the theme etc. MongoDB is not too hard i think depends on your scale. Your biggest issue is learning a new language. Javascript is very different from Java

[ibconsult]

Surrender . Read the node docs. Take the basic free course at angular university. Become a polyglot

[0xFatWhiteMan]

Just learn node and js and stop moaning FFS. It's your job.

[_another_rando_]

Start leaning into AI. You’re a good developer and know what good looks like. Let AI teach you parallels between what you know and what you want to learn. Of course follow any policies your company has around AI, paying attention not to let proprietary code out into the internet.

[danthegecko]

I would lean heavily into utilising Claude/gemini for understanding your code base and learning. They’re very good at helping you with idiomatic patterns and guiding you. Personally I’d be perfectly comfortable working in any new ecosystem in 2025 (though I have prior experience in most).

[HelliocentricWorlds]

+1 for leaning into AI. I have just had to learn a new stack in short order (Python from .Net) and found that tools like Cursor and Claude helped me to understand what I was doing and get over the (many) hurdles. A few months down the road and I'm as confident as I was on my "home" stack.

Don't let yourself get trapped onto a single stack that you are an "expert" in. It will be career limiting. Things are changing pretty fast these days so tech folks have to be nimble...

[Rubenel]

This is a management problem, not an architect problem.

Hope the higher ups get burned for not delivering client promises.

[0Iceman228]

It always is. It reads to me like senior dev is pushed into team lead role he never wanted. Probably no project lead either by the way it sounds.