By Peter Miller · Published September 1, 2026 · Last updated: September 20, 2026
8 min read
Myth: coders are finished and philosophy majors are the new elite. Reality: two different job markets got mashed into one viral story, and your resume can't chase both at once.
You've read the tech slump philosophy boom takes. Some are half right. Entry-level app dev is tighter than platform and security work. Roles that need careful judgement are real, but they're not hiring by the thousand. What you need tonight isn't a trend essay. It's a positioning choice: which search strings will you show up in when a recruiter types into Workday?
Whichever track you pick, the gate is the same. Check your resume for free and confirm your headline and first three bullets match the titles in the postings you're targeting. A judgement-heavy story buried under a generic technical title won't surface in either search.
Below: how each track actually hires, a side-by-side comparison table, resume bullets that fit each path, and a decision rule for which file to send this week.
What the tech slump philosophy boom headline misses
The durable split is producing versus deciding, not STEM versus humanities. A platform engineer who designs an ambiguous migration is on the deciding side. A philosophy graduate writing generic content briefs is on the producing side. The degree label is noise. The task shape is signal.
Tech slump stories usually lump every software job together. That hides the split inside tech: infrastructure, security, and data platform reqs still search for concrete tools and incident ownership. General junior dev roles compete harder because the task is well specified and easier to compare across candidates.
Philosophy boom stories usually skip volume. AI evaluation, policy, trust and safety, and technical writing roles reward reasoning, but most still ask for domain context. Healthcare policy wants healthcare exposure. Fintech governance wants fintech nouns in dated bullets. Reasoning without domain reads academic on a resume.
Your career path decision tonight is simpler than the headlines: which reqs can you honestly match with your last two years of work? Count those postings before you rebrand. For how to count without guessing, see which industries are hiring .
Two resume tracks: builder vs decider
Use this table to pick a track, then rewrite one file for that track only. Mixing columns is how you end up invisible in both searches.
| Criteria | Builder track (technical slump pockets) | Decider track (judgement boom pockets) |
|---|---|---|
| Headline title | Matches posting language: Site Reliability Engineer, Data Platform Engineer, Security Analyst | Matches posting language: AI Policy Analyst, Trust and Safety Specialist, Technical Writer |
| Proof shape | Shipped systems, uptime, latency, tickets closed, tools in production | Rubrics written, edge cases ruled, policies adopted, decisions owned |
| Skills section | Languages, clouds, frameworks named in reqs | Domain nouns plus methods: HIPAA, SOC 2, evaluation design, stakeholder review |
| Typical search string | ("SRE" OR "platform engineer") AND (Kubernetes OR Terraform) | ("policy analyst" OR "trust and safety") AND (AI OR moderation) |
| When to choose it | Your last roles shipped code, owned on-call, or ran migrations | Your last roles wrote rules, settled disputes, or evaluated ambiguous outputs |
Builder track bullets
Before: Worked on backend services and collaborated with cross-functional teams.
After: Owned payment API on-call for 12 microservices in AWS, cut p95 latency from 420ms to 180ms in Q2 2025.
Recruiters screening platform roles search tools and scope markers, not teamwork adjectives. Put Kubernetes in a bullet with a month, not only in a sidebar icon.
Decider track bullets
Before: Reviewed model outputs for quality.
After: Drafted the evaluation rubric that separated confidently wrong answers from uncertain ones, which the review team adopted for all consumer-facing prompts in March 2025.
Judgement work disappears when you only list deliverables. Name the decision, the audience, and the date it stuck.
Copy-paste block: headline swap for one role
BUILDER VERSION (paste at top of resume)
Site Reliability Engineer · 5 years · AWS/Kubernetes
Bullet 1: Led zero-downtime migration of 8 services to EKS,
Mar–Jun 2025
Bullet 2: Cut incident MTTR from 47 to 19 minutes via runbook
rewrite and PagerDuty routing
DECIDER VERSION (separate file, same person)
Trust and Safety Analyst · 5 years · consumer marketplaces
Bullet 1: Wrote escalation policy for impersonation reports,
adopted by 3 regional teams in Apr 2025
Bullet 2: Built QA sample that flagged 14% of listings with
policy conflicts before publish
Decision rule for this week
Open five postings you'd actually accept. If four lean builder, ship the builder file. If four lean decider, ship the decider file. If it's split, you don't have a positioning problem. You have a target list problem. Narrow the list before you rewrite bullets.
I've screened hybrid files where the title said Software Engineer and the bullets only described policy workshops. Recruiters on the technical req never opened them. Pick one search story per application batch.
For cross-field applications that need a letter to explain the pivot, pair the decider file with guidance from career change resume examples .
Positioning traps on both sides of the debate
Chasing the headline instead of the posting. A trend piece is not a job description. Count reqs, then align titles.
Hybrid titles that match nothing. Technical Strategist, Innovation Partner, and Operations Professional rarely appear in recruiter filters. Use the title from the ad, even if it feels narrow.
Leading with reasoning and no domain. Decider roles still want industry nouns in dated bullets. Policy without HIPAA, finance, or product context reads like coursework.
Staying on builder bullets when you're pivoting. If you're moving to evaluation work, your top three bullets must show rubrics and rulings, not repos you haven't touched in two years.
Before: One resume titled Professional with six generic lines trying to span both markets.
After: Two files, two headlines, three bullets each that match one search pattern.
Aim the file before you polish it
Paste a target posting into job match score and read what's missing from your builder or decider version. Rewrite the first three bullets to close the gap, then upload to HireFlow's free ATS resume checker and confirm the headline imports as plain text.
Cross-field applications need a letter that explains the pivot in one paragraph. Generate a cover letter after the resume matches the track. The letter carries motivation the resume shouldn't.
Pick one track this week
The tech slump philosophy boom debate is useful only if it forces a resume choice. Builder track for tool-and-ship reqs. Decider track for rubric-and-rule reqs. Count five postings, align one file, and stop splitting your story down the middle.
- Duplicate the resume. Change headline and top three bullets per track.
- Name a decision or a shipped system in bullet one, with a date.
- Apply in batches aimed at one search pattern at a time.
Rewrite tonight, then run a free ATS check on the version you're sending first.
Read more
Frequently asked questions
There is a growing set of roles that reward reasoning, judgement, and careful writing, especially around AI evaluation, policy, and trust and safety. Calling it a boom overstates the volume. The absolute number of those jobs is still small next to technical hiring families.
Tech hiring has been uneven, not uniformly dead. General entry-level application development has been harder than infrastructure, security, data platform, and deployment work. Treating tech as one market produces resume advice that fits nobody.
Pick the track the postings you can actually win require. If five open reqs ask for Python and incident response, position technical. If they ask for policy drafting and evaluation rubrics plus a domain, position judgement-heavy. Don't split the file down the middle.
Rarely. Recruiters search different title strings and tool lists. A hybrid title like Operations Professional matches neither posting language. Duplicate the file, change the headline and first three bullets, and aim each version at one search pattern.