dice-easy-apply
Automate Dice.com Easy Apply searches and applications with Puppeteer/Chromium, resume and cover-letter uploads, remote-role filtering, and conservative application guardrails.
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 6
- Forks
- 0
01 前言 Front Matter
- name
- dice-easy-apply
- license
- MIT
- metadata
- { "tags": [ "jobs", "dice", "automation", "puppeteer", "easy-apply" ], "supported_agents": [ "claude-code", "openclaw", "hermes", "codex", "cursor", "windsurf", "goose", "aider", "roo-code", "cline" ] }
- description
- Automate Dice.com Easy Apply searches and applications with Puppeteer/Chromium, resume and cover-letter uploads, remote-role filtering, and conservative application guardrails.
- when_to_use
- Use when you need an AI agent to search Dice.com jobs and submit Dice Easy Apply applications from a verified resume and cover letter.
02 资源文件 1
- 参考文档skill-report.json60.9 KB
03 SKILL.md 正文
Dice Easy Apply Automation
This skill helps an AI coding/operations agent build and run a repeatable Dice.com Easy Apply workflow.
It is intentionally public and credential-free. It contains no usernames, passwords, cookies, private profile paths, or user-specific secrets.
What it does
- Searches Dice jobs using the explicit Remote workplace filter.
- Focuses on software, web, full-stack, frontend/backend, AI, GenAI, LLM, Claude/OpenAI/Codex-style roles.
- Uses Dice in-site Easy Apply flows only, unless the operator explicitly approves external ATS applications.
- Uploads a verified resume PDF and optional cover-letter PDF.
- Uses a persistent Chromium profile so login can be performed manually once and reused safely.
- Keeps state/log files so daily reruns avoid duplicates.
- Skips roles with explicit onsite/hybrid/local/travel/clearance constraints or unknown required questions.
Safety rules
- Do not store job-board credentials in scripts, skills, memory, logs, or reports.
- Pass credentials only via one-off environment variables if absolutely necessary, or use a pre-authenticated browser profile.
- Stop for CAPTCHA, MFA, suspicious-login checks, identity verification, or account-security prompts.
- Do not fabricate answers. Skip forms requiring salary expectations, essays, custom cover letters, relocation preferences, travel, or unverifiable facts.
- Treat Dice match percentages as advisory only. Do not skip a role solely because Dice reports a low match score if the role title is inside the resume's wheelhouse.
- Gen AI / Generative AI Engineer should be treated as a software-engineering role when the resume supports web/software/AI work.
Recommended search URL
Use Dice's remote filter directly, not a radius search:
https://www.dice.com/jobs?filters.workplaceTypes=Remote&filters.easyApply=true&q=<QUERY>
For contract/direct-hire filtered searches, add Dice's employment and employer filters:
https://www.dice.com/jobs?filters.easyApply=true&filters.employmentType=CONTRACTS&filters.employerType=Direct+Hire&filters.workplaceTypes=Remote&q=<QUERY>
Useful query set:
gen ai engineer
generative ai engineer
llm engineer
ai full stack engineer
frontend ai engineer
web developer
full stack engineer
node react engineer
javascript engineer
typescript engineer
react developer
node.js developer
svelte developer
software engineer
Environment variables
RESUME_PDF=/absolute/path/to/resume.pdf
COVER_PDF=/absolute/path/to/cover.pdf
CHROME_PROFILE=$HOME/.cache/dice-chrome
STATE_DIR=/tmp/dice-easyapply-daily
MAX_SCAN=120
MAX_APPLY=15
DRY_RUN=1
SEARCHES='gen ai engineer|llm engineer|full stack engineer|react developer'
EMPLOYMENT_FILTER=CONTRACTS
EMPLOYER_TYPE='Direct Hire'
Puppeteer launch pattern
const puppeteer = require('puppeteer');
const browser = await puppeteer.launch({
headless: false,
executablePath: process.env.CHROME_BIN || '/snap/bin/chromium',
userDataDir: process.env.CHROME_PROFILE || `${process.env.HOME}/.cache/dice-chrome`,
defaultViewport: null,
args: ['--no-sandbox', '--disable-setuid-sandbox', '--disable-dev-shm-usage', '--start-maximized']
});
let page = await browser.newPage();
page.setDefaultTimeout(30000);
page.on('dialog', async d => {
try {
if (d.type() === 'beforeunload') await d.accept();
else await d.dismiss();
} catch {}
});
Core workflow
- Verify local files exist:
test -f "$RESUME_PDF"
test -f "$COVER_PDF"
- Open Dice with a persistent browser profile and verify login.
- Search remote Easy Apply roles using the query list.
- Extract Dice job IDs from
/job-detail/<id>URLs. - Open each job detail page and inspect only the main job description, not footer/recommended-job/sidebar text.
- Skip explicit onsite/hybrid/local/travel/clearance constraints.
- Open the wizard:
https://www.dice.com/job-applications/<job-id>/wizard
- Replace any stale/default resume with the verified resume PDF.
- Upload the cover-letter PDF where Dice supports it.
- Continue to the review screen.
- Confirm expected filenames and work authorization are visible.
- Submit only if no unknown required questions remain.
- Append a JSONL audit row and save state.
Suggested state
{
"seen": {},
"applied": {},
"skipped": {},
"alreadySubmitted": {}
}
Write state and logs to:
/tmp/dice-easyapply-daily/state.json
/tmp/dice-easyapply-daily/results.jsonl
Skip reasons
Common skip reasons:
not_remote_only_or_has_hybrid_location_textoutside_resume_wheelhouseexternal_ats_not_approvedunknown_required_questioncaptcha_or_verification_requiredcould_not_attach_resumecould_not_attach_cover_letteralready_submitted
Reporting
Report concise results:
Submitted:
- Title — Company — URL
Skipped:
- Title — Company — URL — reason
State: /tmp/dice-easyapply-daily/state.json
Log: /tmp/dice-easyapply-daily/results.jsonl
Pitfalls
- Dice may preselect an older profile resume. Always verify the filename before submitting.
- Dice pages can fire native
beforeunloaddialogs; register a Puppeteer dialog handler and accept beforeunload dialogs. - Dice may close/detach a page after a submit attempt. If navigation reports
Target closed,Session closed, orframe was detached, create a fresh page, re-register the dialog handler, and continue from state. - Do not let unrelated recommendation/sidebar/footer text cause false remote/hybrid skips.
- Do not overfit to a single resume. Keep search queries and skip rules configurable.
04 同仓库更多 Skills
serpmaven
Scrape Google search results (SERP) to JSON with SERP Maven (serpmaven) - a real Chrome browser on a residential proxy with sticky sessions. Run it as a CLI, a Python library, a local HTTP search API (`serve`), an MCP server or a Docker image; set the proxy login, workers, pages and cost tracking. Use when the user wants Google results, rank tracking, a self-hosted SERP API, or live Google search for an AI agent.
revnu-landing-page-audit
Find out why a landing page isn't turning visitors into signups, demos or sales. Audits one page against what the ad, post or search that sends people there promised, then checks the first screen, proof, call to action, friction and mobile. Returns at most 7 prioritized fixes, plus what is fine and what could not be checked; rewrites specific lines and fixes the page in the repo when asked. Never promises a conversion lift. Works without a Revnu account. Use when the user says or asks: "audit my landing page", "why isn't this page converting", "review my homepage", "my ads get clicks but no signups", "people bounce from the pricing page", "CRO review", "improve conversion rate", "is my hero section clear", "roast my landing page", "rewrite my headline", "what's wrong with this page", "landing page feedback", "make the signup page convert better". Not for SEO or AI-search audits, page speed engineering on its own, or building a new page from scratch.
revnu-growth-context
Write down once who buys, what they're stuck on, what it costs, what proof you have and what you've already tried, so every growth task starts from facts instead of a questionnaire. Creates or updates .agents/revnu-growth.md from the repo, the live site and the user, and imports an existing product-marketing.md. Use when the user says "set up our marketing context", "who is our ideal customer", "write our ICP", "describe the product for marketing", "positioning doc", "what's our brand voice", "remember this about our customers", "log what we tried", "what have we learned from marketing", "we changed pricing, update the context", "update our growth notes", "summarize the business for the agent", "import my product-marketing.md", "start a growth doc", or before a first marketing, SEO, outreach or launch task when no context file exists. Works without a Revnu account.
revnu-get-listed
Get onto the third-party pages AI answers and search cite when buyers ask for the best tool in your category: "best X" roundups, directories, review sites, GitHub awesome lists, community threads and comparison pages. Finds which ones are cited, ranks them by fit and effort, and drafts each submission, PR or pitch by the target's own rules. Use when the user says "get us listed", "which directories should we submit to", "how do we get into best-of lists", "why does ChatGPT recommend competitors and not us", "get mentioned in AI answers", "submit to awesome lists", "get on G2", "where are our competitors listed", "pitch listicle authors", "find backlink opportunities", "launch directories", "get into roundups", "Product Hunt alternatives", "where should we be listed", "get cited by Perplexity". Never submits, pays or posts without a yes. Works without a Revnu account.
revnu-ai-readiness-audit
Audit whether your website gives ChatGPT, Perplexity, Claude, Gemini and Google's AI Overviews something worth quoting, and fix the pages that don't. Use when the user says or asks "is my site ready for AI search", "audit my site for AI answers", "AEO audit", "GEO audit", "why doesn't ChatGPT quote our pricing", "make our pages citable by AI", "do I need llms.txt", "does schema help with ChatGPT", "check our structured data", "is our content visible without JavaScript", "AI SEO audit", "optimize our homepage for AI answers", "LLM SEO check", "why does AI get our product wrong", "fix our site for AI Overviews". Checks fetchability and indexability, answers in the raw HTML, entity facts, schema (including JS-injected markup), headings, dates and llms.txt, then gives at most 10 prioritised fixes and edits the repo when asked. Works without a Revnu account.
proxy-troubleshooting
Diagnose residential proxy failures, with NodeMaven's gateway as the reference - 407 with correct credentials, 406, 410, 500, a connection that hangs, ERR_TUNNEL_CONNECTION_FAILED in a browser, Playwright or Puppeteer ignoring proxy credentials, a sticky session that changes IP, geo-targeting that is silently ignored, passwords with special characters, and unexpected traffic from headless Chrome. Use when a proxy connection fails, returns the wrong location, or costs more traffic than expected.