Minimalist Remote Job Board: PHP/Go Dual-Stack Backend With 10 Sites, 5 TG Channels, and 2 Discovery Sources

Recently unemployed and staying at home, I have been quietly running my blog while intermittently looking for remote work. Stepping away from the daily grind of office clock-ins, I often found myself hesitating: should I take on freelance gigs, pursue independent development and entrepreneurship, or look for a full-time remote job? After thinking it over, rather than agonizing over the choice, it seemed better to advance on all fronts and explore multiple paths simultaneously.
My tech stack is a PHP / Go dual-stack backend—PHP has been my primary language for years, and I have delved deep into Go’s concurrency model, microservice governance, and cloud-native practices. I can independently drive projects in both languages. Since I needed to “juggle multiple fronts” (finding full-time work, taking on freelance projects, and exploring startup directions), my information channels could no longer remain as chaotic as before.
I originally had nearly 30 websites + 10 TG channels piled up across two browser windows. But I quickly realized two things: my energy was severely depleted, and the information was highly redundant. Many “remote job aggregators” scrape data from Eleduck and V2EX, and Web3 positions often appear simultaneously across mainstream remote communities and specialized Web3 sites. Switching between dozens of sites usually just surfaced the exact same batch of job descriptions.
So, I went through three rounds of subtraction: first, I cut traditional job boards and inefficient small aggregators; next, I deduplicated the TG channels based on “whether they provided exclusive information”; finally, I separated two “channel discovery sources” to maintain at a low frequency. The final setup retains 10 core job websites + 5 TG channels + 2 discovery sources, covering domestic remote work, PHP/Go verticals, the Web3 sector, and overseas opportunities. This article serves as my personal “information acquisition guide.” Whether I pursue full-time work, freelancing, or independent development, I rely on it to feed me leads.
The flowchart below visualizes these three frequency tiers and their respective information sources:

flowchart LR
    A[Remote Job Search Information Sources] --> B[Daily · Passive Reception<br/>5 TG Channels]
    A --> C[Every Wednesday · Active Screening<br/>10 Job Websites]
    A --> D[Once a Month · Channel Discovery<br/>2 Navigation Sources]

    B --> B1[Remote Workers]
    B --> B2[Remote Work AI Intelligence Station]
    B --> B3[Mid-to-Senior IT Tech Recruitment]
    B --> B4[Overseas Remote / On-site Tech Recruitment]
    B --> B5[DeJob Web3 Recruitment]

    C --> C1[Remote China Aggregator]
    C --> C2[Eleduck / V2EX / yuancheng.work / Larajobs / StudyGolang / Golangprojects]
    C --> C3[DeJob / Rebase Issues / ABetterWeb3]

    D --> D1[greatghoul/remote-working<br/>channels directory]
    D --> D2[platform.work-work.org<br/>Web3 Platform Navigation]

Part 1: Core Job Websites (Active Search)

Based on three dimensions—”one-stop aggregation / language verticals / Web3 sector”—I retained the following 10 information sources. Each was chosen after comparison, either for offering exclusive information or for aligning well with one side of my dual stack.

1. One-Stop Aggregators (Replacing Countless Small Sites)

• Remote China (remote-china.com)
  • Reason for inclusion: An aggregation site maintained by veteran V2EX developer greatghoul, which already scrapes and summarizes job postings from mainstream domestic remote communities (V2EX, Eleduck, etc.). Checking this single site covers most public remote job openings in China, allowing you to delete the V2EX jobs node and various messy secondary aggregators.

2. Language Verticals (Aligned with PHP / Go Dual Stack)

• Eleduck Community
  • Reason for inclusion: The number one destination for domestic remote work. Although aggregation sites display its data, Eleduck itself offers the best interactivity and real-time updates. HR or bosses often reply directly under posts, and both full-time and part-time freelance gigs are available. Lurking actively here helps you seize the initiative.
• V2EX
  • Reason for inclusion: Although Remote China already aggregates V2EX’s job postings, aggregators cannot capture V2EX’s core “community interaction atmosphere” and “real-time discussions.” I added it back not just to read JDs, but to browse posts and lurk. Many hidden remote freelance gigs and technical partnership opportunities are often buried in the comment sections of daily technical exchanges or sharing posts. It helps maintain technical acumen, and the communication efficiency of replying instantly under posts to demonstrate professionalism is irreplaceable by cold aggregation sites.
