Forem: charlie-morrison

Remote Developer Jobs in 2026: Where to Actually Find Them

charlie-morrison — Wed, 29 Apr 2026 00:45:53 +0000

The remote job market in 2026 is confusing. Companies announce RTO mandates every week, yet remote job postings are at an all-time high. What's going on?

Short answer: the companies forcing RTO and the companies hiring remote are different companies. Big tech is pulling people back to offices. Startups, agencies, and international teams are hiring remote like crazy.

Here's where to actually find them.

The Job Boards That Work for Remote

Tier 1 — High signal, lower volume

We Work Remotely — Curated, mostly tech. Companies pay to post, which filters out spam.
RemoteOK — Tag-based search, salary data included. Great for filtering by stack.
Wellfound (formerly AngelList) — Startup-focused. Many remote roles, especially seed-to-Series-B.
Turing — Matches developers with US companies. Vetting process, but pay is above average.

Tier 2 — High volume, more noise

LinkedIn — Use "Remote" filter + specific job titles. Turn on "Open to Work" privately.
Indeed — "Remote" keyword + location filter. Lots of false positives ("remote until office reopens").
Glassdoor — Good for salary research + company reviews before applying.

Tier 3 — Niche / underrated

Himalayas — Clean interface, remote-only companies. Underrated.
Remotive — Newsletter + job board. Good for staying informed.
Working Nomads — Curated remote jobs, email digest format.
FlexJobs — Paid ($10/mo), but vetted listings. Worth it if you're serious.

The Search Strategy

Don't browse job boards. That's how you waste 3 hours feeling productive while accomplishing nothing.

Step 1: Define your search box

What roles? (Be specific: "Senior Frontend Engineer" not "developer")
What stack? (React? Vue? Node? Python?)
What company size? (Startup? Mid-market? Enterprise?)
What timezone overlap? (US hours? EU? Async?)
What salary? (Have a number. Research on Levels.fyi or Glassdoor.)

Step 2: Set up alerts, not searches

Every board above has email alerts or RSS feeds. Set them up with your exact criteria. Check once daily. Don't scroll aimlessly.

Step 3: Apply with intention

For each application:

Extract keywords from the posting — a keyword tool makes this faster
Tailor your resume to match (you only need to adjust 3-5 bullets)
Run it through an ATS checker to verify the match
Write a short, specific cover letter referencing something unique about the company

5 tailored applications beat 50 spray-and-pray submissions.

The "Hidden" Remote Market

The best remote jobs aren't on job boards. They're found through:

Open-source contributions

Companies like Vercel, Supabase, and Cloudflare hire from their contributor communities. If you use their tools, contribute a bug fix or docs improvement. You'll be visible when they have openings.

Developer communities

Discord servers for your stack (React, Rust, Go communities)
Dev.to discussions
GitHub Discussions on popular repos
Slack communities (Rands Leadership, LaunchDarkly, etc.)

People hire people they've interacted with. Show up, be helpful, and opportunities follow.

Direct outreach

Found a company you love that isn't hiring? Email the engineering lead:

"I noticed [specific thing about their product]. I've built [relevant project] using a similar approach. If you're ever looking for a [your role], I'd love to chat."

This works surprisingly often. Most companies have a "we'll create a role for great people" policy.

What Remote-Friendly Companies Look For

Beyond technical skills, remote companies specifically evaluate:

Written communication — Can you explain complex ideas in writing? (Your Dev.to profile or blog counts as evidence.)
Self-direction — Can you manage your own time without a manager checking in daily?
Async awareness — Do you understand that not everyone is online at the same time?
Documentation habit — Do you write things down? PRs with good descriptions, READMEs, decision docs?

If your resume says "excellent communicator" but your GitHub has zero READMEs and your LinkedIn has no posts — that's a contradiction.

The Interview

Remote interviews have their own quirks:

Video setup matters. Good lighting, clean background, stable connection. Test beforehand.
Time zone courtesy. Propose times in THEIR timezone. Shows you understand remote dynamics.
Async exercises > live coding. Many remote companies prefer take-home assignments. Treat them seriously — your code quality, commit messages, and README matter.
Ask about their remote culture. "How does your team handle async communication?" is a great signal that you get it.

Prepare role-specific questions with an interview prep tool so you're not caught off guard.

Red Flags in Remote Job Posts

Watch for these:

"Remote but must be within 30 minutes of the office" — That's not remote.
"Remote for now" — They'll call you back when the lease renews.
No mention of timezone expectations — Could mean "we expect you online during US business hours" which is fine if that's you, painful if it's not.
"Competitive salary" — Usually means "we don't want to tell you it's below market." Ask early.
Required to use monitoring software — Run. Companies that track keystrokes don't trust their people.

The Negotiation Edge

Remote positions have a unique negotiation angle: location-based pay.

Some companies pay based on your location. Others pay market rate regardless. Always ask which policy they use. If they pay by location, factor that into your ask.

A "below market" salary in San Francisco might be amazing if you're in a lower-cost-of-living area. But if the company adjusts down for your location, negotiate from their HQ rate, not yours.

Use salary negotiation scripts to prepare your counter before the offer call.

Action Items

Pick 2-3 job boards from the list above. Set up alerts today.
Update your LinkedIn headline to signal "open to remote"
Run your resume through an ATS check against a remote job you'd apply to
Join 1-2 developer communities in your stack
Apply to 5 targeted positions this week

The remote market is bigger than ever. You just have to look in the right places.

I Built 7 Free Career Tools and Made $0 — But I'm Not Stopping

charlie-morrison — Wed, 29 Apr 2026 00:45:22 +0000

Over the past week, I built 7 free career tools. Total revenue: $0.

Before you close the tab — this isn't a sob story. It's a case study in building something useful with zero budget and what I'm learning along the way.

The Tools

All client-side. No backend. No data collection. No accounts. Just HTML, CSS, and JavaScript:

