u/DryExchange5198

I keep seeing "QA is dead" posts, so I went digging into the actual hiring data for 2026. What I found is way messier — and honestly more interesting — than the doom narrative.

The short version: QA isn't dying. It's splitting in two. And one half is growing faster than almost anything else in tech.

The part everyone gets right: manual regression testing, repetitive test execution, record-and-playback work — that's declining around 15-20% per year. If your job is clicking through the same flows every sprint, yes, that's going away.

The part everyone gets wrong: roles like AI Test Engineer (testing LLMs and chatbots), SDET, and "Quality Orchestrator" (basically managing fleets of AI testing agents, which is a job title that exists now) are growing 40-60% annually. Demand for AI Test Engineers is growing 40% faster than the average tech role. AI Test Architects are pulling ~$195k median base, with senior principal roles above $320k.

The weirdest data point: the premium shows up at ZERO years of experience. AI-focused testing roles start $15-35k above traditional QA even for juniors. I can't think of another tech specialization where the pay gap opens that early.

A few other things that surprised me:

The most AI-proof skills are the least technical ones. Exploratory testing, business logic validation, UX judgment — the stuff that relies on "does this actually make sense for a human" — is exactly what AI can't do. Everyone's racing to learn frameworks while the actual moat is intuition.

Certifications are simultaneously worth 25-40% more pay AND nearly worthless. Depends entirely on who you're applying to. Enterprises and big consultancies literally filter resumes by ISTQB (the CT-AI cert is the relevant one now). Startups don't care at all — they want a GitHub repo with real test suites, like data slice analysis or model robustness checks. Same credential, opposite value depending on the door you're knocking on.

If you're in QA right now, the realistic path people are actually taking: pick one repetitive task this month and throw an AI tool at it (edge-case generation, visual regression, whatever). Go deep on one framework — Playwright + Python seems to be the default stack — and wire it into CI/CD. Learn LLM evaluation (DeepEval, Promptfoo). Then move from executing tests to designing how testing works.

The market for AI-driven QA is projected at $82B by 2030 at 25-30% CAGR. That is not what a dying field looks like.

Curious what people here are actually seeing — is the "manual QA is doomed" pressure real at your company, or is it mostly LinkedIn noise?

Here's a stat that should annoy every MBA rankings obsessive: median starting salaries are softening to $120K in 2026, down from $125K. Meanwhile Wharton and Harvard grads are still pulling $175-185K. Same degree, wildly different outcomes.

The gap isn't prestige. It's narrative.

McKinsey, Bain, and BCG — the firms that used to hire smart generalists by the truckload — are now passing on "well-rounded" MBAs for candidates with a specific, provable point of view: AI + healthcare, AI + energy, AI + whatever. If you can't say in one sentence what problem you solve, you're not a generalist anymore. You're unemployed.

Which means the thing separating a $185K offer from a rejection letter at the same info session was never the diploma. It was whether the person could answer "so what do you actually do" without stalling.

That's the part nobody with a $250K sunk cost wants to admit — and it's the best news you'll get all year if you don't have the degree:

• The moat was fake. Prestige used to buy you the benefit of the doubt on "figure it out later." That benefit of the doubt is gone, even for Harvard. So the playing field just leveled — not because you got better, but because the credential stopped covering for vagueness.
• AI fluency is the new floor, not the ceiling. Employers don't want someone who used ChatGPT once. They want someone who can show a decision they made better/faster because of it. That's a portfolio move, not a tuition move.
• The "internship as audition" logic applies to you too. MBA programs convert 80%+ of strong interns to FT because trial-by-work beats interview-by-vibes. Translation: a scrappy contract project or a 2-week trial you engineer yourself does more than another round of applications.
• If you can't articulate your narrative, an MBA won't write it for you — it'll just be a six-figure delay before you have to.

The people with the most expensive credential in the room are being told the same thing you are: get specific, get provable, get an AI-fluent story, or get passed over. They just paid $250K to learn it. You get to learn it for free.

