āļ›āļĢāļ°āļāļēāļĻāļ‡āļēāļ™āļ™āļĩāđ‰āļŦāļĄāļ”āļ­āļēāļĒāļļāđāļĨāđ‰āļ§

Technical Product Manager

Location:

Bangkok-based or relocating to Bangkok - hybrid, typically Mon-Wed in-office. Relocation and visa support available.

Reports to:

VP Product (works day-to-day with the CTO and Tech Lead)

The Opportunity

Atiom is an AI-powered performance platform helping service-first brands - led by hospitality - get the best from their frontline teams. We're a ~30-person company with enterprise clients including IHG, Accor, and Minor Hotels.

Let's be direct about why this role exists. AI has made our engineering team fast - front-end ships about as quickly as we can point it at something well-defined. The constraint now isn't building; it's defining

. The step where a rough idea becomes something engineering can actually build - the flows, the edge cases, the 20-50 implementation decisions, the "does this even collide with what we already ship" checks - is where everything backs up today, because it's being done in the spare hours of a CTO and a VP Product who have other jobs.

That's your seat.

You own the pipeline from idea to buildable spec.

You'll run discovery, pressure-test feasibility with the CTO and our Tech Lead, kill the assumptions that would sink a feature before anyone builds it, and hand engineering a PRD they can move on without waiting. This is a hands-on, technical, IC role with real ownership and direct access to the people who make the decisions - not a layer of process on top of one.

Your first mandate

Own the PRD pipeline.

Take the roadmap's live features from concept to a definition-of-ready that engineering trusts - one clear flow, not five ambiguous boards.

Make the pre-mortem a habit.

Before deep specs, front-load the three checks that sink features here: the one make-or-break technical assumption, fit against systems and roles we already ship, and any adjacent in-flight workstream. Catch the sinkers on a whiteboard, not in 1,800 lines of spec.

Tighten the definition surface.

A reusable PRD template, a real definition-of-ready, and backlog/board hygiene that holds up without heroics.

What You'll Own

Feature definition, end-to-end.

You turn approved ideas into buildable PRDs: user logic, edge cases, states, data implications, and the implementation detail that lets engineering move fast. Definition quality is the whole job, not a by-product.

Feasibility and systems-fit.

You reason about our actual platform - the data layer, the role model, how features interact - and you validate the make-or-break assumptions with the CTO and Tech Lead before build. When something is unproven, you say so and you gate it.

The definition process itself.

PRD templates, definition-of-ready, backlog and board hygiene, triage routing.

A consulting voice on how we build.

You'll spot friction in our broader dev process and you're expected to raise it - as recommendations to the CTO and eng leads. You propose; they own. (QA, staging, release, and CI are owned elsewhere - not this role.)

Who You Are

Technical first.

You have an engineering background

  • you've written production code, or worked close enough to it to reason about a data model and a feasibility trade-off, and you can hold your own in a technical conversation with a CTO. This is a hard requirement; we'll probe it.

A proven definer.

~3-6 years, and you've independently owned feature definition

  • taken a vague idea to a spec engineering built from. You think in behaviour, edge cases, and logic, not just screens or tickets.

Someone with backbone.

You'll run a pre-mortem on a senior person's spec and say "we're not building this until we've tested the assumption it rests on" - and make it stick, kindly.

A clear writer in English.

Your specs are the source of truth for the team; they have to be unambiguous. Hard requirement.

AI-native in how you work.

You already use AI across discovery, spec-writing, and prototyping, and you want to push it further. We'll ask for specifics.

This role is probably not for you if

You're a product generalist who manages stakeholders and roadmaps but can't reason about the technical detail underneath a feature.

You want to manage a team - this is a hands-on IC seat, and stays one.

You want to own delivery, QA, or engineering process - that's the CTO's, and you advise, not run it.

You need the spec handed to you. Here, you are the spec.

Likely Candidate Profiles

The Engineer-Turned-PM:

a developer or tech lead who moved into product/spec ownership and prefers defining the right thing to managing a backlog. The strongest fit.

The Technical PM:

a product manager at a B2B/platform company who is genuinely technical - ships PRDs engineering respects, comfortable in the codebase-level conversation.

The Solutions/Delivery Engineer with product instinct:

someone who has lived at the seam between customer need and buildable spec and wants to own the definition end.

What Success Looks Like (first 6-9 months)

Features arrive at engineering fully defined and de-risked

  • flows, edge cases, feasibility, and systems-fit resolved before build.

Engineering is never idle for lack of a defined thing to build.

The CTO and VP Product spend far less time authoring and auditing PRDs - the sign-off gate is a quick safety check, not a rescue.

The pre-mortem and definition-of-ready are standing habits the team actually follows.