• yuancheng.work
  • Reason for inclusion: This is an independent remote job posting platform, not a data-scraping aggregator—positions are published directly by companies on the site. When greatghoul shares remote opportunities on Douban, “yuancheng.work” is cited as an independent information source, rather than scraped from elsewhere.
• Larajobs
  • Reason for inclusion: Replaced the original Learnku job board—the latter simply had too few opportunities. Larajobs is the most established dedicated job board in the Laravel ecosystem. The positions are almost exclusively PHP/Laravel full-time and contract roles, with a high proportion of remote work and a signal-to-noise ratio far exceeding that of general community job boards. For someone with my primary PHP stack, this is the most relevant entry point.
• StudyGolang Job Board
  • Reason for inclusion: A vertical community for the domestic Go scene. The communication efficiency for positions is far higher than searching for a needle in a haystack on general platforms, making it suitable for tracking domestic Go remote opportunities.
• Golangprojects (golangprojects.com)
  • Reason for inclusion: One of the earliest dedicated Go job sites globally, with a large accumulation of positions and support for filtering by “Remote only”. I added this site to cover the overseas Go remote sector—domestic Go positions have a limited ceiling, while overseas remote Go roles (especially in Web3, cloud-native, and observability) offer better salaries and remote-friendliness.

3. Web3 Sector (Remote-heavy, Suitable for Freelance and Startup Exploration)

• DengLian Community (learnblockchain.cn)
  • Reason for inclusion: This is one of the domestic Web3 developer communities with the highest content quality and longest operational history. Since its establishment in 2017, it has accumulated a wealth of systematic blockchain technical blogs, Chinese documentation, and Q&A. Although its built-in job board doesn’t have many positions, I included it primarily as a “learning gateway.” Its Web3 learning roadmap, tutorials for various ecosystems like EVM/Solana/Move, and topics like DeFi, zero-knowledge proofs, and smart contract security perfectly fill the gap in systematic knowledge I need to extend from a PHP/Go backend into Web3. It is not a channel for directly browsing jobs.
• DeJob (dejob.ai)
  • Reason for inclusion: Currently one of the most comprehensive and fastest-updating platforms for Web3 industry recruitment. Well-known projects and teams basically post their JDs here. There are many R&D roles, and both full-time remote and Bounty tasks are available, making it very friendly for freelancers.
• Rebase Network Who is Hiring (GitHub Issues)
  • Reason for inclusion: The Web3 circle values open source and geek culture. Rebase’s GitHub Issues is a place where many small teams and startup projects recruit directly. It has a strong direct-hiring attribute and also serves as a window for finding potential startup partners. (Search for golang / php directly in the Issues)
• ABetterWeb3 (abetterweb3.notion.site)
  • Reason for inclusion: A community-maintained Notion job board. It features many direct hiring posts from Chinese Web3 projects with stable updates, making it convenient to filter for full-time/part-time and language requirements directly within the table.

Note: The three Web3 sites in the website section are for “active screening.” Together with the Web3 channel in the TG section below, they form an “active + passive” dual-channel approach for the same sector, rather than two sets of duplicate information—the TG side only retains push sources that do not overlap with the websites.

Part 2: Telegram Channel Subscriptions (Passive Reception)

Actively browsing websites consumes energy, whereas TG channels act like precise information stream recommenders. Among the original 10 channels, quite a few were secondary distributions of the same positions found on the websites above (for example, abetterweb3’s TG channel completely duplicated the Notion website), and some had small subscriber counts and low signal-to-noise ratios. After deduplicating based on “whether they provide exclusive information not covered by the websites,” I narrowed it down to 5.
I will continue to tweak this section later, but below is the current streamlined version.

• Remote Workers (23,900 subscribers): Operated by greatghoul, syncing the highlights from remote-china, serving as the main push source for general aggregation.
• Remote Work AI Intelligence Station (600 subscribers): After subscribing, it automatically pushes matching positions based on relevance. It is currently the only channel where you “don’t have to manually scroll.” The signal-to-noise ratio is good, making it worth keeping and nurturing.
• Mid-to-Senior IT Tech Recruitment (6,200 subscribers): Focused on domestic mid-to-senior roles, serving as a backup source for expanding into higher-level positions.
• Overseas Remote / On-site Tech Recruitment (7,500 subscribers): The main push source for overseas opportunities, and also a window for accessing overseas freelance projects (there are 3 similar overseas channels with highly overlapping content; for now, only this one is retained).
• DeJob—Web3 Recruitment & Job Search Channel (44,500 subscribers): Corresponds to the DeJob website. A must-follow for the Web3 sector, featuring the largest subscriber base and the fastest updates.

