Tuyển dụng Technical Program Manager tại Hồ Chí Minh

Top 3 Reasons To Join Us Hi-tech working environment Young and dynamic colleagues International experience The Job

Technical Program Manager

Location: Ho Chi Minh City, Vietnam (on-site)

Level: Mid to senior (5+ years, at least 3 in a delivery or program role on software products)

Language: Strong written and spoken English

Reports to: Head of Product

Compensation: Competitive base, performance bonus, equity participation

The role

We have several features and projects in flight at once, and most of them depend on something outside our team: a partner's system access, a client's data, a vendor's delivery, a customer trial with a fixed start date.

You own the schedule. That means the plan across all features and projects, the dates everyone has committed to, the dependencies on external parties, and keeping every stakeholder, inside and outside the company, accurately informed about where things stand.

This role does not decide what we build or how it is built. Product owns the requirements and engineering owns the technical design. You own whether it lands on the date we said, and whether everyone who needs to know that it won't has known early enough to act.

What you will do

Schedule and delivery

• Own the delivery plan for all active features and projects: the timeline, the dependencies between features, and the critical path.
• Collect the dates each person commits to at the start of a feature, get them approved, and hold the team to them.
• Track progress against those dates daily from the work record (Jira), not from impressions. Catch a slip on a named task within days, not at the end of the timeline.
• When a date is at risk, bring the options to product and engineering leadership with the trade-off stated: what scope comes out, or what date moves. Cutting scope is the first option we consider. You make sure the decision gets made and recorded; you do not make it alone.
• Run the recurring delivery rhythm: the weekly status, the risk review, and the mid-build check-ins where overdue work is the agenda.
• Keep the timeline and status documents current and correct. A bar showing work as in progress when it never started is a defect, and you fix it.

External stakeholders

• Be the day-to-day contact for external partners, clients and vendors on everything related to schedule and delivery.
• Agree deliverables and dates with each external party, write them down, and track them the same way as internal work.
• Chase what we are waiting on from partners (system access, test accounts, data, sign-offs), because on most projects an external dependency is what actually sets the date.
• Tell external stakeholders about changes to dates or scope before they have to ask, with the reason and the new plan.
• Prepare and run status meetings with partners and clients, and follow up in writing with what was agreed, who owns each action and by when.
• Plan upcoming projects with external parties: milestones, what each side delivers, and the dates they depend on, before work starts.

Reporting

• Produce one concise status report for leadership each week: what shipped, what is at risk and why, what is blocked and on whom, and what decisions are needed.
• Keep one accurate view of every commitment made to an external party and whether we are on track to meet it.

Using AI in your work

• Use AI tools every day to do more of this job in less time: drafting status reports, meeting notes and partner updates, summarising long Slack threads and Jira activity, and preparing plans and risk lists for review.
• Build and improve small automations that pull status from Jira, GitLab and Slack into reports, so time goes into chasing risks rather than copying data between tools.
• Check what the tools produce before it goes out. A status report with one wrong date damages trust with a partner more than a late report does, so the accuracy of anything you send is your responsibility, whoever or whatever drafted it.
• Share what works with the rest of the team, and help product, engineering and QA get more out of the same tools.

Your Skills and Experience

What we look for

In priority order:

1. You find slips early. You read a plan and see where it will break. You ask "what is this date waiting on?" before anyone else does, and you notice when a task has quietly stopped moving.

2. You report status accurately. You report the bad news the day it becomes true, in plain words, with what it affects. "On track" means you checked, not that nobody complained. Being silent about a slip is the one failure we treat as serious.

3. You use AI to get more done, and you check its output. You already use tools like ChatGPT, Claude or Copilot in your daily work, not just occasionally. You can show us how they have made you faster or improved something you delivered: a report, a plan, a process. You also know where they go wrong (invented facts, wrong dates, confident summaries of things that were never said) and you catch those errors before anyone else sees them.

4. You manage external parties well. You have run delivery with clients, partners or vendors who do not report to you. You can hold a partner to a date without damaging the relationship, and you know how to escalate when a dependency stalls.

5. You understand software delivery well enough to spot a bad estimate. You do not need to write code, but you know what a spec, a merge request, a deployment and an environment are. When a developer says "almost done", you know which questions to ask.

6. You write clearly. Most of our coordination is written and asynchronous. Your status updates, meeting notes and follow-ups need to be short, specific and hard to misread.

7. You use tools rather than spreadsheets alone. Our status tracking is partly automated from Jira, GitLab and Slack. You are comfortable with Jira and can read a Gantt chart critically.

Requirements

• 5+ years in software delivery, with at least 3 as a technical program manager, delivery manager or project manager on software products.
• A track record of delivering projects that involved external clients, partners or vendors, with dates you were accountable for.
• Working knowledge of agile delivery, Jira (epics, tasks, estimates, time logging) and release processes.
• Experience building and maintaining multi-project timelines with cross-team dependencies.
• Regular, hands-on use of AI tools in your work, with examples of how they improved your productivity or the quality of what you delivered.
• Strong written and spoken English.
• Bachelor's degree in computer science, engineering, business or a related field, or equivalent experience.

Nice to have

• Experience in fintech, e-commerce, marketplaces or accounting software.
• PMP, PRINCE2, CSM or similar certification (useful, not required).
• Experience working with AI-assisted development teams, or building your own AI-assisted workflows or automations (scripts, agents, integrations with Jira or Slack).

Why You'll Love Working Here

What you get

• Competitive package
• Professional working environment
• Opportunities to challenge and develop your career
• Social insurance, health insurance, unemployment insurance as labor law stipulated