Data Transformation Project Manager_ Life Science
Notify me about similar jobsAbout this opportunity
メルクと一緒に、あなたの力を発揮しよう！
冒険、限界への挑戦、そして発見に焦がれるあなたへ。あなたの大志を、メルクで羽ばたかせましょう！科学とテクノロジーを駆使したイノベーションに情熱を注ぐメルクのスタッフは世界中で活躍中です。ヘルスケア、生命科学、エレクトロニクスの分野で、メルクのソリューションは人々の暮らしをますます豊かなものにしています。あなたとメルクの力を合わせて、大きな夢を抱きましょう。メルクは、人、顧客、患者、そしてこの地球という惑星が共存する豊かな世界の構築に情熱を注いでいます。このためメルクでは、好奇心にあふれた人材を募集中です。メルクと一緒に、想像を超えた世界を開拓しませんか？
Your Role:
As our Data Transformation Project Manager based in Japan, you will lead the technology modernization of our Life Science Quality and Regulatory operations in Japan, designing scalable system architectures, establishing engineering best practices, and laying the groundwork for future-ready digital infrastructure. You will collaborate closely with local and global teams, acting as the technical anchor for this program.
What you will do:
Design and implement scalable, maintainable IT system architectures suited to the regulatory and quality requirements of our Japan Life Science operations.
Define and enforce engineering standards across software development practices, ensuring solutions are reproducible, secure, and built to last.
Drive code quality through automated testing, structured code reviews, and disciplined Git workflows.
Communicate technical concepts clearly to both engineering teams and non-technical business stakeholders, including Quality and Regulatory functions.
Contribute to the company's broader AI capabilities where applicable, supporting the design of agentic or LLM-based systems as the program matures.
Who You Are:
Experienced software engineer and system architect with a proven track record in complex, production-grade environments.
Hands-on with core AWS services and proficiency in Infrastructure as Code (Terraform, AWS CDK, or CloudFormation).
Solid grasp of CI/CD, containerization (Docker / Kubernetes), automated testing, and observability.
Security-conscious, with knowledge of authentication, authorization, and secure system design.
Strong communicator, able to align cross-functional teams and bridge technical and business perspectives.
Culturally adaptable, ideally with experience working in or with Japan-based organizations. Proficiency in Japanese is a plus.
Familiarity with agentic system design or LLM-based architecture (e.g. LangChain, RAG pipelines, vector databases) is an asset, though not a primary requirement for this role.
私たちが提供するもの：私たちは、さまざまな背景、視点、人生経験を持つ好奇心旺盛な人々で構成されるグループです。この多様性が卓越性と革新を促進し、科学と技術のリーダーシップを強化すると信じています。私たちは、すべての人が自分のペースで成長し発展するためのアクセスと機会を創出することにコミットしています。何百万もの人々に影響を与え、誰もが人類の進歩を支持できるようにする包括性と帰属感のある文化を築くために私たちに参加してください！
今すぐ応募して、発見を促し、人類の発展を高めることに専念するチームの一員になりましょう！
Job details
How this role compares
Computed from every other active Regulatory Affairs role in our database, not just this employer's listings.
We currently track 544 comparable Regulatory Affairs roles across 109 biopharma companies.
Salary context
127 of 544 peers report a salary range (USD, annualized)
Peers share this role's job function. This posting doesn't list a seniority level, so peers aren't narrowed by seniority either -- the range below may span more levels than usual.
Where these roles are based
Top locations among the 544 comparable roles
+ 44 more countries
Seniority mix
429 of 544 peers have a known seniority level
Therapeutic area mix
53 of 544 peers have a known therapeutic area; the rest are genuinely unlabeled, not hidden
Similar opportunities
The closest matches from our peer group, ranked by how similar they are, not how well you'd qualify for them -- treat this as market context, not a guaranteed shortlist; a weak match is labeled as one below.
Notify me about similar jobs
Get an email when we spot other openings like this one – same job function, comparable seniority, roles you'd actually want to see.
Or follow a whole field: get every new Regulatory Affairs job in Japan, and choose locations and companies.
How we calculate "similar"
No black box, no LLM guesswork: a deterministic score built from four normalized attributes. Here's this role's own peer group at different match levels, so you can see the mechanism, not just the result.
Every comparison starts from the same 100-point budget: 25 for working in the same function, 40 for the same therapeutic area, 20 for the same or adjacent seniority, 15 for the same country. A dimension we can't confirm on both sides contributes nothing, never a guess, never a free pass.
0 points, never a partial guess. A role we know almost nothing about beyond its function bottoms out at 25%; it never inflates to 100% just because there's little to compare against. Seniority uses a defined ladder (Associate → Manager → Associate Director → Senior → Principal → Director → Senior Director → Executive/VP) so "Director" and "Senior Director" count as adjacent, but "Director" and "Executive/VP" do not.