Removed: abetterweb3 Recruitment & Job Search TG (duplicated the Notion website), Overseas Tech Recruitment/Remote/On-site, Overseas IT Tech Recruitment | Overseas Programmer Jobs (overlapped with the retained overseas channel), Remote Work Job JDs, Remote Work Hub (small subscriber count, duplicated “Remote Workers”).

Part 3: Channel Discovery Sources (Monthly Inspection, Used to Discover New Channels)

The previous 10 websites + 5 TG channels solve the problem of “daily lead feeding,” but the remote and Web3 recruitment ecosystems change rapidly, with new platforms emerging from time to time. Therefore, I separately retained the two navigation sources I used when initially collecting channels. Their positioning is “sources for discovering new channels” rather than “entrances for browsing jobs”—they do not post JDs directly, but rather aggregate “where to find JDs.” The frequency can be dialed down to once a month.

• greatghoul/remote-working (channels directory)
  • GitHub URL: https://github.com/greatghoul/remote-working/tree/master/channels
  • Positioning: One of the most comprehensive open-source repositories for domestic remote work resources. The channels directory continuously catalogs new remote work websites, communities, and channels. Maintained jointly by greatghoul and the community, it is the source for discovering new domestic remote channels.
  • How to use: Click in to review the channels directory and recent commits once a month. Evaluate whether any newly added channels are worth incorporating into the core website list; do not use it for browsing jobs on a daily basis.
• platform.work-work.org
  • Positioning: An aggregated navigation for Web3 recruitment platforms, summarizing the entry points for a host of Web3 job sites like DeJob, ABetterWeb3, and Rebase. It is the source for discovering new Web3 channels.
  • How to use: Similarly, inspect it once a month to see if any new Web3 recruitment or Bounty platforms have launched, and then decide whether to include them in the core list. For daily job browsing, go directly to DeJob / Rebase Issues / ABetterWeb3 without detouring through the navigation site.

These two sources act as “gatekeepers”—ensuring that streamlining doesn’t cause us to miss out on emerging quality channels, while also not consuming daily energy. The iteration rhythm of the core list is driven by them: discover new channels → evaluate → replace or add to the 8+5 list.

Part 4: Refresh Rhythm

With passive push notifications from TG + low-frequency inspections from the two discovery sources, the rhythm is adjusted into three tiers: “daily passive + weekly active + monthly inspection.”

🗓️ Daily (Passive Reception, Fragmented Time)

Casually scroll through the 5 TG channels. When you see titles containing “PHP”, “Go”, “Golang”, “Backend”, or “Bounty”, click to open them; forward suitable ones to “Saved Messages” for unified processing later. Among them, the “Remote Work AI Intelligence Station” will automatically push based on match relevance, essentially eliminating the need to scroll actively.

🗓️ Every Wednesday (Active Screening, Centralized Submissions, Approx. 1 Hour)

Open the 10 core job websites centrally:

• First 20 minutes: Scan Larajobs (PHP), StudyGolang + Golangprojects (Go) to see if any relevant positions or freelance gigs were posted on these vertical sites over the past week.
• Middle 20 minutes: Open Remote China and yuancheng.work, Ctrl+F search for “PHP” and “Go” to fish out domestic general remote positions that TG might have missed; casually check Eleduck for new posts and comment replies.
• Last 20 minutes: Immerse in browsing the three Web3 sites (DeJob, Rebase Issues, ABetterWeb3),集中读 JD、判断项目靠谱度。
  Set aside Wednesday to uniformly process the leads collected this week: submit full-time resumes, reply to freelance requests, or chat with potential startup project teams.

🗓️ Once a Month (Channel Inspection, Approx. 30 Minutes)

Open the 2 discovery sources: greatghoul/remote-working’s channels directory and platform.work-work.org. Check if any new remote/Web3 recruitment channels have emerged recently, and after evaluation, decide whether to replace or add them to the core list. This tier is not for browsing jobs, but purely to prevent information sources from aging.

In Closing

Cutting out duplicate noise and focusing only on high-quality information sources is meant to channel the saved energy into what truly matters—reviewing Go’s concurrency and microservices, improving open-source projects, taking on freelance gigs, and writing blog posts to consolidate technical knowledge. Retaining the two discovery sources as “gatekeepers” ensures that streamlining doesn’t lead to missing out on newly emerging quality channels. Whether I ultimately move toward full-time remote work, freelancing, or independent development, this minimalist “8+5+2” dashboard is the foundation for my multi-track progression.