Open role
Last updated: May 2026
Project Manager, JP/EN
Keep Japanese client projects organized from discovery through handover, with clear scope, notes, risks, decisions, demos, and next actions.
JP/EN
language
Bilingual status notes, client communication, and handover support.
Weekly
cadence
Kickoffs, demos, decisions, follow-up actions, and risk tracking.
Scope
focus
Acceptance criteria, exclusions, assumptions, and change management.
Handover
outcome
Runbooks, meeting notes, decision logs, and next-step documentation.
Buyer Guide
What Project Manager, JP/EN helps buyers confirm
Project Manager, JP/EN covers the operational details that matter when a Japanese company works with an overseas software partner. The practical questions are contract, invoicing, timezone, language, data handling, meeting rhythm, and handover.
For Japan B2B buyers, technical capability is only one part of trust. The engagement also needs to be explainable to procurement, security, management, and business users. Urbano DX documents those assumptions before a sprint begins.
Use this page as an internal briefing before the first conversation. NDA, SOW, billing details, data assumptions, and weekly demo rhythm can then be confirmed per engagement.
Confirm
Contracting, invoicing, timezone, language, data, and handover.
Japan-facing support
Bilingual summaries, weekly demos, and procurement-friendly documentation.
Before kickoff
NDA, SOW, data assumptions, meeting rhythm, and owners.
What you will do
You will keep delivery calm and legible. The job is to make sure client expectations, engineering scope, decisions, and handover materials stay aligned.
- Coordinate kickoffs, weekly demos, decisions, and follow-up actions
- Maintain bilingual status notes, acceptance criteria, and risk logs
- Keep client expectations aligned with engineering scope and delivery reality
- Support handover materials, meeting cadence, and procurement documentation
What good looks like
A good project feels boring in the best way: the next action is clear, risks are visible early, and nobody discovers a hidden assumption at the end.
- Clear agenda before meetings
- Short decision notes after meetings
- Visible risk and dependency log
- Acceptance criteria that match the build
- Clean handover at the end
Who fits
Best for someone who can translate between business users and engineers, keep details calm, and protect fixed-scope delivery.
- Japanese business communication
- English working communication
- Software or SaaS delivery experience
- Strong writing and follow-up
- Comfort managing ambiguity without drama
What you will not do
This role is not ceremony for ceremony's sake. The value is visible coordination that helps engineers build and buyers decide.
- No meeting bloat
- No vague status updates
- No hiding scope risk
- No final handover scramble
Role rhythm
1
Kick off
Confirm scope, owners, cadence, acceptance criteria, and communication rules.
2
Run cadence
Keep demos, notes, risks, and decisions moving every week.
3
Protect scope
Surface changes early and keep the build aligned with written acceptance criteria.
4
Handover
Prepare notes, runbooks, decision logs, and next-step recommendations.
Buyer FAQs
Is this a technical PM role?
It is delivery-facing and technical enough to coordinate software, APIs, AI workflows, acceptance criteria, and risks with engineers and clients.
Is Japanese required?
Yes. Strong Japanese and English business communication are required.
How should I apply?
Send a short introduction, relevant experience, language background, and LinkedIn or CV to [email protected].
Scope the first sprint
Bring the app, API, LLM feature, or AI workflow you want to test. We will turn it into a clear first-sprint scope.
Start a conversation