n8n Developer Needed – Automated Job Search & Application System

I am looking for an n8n automation developer to build and fully set up a personal system that automatically finds suitable jobs, evaluates them against a candidate profile, assists with or completes applications, finds relevant recruiters, and keeps everything organized in one place. Existing n8n templates, open-source workflows and reusable components can and should be used where appropriate. There is no requirement to rebuild standard functionality from scratch. The developer must not only build the system but also install, configure and test it on my own system/accounts so that it is fully operational and ready for me to use. 1. Automated Job Search The system should automatically search multiple configurable sources, including: • Major job boards • Remote-job websites • Recruitment-company career pages • Company career pages • ATS-hosted vacancies Searches should run automatically at configurable intervals. I should be able to change: • Job titles • Keywords • Locations/countries • Remote/on-site preferences • Sources • Minimum suitability score • Search frequency without requiring the developer to modify the system. 2. Remove Duplicate Jobs The same vacancy may appear on several websites. The system should identify duplicates so that the same vacancy is not repeatedly shown or applied to. It should remember previously processed and applied jobs so they are not treated as new vacancies during later searches. 3. Job Matching & Scoring The system should compare vacancies against a stored master CV/professional profile. Each job should receive a suitability score from 0–100 based on configurable factors such as: • Job title • Seniority • Experience • Skills • Qualifications • Industry • Location • Remote eligibility • Compensation where available • Mandatory requirements • Other configurable criteria For suitable jobs, it should briefly explain: • Why the candidate is a good match • Important gaps or concerns Jobs below a configurable minimum score should be ignored or archived. 4. Application Documents For suitable vacancies, the system should be able to prepare: • Tailored CV/resume • Cover letter where required • Suggested answers to application/screening questions Factual candidate information must come from the stored master candidate profile and must never be invented. Different generated CV versions should be identifiable so it is possible to know exactly which CV was used for each application. 5. Manual or Automatic Application For suitable vacancies, there should be two possible actions: MANUAL APPLY or AUTO APPLY Where technically possible, the system should open the employer/application page, complete the application form, upload the appropriate CV/documents, answer standard questions and submit the application. This should support commonly used ATS/application systems where technically feasible, including: • Greenhouse • Lever • Workday • Ashby • Similar commonly used systems If an application cannot be completed reliably, the system should stop and mark it: MANUAL ACTION REQUIRED rather than entering incorrect information or failing silently. The result should be recorded as: • Successfully applied • Manual action required • Failed • Duplicate/already applied • Vacancy expired/closed The system must never submit the same application twice. 6. Daily Recruiter Search The system should identify approximately 10–20 relevant recruiters/recruitment professionals per day based on configurable: • Job functions • Industries • Seniority • Markets/locations Where available from permitted/public sources, it should collect useful professional/contact information together with the source/profile link. Duplicate recruiters should not repeatedly appear as new contacts. 7. Recruiter List & Follow-ups The system should keep a simple list showing: • Recruiter name • Company • Relevant market/function • Profile/source link • Available contact information • Date identified • Whether contacted • Date contacted • Response • Notes • Next follow-up date Simple stages can include: New → Contacted → Connected → CV Sent → Conversation → Opportunity → Follow-up It should clearly show which recruiters need follow-up each day. 8. Record of Jobs & Applications The system should keep a simple record including: • Company • Job title • Location • Remote/on-site • Original job URL • Source • Job description • Match score • Date discovered • Date applied • Manual/automatic application • CV version used • Application result/status • Notes The original job description should preferably be saved because online vacancies may later be removed. Simple stages can include: New → Review → Applied → Interview → Rejected → Offer I should also be able to manually change these statuses. 9. Simple Web Page to View Everything There should be a simple password-protected web page where I can easily view and manage everything. It should show information such as: • Jobs found today • New suitable jobs • Highest-scoring jobs • Applications completed today • Applications requiring manual action • Recruiters found today • Recruiters to contact • Follow-ups due • Interviews • Rejections/offers Sections can include: Jobs | Applications | Recruiters | Follow-ups | Interviews | Results From the jobs section I should be able to: • Open the original vacancy • See the match score • See why it matches / important gaps • View generated application documents • Choose Manual Apply or Auto Apply where available • Update the status A simple functional page is sufficient. It does not need to be an elaborate custom application. 10. Simple Results Summary The system should provide basic totals/results such as: • Jobs searched • Suitable jobs found • Applications submitted • Applications by source • Manual vs automatic applications • Interviews received • Rejections • Offers • Recruiters identified • Recruiters contacted • Recruiter responses Simple tables and numbers are sufficient. Elaborate charts are not required. 11. Alerts For high-scoring jobs and items requiring attention, the system should be capable of sending notifications through a configurable method such as email, Telegram or another simple notification service. Notifications should focus on relevant/high-scoring jobs rather than every vacancy found. 12. Reliability & Control The system should: • Run automatically on schedule • Avoid duplicate jobs • Avoid duplicate applications • Avoid duplicate recruiter records • Record failed searches/applications • Allow failed items to be retried • Clearly flag anything requiring manual action • Have a simple Pause/Resume option • Keep basic logs so problems can be identified • Continue functioning if one job source temporarily fails • Avoid unnecessary API/scraping costs 13. Easy Configuration Important settings should be easy for me to change without programming, including: • Job titles • Search keywords • Locations • Remote preferences • Sources • Minimum match score • Search frequency • Recruiter search criteria • Manual/automatic application preference A Google Sheet, simple configuration page or similar approach is acceptable. 14. Installation, Setup & Testing Installation and setup are part of the project. The developer must: • Install/import the completed workflows into my n8n environment • Configure the required services/integrations with me • Connect the required accounts/APIs • Configure the database/storage • Set up the web page • Configure the candidate profile/CV • Configure initial job-search criteria • Test the complete process from job discovery through application • Test recruiter discovery and follow-up records • Fix errors identified during testing • Leave the system fully operational and ready for daily use Simply providing workflow JSON files or source code without installation and working setup will not be considered complete delivery. 15. Ownership & Handover The completed system must run using accounts/infrastructure controlled by me. At completion I should receive: • Complete n8n workflow(s) • Workflow JSON exports • Any scripts/source code used • Web page/files • Setup/configuration instructions • List of required external services/APIs • Expected recurring costs • Short video walkthrough showing how to operate and modify the system • All necessary configuration information There should be no continuing dependency on the developer's personal accounts or services after handover. 16. Cost Control Before starting, the developer should clearly explain: • Which external services/APIs are required • Which are free • Which are paid • Approximate expected monthly running cost Where practical, lower-cost/free solutions should be preferred without significantly reducing reliability. Budget, Payment & Completion Time Budget is strictly $100–$150 fixed price. Full payment will be released after the agreed system has been completely built, installed on my system, configured, tested and confirmed working according to the agreed requirements. Existing templates, workflows, open-source projects and reusable components are encouraged. The objective is a practical personal automation system, not an expensive custom software platform. Please state clearly in your proposal: How many calendar days you require to completely build, install, configure and test the system. When Applying Please answer all of the following: 1. Have you built a similar job-search, job-application, browser/form automation or n8n system before? 2. If yes, please show a demo, video, screenshots or other evidence of the actual working system. 3. Have you automated filling and submitting forms on systems such as Greenhouse, Lever, Workday or Ashby? 4. What technology would you use for automatic form filling and submission? 5. Which existing workflows/templates/open-source components would you reuse rather than rebuilding? 6. Can you deliver all the requirements above within the stated $100–$150 fixed budget? 7. If anything listed above cannot be reliably automated, please identify it clearly before accepting the project. 8. Which paid services/APIs will be required and what should their approximate monthly cost be? 9. How many calendar days will you require for complete development, installation, configuration and testing? 10. Will you personally install and configure the completed system in my n8n environment and leave it fully operational? 11. What support will you provide if bugs are found immediately after delivery? Please do not send a generic proposal. Preference will be given to developers who can demonstrate similar working automation and clearly explain how they would implement this project within the stated budget. The project will be considered complete only after the agreed functions have been installed, configured and successfully tested.