A friend of mine has sent almost 60 applications this year. Two interviews. She's started saying "maybe I'm just not good enough anymore." So I spent an afternoon pulling actual 2025-2026 hiring data instead of just reassuring her, because vague comfort doesn't fix anything and neither does blind guessing.

Here's what the numbers actually say.

A typical corporate posting gets around 250 applications. Out of those 250, only 4 to 6 people get invited to interview. That's not a 60-application problem, that's a 2-3% conversion rate no matter how good you are — most sources now put the average job seeker at 27 to 42 applications per single interview, not per job.

Getting to an actual offer takes more. BLS data puts it at 21 to 80 applications, and here's the part that surprised me: past 80 applications, your odds of getting an offer actually go down, from roughly 31% to 20%. Spray-and-pray past a certain point isn't just tiring, it's mathematically worse.

A big chunk of that 250 never gets read by a person at all. Roughly 70-80% of resumes get filtered by an ATS before a human sees them — formatting or keyword mismatches, not merit.

The part that actually changes what I'd do differently: where you apply from matters more than how often. Referrals are only about 2% of applicants but make up 11% of actual hires — a referral is worth something like 5x a cold application. And applying straight through a company's own careers page instead of a job board makes you roughly 4x more likely to get hired for that same role. Same effort, wildly different odds.

Last thing — once you do get an offer, don't sit on it forever deciding. 61% of candidates take the first offer they get. Employers know this and are moving faster because of it (most hiring now closes in around 41-44 days). If you're waiting to see what else comes in, that calculus is worth knowing.

So the honest reframe: 60 applications with 2 interviews isn't a sign you're falling behind, it's roughly on pace with what the data says is normal right now. What's worth changing isn't the volume, it's the mix — fewer blind job-board submissions, more direct-to-career-page applications and warm intros, and stop treating every rejection as a referendum on you. A meaningful chunk of that funnel was never going to convert no matter who you were.

I keep seeing this read as "even Microsoft is struggling." It's the opposite. This was one of the most profitable quarters in the company's history. The layoffs aren't a distress signal — they're a reallocation.

Here's the part that actually matters if you're thinking about your next move:

The cuts are hitting sales, consulting, and Xbox operations. The AI and Copilot teams were explicitly protected — Azure OpenAI, GitHub Copilot, the research org. Microsoft is spending over $100B on AI infrastructure this year, and the people building against that money are the last ones they'd touch.

So the story isn't "tech is collapsing." The story is that a hugely profitable company is telling you, in the clearest possible language, which roles it considers the future and which it considers overhead.

What I take from this as someone who thinks about career moves constantly:

• "Safe" is not a company name. A dream job at a dream company gave people two straight years of layoff anxiety. Prestige is not protection.
• The dividing line isn't "AI engineer vs. everyone else." It's close to where the money is going vs. far from it. You don't have to become an ML researcher. You have to be legibly connected to what your company is actually investing in.
• If your role runs fine on autopilot, that's exactly the profile being moved off payroll — no matter how well you personally do it.

None of this is a reason to panic. It's a reason to read the signal. When a company making record money still cuts a function, that's the most honest data you'll ever get about where that function stands.

Curious what everyone else sees here — is this changing how any of you are thinking about where to position next?

The line from that Karpathy conversation that reframed my whole job hunt: you can outsource your thinking, but you can't outsource your understanding.

Everyone's anxious that AI is faster and sharper than them. It is. That was never the contest.

Here's the part nobody tells you. AI is a worker that's brilliant and confidently wrong, often in the same breath. It'll hand you something that looks flawless with a fundamental mistake buried in it — the kind only someone who actually understands the work would catch. The example that stuck with me was an agent quietly building the wrong thing because it had no real idea what it was making.

So the value didn't go to whoever produces fastest. It went to whoever understands well enough to direct the work and catch what's broken.

For those of us switching fields, that's the opening. You don't win by out-producing someone with ten years in the seat. You win by showing judgment — I know what good looks like here, I can write the brief precisely, I can look at a perfect-looking result and tell you where it breaks.

