You’ve built a few sites. You’ve got some experience in Elementor or another page builder. You’ve even dabbled with WooCommerce. That’s cute. But here’s the thing: at LightSpeed, we don’t need someone who just drags blocks around. We need someone who knows how WordPress actually works — and is hungry to learn how modern WordPress is built.

This is your invitation to level up from site assembler to real developer.

Job Specification – Junior WordPress Block Theme Developer

Role Purpose: Join the LightSpeed team to design, build, and maintain modern WordPress block themes, working directly with our design systems and product teams.

Key Responsibilities:

• Develop custom WordPress block themes starting from default core themes.
• Implement designs from Figma Dev Mode into functional code.
• Work collaboratively via GitHub issues, branches, and pull requests.
• Maintain code quality, accessibility, and alignment with our design system.
• Document all development progress in README.md files.
• Participate in code reviews and accessibility checks.

Core Skills:

• HTML, CSS (Sass), and basic PHP knowledge.
• Understanding of theme.json, patterns, templates.
• Git and GitHub fundamentals.
• Figma Dev Mode basics.
• Eagerness to learn AI-assisted development workflows.

Nice to Have:

• JavaScript experience.
• WooCommerce familiarity.
• Prior work with block plugins.

The Three Types of Candidates We Expect

1. Intern with No Experience: No prior coding experience, but high motivation to learn and commit to a structured training plan.
2. Page Builder WordPress User: Experienced in tools like Elementor, but no GitHub experience. Ready to transition into block theme development.
3. WordPress Developer with GitHub Experience: Some block theme exposure or solid GitHub workflow knowledge; can hit the ground running faster.

Each path has the same end goal — to become a fully capable LightSpeed block theme developer.

What This Role Is (and Isn’t)

• ❌ If your idea of development is swapping out a template in Elementor, we’re not the agency for you.
• ❌ If you panic at the sight of theme.json or think GitHub is “that place people put zip files”, this is going to hurt.
• ✅ If you’ve got curiosity, persistence, and the willingness to unlearn page builder habits, you’ll fit right in.

We build block themes, custom plugins, and design systems that integrate directly into WordPress core’s Full Site Editing (FSE) tools. We work in GitHub, live in VS Code, lean heavily on GitHub Copilot, and have a borderline obsessive relationship with our Figma design systems.

The Curriculum You’ll Follow

We’ve put together a structured, 12-week onboarding program that will turn a capable junior (or even a smart career-switcher) into a developer who can ship real features in our products.

Our Block Theme Development Workflow

At LightSpeed, we’ve honed a consistent, collaborative, and AI-augmented workflow for building block themes. Here’s how we approach it step by step:

1. Start with a Solid Base

Every project begins with the latest default WordPress theme (currently Twenty Twenty-Five). This gives us a stable, standards-aligned foundation to build on.

2. Translate Designs into the Site Editor

We bring Figma designs directly into the WordPress Site Editor, shaping a base theme that mirrors the design system from the start.

3. Generate and Version the Theme

Once the initial setup is ready, we use the Create Block Theme plugin to export the theme. From there, it’s committed to GitHub for version control and collaboration.

4. Sync with the Design System

In VS Code, we align the theme.json file with the design tokens defined in Figma. GitHub Copilot and MCP servers help us keep Figma variables and theme configuration in sync.

5. Document Progress

Every milestone is documented in the project’s README.md. This running log ensures the whole team—and future contributors—understand decisions made along the way.

6. Manage Work in GitHub

Tasks are broken down into GitHub Issues, with branches spun up for each issue. Pull requests (PRs) are linked back to issues, ensuring nothing slips through the cracks.

7. Review and Test Continuously

Automation does the first pass—CodeRabbit and Copilot run checks on every PR. Human reviewers then validate the approach, making sure quality, performance, and design fidelity are intact.

8. Extract Design Tokens from Figma

Developers pull exact values (colours, typography, spacing) from Figma Dev Mode, reducing guesswork and ensuring precision.

9. Build Accessibility in From Day One

Accessibility isn’t a checklist item at the end—it’s embedded into every stage of design and development.

10. Deploy Automatically

When a PR is approved, the theme auto-deploys to our development server, giving us immediate visibility and reducing manual steps.

11. Plan for the Future

Our next big milestone is to integrate Playwright for automated browser testing, taking QA beyond static checks and into real-world interaction testing.

Conclusion & How to Apply

If you’re ready to put in the work, read the linked resources, complete the minimum curriculum, then send us the following:

• Your GitHub profile.
• Your LinkedIn profile.
• Any Figma work you’ve done.
• A thoughtful cover letter explaining why you’re the right fit.

If you think you’ve got the passion and curiosity to grow into a modern WordPress developer, we’d love to meet you. Send us a message through our contact page to request an interview and start your journey with LightSpeed.

Links Recap:

• LSX Demo Theme Repo
• LSX Design Theme Site
• Tour Operator Plugin
• LightSpeed Blog
• LightSpeed About
• Figma Dev Mode Courses
• Figma Community LSX Design System
• Model Context Protocol
• GitHub Copilot
• Ollie’s Theme Academy
• GitHub Skills