One of our U.S. digital agency partners needs a senior Drupal engineer to take technical ownership of their client sites. You'd be the go-to person on a handful of projects at a time: shaping the architecture, writing a good share of the code yourself, and making sure the rest of the team is never stuck.
You'd join their engineering team as a weKnow contractor, working remotely from Latin America on a schedule that overlaps with Pacific Time (U.S. West Coast).
The day to day
- Write Drupal code across the whole stack (custom modules, theming, configuration) and keep it readable for whoever touches it next.
- Decide how each feature should be built. Contributed modules usually come first, and custom code is for the cases where they fall short.
- Move content from legacy platforms into Drupal, mapping and cleaning the data and verifying nothing gets lost.
- Connect sites to external services through their APIs, including the messy ones.
- Profile slow pages and fix what you find, whether that's a database query, a caching gap or the hosting layer.
- Lock down roles, permissions and configuration so sites stay secure.
- Ship decoupled front ends in React when a project calls for headless Drupal or WordPress.
Leading the work
- Turn project scope into a plan: milestones, tickets and estimates the team can actually work from.
- Unblock other engineers with context, pairing and code reviews that teach something.
- Join planning with project managers and designers so technical risks show up before they get expensive.
- Run point on releases, deployment pipelines and post-launch support, and take the lead when a site goes down.
- Talk directly with clients (and their developers, when they have them) about options and trade-offs, in plain terms.
- Write things down: architecture decisions, test plans, handoff notes and status updates.
AI in your workflow
weKnow engineers lean on AI coding assistants, and we expect them to stay in charge of the result.
- You're comfortable using AI for boilerplate, refactors, research and docs.
- You read and test AI-generated code the way you'd review a junior developer's pull request before merging it.
- You check what each client allows, and you never paste their data or their users' data into an AI tool.
Requirements
- At least 5 years building Drupal sites professionally, with time spent as the technical owner of a project.
- Deep PHP and Drupal knowledge, plus solid JavaScript, HTML and CSS.
- A track record of running more than one project at once and guiding other developers.
- Hands-on work with data migrations, API integrations and React-based headless builds.
- Comfort debugging at every layer: SQL, caching, access control and, when needed, a Linux server.
- Daily use of Git, pull request reviews, automated tests and CI/CD.
- Advanced English, written and spoken. You'll be on calls with U.S. clients every week.
- Experience working with remote teams across time zones.
- You already use AI coding assistants in your own work.
Bonus points
- Pattern libraries or design systems built with Storybook or similar tools.
- Patches or modules on drupal.org, or any open source contributions.
- You've given talks or run workshops.
Sound like you?
Send us your CV and a short note about a Drupal project you led. We’ll get back to you.