I rewrote how I talk in interviews around exactly that. Less "here's everything I did." More "here's how I'd spec this, and where I'd expect it to go wrong."

For the switchers here: in the field you're moving into, what's the part you think still needs a human who understands — not just someone who can produce?

Today's biggest hirer isn't Google or Apple — it's Walmart, with 8,160 open roles. Hilton, Unilever, and Apple round out the top five.

And the role teams want most? Product Manager — 14,421 openings, ahead of Software Engineer. Hottest US market: San Jose.

The market isn't closed. It's just noisy. The roles are real, and they moved today.

Land the offer. Not lose your mind.

For two years I treated my career gap like a stain. Caregiving stretch, then a layoff on top of it. Every resume I sent, I was quietly trying to make the hole disappear — switched to a skills-based format, shaved the dates down, hoped nobody would do the math.

Callbacks were terrible. I assumed it was the gap.

It wasn't. It was the hiding.

Here's what flipped it for me. A hiring manager looking at a gap is really only asking three things:

• What were you doing before this?
• What happened in the middle?
• Why do you make sense for this role, now?

The functional resume answered none of those. It just screamed "this person is covering something up." The day I switched back to a normal dated layout — skills summary on top, real history underneath — and added one plain line for the break ("Career break — caregiving, plus a data analytics cert"), the tone of the replies changed. Not magic. Just no longer making them squint.

The part that actually annoyed me: the data says a recent gap barely costs you anything for the first six months or so. People fresh off a layoff often interview at a higher rate than people who already have jobs — because they're available and motivated. I spent two years managing a penalty that, early on, mostly wasn't there.

One neutral sentence does more than a clever format ever did. You don't owe anyone the full story.

Curious where everyone else landed on this — did naming your gap directly help you, or did you find hiring managers still flinched at it? Want to know if my experience is the norm or the exception here.

I track daily job postings across the US. Here's what this week's data (June 29) actually looks like:

• Product Manager: 14,398 open roles (+6 net new today)
• Software Engineer: 11,177 open roles (+39 net new today)
• Financial Analyst: 6,755 open roles (+10 net new today)
• Data Scientist: 4,988 open roles (+10 net new today)

That's 37,000+ active postings across just four job titles. "Nobody's hiring" doesn't hold up.

What's actually interesting:

1. PM roles outnumber SWE roles. 14.4K vs 11.2K. If you're a developer thinking about pivoting to product — the demand is real.
2. San Jose dominates PM and SWE, but not finance or data. Financial analysts? New York has 1,000 open roles. Data scientists? Also NYC at 539. The "move to the Bay Area" advice is only half right — it depends on your function.
3. Concord, CA has 473 SWE jobs. Not SF. Not Palo Alto. Concord. Notion, Anthropic, Fivetran, Gusto — they're posting onsite roles there. If you're only searching "San Francisco" you're missing listings 30 miles east.
4. Pleasanton has 691 PM roles. Abbott, Evisor, remote-hybrid positions paying $160K-$210K. Suburban tech hubs are quietly stacking up.
5. Financial analyst salaries vary wildly by city. Same title, same level — Dallas posts at $141K (Caterpillar), LA at $278 (government rates). Location arbitrage is real if you're flexible.

The pattern: Jobs aren't disappearing. They're dispersing — away from the obvious metros, into secondary cities, into titles people aren't searching for. The candidates who adjust their search radius and title keywords will have a massive advantage.

Spent a while looking at how remote roles actually get filled, and the pattern is almost backwards from what people optimize for.

Most applicants pour everything into proving they're skilled. But for a remote hire, skill is table stakes — the resume already cleared that bar or you wouldn't be in the room. What the hiring manager is actually afraid of is different: that they bring you on, you go quiet for two days, a deadline slips, and nobody notices until it's a fire. They can't tap a remote person on the shoulder. So they screen hard for one thing: will this person manage themselves and over-communicate, or am I going to be babysitting across time zones?

