u/Trungks_Ousi

Okay I need a gut check because I’ve been stewing on this all evening and I can’t tell if I’m being reasonable or just bitter.
Our promotion policy leans heavily on years of experience. Basically a level every 2 years (3 YOE, 5 YOE, 7 YOE, and so on). I’ve been here almost 5 years now, made Senior Software Engineer riding that same track like everyone else. Paid my dues, waited my turn, didn’t make a fuss.
Then today I found out two juniors who’ve been here all of 2 years have been getting promoted every single year. Yes, they each came in with around 1.5 years of prior experience. But here’s the part that’s eating at me: they still joined at our absolute lowest title, the one we hand to total freshers. So how is it that they get a bump every year while the rest of us crawl up every two?
And honestly I feel kind of gross even typing this out, because part of me knows comparison is a trap and I should just be happy with where I am. But another part of me is sitting here going… wait, did I just quietly accept a slower path that nobody actually had to take?
So I need outside eyes. Am I being jealous and entitled here, or is there something real worth raising? And if it is worth raising, who do I even go to. My manager? HR? Higher up? Or do I just swallow it and let it go?
(AFor extra flavor, leadership is also going all-in on some AI-first push that’s already broken things in prod, so morale is hovering somewhere near the floor. Not helping my mood right now.)

Okay I need a gut check because I’ve been stewing on this all evening and I can’t tell if I’m being reasonable or just bitter.
Our promotion policy leans heavily on years of experience. Basically a level every 2 years (3 YOE, 5 YOE, 7 YOE, and so on). I’ve been here almost 5 years now, made Senior Software Engineer riding that same track like everyone else. Paid my dues, waited my turn, didn’t make a fuss.
Then today I found out two juniors who’ve been here all of 2 years have been getting promoted every single year. Yes, they each came in with around 1.5 years of prior experience. But here’s the part that’s eating at me: they still joined at our absolute lowest title, the one we hand to total freshers. So how is it that they get a bump every year while the rest of us crawl up every two?
And honestly I feel kind of gross even typing this out, because part of me knows comparison is a trap and I should just be happy with where I am. But another part of me is sitting here going… wait, did I just quietly accept a slower path that nobody actually had to take?
So I need outside eyes. Am I being jealous and entitled here, or is there something real worth raising? And if it is worth raising, who do I even go to. My manager? HR? Higher up? Or do I just swallow it and let it go?
(AFor extra flavor, leadership is also going all-in on some AI-first push that’s already broken things in prod, so morale is hovering somewhere near the floor. Not helping my mood right now.)

Genuine question, because I keep seeing this workflow pitched as the future. The idea is you skip the whole Figma-handoff-to-dev loop entirely. You describe a change, or tweak something, an agent like Claude Code applies it straight to the real codebase, and you see it live in the actual product.
On paper it kills the telephone game. No more opening the build and finding the dev shipped it 80% like your design. But it also drops you into a world of existing components, conventions, and constraints, where the thing fights back in ways a Figma canvas never does. You’re not on a blank canvas anymore. You’re in someone else’s house with someone else’s rules.
So setting aside whether the AI is even capable of it yet, do you actually want to work this way? Is leaving the design tool and getting your hands in the codebase freeing? Or does it just turn you into a junior dev with extra steps?
And if you’ve actually tried it on a real product, not a demo, I really want to hear it. Did it feel like power, or did it feel like a trap?

Genuine question, because I keep seeing this workflow pitched as the future. The idea is you skip the whole Figma-handoff-to-dev loop entirely. You describe a change, or tweak something, an agent like Claude Code applies it straight to the real codebase, and you see it live in the actual product.
On paper it kills the telephone game. No more opening the build and finding the dev shipped it 80% like your design. But it also drops you into a world of existing components, conventions, and constraints, where the thing fights back in ways a Figma canvas never does. You’re not on a blank canvas anymore. You’re in someone else’s house with someone else’s rules.
So setting aside whether the AI is even capable of it yet, do you actually want to work this way? Is leaving the design tool and getting your hands in the codebase freeing? Or does it just turn you into a junior dev with extra steps?
And if you’ve actually tried it on a real product, not a demo, I really want to hear it. Did it feel like power, or did it feel like a trap?

Genuine question, because I keep seeing this workflow pitched as the future. The idea is you skip the whole Figma-handoff-to-dev loop entirely. You describe a change, or tweak something, an agent like Claude Code applies it straight to the real codebase, and you see it live in the actual product.
On paper it kills the telephone game. No more opening the build and finding the dev shipped it 80% like your design. But it also drops you into a world of existing components, conventions, and constraints, where the thing fights back in ways a Figma canvas never does. You’re not on a blank canvas anymore. You’re in someone else’s house with someone else’s rules.
So setting aside whether the AI is even capable of it yet, do you actually want to work this way? Is leaving the design tool and getting your hands in the codebase “freeing”? Or does it just turn you into a junior dev with extra steps?
And if you’ve actually tried it on a real product, not a demo, I really want to hear it. Did it feel like power, or did it feel like a trap?

The organization I work for recently hit a massive setback. The writing is on the wall: we have about 5-6 months to turn things around, or the layoffs are going to start.

But instead of tightening up, absolute madness has taken over.

Our CTO has suddenly granted full frontend codebase access to everyone in the office. People from the Marketing and Design teams are literally pushing code straight to PROD.All using claude. It is humiliating to watch.

To make matters worse, the CTO has openly started asking non-engineers to take over frontend tasks, brushing it off as just "a few lines of HTML-CSS-JS."

I've been in this industry for near 6-7 years, and I feel like this is a glaring sign that the frontend team is going to be the first one to the slaughterhouse when the time comes.

I need a reality check from the community:

1. Is this kind of "cross-team" cowboy coding happening anywhere else, or is my CTO losing his mind?
2. What should be my next move here?
3. Should I take this as a sign to pivot to Full-Stack, or abandon ship entirely?

TL;DR: Company has a 6-month runway before layoffs. CTO panicked, gave marketing/design direct access to push frontend code to PROD, and called our jobs "just a few lines of HTML/CSS." Trying to figure out if I need to pivot to full-stack or just run.

I’m a 30-year-old frontend developer with 5 years of experience. Most of my work has been in Angular + PHP, I’m comfortable with React, and I’ve built a few small full-stack side projects using Express.js just for practice.
Like many of you, I’m watching the AI wave and the crazy job-market uncertainty and I’m starting to feel lost. Frontend roles (especially Angular/PHP) already feel like they’re shrinking or getting heavily commoditized. I know the only real option is to upskill seriously, but I’m stuck between two paths and would love your honest opinions:

1. Go the Backend route,grind LeetCode-style DSA + algorithms, learn Node.js deeper (or maybe Java/Spring or .NET), and become a solid full-stack/backend engineer.
2. Dive into AI Engineering,this one I know almost nothing about. I keep seeing posts about “AI Engineer” roles but I have zero idea what the actual day-to-day work or required skill-set looks like for someone coming from a traditional web-dev background.
   My questions for you:
   • Which path makes more sense in 2026–2027 for someone with my exact background?
   • What are the realistic timelines and roadmaps for each?
   • Is AI Engineering actually accessible without a CS master’s or heavy math background, or is it mostly hype right now?
   • Any other directions I should consider (DevOps, low-code platforms, product engineering, etc.)?
   I’m willing to put in 6–12 months of serious focused learning, but I don’t want to waste time chasing something that might be saturated or overhyped.
   Would really appreciate brutal honesty + any resources/roadmaps that helped people in similar situations. Thank you in advance!