Red Flags in Remote Job Postings Every Developer Should Know

When you're actively searching for a remote developer role, there's pressure to apply quickly. New listings feel urgent. You don't want to miss a good one. So you skim the description, check a few requirements, and hit apply.

This speed works against you when the listing itself is the problem. Not every remote job posting is honest about what the role involves, how the company operates, or whether the position even exists in the form described. Some are misleading by accident (sloppy writing, outdated templates). Others are misleading by design (lead generation, bait-and-switch, outright scams).

Learning to spot the warning signs takes practice, but it saves a lot of wasted time. Here are the red flags that experienced developers learn to watch for.

"Remote" that isn't actually remote

This is the most common bait-and-switch in remote job listings, and it comes in several flavors.

"Remote but must be within commuting distance." The listing says remote, but somewhere in the fine print it requires you to live within 50 miles of an office for "occasional" in-person meetings. "Occasional" might mean quarterly, or it might mean every Tuesday. You won't know until you ask, and by then you've already spent time on the application.

"Remote during probation, then hybrid." Some companies offer remote work for the first few months and then expect you to transition to hybrid once onboarded. This is a legitimate arrangement for some people, but it should be stated clearly in the title, not buried in paragraph four of the description.

"Remote (US only)" with no further explanation. This might mean the company has a legitimate tax or compliance reason for geographic restrictions. Or it might mean they want US time zone coverage but listed it as "remote" to game the search filters. If the listing says remote but restricts you to a specific metro area, it's hybrid with extra steps.

The Stack Overflow Developer Survey consistently shows that developers rank misleading remote tags as one of their top frustrations with job boards. The fix from your end is simple: before applying, check the company's career page directly and look for their stated remote work policy. If it's not clear there, ask in the first screen.

No salary information at all

Pay transparency laws are expanding (Colorado, California, New York, Washington in the US; the EU Pay Transparency Directive across Europe), but plenty of remote postings still skip salary entirely. This is a yellow flag at minimum.

Here's the thing: companies that pay well usually want you to know about it. Competitive compensation is a selling point. When a company hides the salary, the most common reason is that the number isn't competitive and they'd rather discuss it after you're already invested in the process.

Hired's State of Software Engineers report found that roughly 40% of tech listings still omit compensation data. That's a lot of listings where you're flying blind.

What to do: check Levels.fyi and Glassdoor for the company's typical ranges. If the company is too small for public salary data and the listing doesn't mention compensation, consider whether the role is interesting enough to justify the gamble. If not, move on. Your time is worth more than a mystery salary.

Platforms that aggregate from many sources can help here. Remote Genie AI lets you filter by salary range upfront, so you only see roles that meet your minimum before you start reading descriptions.

Vague role descriptions

A well-written job posting tells you what you'll actually be doing. A vague one tells you nothing while using a lot of words.

Watch for descriptions that are mostly corporate filler:

• "You'll work on challenging problems in a fast-paced environment"
• "We're looking for a passionate developer who loves to learn"
• "You'll collaborate cross-functionally with stakeholders to drive impact"

None of these sentences contain information. They don't tell you what the tech stack is, what the team builds, who you'd report to, or what a typical week looks like. If a company can't articulate what the job involves, that's either a sign they haven't thought it through or they're deliberately keeping it vague to attract a wide pool and sort later.

Good job postings tell you: what the team is building, what technologies you'll use, who you'll work with, what problems you'll solve in the first 6 months, and what seniority level they're actually hiring for. If most of those are missing, the listing isn't worth your time.

Unrealistic requirements lists

You've seen these. A listing that asks for:

• 8+ years of experience with a framework that's been around for 5 years
• Expert-level proficiency in 6 different programming languages
• "Full-stack" meaning backend, frontend, mobile, DevOps, and database administration
• Senior title with mid-level compensation

These postings are usually written by someone who doesn't understand the role, often an HR generalist or a manager who copied requirements from three different positions into one listing. Sometimes they're aspirational wish lists where the company plans to hire whoever seems closest. Other times they're genuinely looking for a unicorn and will keep the listing open for months.

The risk isn't that you won't get the job. The risk is wasted time. If the requirements are incoherent, the role itself might be poorly scoped, which means unclear expectations, scope creep, and frustration once you're in the seat.

