Careers listings that follow hiring activity.
Keep public page listings useful and current.
Where this work fits
The sitemap work started with a mismatch: many submitted pages were not useful search results, while worthwhile profiles were hard to find. Careers pages also needed to stop advertising jobs after hiring had closed.
I connected careers sitemap updates to changes in hiring activity. An organization needed to leave that directory when it no longer had qualifying open jobs; queued updates kept those changes separate from the user’s request.
A page becomes discoverable
Alex Okafor
Software engineer
Pages to discover.
Only public pages belong in the sitemap
Public pages enter the sitemap so search engines can find them. Private pages stay out of the list.
How discovery works
A sitemap gives search engines a list of pages to discover. It helps crawlers find content, but does not guarantee indexing. Page access controls remain separate from sitemap inclusion.
Coverage or relevance?
A longer sitemap could still send a search engine to empty or outdated pages. I focused on useful coverage and kept existing listings current through events and cache invalidation. An update needed to change the relevant listing without rebuilding every directory.
The skills behind the work
- Scala
- Backend development within established services, including asynchronous work and integration boundaries.
- Message queues
- Let a change trigger work separately from the request that produced it.
- Sitemaps
- Provide search engines with a structured list of public pages they can discover.
Profile indexing improved. Careers listings became more selective, removing pages that no longer reflected active hiring. For that part of the work, fewer submitted pages was a useful result.