BigCommerce & WordPress Developer

We need a hands-on developer with proven BigCommerce and WordPress experience for ongoing e-commerce development. The work includes responsive page implementation, reusable templates, platform integrations, technical fixes and deployment support. Success means shortening the cycle from a complete brief to an accepted, QA-ready staging build without compromising existing architecture, storefront functionality, analytics, SEO, performance, accessibility or security. AI-assisted development is required. Use AI where it improves delivery, but you remain accountable for architecture, every code change, testing and the final result. WHAT YOU WILL DO • Build responsive pages and components from approved Figma designs and specifications. • Extend existing BigCommerce themes or headless storefront layers. • Build and extend WordPress themes, templates, blocks and structured fields. • Create reusable, data-driven templates and conditional sections. • Integrate platform APIs, catalog or review data, analytics and third-party services. • Preserve existing structured data, canonical behavior, analytics, plugins, apps, checkout and storefront functionality. • Diagnose build, runtime and integration regressions. • Work through Git branches, pull requests, local builds and staging. • Deliver QA evidence plus concise change and rollback notes. REQUIRED EXPERIENCE • Personal production work on both BigCommerce and WordPress. • BigCommerce theme-level or headless development, not admin-only work. • WordPress PHP, custom themes and Gutenberg or ACF. • HTML, CSS, JavaScript or TypeScript, PHP and Git. • Accurate implementation from Figma across desktop and mobile. • Working safely inside established or legacy codebases. • A repeatable AI-assisted workflow that measurably reduces accepted delivery time. • You must personally perform the work and disclose any collaborators or subcontractors. STRONGLY PREFERRED • Stencil, Handlebars, Vue, Nuxt or Node. • BigCommerce APIs and data integrations. • WordPress custom post types, structured fields and technical maintenance. • JSON or CSV generation and other scalable content workflows. • Structured-data implementation and rendered-output validation. • WordPress staging, backups, security, PHP updates and plugin compatibility. HOW TO APPLY Start with: Dual-platform proof Include: • Your strongest live BigCommerce example and strongest live WordPress example. • For each: your exact contribution, stack, code path, access level, collaborators, delivery time and measurable result where available. • A five-minute unedited Loom. Do not use slides. Show the live work plus redacted code, commit, pull-request or CMS evidence. • One complex implementation beyond visual styling, such as a data-driven template, integration, technical fix or deployment issue. • One real AI-assisted task: the source brief, what AI produced, what you corrected or rejected, testing completed and actual time saved. • Your availability, time zone, rate and confirmation that you will personally complete the work. Applications without verifiable personal proof from both platforms will not be reviewed. SCREENING QUESTIONS 1. Which BigCommerce and WordPress stacks have you personally shipped to production? 2. Describe one project where you inherited an existing or legacy architecture. What did you deliberately avoid changing, and why? 3. Describe one AI-assisted build, including elapsed time, what AI generated, what you changed or rejected and how you tested it. 4. Describe one build, deployment or integration failure you personally diagnosed and fixed. 5. What QA evidence do you provide with every staging delivery? 6. What is your realistic cycle time from a complete brief to a QA-ready staging build for a standard page on each platform? PAID TEST Qualified finalists may receive two compact paid tasks using anonymized materials: one BigCommerce task and one WordPress task. Each will include dynamic or conditional content and existing code conventions. Scope, fee and committed turnaround will be agreed before work begins. Deliver working previews, code or pull requests with commit history, local build proof, desktop and mobile QA evidence, an AI-use summary, a QA checklist and a short walkthrough. No production access or deployment during the test. Evaluation will cover promised versus actual delivery time, implementation accuracy, architecture fit, reusability, responsive behavior, accessibility, performance, integration and SEO safety, testing and brief adherence. BOUNDARIES No production changes, credential sharing, unapproved dependencies or unreviewed AI-generated code. Preserve the existing architecture and integrations unless a change is explicitly approved. CONTRACT Paid test first. Strong candidates may receive ongoing work based on quality, speed and reliability.