Almost nobody answers that question in the interview. Here's what actually moves it:

1. Show your operating system, not just your wins. When they ask about your day, don't say "I'm self-motivated." Walk them through how you actually run a day solo — how you batch work, where you write decisions down, how you flag a blocker before it becomes a problem. That's proof they can't get from a resume.

2. Make "async" something you do, not a buzzword. The signal they want: you write clearly and pick the right channel instead of booking a call for everything. If you can describe a time you killed a meeting by writing a good doc, you're already ahead of most of the field.

3. Treat your setup as part of the interview. Bad audio and a face in shadow read as "not ready for this." A decent mic, light from the front, framed with a little headroom (not a webcam aimed up your nose) — it feels superficial, but it's the only physical evidence they have that you take the format seriously.

4. Negotiate with numbers, not adjectives. "I restructured X and cut Y by 25%" beats "I'm a hard worker" every time. And don't only chase base salary — flexible hours, equipment/wellness stipends, and learning budgets are often easier to win and add up to real money.

TL;DR: The remote job doesn't go to whoever looks most impressive. It goes to whoever looks least risky to manage. Optimize for "you'll never have to wonder what I'm doing," and the rest takes care of itself.

Checked today's open-role counts for 4 roles across US metros. Every single #1 city was either San Jose or New York — and the split is suspiciously clean.

• Software Engineer → San Jose (1,009 open)
• Product Manager → San Jose (1,941)
• Data Scientist → New York (537)
• Financial Analyst → New York (1,001)

Build roles cluster in the Bay. Analyst/finance roles cluster in NYC. Both cities show up in the top 5 for all four — they just trade #1 depending on whether the job builds the product or measures it.

The thing that actually surprised me: there are more open Product Manager roles right now (14,429) than Software Engineer roles (11,153). Not what I expected.

Caveat — this is a single day, so don't read too much into the exact counts. But the geographic pattern held across every role I pulled. Does this match what you're seeing in your own search?

Python is now #1 on GitHub and TIOBE. The intuitive read — "great, learn it, get hired" — is the part the data no longer backs up. The language winning is exactly what made knowing it, by itself, close to worthless on a resume.

Three numbers:

• 51% of pro devs use AI tools daily (Stack Overflow 2025). The thing a bootcamp teaches you is the thing your editor now autocompletes. Syntax stopped being scarce.
• Half the Python community has under 2 years of experience, and 39% started in the last 2 years (JetBrains/PSF survey). "I know Python" went from differentiator to table stakes.
• Trust in AI output dropped to 29% even as usage rose — 45% say debugging AI code takes longer than writing it. So the paid skill flipped from writing code to judging it.

Put together: the easier a language is to start, the harder it is to stand out in. The premium didn't disappear — it moved. Not to Python the language, but to what you point it at: ML/data infra, system design, async-first APIs (FastAPI jumped 29%→38% in one survey cycle). Generalist "Python dev" is the squeezed middle.

And if you're web-focused: JS/TS still has more raw openings than Python. The profile winning is "bilingual" — deep in one stack, conversant in the other.

"Learn Python" was great advice in 2018. In 2026 it's incomplete. The full version: learn it and go deep somewhere AI can't follow you yet.

People who actually hire — are generalist Python roles still filling easily, or has the bar quietly moved to "Python + a specialty"?

Sources: Stack Overflow 2025 Developer Survey; JetBrains/PSF Python Developers Survey.

Been reading through a few takes on where tech hiring is actually heading in 2026, and a handful of shifts kept coming up. Putting them here because they cut against a lot of the advice still floating around this sub:

• The brand name on your resume stopped guaranteeing safety. Layoffs at the big players now hit regardless of performance. The "coast at a FAANG, great WLB" era people still chase seems mostly gone.
• AI literacy went from bonus to baseline. It's not a differentiator on your resume anymore — it's the floor. The people staying valuable are the ones who can actually ship AI into a product, not just talk about it.
• FAANG is getting swapped for a different set of names. Meta, Anthropic, NVIDIA, Google, OpenAI, SpaceX keep getting grouped together now. Streaming and e-commerce read as "mature" — less explosive upside than they had.
• The most underrated move might be leaving tech entirely. Banking, healthcare, and manufacturing all need engineers, often with better hours and a lot less layoff anxiety. Lower ceiling on pay, higher floor on sanity.