āļ›āļĢāļ°āļŠāļšāļāļēāļĢāļ“āđŒāļ—āļĩāđˆāļˆāļģāđ€āļ›āđ‡āļ™
  • āđ„āļĄāđˆāļĢāļ°āļšāļļāļ›āļĢāļ°āļŠāļšāļāļēāļĢāļ“āđŒāļ‚āļąāđ‰āļ™āļ•āđˆāļģ
āļĢāļ°āļ”āļąāļšāļ•āļģāđāļŦāļ™āđˆāļ‡āļ‡āļēāļ™
  • āļĢāļ°āļ”āļąāļšāļœāļđāđ‰āļˆāļąāļ”āļāļēāļĢ / āļ­āļēāļ§āļļāđ‚āļŠ
āđ€āļ‡āļīāļ™āđ€āļ”āļ·āļ­āļ™
  • 100,000 - 150,000 THB, āļŠāļēāļĄāļēāļĢāļ–āļ•āđˆāļ­āļĢāļ­āļ‡āđ„āļ”āđ‰
āļŠāļēāļĒāļ‡āļēāļ™
  • āļšāļĢāļīāļŦāļēāļĢāļœāļĨāļīāļ•āļ āļąāļ“āļ‘āđŒ / āļšāļĢāļīāļŦāļēāļĢāđāļšāļĢāļ™āļ”āđŒāļŠāļīāļ™āļ„āđ‰āļē
  • āđ„āļ­āļ—āļĩ / āđ€āļ‚āļĩāļĒāļ™āđ‚āļ›āļĢāđāļāļĢāļĄ
  • āļāļēāļĢāļˆāļąāļ”āļāļēāļĢ
āļ›āļĢāļ°āđ€āļ āļ—āļ‡āļēāļ™
  • āļ‡āļēāļ™āļ›āļĢāļ°āļˆāļģ

āđ€āļāļĩāđˆāļĒāļ§āļāļąāļšāļšāļĢāļīāļĐāļąāļ—

āļˆāļģāļ™āļ§āļ™āļžāļ™āļąāļāļ‡āļēāļ™:10-50 āļ„āļ™
āļ›āļĢāļ°āđ€āļ āļ—āļšāļĢāļīāļĐāļąāļ—:āđ€āļ—āļ„āđ‚āļ™āđ‚āļĨāļĒāļĩāļŠāļēāļĢāļŠāļ™āđ€āļ—āļĻ
āļ—āļĩāđˆāļ•āļąāđ‰āļ‡āļšāļĢāļīāļĐāļąāļ—:n/a
āđ€āļ§āđ‡āļšāđ„āļ‹āļ•āđŒ:www.atiom.ai
āļāđˆāļ­āļ•āļąāđ‰āļ‡āđ€āļĄāļ·āđˆāļ­āļ›āļĩ:2024

Atiom āđ€āļ›āđ‡āļ™āđāļžāļĨāļ•āļŸāļ­āļĢāđŒāļĄāļ”āđ‰āļēāļ™āļ›āļĢāļ°āļŠāļīāļ—āļ˜āļīāļ āļēāļžāļāļēāļĢāļ—āļģāļ‡āļēāļ™āļŠāļģāļŦāļĢāļąāļšāļ­āļļāļ•āļŠāļēāļŦāļāļĢāļĢāļĄāļ—āļĩāđˆāđƒāļŦāđ‰āļ„āļ§āļēāļĄāļŠāļģāļ„āļąāļāļāļąāļšāļ‡āļēāļ™āļšāļĢāļīāļāļēāļĢ āđƒāļŠāđ‰āđ€āļ•āļĢāļĩāļĒāļĄāļ„āļ§āļēāļĄāļžāļĢāđ‰āļ­āļĄ āļāļķāļāļ­āļšāļĢāļĄ āđāļĨāļ°āļ§āļąāļ”āļœāļĨāļ—āļĩāļĄāļŦāļ™āđ‰āļēāļ‡āļēāļ™ āļ•āļąāđ‰āļ‡āđāļ•āđˆāđ‚āļĢāļ‡āđāļĢāļĄāđ„āļ›āļˆāļ™āļ–āļķāļ‡āļ‡āļēāļ™āļšāļĢāļīāļŦāļēāļĢāļ­āļēāļ„āļēāļĢāļŠāļ–āļēāļ™āļ—āļĩāđˆ āļāđˆāļ­āļ•āļąāđ‰āļ‡āđƒāļ™āļ›āļĩ 2020 āđ‚āļ”āļĒ Matt Spriegel, Ali Nosrati āđāļĨāļ° Devin Licastro

  • āļĄāļĩāļžāļ™āļąāļāļ‡āļēāļ™āļŦāļ™ ...
