The-DevOps-Daily / The-DevOps-Daily/devops-daily
DevOps job board
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- TypeScript
- Stars
- 1.1k
- Forks
- 392
- Avg merge
- 5h 8m
- Merged PRs (30d)
- 121
Description
Summary
DevOps engineers looking for jobs is a huge, high-intent audience. Aggregate listings from public sources and republish on /jobs. Auto-refresh daily via GitHub Actions.
Sources to aggregate
- HN Who's Hiring threads (parse monthly thread, extract listings tagged DevOps/SRE/Platform)
- YC Work at a Startup public feed
- Company careers pages via JobSchema (if they publish it) or scraping
- Well-known DevOps-first companies' RSS feeds (HashiCorp, Grafana, CNCF-adjacent orgs)
Features
- Filter by role (DevOps / SRE / Platform / Cloud Architect)
- Filter by remote / region
- Salary band when available
- Experience level
- "Last seen" timestamp — freshness indicator
- Sort by recency / salary / seniority
Architecture
- GitHub Actions cron runs scraper daily
- Writes to
content/jobs/*.json - Static regen picks up new listings on next build
- Failed / stale listings auto-expire after 30 days
Monetization angle
- Featured listings (paid promotion at the top)
- Company profile pages
- Newsletter cross-promo ("3 new DevOps jobs this week")
Why
- High-intent audience with commercial value
- Complements our educational content (people learning DevOps eventually need jobs)
- Natural sponsor surface
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the /jobs entry point and reviewing the existing build and GitHub Actions workflow structure. Inspect content/jobs/*.json and determine how the static build consumes it. Done means daily aggregation from the listed sources, filtering and sorting, freshness-based expiry, and the proposed job-board features are implemented and documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- content, devops, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100