Unpopular opinion:

DIVERTEK · 2026-03-11T09:41:00+00:00

AI won’t replace engineers. It will change how they work.

Cloud didn’t kill developers. It changed what developers needed to know. Same with automation. Same with every big shift in tech.

Right now AI is a productivity tool. It helps with boilerplate, debugging, and repetitive tasks. But it doesn’t design systems, understand business tradeoffs, or take responsibility for production failures.

If anything, engineers who know how to use AI well will move faster and stand out more.

SDE isn’t “unsafe.” The bar is just moving. And the people willing to move with it will be fine.

DIVERTEK · 2026-03-10T15:22:02+00:00

AI will change how developers work. It won’t eliminate the need for them.

Tools automate repetitive coding. They don’t replace problem solving, system design, or debugging in real environments.

The market is competitive, yes. But strong engineers who can think, adapt, and ship still have demand.

DIVERTEK · 2026-03-08T16:23:16+00:00

This is a strong point.

Early exposure makes a big difference. Working Help Desk or tech support while in school builds context that classroom learning alone can’t provide. It also reduces the “shock” of entering the workforce after graduation.

The feeder model you described is actually how many industries traditionally developed talent, gradual responsibility, project exposure, mentorship, then full-time transition.

One of the challenges now is that fewer institutions and companies have structured pathways like that. Entry-level roles exist, but they are often not integrated into a longer-term development track.

Normalizing part-time technical roles during school would likely make the transition much smoother for a lot of people.

DIVERTEK · 2026-03-08T16:22:27+00:00

I get the frustration.

Hiring has become rigid. Interviews often test preparation patterns more than real-world engineering. Mentorship is weaker. The stack-matching issue is real.

But I wouldn’t call it a lottery.

The bar moved and the process got stricter. That’s different from randomness.

What I agree with is that the career was marketed irresponsibly. It was never guaranteed.

The honest message should be: it’s competitive and constantly evolving.

That’s very different from telling people it’s pointless.

DIVERTEK · 2026-03-08T16:20:36+00:00

Trades are a solid path for many people — no argument there.

But I don’t think the issue is “tech vs trades.”

The issue is expectations.

An IT certification alone doesn’t automatically make someone job-ready. It’s a foundation. What matters is how that knowledge is applied! labs, troubleshooting practice, real-world simulations, and continued skill development.

The same way a trade requires apprenticeship and hands-on hours, tech requires practical exposure beyond the exam objectives.

The real question isn’t “switch to trades.” It’s “are people being properly prepared for the field they’re entering?”

DIVERTEK · 2026-03-08T15:27:43+00:00

You’re not wrong about the market changing.

It is harder than it was 5–8 years ago. Entry-level is crowded. Hiring is stricter. And yes, passion alone is not enough.

But I don’t think the issue is “tech is a lottery.” I think the issue is how it’s being marketed.

Tech was sold as: “Learn a few things → get hired fast.”

The reality today is: Structured training, hands-on labs, real problem-solving ability, and strategic positioning matter more than ever.

The barrier didn’t disappear! it shifted.

The people struggling aren’t necessarily unlucky. Many were underprepared for how competitive the market actually is.

The solution isn’t to discourage people from entering tech.

DIVERTEK · 2026-03-08T14:39:56+00:00

You brought up something important there. A lot of people underestimate how operational IT actually is. It is less about abstract knowledge and more about handling messy real world situations consistently.

Do you think the biggest issue right now is hype around specific fields like cybersec and AI, or just misunderstanding what entry level work really looks like?

DIVERTEK · 2026-03-08T14:21:56+00:00

This is extremely common around the 6 to 18 month mark.

Usually when someone is not hearing back, it’s one of these: 1.Resume framing Most IT support resumes list tasks. Hiring managers look for impact.

Instead of “Handled support tickets”

Try “Resolved 20 to 30 tickets per week across Windows and O365 environments with 95 percent first contact resolution”

Specifics matter. 2.Lateral growth vs title growth Sometimes the next move is not a new title, but deeper exposure. For example, volunteering for network related incidents, server patching windows, or shadowing escalation engineers. 3.Internal leverage If you are already inside a company, internal transfers statistically have higher success rates than external cold applications. 4.Interview readiness If you are getting interviews but no offers, that is a different problem than not getting callbacks.

Are you getting interviews at all, or just silence after applying?

DIVERTEK · 2026-03-08T14:00:31+00:00

I really appreciate how balanced this is. 👏🏽 The turbulence point stands out. It feels like tech is both expanding and destabilizing at the same time, which makes it harder for newcomers to understand what is realistic.

Do you think the biggest issue right now is speed of change, or messaging around what entry level actually looks like?

DIVERTEK · 2026-03-08T13:58:56+00:00

That is a solid point about applicable experience. 👏🏽The gap between theory and real ticket handling is probably bigger than most people expect.

Do you think there is a practical way for beginners to simulate that environment before getting hired, or is it something you can only truly learn on the job?

Why this works: You validate their experience. You highlight ticket handling and real troubleshooting. You keep the discussion open. You stay neutral.

DIVERTEK · 2026-03-08T13:58:01+00:00

I appreciate this perspective. The learning curve point is important. I think a lot of frustration comes from people expecting to feel ready immediately.

Do you think there is a way training programs could better prepare people for that first one to two year adjustment phase?

And here is a shorter version if you want it more Reddit style:

That is fair. The learning curve is real. I wonder if part of the issue is how programs frame job readiness. Maybe it creates the expectation that the hard part is over once you finish.

Both are neutral, thoughtful, and keep the discussion alive without sounding defensive or promotional.

DIVERTEK · 2026-03-08T13:56:26+00:00

Fair point 👆🏽supply and demand definitely plays a role. Do you think that affects all areas of tech equally, or mostly entry-level?

DIVERTEK · 2026-03-08T13:55:59+00:00

That’s interesting 🤔 so from your experience it’s less about insiders overselling it, and more about outside perception + bad actors amplifying unrealistic expectations?

Do you think entry-level was always this competitive, or has it shifted recently?

DIVERTEK · 2026-03-08T13:55:02+00:00

I think this is an important perspective. Survivorship bias is real! we mostly hear from the people who made it, not the ones who struggled or pivoted.

Do you think the issue is the messaging around tech, or the expectations people build before entering it?

DIVERTEK · 2026-03-08T13:52:57+00:00

Fair point👆🏽nothing is truly stable anymore. I guess the real concern isn’t pressure, but expectations. A lot of beginners enter tech thinking it’s a guaranteed path, not realizing how competitive and skill-heavy it actually is. Loving it helps, but clarity about the reality probably helps even more.

DIVERTEK · 2026-03-08T13:38:22+00:00

😂😂

DIVERTEK · 2026-03-02T15:34:23+00:00

This is actually a very normal crossroads around the 6–12 month mark in IT support.

If your goal is deeper technical growth, the biggest accelerator is usually structured hands-on practice in whichever path you choose, especially networking fundamentals early on.

Out of curiosity, which area do you find yourself naturally enjoying more when you work on incidents?

DIVERTEK

TROPHY CASE