None of this is gospel — it's a read on the direction, not a guarantee. But if you've been grinding exclusively toward one Big Tech offer, it might be worth widening the net.

For people who've actually job-hunted in the last 6 months: does this match what you're seeing, or is it overblown?

Pulled today's consumer-sector hiring numbers and the mix caught me off guard. The brands adding the most net-new roles right now are paint (Valspar, +1,800), eyewear (EssilorLuxottica), and grocery (Albertsons) — not a software company in sight.

Two things stood out:

• Total listings ≠ growth. EssilorLuxottica has the most open roles overall (3,200+), but Valspar is the one actually scaling fastest — nearly all of its postings are net-new this cycle, while EssilorLuxottica looks more like replacement/churn hiring.
• It's hands-on work, and it's global. Lens-tray operators, assembly shifts, night stockers, baristas, branch service reps — spread across Australia, India, Denmark, Lithuania, Brazil, and the US.

If you've been grinding exclusively for tech/startup roles, the volume right now is sitting somewhere pretty different.

Where's the hiring actually happening in your field? Curious whether this manufacturing/retail tilt holds beyond this snapshot.

Most applicants treat "apply" as something you do whenever you're at your laptop — Sunday night, Friday at 5pm, doesn't matter. But a recruiter's inbox doesn't run on your schedule. It piles up Friday afternoon, sits all weekend, and gets triaged Monday in a scramble. By the time anyone is reading carefully, it's mid-week.

The window that consistently performs best: Tuesday through Thursday, roughly 6–10 AM local to the hiring team. Wednesday morning is the peak.

The logic is boring but real:

• Mondays are catch-up chaos — your application lands in a pile.
• Tue–Thu mornings are when recruiters actually work the queue, fresh, before meetings eat the day.
• Friday everything winds down, and weekends are basically offline. Submit then and you just sit at the bottom of the stack — which is exactly where good candidates quietly disappear.

Stack that with the 24–48 hour rule: the earlier you apply after a role goes live, the better your odds, because recruiters often start screening before the posting even closes. Early + morning window = two advantages compounding.

Two caveats so this doesn't turn into cargo-cult advice:

1. These are directional patterns, not laws of physics. A strong fit applying Friday at 4pm still beats a weak fit applying Wednesday at 8am. Timing is a tiebreaker, not a substitute.
2. Most roles never hit a public board in the first place (the iceberg in the graphic) — a big share get filled through referrals and networks before they're ever posted. So all this submit-timing stuff only applies to the visible slice. For the hidden slice, the "golden window" is just talking to people consistently, before you need anything.

Why post this now and not in September: the late-summer / early-fall hiring surge is real — fresh Q3/Q4 budgets, roles teams want filled before the holiday lull. The people who set up their LinkedIn, resume, and a short target list now are the ones submitting in that window the second a posting drops. The prep is the unsexy part that actually wins.

TL;DR: If you get to choose when to submit, aim for Tue–Thu, 6–10 AM, Wednesday best, within 24–48 hrs of the posting going live. And don't let perfect timing distract you from the majority of hiring that happens through people, not portals.

Curious what others here have seen — has anyone actually tracked their own submit time vs. response rate? I'd genuinely like more real data points beyond ours.

Been tracking global job posting data and wanted to share what stood out this week, since a lot of threads here assume the market is dead.

US role volumes (June 21):

• Product Manager: 13,946
• Software Engineer: 11,133 (+492 from last week)
• Financial Analyst: 6,412
• Data Scientist: 4,883

Biggest surprise: Industrial tech, not FAANG, led hiring gains. Cummins alone added +723 roles in a week. onsemi +489. These aren't layoff companies — they're quietly scaling.

