career-ops

Least-privilege permissions

• Run the agent in an isolated user account with read-only access to your CV file; do not grant write access to sensitive directories
• Store job board credentials in a dedicated secrets manager (e.g., 1Password, Bitwarden) rather than plaintext config files; rotate credentials after each job search cycle
• Restrict file system access to a single sandboxed directory for application artifacts; disable network access except to whitelisted job board APIs

Network isolation

• Run the agent locally without internet access; manually export job postings as text files to analyze offline
• If internet is required, route traffic through a VPN and monitor all outbound connections; block any domains not explicitly needed for job board APIs
• Disable telemetry and auto-update features; verify no analytics endpoints are called during resume/cover letter generation

Monitoring

• Log all credential access attempts and file reads/writes to a tamper-evident audit log before running the agent
• Capture generated resumes and cover letters immediately after creation; compare against your actual CV to detect prompt injection artifacts or data leakage
• Review application history for anomalies: unexpected job submissions, altered resume content, or connections to unknown third-party services

Red flags to watch for

• Generated cover letters or resume sections that contradict your actual CV or include fabricated experience
• Credentials stored in plaintext in config files, .env files, or npm cache directories
• Unmaintained or rarely-updated npm dependencies; run npm audit before first use and after each update
• Resume over-optimization that removes legitimate qualifications or creates ATS-incompatible formatting; always manually verify before submission