A reasonable rule: if you match 60-70% of the requirements, it's usually worth applying. If the requirements read like they were written for three different people, think twice.

The listing has been up forever

A job posting that's been active for three months is telling you something. Either the company is being extremely selective (possible but uncommon for standard engineering roles), or there's a reason they can't fill it.

Common reasons a listing stays open indefinitely:

The compensation is below market and qualified candidates keep declining offers. The requirements are unrealistic. The team has a reputation problem (high turnover, bad management) and word has spread. The company is "collecting resumes" without an immediate plan to hire. Or the listing is evergreen and they hire from it periodically, which is legitimate but usually stated.

Check the company's Glassdoor reviews, especially recent ones from the engineering team. Look at LinkedIn to see if the team has had a lot of departures in the past year. This takes five minutes and can save you from walking into a bad situation.

Scam postings

Remote work scams have increased alongside the growth of legitimate remote hiring. Most target junior developers or people new to remote work, but they can catch anyone who's moving quickly through applications.

Warning signs:

The "interview" is conducted entirely over text chat, never video or phone. Legitimate companies want to see and talk to candidates.

You're asked to pay for equipment, training, or a background check. Real employers cover these costs.

The offer arrives after a single short conversation with no technical assessment. Engineering hiring almost always involves some form of technical evaluation.

The email comes from a Gmail or Outlook address instead of a company domain. This alone doesn't confirm a scam, but combined with other signals it's a strong indicator.

The company name doesn't match anything you can find online, or the website is a single page with stock photos and no real content.

If something feels off, trust that instinct. Look up the company independently (not through links they send you), check if the role exists on their actual career page, and search for "[company name] scam" before sharing any personal information.

Too much emphasis on "culture" with no substance

A listing that spends two paragraphs on the tech stack and eight paragraphs on how amazing the culture is should raise an eyebrow. Culture sections aren't bad by themselves, but when they dominate the posting while the actual role details are thin, it's often a sign that the company knows the job itself isn't the selling point.

Watch for phrases like "we're a family" (usually means poor boundaries) and "we work hard and play hard" (usually means long hours). "Unlimited PTO" sounds generous, but multiple workforce studies have found that employees at companies with unlimited policies actually take less time off than those with a fixed number of days.

The best signal for company culture isn't the job posting. It's Glassdoor reviews, the company's engineering blog, and conversations with current or former employees.

Suspicious urgency

"We need to fill this role immediately." "This posting closes in 48 hours." "Apply now before it's too late."

Legitimate companies do have urgent hiring needs sometimes. But artificial urgency in a job posting is a pressure tactic. It's designed to make you skip due diligence, apply quickly, and accept faster than you normally would.

Good roles don't need pressure tactics. If a company's work is interesting and the compensation is fair, they don't need to rush you. Take your time. Any company that loses interest because you took three days instead of three hours to apply isn't one you want to work for.

How to protect your time

You can't avoid every bad listing, but you can build habits that minimize exposure.

Spend 60 seconds vetting before you invest 30 minutes applying. Check the company's career page. Skim their Glassdoor. Look at the salary data. This quick check catches most of the problems listed above.

Use platforms that do some vetting for you. Aggregators that deduplicate and surface fresh listings reduce your exposure to stale and duplicate postings. Remote Genie AI aggregates from 20,000+ sources and prioritizes recent, active listings, so you spend less time weeding out dead postings yourself.

Upload your CV to get AI-ranked results. When the platform matches your profile against job descriptions, the most relevant roles surface first. You spend your time on roles that actually fit rather than clicking into listings that turn out to be mismatches.

Track what you apply to. A job tracker helps you notice patterns: if you keep running into the same red flags from certain companies or boards, you can adjust your sources.

Conclusion

Most remote job listings are legitimate. But enough of them are misleading or poorly written that building a quick vetting habit pays off fast. The 5 minutes you spend checking a company before applying is almost always cheaper than the hour you spend on an application that leads nowhere.

Make it part of your process: check the company, look at salary data, read the full description for actual content, and trust your instincts when something feels off.

Start your search with Remote Genie AI where listings are aggregated from 20,000+ sources, filtered by your criteria, and ranked by CV fit, so more of what you see is already worth your time.