Customer Success Engineer​/Devops

Boston, Massachusetts;
New York, New York, United States;
San Francisco, California, United States

Postman is the world’s leading API platform, used by more than 45 million+ developers and 500,000 organizations, including 98% of the Fortune 500. Postman is helping developers and professionals across the globe build the API‑first world by simplifying each step of the API lifecycle and streamlining collaboration—enabling users to create better APIs, faster.

The company is headquartered in San Francisco and has offices in Boston, New York, Austin, Tokyo, London, and Bangalore – where Postman was founded. Postman is privately held, with funding from Battery Ventures, BOND, Coatue, CRV, Insight Partners, and Nexus Venture Partners. Learn more at  or connect with Postman on X via @get postman.

We're building out the Customer Success Engineering team at Postman, and we need business‑minded engineers who can solve real problems  will partner closely with Customer Success Managers and own the “How” of technical solutioning. This is a consultative role that requires both depth and versatility. This is no support role; you'll be the technical architect of Customer Success, turning complex and nuanced challenges into repeatable solutions that benefit our entire enterprise customer base.

As a CSE, you consult on the technical implementation path. When a customer needs to get from point A to point B, you figure out how to make it happen – whether that means architecting workflows within Postman, guiding integrations, or creating pragmatic workarounds when the product doesn't quite fit. A key part of this role is turning individual solutions into reusable assets that shorten time to value for future customers.

We don’t believe in reinventing the wheel each time.

Success in this role requires a blend of technical expertise, systems thinking, and the ability to translate complex business objectives into actionable implementation steps.

• Value Acceleration at Scale: 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.
• Technical Discovery and Solutioning: 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.
• Collateral and Enablement: Build reusable assets such as technical guides, templates, scripts, or reference implementations that scale best practices across customers.
• Product Feedback Loop: Capture customer challenges, propose interim solutions, and document gaps to inform product roadmap discussions.
• Adaptive Problem Solving: When out‑of‑the‑box functionality is insufficient, design pragmatic solutions (workarounds, custom scripts, integrations, etc.) to help unblock and activate customers.

You need 6‑8+ years in a technical customer‑facing role and a portfolio of “built things”.

Customer Success Engineering, Solutions Engineering, Forward Deployed Engineering, Technical Account Manager… the title doesn't matter as much as the hands‑on technical work that solves real problems for customers.

You should have:

• Strong foundation in Computer Science or Engineering (degree or equivalent real‑world experience)
• Deep understanding of APIs, developer workflows, and modern Dev Ops 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
• You should be comfortable in Postman and familiar with the broader developer toolchain – Git Hub, AWS, Azure, and other pipelines. Most importantly, you need to understand how enterprises actually build and ship software
  , not just how they…