Job Content Management System (CMS)
Built the content management system behind Job Landing, covering country-based pages, modular sections, job and company collections, search-term collections, push notifications, and complex filter logic with optimized endpoints.
Job Landing needed a flexible backend CMS so business teams could manage country-based landing pages, curated collections, and discovery flows without hardcoding page content into the frontend.
- Each country homepage needed its own page structure and multiple configurable sections
- Content blocks had to support jobs, companies, and quick-search terms from different data sources
- Filtering and curation logic needed to handle complex unlimited AND/OR conditions for collections
Built a CMS that let internal teams compose country pages from modular sections, connect each section to different collection types, and manage push-notification content from one backend workflow.
- Created page and section management for country-based homepages
- Implemented job collection, company collection, and search term collection support
- Added push-notification tooling, Google Indexing API integration, and 4-hourly cron updates so section data could refresh when newly added jobs matched saved filter conditions
Made backend decisions that prioritized flexibility for content teams while keeping query behavior predictable enough for production traffic.
- Modeled sections as reusable content containers so one page could mix multiple collection-driven blocks
- Supported nested AND/OR-style filter logic to avoid rebuilding new endpoints for each curation need
- Used caching and endpoint optimization to keep CMS-driven pages responsive while querying and presenting around 1,000 jobs
- Used a 4-hourly cron to refresh section results so newly added jobs could appear when they matched existing collection filters
Accepted more backend complexity in exchange for a CMS that could support richer business-controlled landing experiences without frequent code changes.
- Unlimited filter combinations increased implementation complexity but gave the content team much more control
- Country-based page composition required more backend structure but reduced hardcoded frontend content maintenance
- Scheduled refresh logic added backend work, but it removed the need to manually rebuild section data whenever new matching jobs were added
The CMS turned Job Landing into a more configurable product surface where content, discovery, and engagement workflows could be managed operationally instead of manually coded each time.
- Enabled country-specific homepage management from the backend
- Improved content curation through modular sections and flexible collection filtering
- Extended CMS operations into discoverability workflows through Google Indexing API integration while keeping filter-based sections up to date as new matching jobs were added