u/ActionAggressive9069

Most AI posts here are either “AI will replace us” or “never use it, protect your fundamentals.”

But we also need to talk about the middle ground, which is what actually using it looks like on the job without losing your ability to think through problems yourself.

Here’s what’s worked practically base on exp:

•Use it to understand, not to finish When you’re stuck, ask AI to explain the concept behind the problem, not to solve it. You still write the solution. The understanding stays with you, the shortcut doesn’t.

•Use it for the boring parts, not the thinking parts Boilerplate, repetitive syntax, formatting, documentation. Offload that. The actual logic, architecture decisions, debugging your own code, that stays yours. That’s where the skill builds.

•Test it like a tool, not a source of truth AI gets things wrong, especially on newer libraries or edge cases. If you can’t read what it gave you and explain why it works, you don’t actually have a solution yet.

•Use it to get unstuck, not to skip being stuck Being stuck is where most of the learning happens. AI is useful for getting past a wall after you’ve actually sat with the problem, not as a first move the second something gets hard.

Junior devs who are going to struggle aren’t the ones using AI, they’re the ones who can’t work without it the second the internet goes down. Do not rely too much on a.i and make sure while using it u are still learning manually.

Apparently most CVs don’t get rejected because the candidate wasn’t good enough, they get rejected because the CV made it too hard to see that they were.

These are the things that are apparently hurting more than helping:

Writing “responsible for managing a team” instead of what actually happened. numbers are what people remember, not vague descriptions.

The entire “hardworking, dedicated, team player” line. a hiring manager with 12 years of experience said they have never once selected someone because their CV said hardworking. not once.

Listing every job going back 10+ years. last 3 roles maximum.

Generic hobbies like reading and travelling. either skip it or write something that actually says something about who you are.

Putting your current salary anywhere on the CV. the moment it’s on paper it becomes the anchor for every offer.

Starting your summary with “seeking a challenging role.” two lines, your strongest credential and your clearest value, that’s what actually gets you the call.

Is anyone else realizing the CV advice they got from school was doing more damage than good?

Tutorials won’t build your logic, practice does..

Instead of actually thinking…Watching tutorials feels like progress…finishing a course feels like progress… but if you can’t solve a problem you’ve never seen before, the logic is not there yet.

This how it actually works.

1. Solve problems daily, even small ones
One problem a day builds stronger thinking habits than binging courses.
2. Understand before you code
Spend time on inputs, outputs, and steps first. Good programmers think before they type.
3. Break big problems into smaller parts
Solve one piece at a time. Reduces confusion, improves clarity.
4. Trace code manually
Run your logic on paper step by step. Best way to catch how values actually change.
5. Read other people’s code
You pick up shortcuts, patterns, and cleaner logic structure faster than almost any other method.
6. Focus on understanding, not memorizing Memorized solutions fall apart on new problems. Logic you understand adapts to anything.
7. Debug deeply
Don’t just fix the error, understand why it happened. That’s where the real learning is.

Interviews test how you think, not what you’ve memorized. Logic is the actual skill!

I used to think feeling like a fraud meant I genuinely didn’t belong somewhere.

I took wayyyyyyy too long to realize it usually means the opposite.

1. thinking the feeling was evidence I treated feeling unqualified as proof I actually was. turns out it’s just my brain reacting to unfamiliar territory, not an actual fact about my ability.

2. waiting to feel confident before acting like I knew what I was doing confidence apparently shows up AFTER competence, not before. I kept waiting to feel ready, which just meant I waited way longer than I needed to.

3. comparing my behind the scenes to everyone else’s highlight reel the people who looked the most effortless in the room were almost never actually feeling that effortless. I just couldn’t see their version of the same panic.

4. staying quiet because I thought it made me look humble it didn’t make me look humble, it just made my actual work invisible to everyone around me 🙃

5. treating comfort as the goal the one time I actually felt 100% comfortable in a role, I realized later that was exactly when I’d stopped growing. discomfort was doing more for me than I gave it credit for.

6. thinking the feeling was supposed to fully go away eventually still waiting on that one honestly. eventually I just stopped waiting for it to disappear and started functioning alongside it instead.

