We are looking for an experienced WordPress developer to upgrade an existing custom Greenhouse Harvest API integration from V2 to V3.
Project overview
A WordPress careers section currently displays job listings, supports job-search filters, opens individual job pages, and provides the existing application entry flow. The integration is implemented as a custom-coded plugin maintained in GitHub.
This is not a new or full API integration. The task is to review the current implementation and migrate only the existing in-scope read endpoints and related data mapping from Harvest V2 to V3 while preserving the current front-end behavior.
What you will do
Review the official Harvest V2-to-V3 migration documentation and the existing plugin code.
Upgrade the supplied V2 endpoints to their correct V3 equivalents.
Update authentication, pagination, response parsing, and data mapping where required by V3.
Preserve job listings, search/filter behavior, individual job pages, and the existing application entry flow.
Test the changes on a staging environment.
Submit clean, reviewable code through GitHub and provide short technical/testing notes.
What we provide
A staging environment for development and testing.
Access to the existing custom plugin repository.
A list of the endpoints that must be migrated.
Guidance on the PHP files responsible for the current integration.
Support from developers familiar with the V2 implementation.
A detailed private brief for shortlisted candidates.
Required experience
Strong WordPress and PHP development experience.
Recent hands-on experience with custom API integrations in WordPress.
Ability to understand API documentation, authentication, pagination, and changing response schemas.
Comfortable working with GitHub and testing changes on staging.
English communication is mandatory.
Please include in your proposal
Two or three recent examples of custom API integrations you implemented in WordPress, including what you personally built.
Any experience with Greenhouse, Harvest API, job-board integrations, or API version migrations (not mandatory).
Your hourly rate.
Your availability and timezone.
A short explanation of how you would approach reviewing and upgrading an existing API integration.
Important
Generic proposals without relevant WordPress API examples and an hourly rate will not be considered. Full project details will be shared privately with shortlisted candidates.
Technical reference: Greenhouse Harvest READ Endpoint Migration Guide
Write "api" in the beginning of your proposal to filter out among spammers
