iProv logo

Full-Stack WordPress Developer (WP Engine / Genesis / ACF) — Ongoing Support + Builds (AI Automation Bonus)

iProv
Full-time
On-site
Little Rock, Arkansas, United States
WordPress Development

Job Summary

We're hiring a Full-Stack WordPress Developer for ongoing website maintenance and new feature development across multiple WordPress sites. You'll work inside an established stack (WP Engine + Genesis + ACF Pro) and own tasks end-to-end: implementation, testing, troubleshooting, and deployment.

This role is ideal for someone who is fast, accurate, process-driven, and comfortable shipping reliable work through a staging → QA → production workflow.

Tech Stack

  • WP Engine hosting (staging + production workflows)

  • WordPress (latest versions)

  • Genesis Framework

  • Custom Genesis Child Theme (Altitude Pro–based)

  • ACF Pro (custom blocks, CPTs, field groups)

  • Gravity Forms

  • Agile Store Locator

  • Additional plugins as needed per site

Responsibilities

Ongoing Maintenance & Support

  • Update website content using provided copy

  • Fix internal 301/404 errors and broken links

  • Repair broken images, embeds, and media issues

  • Update plugins safely and consistently

  • Update WordPress core versions

  • Manage PHP version updates in WP Engine

  • Troubleshoot and resolve front-end issues (CSS/JS/layout)

  • Perform light WordPress database work (phpMyAdmin-level tasks)

  • QA test thoroughly before pushing updates live

Full-Stack Build Work (Core to This Role)

  • Build and maintain ACF field groups, CPTs, templates, and reusable components

  • Develop and extend custom Gutenberg/ACF blocks

  • Customize Genesis child theme templates and functionality (PHP)

  • Implement integrations (Gravity Forms, maps/locator tools, third-party APIs)

  • Debug performance issues, plugin conflicts, and theme-related bugs

  • Implement best practices for security, performance, accessibility, and SEO fundamentals

  • Work with Git-based versioning (when applicable) and maintain clean release practices

Workflow Expectations (Required)

  • Each project/task includes a pre-approved time estimate

  • If work can be completed within the estimate → bill normally

  • If additional time is required → provide a revised quote before logging extra hours

    • No additional hours may be billed without written approval

  • All work must follow proper WP Engine staging-to-production workflow:

    • Push production to staging

    • Perform updates/builds in staging

    • QA testing

    • Deploy to production

Qualifications

  • Strong WordPress development experience (theme + functionality)

  • Strong PHP (WordPress hooks/actions/filters, templating, debugging)

  • Solid front-end skills (HTML, CSS, JavaScript)

  • Experience with Genesis Framework

  • Strong ACF Pro experience (CPTs, templates, custom blocks)

  • Comfort working in WP Engine environments

  • Familiarity with Gravity Forms

  • Basic database competency (WordPress tables, safe edits)

  • Detail-oriented with strong written English communication

  • Reliable, responsive, and able to follow SOPs

Bonus Skills (Nice-to-Have): AI Agent Builder / Automation Coder

This is not required, but a plus if you can support lightweight automations that reduce manual work.

Examples:

  • Building simple AI agents/workflows for internal ops (intake helpers, QA assistants, content utilities)

  • Integrations using APIs/webhooks (forms → CRM → sheets, etc.)

  • Automation tools (Zapier, Make, n8n) and/or small scripts (Python/Node)

  • Prompt/system design for consistent outputs

How to Apply

Please include:

  • Resume or LinkedIn

  • Portfolio links (sites you've built/maintained)

  • Answer the questions below

  • Availability (hours/week)

  • Hourly rate or Salary request

  • Optional: GitHub/code samples

Background and stack fit (Please answer when submitting the application)

  1. How many years have you developed on WordPress (not just page builders)?

  2. Which theme frameworks have you worked with (Genesis, Sage, Underscores, custom, etc.)? Describe your Genesis experience specifically.

  3. How often do you build with ACF Pro (field groups, CPTs, blocks)? Give 2–3 examples of what you built.

  4. Have you built custom Gutenberg blocks (ACF Blocks or native)? Which approach do you prefer and why?

  5. What's your comfort level with PHP in WordPress (hooks, filters, template hierarchy, debugging)? Provide an example of something you coded.