Customer Success Engineer - Apac

Postman Postman · Enterprise · Singapore · Remote · Customer Experience & Services

Postman is seeking a Customer Success Engineer to partner with customers, understand their technical challenges, and architect solutions using Postman's API platform. This role involves translating business objectives into technical implementations, building reusable assets, and providing product feedback. The ideal candidate has a strong background in software engineering, APIs, and developer workflows, with experience in customer-facing technical roles.

What you'd actually do

  1. You'll unblock customers facing everything from basic setup issues to complex architectural challenges. However, your role isn’t _just_ to fix individual problems – your goal is to identify patterns and build solutions that prevent those problems from happening again. When you solve for one customer, you're solving for hundreds.
  2. Partner with CSMs to understand the business objectives, then translate those into technical reality. This means deep technical discovery, understanding their entire stack, and designing implementation paths that actually work in production. No theoretical solutions – everything needs to be battle-tested and deployable.
  3. Build reusable assets such as technical guides, templates, scripts, or reference implementations that scale best practices across customers.
  4. Capture customer challenges, propose interim solutions, and document gaps to inform product roadmap discussions.
  5. When out of the box functionality is insufficient, design pragmatic solutions (workarounds, custom scripts, integrations, etc.) to help unblock and activate customers.

Skills

Required

  • 6-8+ years in a technical customer-facing role
  • Computer Science or Engineering degree or equivalent real-world experience
  • JavaScript and related technologies such as Node.js or TypeScript, or equivalent experience with other modern scripting languages
  • Deep understanding of APIs, developer workflows, and modern DevOps practices
  • Proven ability to scope ambiguous problems and deliver working solutions quickly
  • Experience building technical collateral that scales - scripts, templates, automation tools
  • Comfort engaging both individual developers and enterprise architects

Nice to have

  • familiarity with the broader developer toolchain – GitHub, AWS, Azure, and other pipelines

What the JD emphasized

  • technical architect of Customer Success
  • turning complex and nuanced challenges into repeatable solutions
  • translate complex business objectives into actionable implementation steps
  • deep technical discovery
  • designing implementation paths that actually work in production
  • battle-tested and deployable
  • build reusable assets
  • scale best practices across customers
  • document gaps to inform product roadmap discussions
  • design pragmatic solutions
  • script, templates, automation tools
  • how enterprises _actually build and ship software_