āļ­āđˆāļēāļ™āļ•āđˆāļ­

āļĢāđˆāļ§āļĄāļ‡āļēāļ™āļāļąāļšāđ€āļĢāļē: Joining our team in Bangkok means working directly on high-impact technology that touches hundreds of thousands of frontline employees worldwide. We foster a collaborative, agile culture where autonomy is deeply respected, bureaucracy is discarded, and your ideas shape products rolled out to world-c ... āļ­āđˆāļēāļ™āļ•āđˆāļ­

āđ€āļ‚āļ•āļ—āļĩāđˆāļ•āļąāđ‰āļ‡āļ—āļĩāđˆāļ—āļģāļ‡āļēāļ™: āļ›āļ—āļļāļĄāļ§āļąāļ™
Display map
āļ—āļĩāđˆ WorkVenture āđ€āļĢāļēāđƒāļŦāđ‰āļĄāļđāļĨāđ€āļŠāļīāļ‡āđ€āļāļĩāđˆāļĒāļ§āļāļąāļšāļšāļĢāļīāļĐāļąāļ— āļšāļĢāļīāļĐāļąāļ— āđ€āļ­ āļ—āļīāļ­āļ­āļĄ (āđ„āļ—āļĒāđāļĨāļ™āļ”āđŒ) āļˆāļģāļāļąāļ” āđ‚āļ”āļĒāļĄāļĩāļ‚āđ‰āļ­āļĄāļđāļĨāļ—āļĩāđˆāđ€āļāļĩāđˆāļĒāļ§āļ‚āđ‰āļ­āļ‡ āļ•āļąāđ‰āļ‡āđāļ•āđˆāļ āļēāļžāļšāļĢāļĢāļĒāļēāļāļēāļĻāļāļēāļĢāļ—āļģāļ‡āļēāļ™ āļĢāļđāļ›āļ–āđˆāļēāļĒāļ‚āļ­āļ‡āļ—āļĩāļĄāļ‡āļēāļ™ āđ„āļ›āļˆāļ™āļ–āļķāļ‡āļĢāļĩāļ§āļīāļ§āđ€āļŠāļīāļ‡āļĨāļķāļāļ‚āļ­āļ‡āļāļēāļĢāļ—āļģāļ‡āļēāļ™āļ—āļĩāđˆāļ™āļąāđˆāļ™ āļ‹āļķāđˆāļ‡āļ‚āđ‰āļ­āļĄāļđāļĨāļ—āļļāļāļ­āļĒāđˆāļēāļ‡āļšāļ™āļŦāļ™āđ‰āļēāļ‚āļ­āļ‡āļšāļĢāļīāļĐāļąāļ— āļšāļĢāļīāļĐāļąāļ— āđ€āļ­ āļ—āļīāļ­āļ­āļĄ (āđ„āļ—āļĒāđāļĨāļ™āļ”āđŒ) āļˆāļģāļāļąāļ” āļĄāļĩāļžāļ™āļąāļāļ‡āļēāļ™āļ—āļĩāđˆāļāļģāļĨāļąāļ‡āļ—āļģāļ‡āļēāļ™āļ—āļĩāđˆāļšāļĢāļīāļĐāļąāļ— āļšāļĢāļīāļĐāļąāļ— āđ€āļ­ āļ—āļīāļ­āļ­āļĄ (āđ„āļ—āļĒāđāļĨāļ™āļ”āđŒ) āļˆāļģāļāļąāļ” āļŦāļĢāļ·āļ­āđ€āļ„āļĒāļ—āļģāļ‡āļēāļ™āļ—āļĩāđˆāļ™āļąāđˆāļ™āļˆāļĢāļīāļ‡āđ† āđ€āļ›āđ‡āļ™āļ„āļ™āđƒāļŦāđ‰āļ‚āđ‰āļ­āļĄāļđāļĨāļˆāļĢāļīāļ‡āļŠāļĄāļąāļ„āļĢāļ‡āļēāļ™ āđ€āļĄāļ§āļīāļ™ āđ€āļĄāļŠāļŠāđŒāļŠāļĄāļąāļ„āļĢāļ‡āļēāļ™ āđ€āļ­āļ—āļđāļ‹āļĩ āļĄāļĩāđ€āļ”āļĩāļĒāļŠāļĄāļąāļ„āļĢāļ‡āļēāļ™ āļŠāđāļāļ™āļ­āļīāļ™āđ€āļ•āļ­āļĢāđŒāļŠāļĄāļąāļ„āļĢāļ‡āļēāļ™ āđ€āļ‹āđ‡āļ™āļ—āļĢāļąāļĨāļ­āļ­āļ™āđ„āļĨāļ™āđŒ