Resume ATS Checker — Scores your resume against a job description
LinkedIn Headline Generator — Generates headlines by role and industry
Cover Letter Generator — Tailored cover letters in 4 tones
Salary Negotiation Scripts — Scripts for offers, raises, counters
Interview Follow-Up Emails — 5 email types, 4 tones each
Interview Question Generator — Role-specific prep with STAR method
Job Keyword Extractor — Extract keywords from job postings

Total development time: maybe 15 hours. All hosted on GitHub Pages (free). Domain: $12/year.

Why Free?

Because nobody buys tools from people they don't trust yet.

My theory: free tools that actually help → people remember the name → some percentage buy the premium version later (or tell others).

The premium is a $12 Job Search AI Toolkit with deeper AI prompts for resume optimization, interview prep, and salary negotiation. It's on Lemon Squeezy.

Zero sales so far.

What's Actually Working

Dev.to articles are the main traffic driver. 160+ views across 19 articles in about 5 days. That's not great, but it's real people finding the content through Google.

Career content dramatically outperforms dev content. My article "Stop Applying to Jobs Wrong" has 33 views. Technical tutorials average 2-5. The career niche on Dev.to is less saturated than web development tutorials.

Google is indexing Dev.to articles. 6 of 19 are already in Google search results. My personal site (charliemorrison.dev) has zero indexed pages after 30+ days. Dev.to's domain authority does the heavy lifting.

Free tools get mentioned in articles naturally. Each article links to 2-3 relevant tools. It doesn't feel spammy because the tools actually relate to the advice.

What's Not Working

My website isn't indexed. charliemorrison.dev is invisible to Google. I found and fixed a sitemap bug yesterday (dates were corrupted), so hopefully that changes soon.

Zero conversions. 160+ views, 0 sales. Possible reasons:

Not enough traffic yet (likely — 160 is nothing)
The paid product isn't compelling enough
Dev.to readers aren't my target buyers
The CTA isn't strong enough

Engagement is low. 3 reactions total across 19 articles. No comments. The articles are getting views but not sparking discussion.

The Math

Costs so far:

Domain: $12/year (charliemorrison.dev)
Hosting: $0 (GitHub Pages)
Everything else: $0

Revenue: $0

ROI: undefined (division by almost-zero)

Time invested: ~20 hours over 5 days

At current trajectory, I need the content to reach ~1000 monthly views before even one sale is statistically likely (assuming 0.1% conversion rate, which is low-end for digital products).

What I'd Do Differently

If I started over:

Start with the articles, not the tools. Content drives discovery. I should have written 10 articles first, then built tools based on what people actually clicked on.
Focus on one platform deeply. I spread across Dev.to, GitHub, and my own site. Should have gone all-in on Dev.to for the first month.
Build an email list from day one. Free tools should capture emails (with consent). A list of 100 interested people is worth more than 1000 anonymous pageviews.
Price higher or price at zero. $12 is awkward — too expensive for an impulse buy, too cheap to feel premium. Either make it free (and monetize with affiliates/upsells) or make it $49+ with more value.

What's Next

I'm not pivoting — the data says career content works. I'm doubling down:

More articles targeting job search keywords
Building an email capture into the free tools
Testing different price points
Getting charliemorrison.dev indexed (the sitemap fix might help)

The honest truth: most side projects die at the "zero revenue" stage because the creator gets discouraged. I'm treating this as a learning exercise. If it generates even $1, I'll know the model works and can scale it.

If it doesn't — at least I've built 7 genuinely useful tools and written 20+ articles that help people find jobs. That's not nothing.

