Technical Project Manager English/Scrum/Jira/AWS

About the role

Excellent written and verbal English is the hard requirement for this role. It is the single most important thing we are looking for, so please read the rest with that in mind.

You will be the person who keeps our engineering team coordinated, informed, and moving. You will work directly with the founder and the engineering team here in Ho Chi Minh City, and you will talk with our US-based stakeholders every day. Your job is to turn high-level direction into tracked, prioritized work, raise blockers early, and make sure the right people know the right things at the right time.

This is a communication role first. The technical understanding matters because it is what lets you communicate well. You need to sit in on architecture discussions and follow them, read a ticket about a schema change and understand what is really being asked, and know when a quick fix is not actually quick. You do not need to write code.

Because English is the primary filter, we are not asking for a long project management track record. What we do need is enough time working in or around software teams that you know how things really run: sprints, backlogs, code review, incident response, and the difference between done and done done.

Responsibilities

• Own the day-to-day coordination of engineering work, including tickets, sprint planning, standups, and retros. Keep a clear, prioritized task list so the team knows what matters most each day and why.
• Turn direction from leadership into well-scoped, tracked work, and turn status back into a form leadership can actually act on.
• Sit in on technical discussions, follow them accurately, and write clear summaries that capture the decisions made, the follow-ups needed, and the open questions.
• Track dependencies and blockers across projects so nothing falls through the cracks, whether between engineers or between the engineering team and stakeholders in other time zones.
• Keep engineering documentation, roadmaps, and status views up to date and honest.
• Reach out to US-based stakeholders proactively, sending updates before they are asked for rather than after.
• Ask good questions. If something does not make sense, say so instead of papering over it.

The oppotunity
You will work directly with the founder and a small, senior engineering team on a system that sits at the center of the business, with real ownership of how the team communicates and stays organized. If you have the English skills and the curiosity to grow into the technical side of the work, this role will stretch you quickly and give you access to work that most PMs at your experience level never get to see.

Required qualifications

• Excellent written and verbal English. You can hold a nuanced conversation, catch subtle meaning coming the other way, and write clear summaries under time pressure. This is the top filter, and no amount of other strengths makes up for weakness here.
• Technical understanding good enough to follow an engineering conversation from start to finish, covering cloud services, APIs, databases, deployments, and incidents. You do not build these systems, but you understand what is being discussed when engineers do. You do not need to write code or know any specific language or framework.
• Two or more years working in or around software engineering teams , whether as a PM, engineer, QA, technical support, or something similar. Enough exposure that you know how software companies actually operate day to day.
• Comfort with common engineering tools , including Jira or an equivalent, the basics of Git such as branches, pull requests, and code review, and documentation platforms like Notion or Confluence.
• Strong organizational instincts. You keep track of what is owed to whom, you notice what is slipping, and you follow up without being asked.

Strongly preferred

• Formal PM experience at a software company, using Scrum, Kanban, or something similar, even if it was brief.
• A working, conceptual familiarity with AWS or another major cloud platform: what Lambda is, what a database looks like, and roughly how GraphQL differs from REST. Our stack is AWS and AppSync (GraphQL) on the backend and Vue, React, and TypeScript on the frontend, but none of this is required and a strong candidate can pick it up quickly.
• Experience communicating and coordinating with US-based teams across time zones.
• A CS degree, an engineering background, or self-directed technical learning, anything that shortens the ramp on the technical side.
• Confident use of AI tools such as Claude or ChatGPT for writing, summarizing meetings, and organizing information.

What success looks like

• The engineering team starts each day knowing the top priorities and why they matter.
• US stakeholders feel informed. They get clear, proactive updates and are never caught off guard by slippage.
• Technical discussions turn into written summaries the whole team can rely on.
• Blockers and dependencies get surfaced and resolved early, well before the deadline.
• Nothing important falls through the cracks between people or across time zones.

• Competitive Income: Attractive salary, 13th-month salary, and annual salary review.
• Health & Benefits: PTI Healthcare insurance, annual health check-ups, and 12 paid leave days.
• Great Work-Life Balance: Monday - Friday (8:30 AM - 6:00 PM with 1.5h lunch break)
• Office Perks: Free parking, daily free snacks & drinks, birthday gifts, year-end party, and company trips