Do you also realize way too late that the discomfort was actually a decent sign and not a red flag? what’s the moment you realized the discomfort you were running from was actually trying to tell you something?

People drop coding, bootcamps, or any technical skill right at the point it stops being fun and turns into boring grind. That part’s normal.

What’s not normal is how often that dropoff gets repackaged as a discovery instead of just admitted as a dealbreaker. The actual thing is whether someone can name the specific thing they didn’t like.

- “I don’t want to debug backend code for eight hours a day” is a useful conclusion.
-“I realized I’m actually more of a creative AI power user” usually means the exact same thing, just different but still it sounds like growth instead of giving up.

This will always the experience for those who did a self-taught and got a bootcamp paths. Someone grinds for a few weeks, hits the unglamorous part, debugging, syntax errors, reading docs at 1am, and instead of saying “this is harder and more boring than I expected,” they understand it as finding their true calling somewhere else.

Sometimes that’s genuinely true. Most of the time it’s just a more marketable way of saying you didn’t want to push through the hard part.
The difference matters because one version teaches you something real about your own limits. The other just protects you from sitting with the discomfort of quitting.

Is calling yourself an “AI power user” instead of an engineer a legitimate pivot or just a rebrand for not wanting to learn the fundamentals?

I just learned this (saw it in other platform) and felt like sharing because it would’ve genuinely changed how I approached internships if I knew it earlier.

There’s basically three waves of internship recruiting, not just one big “internship season” like most people assume.

The first wave is happening right now through summer, this is when the big quant, consulting, and banking firms lock in talent. Many of these have already started closing applications, which is wild for something labeled “summer 2027.”

Second wave runs august to november and this is the biggest one, most companies open up here and earlier applicants get better odds.

Third wave is feb to april, basically companies still filling spots or adding new headcount last minute. apparently this is the wave most people end up stuck in by default, not because they planned for it, but because they didn’t know the earlier waves existed.

kind of reframes the whole “I’ll start looking in spring” mentality a lot of people default to. By spring you’re not early, you’re picking through whatever’s left after two other waves already happened.

Hope this will help everyone applying for their internship✨

Preparing for tech interviews was ⚰️brutal💀! Not because the concepts were impossible, but because there’s SO much content out there that it’s easy to waste months on the wrong resources.

I made a lot of mistakes. I watch random videos, jump between platforms, restart courses halfway through. It was chaotic and honestly demoralizing because I wasn’t seeing real progress.

Then I got strategic about it. Instead of consuming everything, I picked ONE best channel for each skill I needed to master. And that changed everything.

Here’s the breakdown of what actually worked for me:

DSA Foundation
NeetCode was my starting point. The way Neet breaks down problems is just different, it clicks in a way other tutorials don’t. If you’re starting from scratch with Data Structures and Algorithms, this is where I’d begin.

Pattern Recognition
Abdul Bari’s LeetCode Patterns course made me realize that most interview problems aren’t unique they follow patterns. Once you see the patterns, suddenly 200 problems feel like 20 variations of the same thing. This was a game-changer for me.

System Design
System Design intimidated me the most. Gaurav Sen’s channel broke it down into digestible pieces. He explains the why behind design decisions, not just the what. That made all the difference when I got asked design questions in actual interviews.

Mock Interviews
Pramp was where I actually practiced talking through problems out loud. This was crucial because knowing how to solve something and being able to communicate it clearly are two different skills. I did maybe 15 mock interviews before my real ones.

Behavioral Prep
Jeff H Sipe’s channel helped me actually prepare for the behavioral round instead of winging it. Most people focus only on coding and then bomb the behavior interview. I wasn’t going to be that person.

The Rest
•Nick White for coding rounds (clean, straightforward)
•Back To Back SWE for deep problem-solving
•Errichto for advanced DSA when I felt stuck
•Exponent for interview strategy and mindset
•Self Made Millennial for resume and career positioning (honestly, this helped me stand out before I even got to the interview)
•Clément Mihailescu for real interview questions with walkthroughs
•William Lin for advanced techniques
•MIT OpenCourseWare for CS fundamentals when I had gaps

