Role Overview

Senior Technical Lead

Platform Modernization & AI Systems

Type - Full-Time

Location- Remote

Reports To - VP of Product

Level - Senior / Tech Lead

About the Role

We run a marketing agency serving 20+ active clients on a WordPress and Kadence-based platform. It works - and it's actively serving customers - but we've outgrown it. We're moving toward a Laravel + Filament central hub that gives us multi-tenant control, reliable data ingestion, and AI-assisted content workflows.

This is not a greenfield project, and it's not a quick one. It's a deliberate, multi-phase migration that will unfold over months - with real clients on the line the entire time. You will be responsible for keeping production stable while progressively building the system that replaces it.

The person we're looking for doesn't just know how to build the destination. They understand where we're coming from, how to get from here to there without dropping anything, and how to do it as a small team with limited overhead - prioritizing the right work at the right time.

Where We Are Today

Current Stack - _Serving customers in production today

WordPress Multisite

Kadence Theme / Blocks

CSV-based content ingestion

20+ active client accounts

Target State - _Migrated progressively - no big bang

Laravel + Filament central hub

Multi-tenant architecture

Queue-based ingestion pipelines

AI-assisted content workflows

How We're Getting There

This role owns the migration path. We expect a phased approach that keeps clients live at every step:

Phase 1 - Audit & Design

Assess current WP/Kadence architecture, content structures, and CSV workflows. Design multi-tenant data model and migration strategy.

Phase 2 - Parallel Build

Develop Laravel/Filament hub alongside existing WP system. No client disruption - new platform builds in parallel.

Phase 3 - Pilot Migration

Migrate 1-2 internal or low-risk clients. Validate ingestion pipelines, environment tooling, and content parity.

Phase 4 - AI Layer

Introduce AI-assisted content workflows with structured prompts, brand voice configs, and human-in-the-loop approval.

Phase 5 - Progressive Rollout

Migrate remaining clients in cohorts. Maintain WP fallback until each client is fully validated on new platform.

What You'll Own

The migration strategy - how we move from WordPress/Kadence to Laravel/Filament without service disruption
Laravel + Filament hub development: client environment management, content ops, data ingestion
Multi-tenant architecture design and implementation
CSV/data ingestion pipelines: queue-based, fault-tolerant, and auditable (replacing current WP ingest)
AI-assisted content workflows: LLM API integration, prompt design, brand voice config, approval flows
WordPress environment stewardship during transition - keeping 20+ client sites stable
The technical roadmap, with real input into sequencing and priorities
Day-to-day technical leadership of the existing team - supporting active client website builds on WP/Kadence while the new platform takes shape
Establishing and enforcing development standards, code review practices, and build processes that work across both the current WP environment and the emerging Laravel platform
Defining and implementing repeatable processes for new client site builds - templating, onboarding checklists, handoff documentation, and quality gates
Mentoring and guiding the existing development team through the transition - building their capability on the new stack without stalling current client delivery

What We're Looking For

Platform & Migration Experience

Proven experience migrating live production systems - not just greenfield builds
Deep WordPress knowledge: content architecture, plugin ecosystem, multisite, data structures
Familiarity with Kadence theme/blocks - enough to audit and replicate frontend behavior
5+ years of Laravel; hands-on Filament or equivalent admin panel experience
Ability to design multi-tenant systems with a clear opinion on shared vs. isolated data models

Reliability Engineering

Experience building background job pipelines (Laravel Horizon, Redis, queues)
Thinks about rollback, failover, and data integrity from day one
Knows how to run two systems in parallel and cut over safely

AI & Automation

Production LLM API integration (Anthropic, OpenAI, or similar) - not just experiments
Treats prompt engineering as a design discipline tied to content schemas
Has built or designed human-in-the-loop workflows for AI-generated content
Understands cost controls, caching, and token budgeting at scale
Defines and enforces quality standards for AI-assisted code generation, including review strategies, automated checks, and prompt constraints to prevent low-quality outputs from entering production

Leadership & Process

Leads by doing - sets the technical standard through their own work and brings the team along rather than delegating from a distance
Implements process where it doesn't exist - build workflows, review checklists, deployment standards - without letting process become overhead
Keeps the team unblocked on active builds while managing their own migration work - knows how to context-switch without dropping either thread
Slows down on ambiguous problems before writing code - and creates clarity for others, not just themselves
Communicates tradeoffs clearly to both the team and non-technical stakeholders - can translate technical risk into business terms and vice versa
Treats documentation, system design, and process definition as core leadership deliverables - not afterthoughts
Comfortable owning decisions in a lean environment - with real accountability

Nice to Have

Experience with headless or decoupled frontend architectures
Familiarity with Laravel Forge, Ploi, or Docker-based environment provisioning
Background inside a marketing or digital agency
Experience managing white-label or multi-brand SaaS platforms

What This Is Not

This is not a ticket-closing role, and it's not a clean-slate build. You'll be navigating a live system with real customers while building its replacement - and doing it without a large team behind you. There's no dedicated QA function, no army of developers to delegate to, and no big-bang go-live at the end. The migration will happen in stages over an extended timeline, and progress will be measured in stability and incremental momentum, not sprints.

If you need a fully resourced team, a scoped backlog, or external validation at every step to do your best work, this isn't the right fit. We want someone who treats migration risk as a design constraint, works well with limited support, and builds accordingly.

Why This Role

You'll own the architecture of a system that directly determines how 20+ clients are served
Real AI integration work with production stakes - not a proof of concept
A clear mandate: modernize without breaking what's working
A small, focused team where your decisions carry real weight - and real ownership comes with it

Senior Technical Lead (Platform Modernization & AI Systems) - Remote LATAM