I need a seasoned Laravel developer to architect a fully-featured job aggregation module that connects my site to the Careerjet and CareerBuilder APIs, ingests their listings on a schedule, and publishes them in real time while respecting each provider’s licence terms and branding rules. Core workflow • Securely call both APIs (or compatible ATS feeds) via Laravel queue jobs or scheduled commands. • Normalise the incoming payloads, store them in a dedicated MySQL table, and keep them updated or expired according to each source’s requirements. • Expose the data through an elegant search and filtering interface (keywords, location, category, salary, date, etc.) with pagination and fast, indexed queries. Role-based access Three permission tiers must exist from day one—Admin, Job Seeker, Employer—each with clearly separated capabilities handled through Laravel Policies or Gates. Admin alone can trigger manual syncs, edit or remove listings, and view API logs. Compliance & scalability notes – Every request and response should be logged for audit purposes. – Rate limits, retry logic and back-off policies must keep us within the official usage quotas. – The codebase has to follow PSR-12, be fully namespaced, and sit behind a controller-service-repository structure so we can extend it to other providers later without major rewrites. Deliverables 1. Clean, documented Laravel codebase with environment-driven API credentials. 2. Migration & seeder files for jobs, sources and role/permission tables. 3. Blade or Vue components for the search/filter UI. 4. Postman (or similar) collection showing all integration endpoints. 5. Short deployment guide and any cron entries required for automatic sync. Acceptance criteria • Jobs from both sources appear in the database and on the front-end within the configured interval. • Search results are accurate and can be filtered by at least five key facets. • Each user role is restricted to its own dashboard actions. • No provider policy violations are flagged in a two-week monitoring window. If you have recent experience with multi-source data ingestion in Laravel, robust API error handling, and role-based workflows, I’d love to see your approach and timeline.