Overtime I eventually realize that you don’t need all 14 channels to pass interviews. But having a curated list kept me from falling down the rabbit hole of random content. I knew exactly what to study and where to study it.

The other thing is watch in order. I started with fundamentals (NeetCode, Abdul Bari), then moved to applications (LeetCode patterns, mock interviews), then the specifics (behavioral, system design, strategy). Jumping around wastes time.

If you’re prepping for tech interviews and feeling lost, try this list. Start with what you’re weakest at, and give each channel at least 2-3 weeks before jumping to the next one. Your future self will thank you. Good luck!

For you personally, how do you feel about this?because I keep seeing completely different camps online.

Some said if you’re already job hunting, you’re basically checked out and shouldn’t be getting praised or trusted with bigger projects, that energy should go to people who are “all in.” The other also says the loyalty only goes one way anyway, companies lay people off the second numbers dip regardless of how hard you worked, so why would employees owe anything different.

What’s weirder is the people getting raises and good reviews right now are often the same people quietly interviewing elsewhere. Managers either don’t know, or know and just don’t say anything because losing a strong performer mid-project is worse for them than pretending not to notice.

So where’s the actual line? Is putting in real effort while job hunting just being smart, or is it kind of a quiet form of dishonesty toward the people who trust you day to day.

If anyone here has been on either side of this, the one job hunting while top performing, or the manager who found out an employee was interviewing the whole time.

I just saw a breakdown of someone’s job hunt strategy and it’s basically the opposite of what everyone tells you to do. What they did instead of mass applying to 200+ jobs, they picked 3 companies. that’s it. three.

what they did differently:

They picked 3 companies only.
instead of spraying applications everywhere

researched deeper than most people bother to. studied the company’s products, leadership, recent launches, strategy. by interview time they actually had real opinions about the business, not just “I’m passionate about your mission”

rewrote their resume in the company’s language.
Matched the wording to the actual job description instead of generic resume-speak. Apparently this alone doubled the callback rate

networked before applying.
messaged people already in that role and asked real questions instead of begging for referrals. a few conversations turned into referrals naturally

interviewed like a consultant, not a student.
focused on making the interviewer’s job easy. clear answers, specific numbers, real product thinking instead of trying to sound impressive

result: 3 applications, 2 offers.
The part that’s actually interesting!
most people think more applications = more chances. but if your application looks identical to everyone else’s, volume doesn’t help, you’re just adding noise to a stack nobody’s reading closely.

If you want to try this yourself

- Claude can connect directly to indeed now.

(search and tools menu → add connectors → indeed, takes about 3 minutes). once it’s set up, here’s the kind of stuff you can ask it:

The prompts✨
-“pull job listings for [role] in [location] from the last 2 weeks. only keep the ones where my experience covers at least 80% of what’s required. skip backfills/reposts. give me the top 5 with a quick reason I’m a fit for each”

-“compare this listing to my resume and tell me the top skills I’m missing, ranked by how often they show up. suggest a bullet I could add for each if it’s true for me”

-“find out who’s probably hiring for this role, check their linkedin/recent posts, and tell me what they actually seem to care about that’s not in the job description”

-“pull listings for [role, one level up] that show real pay. give me a target salary range based on that, not my current salary”

-“write me a short cover letter that opens with one specific reason I want this role right now, not generic enthusiasm. cut anything that sounds AI-written”

-“pull the last 10 listings for this role, find what keeps showing up in at least 3 of them, and predict the most likely interview questions based on that”

it basically automates the deep research step instead of you digging through company pages for hours.

‼️the real takeaway
It’s not about working harder, it’s being way more intentional with way less effort. three good-fit applications will beat thirty mediocre ones almost every time.

would you actually trust and try this method, or does putting all your eggs in 3 baskets feel too risky?

There’s a moment you realize you’ve outgrown your job. happens in an instant but most people walk past it for years.

Based on my experience, it’s never one big dramatic thing.

It’s usually small and quiet. You finish a task that used to challenge you and feel nothing. not pride, not stress, just nothing, or someone asks how work is going and you give the same flat answer you gave six months ago, word for word.

That’s the moment. most people walk right past it, thinking maybe they’re just tired of the company.