What's your experience with monetizing dev content or side projects? I'd genuinely love to hear what worked (or didn't) for you.

All tools are free, open-source, and run entirely in your browser: charliemorrison.dev

How I Built a Developer Portfolio That Actually Gets Responses (Template Inside)

charlie-morrison — Wed, 29 Apr 2026 00:41:04 +0000

My first developer portfolio was a React app with smooth animations, dark mode, and exactly zero job offers.

The problem wasn't the code. The problem was that I treated it like a coding exercise instead of a sales page.

What Hiring Managers Actually Look For

I talked to a dozen people who review portfolios. The consensus was surprisingly consistent:

Can this person build things? (Show projects, not just list them)
Do they communicate clearly? (Project descriptions matter more than the code)
Would I want to work with them? (Blog posts and writing signal this)

Nobody mentioned animations, dark mode, or which framework you used for the portfolio itself.

The Portfolio Structure That Works

After testing different approaches, here's what consistently gets responses:

Above the Fold

Name, role, one sentence about what you do
One CTA: "See my work" or "View projects"
That's it. No life story, no mission statement, no "passionate developer who loves clean code"

Projects Section (3-4 max)

For each project:

Screenshot or demo GIF (people are visual — a wall of text loses them)
One sentence: what it does
One sentence: what you learned or what was challenging
Tech stack as tags/badges
Links: live demo + source code

The key: each project should demonstrate a different skill. Don't show 4 React apps. Show a React app, an API, a data visualization, and a CLI tool.

About Section

2-3 sentences about your background
What you're looking for (be specific — "frontend roles at mid-stage startups" not "exciting opportunities")
Link to resume (PDF download)

Blog/Writing (Optional but Powerful)

Even 2-3 short posts show you can think and communicate. Write about:

A problem you solved and how
Something you learned recently
Your take on a tool or technology you've used

The Projects That Get Attention

Based on what actually impressed the hiring managers I talked to:

Shows technical depth:

A tool with real users (even 10 users counts)
An open-source contribution (with link to the PR)
Something that processes real data (API integration, web scraping, data pipeline)

Shows product thinking:

A project with a clean UI that someone non-technical could use
Something that solves YOUR OWN problem (authenticity is obvious)
A project with error handling, loading states, edge cases considered

Red flags they mentioned:

Tutorial follow-alongs (they can tell)
Apps that only work on localhost
Projects with no README
"Coming soon" sections

Free Portfolio Template

If you're starting from scratch, here's a dead simple structure that works. No framework needed — plain HTML/CSS, host on GitHub Pages for free:

index.html
├── Hero (name, title, one line)
├── Projects (3 cards with screenshots)
├── About (short paragraph + resume link)
├── Contact (email + GitHub + LinkedIn)
└── Blog (optional - link to Dev.to)

Don't overthink it. A clean static page that loads fast beats a fancy React app that takes 3 seconds to render.

The irony: the best portfolio is one you spent 20% of the time building and 80% filling with real projects. Most developers do the opposite.

The Resume Connection

Your portfolio and resume should tell the same story. The projects on your portfolio should match the experience bullets on your resume.

If your resume says "Built a customer dashboard that reduced support tickets by 40%," that project should be on your portfolio with a demo link.

Quick tip: before you apply, run your resume through an ATS checker to make sure it actually matches the job description. A beautiful portfolio means nothing if your resume gets filtered out before anyone sees it.

What to Do Today

Audit your current portfolio (or lack of one). Does it pass the 5-second test? Can someone understand what you do and see your work in 5 seconds?
Pick your top 3 projects. Not your 3 most complex — your 3 most demonstrable.
Write one paragraph per project. What it does, why it's interesting, what you learned.
Deploy it. GitHub Pages, Netlify, Vercel — all free. No excuses.
Link everything. Portfolio links to resume, resume links to portfolio, both link to GitHub and LinkedIn.

The best portfolio isn't the prettiest one. It's the one that makes a hiring manager think "this person can build things I need built."

Your Job Application Is Being Scored by AI — Here's How to Win

charlie-morrison — Wed, 29 Apr 2026 00:40:32 +0000

In 2026, roughly 75% of resumes never reach a human. They're filtered by AI before anyone reads them.

This isn't news. But what most people get wrong is how modern ATS systems actually work — and what that means for your application strategy.

How Modern ATS Actually Works (It's Not Keyword Stuffing)

Old ATS systems from 2020 were basically ctrl+F on steroids. Find keyword, check box. That era is over.

Modern systems like Greenhouse, Lever, and Workday use semantic matching. They don't just look for "Python" — they understand that "built data pipelines using Python and Pandas" is more relevant than "Python" listed in a skills section.

What this means for you:

Context matters more than keywords. Don't list "Python" — describe what you built with Python.
Relevance scoring is real. The system ranks you against other applicants. A 90% match beats a 70% match, even if both "have the keyword."
Section structure matters. ATS systems parse sections differently. A skill mentioned in your experience section carries more weight than one in a standalone skills list.

The 5 Things That Actually Tank Your Score

I've tested hundreds of resumes through ATS parsers. These are the consistent failure patterns:

1. Creative Formatting

Tables, columns, headers in text boxes, icons — they all break parsing. The ATS sees garbled text, and your carefully designed resume becomes unreadable.

Fix: Single column. Standard section headers (Experience, Education, Skills). No graphics.

2. Missing Job Title Match

If the posting says "Frontend Engineer" and your resume says "UI Developer," you're already behind. The semantic match might catch it, but why take the risk?

Fix: Mirror the exact job title from the posting somewhere in your resume (your title, summary, or a "Target Role" line).

3. No Quantified Results

"Responsible for improving performance" tells the algorithm nothing. "Reduced page load time from 4.2s to 1.1s, improving conversion rate by 23%" tells it everything.

Fix: Every bullet point needs a number. If you can't measure it, estimate it. "Handled 50+ daily customer inquiries" beats "Handled customer inquiries."

4. Keyword Mismatch

The job says "CI/CD pipelines" and you wrote "automated deployment workflows." Same thing, but the ATS might not make the connection.

Fix: Use the exact terminology from the job description. Run your resume against the posting in a keyword extraction tool to find what you're missing.

5. Skills Section Without Hierarchy

Listing 30 skills in alphabetical order tells the ATS nothing about your proficiency. A hiring manager scanning it learns nothing either.

Fix: Group skills by category (Languages, Frameworks, Tools, Cloud). Lead with your strongest. Drop anything you can't discuss in an interview.

The 80/20 Rule for Job Applications

Instead of spraying 100 applications, try this:

Find 5 jobs you're genuinely qualified for (80%+ skill match)
Extract keywords from each posting — use a keyword extractor if you want to be thorough
Customize your resume for each one — not a rewrite, just adjust the top 3 bullets and skills emphasis
Write a targeted cover letter — even a quick generated one beats no cover letter
Score your resume against the posting — an ATS checker shows you the match before you submit

Five targeted applications with 90%+ ATS scores will outperform 50 generic ones every time.

What Happens After the ATS

Let's say you pass the filter. Now a human sees your resume for an average of 7.4 seconds. What do they look at?

Current/most recent role — title, company, duration
First bullet point under that role — your biggest achievement
Skills section — quick scan for dealbreakers
Education — if they care (many don't anymore)

That's it. 7.4 seconds. Your entire career reduced to a glance.

The implication: your first bullet point under your most recent job is the most important sentence on your resume. Make it your strongest achievement, with numbers.

The Human Side

After all this optimization talk, here's the thing: the best way to bypass ATS entirely is a referral. Employee referrals skip the queue at most companies.

But even with a referral, your resume still needs to be good. The referring employee is putting their reputation on the line. Give them a resume they'd be proud to forward.

Action Steps

Run your current resume through an ATS score check against a job you want
Extract keywords from the posting and compare with your resume
Fix the top 3 issues (formatting, keywords, quantification)
Recheck your score
Prepare for the interview with tailored questions for your target role

The game is rigged, but knowing the rules is half the battle.

The Tech Skills That Actually Get You Hired in 2026 (Not the Ones You Think)

charlie-morrison — Wed, 29 Apr 2026 00:40:01 +0000

Everyone's chasing AI certifications. Meanwhile, the developers actually getting hired in 2026 are doing something different.

I analyzed hundreds of job postings this year, and the pattern is clear: companies don't want someone who "knows AI." They want someone who can ship products that use AI.

The Skills Gap Nobody Talks About

Here's what most job postings actually ask for:

Tier 1 — You won't get past screening without these:

Python or TypeScript (one fluent, one functional)
REST APIs and basic system design
Git workflow (not just git add . — proper branching, PRs, code review)
CI/CD basics (GitHub Actions, at minimum)

Tier 2 — What separates "maybe" from "yes":

Cloud infrastructure (AWS or GCP — pick one, go deep)
Containerization (Docker is table stakes; Kubernetes is a bonus)
Data pipelines or event-driven architecture
Security fundamentals (OWASP top 10, auth flows)

Tier 3 — The actual differentiators:

Building with LLM APIs (not using ChatGPT — building products on the API)
RAG systems, vector databases, prompt engineering in production
Internal developer platforms / platform engineering
Observability and monitoring (you'd be surprised how few devs know Grafana)

What Companies Actually Mean by "AI Experience"

When a job posting says "AI/ML experience preferred," they almost never mean:

PhD in machine learning
Training models from scratch
Publishing research papers

They mean:

Can you integrate an LLM API into a production app?
Can you build a retrieval pipeline?
Can you evaluate whether AI is the right solution (or just a shiny hammer)?

The best signal? A working project on GitHub. Not a tutorial follow-along — an actual thing that solves a problem.

The Resume Problem

Here's where most people fail: they list skills without context.

Bad: "Proficient in Python, JavaScript, React, AWS, Docker, Kubernetes, TensorFlow, PyTorch"

Good: "Built a document processing pipeline (Python, AWS Lambda) that reduced manual review time by 60%. Integrated GPT-4 API for automated classification with 94% accuracy."

The second version shows you can actually use these tools to solve business problems.

If your resume lists 15 skills but zero outcomes — you're invisible to hiring managers. The ATS might pass you through, but the human reading it won't.

Quick check: paste your resume into a free ATS checker to see how it scores against a real job description. Takes 30 seconds.

The Portfolio That Actually Works

Forget building another todo app or weather dashboard. In 2026, these projects catch attention:

An AI-powered tool that solves a real problem (even a small one)
A contribution to an open-source project — even documentation counts
A data pipeline that processes real data and produces insights
A developer tool — CLI, VS Code extension, GitHub Action

The common thread: real utility, not just practice.

The Uncomfortable Truth

The tech job market in 2026 is brutal. 79,000 layoffs in Q1 alone, yet 92% of companies say they're hiring. The contradiction makes sense when you realize: they're not hiring the same profiles they're laying off.

Companies are cutting generalists and hiring specialists. If you're a "full-stack developer who can do a little of everything," you're competing with thousands of identical profiles.

Pick a lane. Go deep. Build proof.

What to Do This Week

Pick ONE skill from Tier 2 or 3 that interests you
Build ONE project that demonstrates it (not a tutorial — a real thing)
Write about what you learned (on Dev.to, your blog, LinkedIn — anywhere)
Update your resume to lead with outcomes, not skill lists
Run your updated resume through an ATS score checker against 3 job descriptions you'd actually apply to

The developers getting hired in 2026 aren't the ones with the most certifications. They're the ones who can prove they build things that work.

I Built a Job Description Keyword Extractor (and Here's What I Learned About ATS)

charlie-morrison — Tue, 28 Apr 2026 20:02:13 +0000

Every job description is a cheat sheet. The hiring manager already told you exactly what they want — it's just buried under corporate filler.

I got tired of manually highlighting keywords in job postings, so I built a tool that does it automatically: Job Description Keyword Extractor. Paste a posting, get categorized keywords. Technical skills, soft skills, tools, certifications — all sorted by how often they appear.

Building it taught me a few things about how ATS systems actually work.

Most resumes fail on keywords, not formatting

Everyone worries about fonts and columns and whether their PDF will parse correctly. That stuff matters, but it's not what kills most applications.

The real filter is keyword matching. ATS systems score resumes based on how many keywords from the job description appear in your resume. Not synonyms. Not related terms. The exact words.

If the posting says "Kubernetes" and your resume says "container orchestration" — that's a miss. If it says "cross-functional collaboration" and you wrote "worked with different teams" — miss again. The machine doesn't understand meaning. It counts matches.

Frequency tells you priority

When a keyword shows up three times in a job description, that's not sloppy writing. That's emphasis. The hiring manager really wants that skill.

My tool highlights these: keywords mentioned 3+ times get green tags, 2 times get yellow. If Python shows up five times and Go shows up once, you know where to focus your resume's real estate.

The categories matter for resume structure

Most people dump all their skills into one section. But job descriptions naturally split into:

Technical skills (programming languages, frameworks, concepts)
Tools and platforms (Jira, AWS, Figma, Salesforce)
Soft skills (leadership, communication, stakeholder management)
Certifications (AWS Certified, PMP, specific degrees)

Your resume should mirror this structure. A skills section with 40 random technologies tells the ATS nothing about priority. But "Core Skills: Python, Django, PostgreSQL" followed by "Tools: AWS, Docker, Terraform" maps directly to how the job was written.

What I actually built

The tool runs entirely in your browser. No backend, no API calls, no data collection. You paste text, JavaScript parses it against ~500 known skill/tool patterns, and you get a categorized breakdown.

It's not perfect — natural language is messy, and some keywords are ambiguous ("Go" the language vs. "go" the verb). But for the core use case of "what keywords should I make sure are in my resume" — it works.

The killer feature (for me at least) is the copy button. Extract keywords, copy the list, open your resume, and check them off one by one. Five minutes of work that can make the difference between your application reaching a human or getting filtered out.

The workflow I'd recommend

Find a job you want to apply for
Paste the description into the keyword extractor
Copy the high-priority keywords
Update your resume to include those exact terms (naturally — don't keyword-stuff)
Run it through the ATS checker with the same job description
If your score is below 70%, keep tweaking

This is what targeted applications look like. One resume per job posting, customized for that specific role. More work than spray-and-pray, but the response rate is incomparable.

The tool is at charliemorrison.dev/job-keywords. There's also a resume checker, cover letter generator, and a few others — all free, all browser-based.

Curious what keywords you find in your current target role?

I Stopped Applying to Jobs Listed as 'Hybrid' — Here's Why

charlie-morrison — Tue, 28 Apr 2026 19:55:35 +0000

Three months ago I changed my job search strategy. I stopped applying to anything listed as "hybrid."

My response rate went up. Not because hybrid jobs are bad — because "hybrid" means whatever the company wants it to mean.

The word means nothing

I applied to nine hybrid roles between January and March. Here's what "hybrid" actually meant at each one:

3 days in office, 2 remote (most common)
4 days in office, 1 remote (basically in-person with a pity day)
"Flexible" — meaning the manager decides week by week
2 days in office but you pick which ones
2 days in office but everyone has to be there Tuesday/Thursday
Fully remote for 6 months then "we'll see"
Remote until the lease on the new office starts

Nine jobs, seven different definitions. One word.

What I actually found out during interviews

The two worst were the "flexible" ones. In both cases, I asked direct questions in the first interview:

"What does hybrid look like day-to-day for this team?"
"Is the schedule fixed or does it vary?"
"Has the policy changed in the last year?"

One interviewer got visibly uncomfortable. Turned out they'd just moved from fully remote to 3 days in-office and morale was tanked. The "hybrid" listing was damage control — they didn't want to say "we reversed our remote policy" in the job posting.

The other one said "we're flexible" three times without ever giving a number. That's a red flag. If they can't define it, they'll change it.

My new filter

Now I only apply to jobs that specify the exact arrangement in the posting. "2 days in office, Tuesday and Thursday" — that's clear. "Hybrid" with no details — skip.

I also started asking these questions before the first interview, in the initial email or recruiter call:

How many days per week is the team in-office right now?
Has this changed in the past 12 months?
Is there a written policy I can see?

If the recruiter can't answer #1 immediately, I pass. Not out of principle — out of efficiency. Life's too short to go through four rounds of interviews for a job that turns out to be "remote" in the listing and "actually you'll need to relocate" in the offer letter.

The 53% trap

53% of remote-capable workers are hybrid right now. That's the majority. And for a lot of people, hybrid genuinely works. My issue isn't with the arrangement — it's with the labeling.

When a company says "remote" they mean remote. When they say "in-person" they mean in-person. When they say "hybrid" they could mean anything from "mostly remote with quarterly meetups" to "we need you in the office every day but legally we can't call it full-time on-site."

The ambiguity costs job seekers hours. Hours spent applying, interviewing, negotiating, only to discover the actual deal isn't what the posting implied.

What would fix this

Job boards could solve this tomorrow. Instead of a single "hybrid" checkbox, make companies specify:

Days per week in-office: [1] [2] [3] [4]
Fixed or flexible schedule
Policy change in last 12 months: Yes/No

LinkedIn actually started doing something like this, but adoption is spotty. Most companies still just check the "hybrid" box and call it a day.

Until the platforms fix it, the filtering falls on you.

Did it actually help?

My application volume dropped by about 40%. But my response rate nearly doubled. Fewer applications, better matches, less wasted time on both sides.

I also stopped getting surprised in interviews. Every role I applied to, I already knew the exact setup. That let me spend interview time on actual work questions instead of playing detective about office policies.

Your mileage will vary. If you're flexible about where you work, "hybrid" ambiguity won't bother you. But if location matters — and for 64% of remote workers, it matters enough to quit over — filtering early saves you from the runaround.

What's your experience been? Have you found "hybrid" means the same thing twice? Genuinely curious.

If you're in job search mode: I built some free career tools — resume checker, LinkedIn headline generator, cover letter builder, salary scripts, interview prep, and follow-up emails. All browser-based, nothing tracked.

AI Won't Replace You — But Your Resume Probably Doesn't Prove That

charlie-morrison — Tue, 28 Apr 2026 19:54:34 +0000

84% of developers either use AI tools or plan to this year. 41% of code is already AI-generated. If you're reading this, you probably use Copilot or ChatGPT daily.

So here's the problem: your resume still says "proficient in Python" and "strong problem-solving skills." That described you in 2019 too. What changed?

Nothing, according to your resume. And that's what hiring managers see.

The real shift happening in 2026

Companies aren't replacing developers with AI. They're replacing developers who don't use AI with developers who do. There's a difference, and it matters for how you present yourself.

The data backs this up. Developer job postings are up 15% since mid-2025, but the roles look different. AI/ML roles are growing fastest. "Traditional" software engineering roles are recovering more slowly. The market wants people who can work alongside AI, not people who pretend it doesn't exist.

Five skills that actually matter right now

Not the fluffy stuff. These are the skills showing up in job postings I've actually read.

1. Prompt engineering (yes, really)

I know, the title sounds fake. But companies are hiring for it at $90k-$130k. What they actually want: someone who can write system prompts, design retrieval pipelines, evaluate model outputs, and debug when the AI hallucinates. If you've spent hours tweaking a Claude system prompt to get consistent JSON output, congratulations — that's the job.

Put on your resume: specific tools (Claude, GPT-4, Gemini), what you built with them, measurable results.

2. AI-assisted code review

Writing code with AI is table stakes. Reviewing AI-generated code is the skill gap. Most developers accept Copilot suggestions without reading them carefully. The ones who catch the subtle bugs — wrong error handling, security holes, inefficient algorithms — those are the ones getting promoted.

Put on your resume: "Reviewed and validated AI-generated code across [X] projects, catching [specific type] of issues."

3. Data pipeline literacy

You don't need to be a data engineer. But if you can't explain what a vector database does, how embeddings work, or why RAG exists, you're going to struggle in interviews. Data engineers and ML engineers are the fastest-growing roles right now. Even if you're a frontend developer, understanding the data layer makes you 10x more useful.

Put on your resume: any experience with embeddings, vector stores, RAG architectures, or data transformation work.

4. Testing AI systems

How do you test something that gives different answers each time? This is a genuinely hard problem, and companies need people who can think about it clearly. Evaluation frameworks, benchmark datasets, regression testing for model outputs — this is all new territory and there aren't established best practices yet.

If you've built any kind of evaluation pipeline, even a janky one, that's worth mentioning.

5. Knowing when NOT to use AI

This sounds backwards, but hear me out. The worst engineers I've worked with this year are the ones who pipe everything through ChatGPT, including things that don't need it. A simple for loop doesn't need AI. A SQL query you've written fifty times doesn't need AI. Judgment about when to reach for AI tools — and when a straightforward solution is better — is underrated.

You can't put this on a resume directly, but you can demonstrate it in interviews and in how you describe your projects.

How to update your resume tonight

Don't just add "AI" to your skills list. That's what everyone does and it means nothing.

Instead:

Replace generic skills with specific tools and outcomes
Add a "Recent AI Experience" section if you have 3+ examples
Quantify impact: "Reduced code review time by 30% using Copilot" beats "Experience with AI tools"
Show what you built, not what you know about

Run your updated resume through an ATS checker to make sure the keywords actually land. Most applicant tracking systems still parse resumes like it's 2015, and formatting issues can tank your score even if the content is solid.

The uncomfortable truth

54% of workers haven't used AI in the past year. If you're in the other 46%, you're ahead. But "ahead" doesn't last. Two hours saved per day using AI tools is the reported average. If your competitor saves two hours a day and you save zero, the gap compounds fast.

The market isn't punishing people who lack AI skills yet. It will be. The developers who update their positioning now — not in six months when everyone else catches up — will have the advantage.

Your Company Just Announced RTO — Here's How to Actually Push Back

charlie-morrison — Tue, 28 Apr 2026 19:53:54 +0000

I've watched three friends lose remote work this year. Same story each time: company-wide email on Monday, "we value collaboration," pack your bags by March.

Two of them complied. One pushed back. Guess who still works from home?

The numbers are on your side

Here's what most people don't realize: only 27% of companies have gone fully in-person in 2026. The rest? 67% still offer some flexibility. Your company might be bluffing, or testing who'll fold first.

More importantly: 76% of companies that allow remote work see better retention. Your manager probably knows this. HR definitely does.

Why most people fail at this conversation

They make it about themselves. "I like working from home" is not an argument. It's a preference, and preferences lose to policies every time.

What works is making it about output. You need receipts.

Before you say anything, gather this

Your last 6 months of performance metrics (reviews, project completions, anything with numbers)
Response times — how fast you reply to messages, close tickets, ship code
Any projects you led or completed while remote
Cost savings (no commute reimbursement, smaller office footprint)

If you can't prove you've been productive remotely, you don't have a case. Be honest with yourself about that.

The actual conversation

Don't email HR. Don't post on Slack. Talk to your direct manager first, one-on-one.

Here's a script that's worked:

"I saw the announcement about returning to the office. Before I adjust my schedule, I wanted to talk about what's worked for me — and for the team — over the past [X months]. My [metric] has been [number], and I've shipped [specific projects]. I'd like to propose continuing our current arrangement, or at minimum a hybrid schedule of [X days]. Would you be open to a trial period?"

Three things this does right:

Acknowledges the policy — you're not ignoring it
Leads with results — not feelings
Proposes a trial — lower risk for the manager to say yes

If they say no

44% of employees comply with RTO mandates. 41% start job hunting. 14% quit outright.

If your company won't budge, that tells you something about how they value your work versus your presence. And right now, 38% of professionals are already looking for new roles in 2026. Remote job postings grew 20% last quarter. The market exists.

But — and I cannot stress this enough — don't rage-quit. Line up the next thing first. Update your resume (here's a free ATS checker if you want to see how it scores), polish your LinkedIn headline (generator here), and start applying quietly.

The hybrid compromise

Full remote might be off the table. That's reality for a lot of people. But hybrid is where most of the workforce is landing: 53% of remote-capable workers are now hybrid.

If you negotiate hybrid, get the specifics in writing:

Which days are office days?
Is it flexible or fixed?
Does it reset if you change teams?
What happens if you relocate?

Verbal agreements have a way of evaporating when new management shows up.

What 64% of workers said they'd do

In a 2026 survey, 64% of remote workers said they'd quit or start looking if forced back full-time. That's not a fringe position — that's most people. You're not being unreasonable by pushing back. You're being normal.

The companies that figure this out will keep their people. The ones that don't will wonder why their best engineers left for a competitor that lets them work in sweatpants.

If you're in the "start looking" camp, I built a bunch of free tools that might help: Resume ATS Checker, LinkedIn Headline Generator, Cover Letter Generator, Salary Negotiation Scripts, Follow-Up Email Generator, and Interview Prep Questions. All client-side, no data collection. Use them.

Skills-Based Hiring Is Real Now — Here's How to Use It to Your Advantage

charlie-morrison — Tue, 28 Apr 2026 00:45:33 +0000

72% of employers now prioritize what you can do over where you went to school.

That stat comes from 2026 hiring surveys. Companies like Google, IBM, and Apple dropped degree requirements years ago. The rest of the market is catching up.

If you don't have a traditional background — no CS degree, career switcher, self-taught — this shift is the best thing that's happened to job searching in a decade. But only if you know how to position yourself.

What "Skills-Based Hiring" Actually Means

Old model: recruiter scans resume for degree, filters by years of experience, schedules interview.

New model: recruiter scans for demonstrated skills, checks for portfolio evidence, schedules a skills assessment.

The practical difference: your resume needs to prove you can do the work, not that you sat in a classroom.

How to Rewrite Your Resume for Skills-Based Hiring

1. Lead With a Skills Summary, Not an Objective

Replace this:

"Seeking a challenging position in software development where I can leverage my degree..."

With this:

"Full-stack developer. Built and deployed 3 production apps (React + Node). Reduced API response times by 40%. Open-source contributor (2,400+ GitHub contributions)."

No degree mentioned. No years counted. Just what you can do and proof you've done it.

2. Reframe Experience as Capability Demonstrations

Instead of listing duties, show outcomes that prove skills:

Duty-based:

Responsible for maintaining the company blog
Managed social media accounts

Skills-based:

Grew blog traffic from 5K to 45K monthly visitors through SEO optimization (Google Analytics, Ahrefs, WordPress)
Built social media presence across 4 platforms — 18K followers, 4.2% engagement rate (Hootsuite, Canva, Buffer)

The second version proves SEO skills, analytics skills, platform expertise — without ever saying "5 years of experience."

3. Add a "Projects" Section

For career switchers or self-taught professionals, Projects is more valuable than Work Experience:

Projects
- E-commerce Dashboard — Real-time analytics for a Shopify store.
  React, D3.js, Shopify API. [Live demo link]
- Open Source: DataClean — Python library for data cleaning.
  340+ GitHub stars, 12 contributors, 2K+ monthly PyPI downloads.

Hiring managers in skills-based companies don't care if you built this at a job or on your couch at 2 AM. They care that you built it.

The Certification Sweet Spot

With skills-based hiring, the right certification can replace years of experience. But not all certs are equal.

High-value:

AWS Solutions Architect / Cloud Practitioner
Google Data Analytics Professional Certificate
CompTIA Security+
PMP (for project management)

Low-value:

Random Udemy course certificates
LinkedIn Learning badges
Anything without a proctored exam

The test: if someone can get it by clicking "next" 50 times, it doesn't prove a skill.

How to Find Skills-Based Employers

Filter for "no degree required" on LinkedIn and Indeed
Look for skills assessments in the application — companies that test you have already made the shift
Check JD language: "proven ability to..." = skills-based. "5+ years of..." = credential-based.
Target companies that publicly dropped degree requirements: Google, Apple, IBM, Accenture, Bank of America, Delta

The Portfolio Beats Everything

A one-page case study showing "I identified X problem, tried Y approach, achieved Z result" is worth more than a resume full of bullet points.

What your portfolio needs:

The skill in action (not just listed)
The outcome (what changed)
Your process (how you approached the problem)

Quick Check: Is Your Resume Skills-Based?

[ ] Skills summary appears above work experience
[ ] Every bullet includes a measurable outcome
[ ] At least 3 tools/technologies named per role
[ ] "Projects" section with links to work
[ ] No reliance on degree as primary qualifier
[ ] Keywords match the JD's required skills

Check your resume: Free ATS Resume Checker — runs in your browser, no data collection.

Practice before the interview: Free Interview Question Generator — get personalized questions for any role.

The shift to skills-based hiring is here. The question is whether your materials reflect what you can do, or just where you've been.

Full AI-powered job search system — 100+ prompts for every stage: Job Search AI Toolkit ($12).

I Applied to 200 Jobs and Got 3 Interviews — Here's What Finally Worked

charlie-morrison — Tue, 28 Apr 2026 00:38:53 +0000

The first 100 applications taught me nothing. Same resume, same cover letter template, same job boards. I'd spend Sunday evening blasting out 20 applications and feel productive. Then silence. For weeks.

By application 150, I was burned out. I started questioning whether I was even qualified for my own career. The rejection emails (when they came at all) were form letters that told me nothing.

Then I changed my approach completely. The next 50 applications got me 3 interviews and 1 offer. Here's the breakdown of what was different.

Phase 1: The Spray-and-Pray Mistake (Applications 1–100)

My strategy: find jobs on LinkedIn and Indeed, click "Easy Apply," attach my one resume, move on. Volume was the game.

Results: 0 interviews. Maybe 5 automated rejections. The rest was silence.

What I learned later: Most "Easy Apply" listings get 200-500+ applications. With a generic resume, you're a number. The ATS filters you out before anyone reads your name.

Phase 2: The Optimization Phase (Applications 101–150)

I started tailoring my resume. Keyword matching. Different versions for different roles. Better cover letters. I even ran my resume through an ATS checker and fixed 12 issues I didn't know existed.

Results: 0 interviews, but I started getting personal rejection emails instead of silence. That sounds like nothing, but it meant humans were actually reading my application. Progress.

What was still wrong: I was still applying to the same saturated job boards. The channel was the problem, not just the content.

Phase 3: The Pivot (Applications 151–200)

Three changes made all the difference:

1. I Stopped Using "Easy Apply"

Instead of bulk-applying on LinkedIn, I started going directly to company career pages. Smaller applicant pools. Sometimes I was one of 15 applicants instead of 400.

How to find these: Google "[job title]" site:greenhouse.io or "[job title]" site:lever.co — these are the direct application portals that many companies use.

2. I Started Reaching Out Before Applying

For roles I genuinely wanted, I'd find someone on the team (not HR) and send a short message:

"Hey [Name], I saw the [Role] opening. I've been working on [specific relevant thing] and the team's work on [specific project] caught my attention. Would you have 10 minutes this week for a quick chat? No pressure at all."

Response rate: About 30%. Those conversations didn't guarantee anything, but when I did apply, my name was already familiar.

3. I Applied to Fewer Jobs but Better

Instead of 20 applications per weekend, I did 5 per week — but each one was genuinely tailored:

Resume customized with the JD's exact language
Cover letter referencing something specific about the company (a recent blog post, a product launch, a public metric)
Follow-up email sent 5 days after applying

Results: 3 interviews from 50 applications (6% hit rate vs 0% before). One turned into an offer.

The Math That Changed My Thinking

Spray-and-pray: 150 applications × 15 minutes each = 37.5 hours → 0 interviews

Targeted approach: 50 applications × 45 minutes each = 37.5 hours → 3 interviews

Same total time. Completely different results. The bottleneck was never effort — it was strategy.

Dealing With the Mental Side

Job searching is lonely. Nobody talks about how demoralizing it is to put yourself out there repeatedly and get nothing back. A few things that helped:

Set a weekly cap. I limited myself to 5 quality applications per week. This prevented the burnout spiral of mass-applying and feeling terrible about the silence.

Track everything in a spreadsheet. Company, date applied, method, status, follow-up date. Seeing the data made it feel less emotional and more like a project I was managing.

Take real breaks. Not "I'll check job boards on my phone while watching TV" breaks. Actual days where I didn't think about applications at all.

Remember the base rate. Even in a great market, response rates for cold applications are 2-5%. If you're at 0% with 50 applications, you're not failing — you're within normal variance. It's the system, not you.

Tools I Actually Used

Resume ATS Checker — caught formatting issues I missed
LinkedIn Headline Generator — tested different angles for my profile
Cover Letter Generator — starting point I customized per company
Follow-Up Email Generator — timed follow-ups after applications

All free, all run in your browser, no data collection.

The Uncomfortable Truth

Most job search advice tells you to "network more" or "optimize your resume." Both matter. But the real shift was psychological: stop trying to be good enough for everyone, and start being specific enough for someone.

A tailored application to one company where you've done your research beats 20 generic ones. Every time.

If you want the full AI-powered job search system with 100+ prompts for every stage (research → apply → interview → negotiate): Job Search AI Toolkit — $12.

How to Beat the ATS: A 2026 Resume Guide That Actually Works

charlie-morrison — Tue, 28 Apr 2026 00:38:47 +0000

If you've applied to 50+ jobs and heard nothing back, it's probably not your experience — it's your resume formatting.

Most companies use an Applicant Tracking System (ATS) to filter resumes before a human ever sees them. Up to 75% of resumes get rejected by ATS before reaching a recruiter.

I spent the last month reverse-engineering how these systems work. Here's what I found.

What ATS Actually Looks For

ATS software parses your resume into structured data: name, email, work history, skills, education. If it can't parse a field, that field doesn't exist.

Things that break ATS parsing:

Tables and columns (most ATS can't read them)
Headers and footers (often ignored entirely)
Images, logos, icons (invisible to parsers)
Fancy fonts or unusual characters
PDF created from design tools (vs. Word export)

The safest format: A single-column .docx or a clean PDF exported from Word/Google Docs. No tables. No graphics. Standard section headings.

The Keyword Match Problem

ATS scores your resume against the job description. If the JD says "project management" and your resume says "managed projects" — some systems won't match that.

How to fix it:

Copy the exact phrases from the job description. If they say "cross-functional collaboration," use those exact words somewhere in your resume.
Put keywords in context. Don't just list skills — embed them in achievement bullets. "Led cross-functional collaboration between engineering and marketing teams, reducing launch timeline by 3 weeks."
Use both the acronym and full term. Write "Search Engine Optimization (SEO)" so the ATS catches both variants.
Mirror the job title. If they're hiring a "Customer Success Manager" and your title was "Client Relations Lead" — add a note like "equivalent to Customer Success Manager" or adjust your title if honest.

Section Structure That ATS Expects

Most ATS systems look for these exact section headings:

Contact Information (name, email, phone, LinkedIn URL)
Summary or Professional Summary
Work Experience or Experience
Education
Skills

Creative headings like "My Journey" or "What I Bring" confuse parsers. Stick with the standard names.

Date format matters too. Use "Jan 2024 – Present" or "01/2024 – Present." Avoid "2024-present" or "Since January 2024."

Quantify Everything

ATS doesn't care about numbers, but the recruiter who reads your parsed resume does. The rule:

Every bullet point should have a number, percentage, or dollar amount.

Bad: "Improved team efficiency"
Good: "Improved team efficiency by 34% by implementing automated code review, saving 12 hours per sprint"

Bad: "Managed social media accounts"
Good: "Grew Instagram following from 2,400 to 18,000 in 6 months (650% increase) with $0 ad spend"

If you don't have exact numbers, estimate conservatively and say "approximately."

The Skills Section Strategy

Don't just dump every skill you've ever heard of. This gets you filtered out for keyword stuffing.

The formula:

List the top 8-10 skills from the job description
Add 3-5 of your strongest skills that aren't in the JD
Group them: Technical Skills | Tools | Soft Skills

Example:

Technical Skills: Python, SQL, Tableau, A/B Testing, Statistical Analysis
Tools: Google Analytics, Mixpanel, Jupyter Notebooks, dbt, BigQuery  
Soft Skills: Cross-functional Communication, Stakeholder Management

The "One Resume Per Job" Myth

You don't need a completely different resume for every application. But you do need 2-3 base versions tailored to different job types.

If you're applying to both "Data Analyst" and "Business Intelligence" roles, those need different keyword emphasis even if the work is similar.

My system:

Create a "master resume" with every bullet you've ever written
Build 2-3 targeted versions for your main job categories
For each application, spend 10 minutes swapping in keywords from the specific JD

Free Tool: Check Your Score

I built a free ATS Resume Checker that runs entirely in your browser (no data collection, no uploads to servers). It checks:

Resume length and formatting
Contact information completeness
Section structure
Action verbs and quantified achievements
Keyword matching against a job description

Paste your resume text + the job description, and it gives you a score out of 100 with specific fixes.

Quick Checklist Before You Apply

[ ] Single column, no tables or graphics
[ ] Standard section headings (Experience, Education, Skills)
[ ] Keywords from JD appear in context (not just listed)
[ ] Every bullet has a metric (number, %, $)
[ ] Both acronyms and full terms included
[ ] Clean .docx or text-based PDF
[ ] Tested with an ATS checker tool

The ATS isn't your enemy — it's a filter with predictable rules. Once you understand those rules, you stop getting ghosted and start getting interviews.

If you want the full toolkit with 100+ prompts for resume optimization, cover letters, interview prep, and salary negotiation: Job Search AI Toolkit ($12).