数据库迁移工程师 - 欧洲、中东和非洲
Database Migrations Engineer - EMEA
Laravel 是全球最流行的 PHP 框架，累计下载量超过 5 亿次。数千个包。开发者社区活跃在各类会议、论坛、Twitter、Discord 服务器以及互联网上所有“应该使用哪个框架？”的讨论帖中。
但 Laravel 不仅仅是一个框架。它是一个完整的平台。从选择技术栈，到构建应用，再到部署、监控和扩展。Laravel Cloud 是我们提供的托管 PaaS，企业客户迁移到此时会遇到一个常见且顽固的障碍：数据库迁移。我们需要一位能直接解决这个问题的人。
为什么这份工作与众不同
你将与企业客户通话，并与他们一起执行迁移。不是处理工单，也不是远程提供建议。而是与客户共同承担技术执行的责任——这在我们签署大型、有影响力的合同时尤为重要，需要交付成果。
你将接手一个真实且持续的功能。已有数据库迁移工作需要负责人——包括与 PlanetScale 的关系以及分散在各个渠道的定期临时请求。你不是从零开始。
简要目标是建立能力，而不是等待完整菜单。与其先定义未来所有可能的数据库，你将通过实践开发这个功能。你将学习客户的需求，将可重复的部分产品化，并为下一步提出依据。
你将分享你的知识。模式是“立即缓解痛点，然后整个团队都能提升。”提供文档、操作手册和轻量级培训，让销售、客户成功和工程团队能够基于你的专业知识，而不是依赖于你。
数据库迁移工程师将负责
- 与企业客户和私有云客户执行数据库迁移。参与通话，承担技术执行，为客户迁移到 Laravel Cloud 成功完成迁移——主要涉及 MySQL 和 Postgres。
- 接管与 PlanetScale 的关系和迁移工作。从当前的临时状态中接手，并以干净、自主的方式运行。
- 将可重复的迁移模式产品化。识别最常见的无停机时间的迁移，并将其打包——包括文档、决策逻辑、边缘情况等，使其不再成为定制化任务。我们希望的是可重复性，而不是个人英雄主义——并着眼于最终将这些知识整合到产品中，无论是通过文档、向导还是自助流程，以便实现产品驱动的客户增长。
查看英文原文
Laravel is the most popular PHP framework in the world. 500M+ lifetime downloads. Thousands of packages. A developer community that shows up at conferences, in forums, on Twitter, in Discord servers, in every "what framework should I use?" thread on the internet.
But Laravel is more than a framework. It's a complete platform. From choosing a stack, to building an app, to deploying it, monitoring it, and scaling it. Laravel Cloud is our managed PaaS, and enterprise customers moving onto it face a common, stubborn blocker: database migration. We need someone who solves that problem directly.
Why This Job Is Unique
You will be on calls with enterprise customers and you will run the migration with them. Not routing tickets. Not advising from a distance. Actually owning the technical execution alongside the customer - which matters most when we sign a large, impactful contract and need to deliver.
You are picking up a real, ongoing function. There is existing database migration work that needs an owner - including the PlanetScale relationship and recurring ad-hoc requests scattered across channels. You are not starting from zero.
The brief is to build the muscle, not wait for the full menu. Rather than first defining every database we will ever offer, you are the one who develops the function in practice. You’ll be learning what customers need, productising the repeatable parts, and making the case for what comes next.
You will seed what you know. The model is "immediate pain relief, then the whole team gets better." Documentation, runbooks, and lightweight training so Sales, CS and engineering compound on your expertise rather than staying dependent on it.
What the Database Migrations Engineer Will Do
- Execute database migrations with enterprise and Private Cloud customers. Sit on calls, own the technical execution, and deliver successful migrations for customers onboarding to Laravel Cloud - primarily MySQL and Postgres.
- Assume ownership of the PlanetScale relationship and migration work. Take over this function from its current ad-hoc state and run it cleanly and autonomously.
- Productise repeatable migration patterns. Identify the most common downtime-tolerant migrations and package them - documentation, decision logic, edge cases - so they stop being bespoke. We want repeatability over heroics — and with an eye towards eventually bringing that knowledge in-product, whether through documentation, wizards, or self-serve flows, so that product-led customers can benefit too.
- Automate recurring migration requests. Map the one-off requests that surface repeatedly across channels and eliminate the manual effort.
- Own broader app and service migrations in the gaps. Act as a generalist migration resource for application and service migrations onto Private Cloud when database migration work permits.
- Distribute what you learn. Write clearly. Build runbooks. Create reference material that makes Sales, CS and engineering better without making them dependent on you.
- Keep the database offering competitive. Stay close to the market — monitoring what alternatives like PlanetScale, Aurora, and Percona offer in terms of pricing, instance classes, and capabilities. Flag proactively when our offering is out of step with what customers are seeing elsewhere, and advise on what needs to change.
Requirements
What We Are Looking For
- Genuine strength across both MySQL and Postgres. We are deliberately optimising for ~80% capability in each over 100% in one. Database specialists tend to plant a flag, and we need coverage across both camps.
- Direct experience with database migrations in a customer-facing capacity. You have been on the calls, you have run the process alongside engineers and customers, and you are comfortable owning the technical execution rather than advising on it.
- A productisation instinct. You see the repeatable pattern inside bespoke work and know how to package it without over-engineering.
- Strong written and async communication. We are fully remote and documentation is how knowledge compounds.
- Comfort operating in a role where part of the scope is yours to define. There is a clear immediate need, and you will also be shaping what the function looks like from here.
Nice to Have
- Experience at a database tooling or infrastructure company - PlanetScale, Percona, Vitess, or similar
- Experience building tooling or automation around migration workflows
- Familiarity with AWS-based infrastructure or PaaS environments
- Experience with AWS DMS or comparable migration tooling — DMS has a role in certain migrations and prior use is a strong signal of hands-on production database migration experience
- A track record of writing, speaking, or teaching publicly about database topics
- Some familiarity with PHP applications
Benefits
- Work From Home
- Health Care Plan (Medical, Dental & Vision)
- Paid Time Off (Vacation, Sick & Public Holidays)
- Family Leave (Maternity, Paternity)
- Stock Option Plan
Originally posted on Himalayas