Here’s the part that’s harder to admit though. staying isn’t really about the job anymore at that point, it’s about everything attached to leaving it. the comfort of knowing what tomorrow looks like. the identity you built around your title. the fear the next place might somehow be worse, even though some part of you already knows it probably wouldn’t be.

People stay. BUT NOT because they’re lazy, but cause outgrowing something is uncomfortable to sit with, and comfort is just easier to defend than growth is.

job isn’t even the real problem most of the time, staying stopped being a decision a while ago and quietly became a default. and defaults don’t feel like choices, that’s why people stay inside them for years without ever questioning it.

Work doesn’t really change when this happens. you do, job stays the same size while you grow past it, and that gap is what you actually feel, not the job itself.

What was the moment you realized you’d outgrown yours? or you still in it and just haven’t said it out loud yet?

Everyone's freaking out about AI and I get it. junior developer postings are down like 40% since 2022. sounds chaotic right?

Here's what nobody's saying clearly though: the jobs didn't disappear, they just got way more selective about who fills them.

\*the actual numbers\* (I did a small research and here’s what I found):

Stanford’s AI index tracked employment for devs aged 22-25 from 2022 to 2025. it dropped 20%. that's real. junior postings fell from 15% of all hiring to 7%. but bootcamp placement data from Course Report still shows 79% of grads landing jobs in 6 months. so like... they're getting hired, just not into the $60k junior roles everyone expects.

What changed?

Companies used to hire juniors to do grunt work, boilerplate code, simple integrations, repetitive stuff while learning. that's AI's job now. a team of 5 senior devs with Copilot can ship what used to need 2-3 juniors. so companies aren't hiring bodies anymore. they're hiring people who can think.

the hiring managers who are still bringing on juniors are explicitly looking for people who know how to work WITH AI, not people who learned to code the hard way.

“Where the real opportunity is”

According to LinkedIn data from 2025, devs who combine AI tool proficiency with actual engineering fundamentals are getting hired 2.3x faster than those who don't. that's not a coincidence.

the shift isn't "no juniors", it's "no juniors who don't know why their code matters." companies like Salesforce cut junior hiring. but enterprise tech companies quietly ramped it up.

Why? So they can afford to train people because they know it pays off long-term.

So yeah the pathway changed. But it's not broken. bootcamp grads are still getting hired. They're just getting hired differently into roles that require thinking, not just typing.

At first it made sense. more applications means more chances. So I just kept applying everywhere. But after a while it turned into the same cycle repeating:

submit… wait …no response… repeat

What actually started breaking down wasn’t effort. It was signal. Most applications weren’t getting rejected because of skill. They were just getting lost in volume.

At some point I noticed:

• the volume didn’t change outcomes
• the fatigue kept increasing
• the feedback stayed almost zero

The weird part is that slowing down didn’t feel logical at first. But fewer, more intentional applications started doing more than mass applying ever did. Not because the resume changed drastically. But because everything around it changed:

• timing
• relevance
• context
• targeting

Even small alignment differences started to matter more than quantity. I don’t think “apply more” is completely wrong. It just stops working once you’re competing in the same pile as everyone else.

At that point, it becomes noise, not strategy

people who’ve been job hunting recently… did you ever hit that same point where more effort stopped translating to more results?

Coming out of interviews, many people assume there’s a similarity between how well it felt and whether you get the job.

In reality, interviews are only one input in a decision that includes a lot of invisible factors.

Here are a few things that often matter more than how “good” the interview felt:

1. Internal candidates already in the pipeline

Even strong external candidates lose here without ever knowing it.

2. Budget shifts during hiring rounds

Roles get paused, downgraded, or re-scoped after interviews already happen.

3. Relative comparison, not absolute performance

You don’t need to do badly to be rejected. Someone else just needs to fit slightly better.

4. Team fit dynamics you don’t see

It’s not just skills. It’s overlap with existing team strengths, gaps, and timing.

5. Pre-existing preferences before the interview even started

Some candidates enter later rounds already “almost decided,” and interviews just confirm direction.

The key misunderstanding is thinking interviews are standalone evaluations.

They’re usually comparisons inside constraints you never see.

A “good interview” often just means you met expectations — not that you beat everyone else in the process.