London market: Finance is driving SWE demand more than anyone talks about. Deutsche Bank, Citi, and Citi were top posters. If you're targeting UK roles, fintech + Python is a stronger signal than chasing Google London.

AI companies: Scale AI, Anthropic, and OpenAI all had SWE postings visible — so the "AI companies aren't hiring" narrative isn't holding.

Happy to share more breakdowns if useful. What's everyone seeing on the ground?

Everyone tells you to move fast after a layoff. Wrong instinct. The whole system is betting on you panicking.

A few things almost nobody tells you:

• You don't have to sign anything on the spot. If you're 40+, the law gives you 21 days to review the severance (45 in a group layoff) and 7 days to revoke after signing. The HR rep who "needs it today" is bluffing.
• Severance is negotiable — almost always. Beyond the cash, push for COBRA subsidies, outplacement, and a neutral reference. And check that accrued commissions, bonuses, and pro-rated vesting are actually in there.
• COBRA is usually NOT your best insurance move. Same plan, but you pay 102% of the premium ($600–2,000+/mo). A spouse's plan or the ACA marketplace (income-based subsidies) is often way cheaper. You get ~60 days — but only 30 for a spouse's plan, so don't sleep on that.
• Back up your contacts before anything else. Access gets cut in minutes. (Don't take proprietary files — that's a lawsuit waiting.)

The people who come out of a layoff okay aren't the ones who moved fastest. They're the ones who slowed down for 48 hours and read the fine print.

Finding the right summer or casual employment requires more than just mass-emailing resumes. According to the sources, the most successful candidates are those who embrace counter-intuitive strategies, from "cold calling" to intentionally shortening their resumes.

1. Your Resume is Too Long

While you may want to list every achievement, brevity is your best friend.

• The One-Page Rule: For summer camp and casual positions, resumes should never exceed one page. Directors often review thousands of applications and will not read a multi-page biography.
• Reverse Chronological Order: Always list your most recent experience first.
• Professionalism First: Ditch the "creative" email address you made in childhood; use a professional one that consists of your name or initials.

2. Emails are Easy to Ignore; People Aren't

The "hidden job market" is often accessed through cold calling—contacting employers before a job is even advertised.

• The Power of the Phone: Emails are easy to delete, but a phone call or in-person visit allows you to speak directly to a decision-maker and prove your initiative.
• Be Persistent: If you don't hear back within a week or two, follow up. Persistence demonstrates enthusiasm and commitment, setting you apart from those who quit after the first hurdle.
• Networking Over Searching: Many students find success by asking parents, friends, and teachers for leads rather than just browsing job boards.

3. Timing Your "Intrusion"

If you choose to walk in or call, when you do it is as important as what you say.

• Avoid the Rush: Never contact a restaurant during lunch (11 AM – 1 PM) or dinner service, or a retail store during a major sale.
• The "Golden Hours": For service and hospitality roles, the best time to visit or call is between 2:00 PM and 4:00 PM, which is typically the least busy period.

4. Dress for the Job You Want, Not the Job You're Doing

Even for casual roles like a camp counselor, your interview attire matters.

• "Dress to Impress": You don't necessarily need a suit, but clean, wrinkle-free clothing and a blazer go a long way in showing you are serious.
• Professional Communication: Treat every email and phone call as part of the interview. Use full sentences, proper spelling, and a professional tone.

5. Don't Wait for Instructions During Trials

If you are lucky enough to land a trial shift (common in restaurants), standing around is the fastest way to lose the job.

• Be Proactive: Use your eyes to find things to do—polish glasses, run for ice, or bus tables—without being asked.
• Prove Your Worth: Showing you are a hard worker during your first summer often leads to being invited back in subsequent years without having to re-apply.

6. Leverage Government Resources

• Canada Summer Jobs (CSJ): This program is a vital resource for youth aged 15 to 30, providing paid work experience and connecting motivated youth with funded employers.
• Apply Early: Government positions and competitive roles can start their hiring processes as early as December.