Skip to content
← Back to all posts
interviews

I Got Tired of Fake Remote Jobs. So I Built My Own Board

A developer working on a laptop with a global job map and clean developer desk

BLUF: When I published I Explored Remote Jobs Without Remote Experience, I did not expect it to resonate so strongly. Many developers reached out to me with the exact same frustration: finding active, legitimate remote engineering jobs without getting trapped in recruiter spam, stale postings, or sign-up paywalls is exhausting. So instead of just writing another advice post, I spent time building something practical: the DevScrolls Remote Job Board. Here is an honest look at why I built it, how we collect and filter the jobs, where the application links actually go, and what we recently upgraded.

Here is the outline of what we will cover:

  1. The Conversations After My Last Post
  2. What Makes Most Job Boards So Frustrating
  3. How We Actually Collect and Filter the Jobs
  4. Where the Application Links Go and What We Upgraded
  5. Realistic Tips for Landing a Remote Role
  6. Staying in the Loop Without the Job Hunt Fatigue

1. The Conversations After My Last Post

When I wrote about exploring global remote work as an Indian developer, I shared my honest experience — the interviews, the take-home tasks, the hesitation around PF statutory benefits, and why I ended up walking away from an offer.

After that post went live, many developers reached out to me on LinkedIn.

Some were junior frontend developers trying to land their first full-time role. Others were senior engineers with 8+ years of experience who were tired of spending 3 hours commuting every day in Bangalore or Pune.

Almost everyone shared the same headaches:

  • “I spend an hour filtering for remote jobs, only to find in the fine print that they expect you in an office three days a week.”
  • “Half of the listings I apply to turn out to be posted 3 months ago with zero responses.”
  • “Recruiting portals make me enter my phone number and upload my resume before even showing me the application link, and then I get spammed by agencies.”

It became clear to me that developers do not need another motivational thread on Twitter or LinkedIn. What we need is a clean, reliable place to check active roles without jumping through hoops.


2. What Makes Most Job Boards So Frustrating

If you have spent even a few evenings searching for remote roles, you have likely run into these three major issues:

  • Ghost Postings: Many portals leave job listings open for months. Sometimes companies do this to collect resumes for future talent pools, or they simply forget to take the post down after hiring someone. You end up spending 45 minutes tailoring your resume for a job that does not exist.
  • Aggregator Traps: You click “Apply,” and instead of taking you to the job, you get redirected through two different ad trackers, landing on an agency site that asks you to create yet another account with a password.
  • Fake Remote Tags: A posting will say “Remote” in the title, but once you read paragraph four, it says “Remote within a 30-mile radius of Berlin” or “Hybrid: 2 days remote, 3 days on-site.”

As developers, we build tools to automate repetitive tasks and eliminate friction. Job hunting should not feel like navigating a maze of dark patterns.


3. How We Actually Collect and Filter the Jobs

I wanted to make this job board as practical and transparent as possible.

Instead of building a closed network or pretending I personally know every hiring manager on earth, we built an automated ingestion and filtering system. Here is how it works under the hood:

  1. Aggregating Verified Sources: We connect to open feeds and verified remote tech APIs (such as Jobicy, Remotive, and curated developer job feeds from tech startups and verified hiring boards).
  2. Filtering Out Non-Engineering Noise: We run the incoming data against negative keyword filters. We automatically throw out recruiting roles, sales, marketing, call-center tasks, and non-technical gigs. Only software engineering, frontend, backend, full-stack, UI/UX, and systems roles make the cut.
  3. Smart Tech Stack Tagging: We inspect the job titles and requirements to automatically tag the roles by relevant tech stacks — React, TypeScript, Node.js, Python, Go, Java, or AI/ML — so you can find what matches your skillset instantly.
  4. Region Normalization: We classify the roles into clear regional buckets: Worldwide (open to anywhere), United States, Europe & UK, and Canada.

Let me be completely transparent about how the job board works for you:

When you find a role on the DevScrolls Job Board and click “Apply,” it redirects you directly to the original verified job post or application portal.

Depending on the company, this might be their direct career portal (like Greenhouse, Ashby, or Lever) or the verified job page where the employer originally listed the role.

There are no registration gates on our site. You do not need to create an account, enter your phone number, or pay anything to browse or apply.

30-Day Rolling Cleanup

One of the biggest upgrades we shipped recently is strict freshness pruning.

Any job listing older than 30 days is automatically purged from the board. If you see a role listed, it was published recently. You will not find stale 90-day-old listings cluttering your search.

Clean Region & Tech Filters

We added one-click region toggles at the top of the board. If you are only looking for roles that hire globally without timezone restrictions, hit Worldwide. If you are looking for US-based contractor roles, select US.

Native Article Discussions

Along with the job board, we upgraded the entire site with community discussion sections. On every article, you can now log in using your Google or GitHub account to leave a comment, ask a question, or share interview feedback without creating a separate password.


5. Realistic Tips for Landing a Remote Role

From reviewing hundreds of incoming remote job postings while building this board, a few patterns stand out:

  • Tailor for Asynchronous Communication: In an office, you can explain yourself with hand gestures and whiteboards. In a remote team, you are judged by how clearly you write pull request descriptions, documentation, and Slack messages. A clean, well-written introductory note goes a long way.
  • Show Your Work Publicly: International teams rarely check college degrees from other countries. They look at what you have actually built. Having a live tool, an open-source project, or a technical write-up showing your problem-solving process gives you immediate credibility.
  • Apply in the First Few Days: Because remote postings get applicants from across the globe, companies often pause intake after receiving a couple of hundred resumes. Checking for fresh roles every couple of days gives you a significant advantage over applying to week-old postings.

6. Staying in the Loop Without the Job Hunt Fatigue

Spending hours scrolling job boards every single day is the fastest way to burn yourself out. A better strategy is setting aside 20 minutes a few times a week, or letting the updates come to you.

Here are two simple ways to stay updated:

  1. Weekly DevScrolls Newsletter: Once a week, I send out an engineering dispatch featuring our latest frontend deep dives, architecture breakdowns, and platform updates. No spam, no marketing fluff — just honest engineering content. You can subscribe right below.
  2. The DevScrolls Telegram Channel: If you prefer quick updates on your phone, join our Telegram Channel. Whenever I publish a new article or update the platform, I drop the direct link there so you never miss a new post.

Take a look at the Remote Job Board, try out the filters, and let me know in the discussion below what other features or filters would be helpful for your search.

Clap
0Discussion
—
Unique views
Santhanakrishnan

Written by Santhanakrishnan

Senior Frontend Engineer & UI Architect with 7+ years of experience building scalable design systems, high-performance web architectures, and clean user experiences.

Discussion

0
Loading discussion...