You will be joining a small, high-impact team covering India and APAC. The work is hands-on, fast-moving, and consequential.
What You'll Do
Customer Onboarding and Platform Activation
Drive enterprise customers from contracts close to a fully activated developer platform. Own the technical setup: identity and access controls (SSO, SCIM, RBAC), workspace configuration, Git integration, CI/CD pipeline onboarding, and API catalog setup. Ensure customers have a governed foundation in place within 30–60 days.
SDLC Automation and CI/CD Integration
Build automated pipelines that run contract tests, governance checks, and artifact syncs on every commit. Integrate platform tooling into standard CI/CD systems — GitHub Actions, GitLab CI, Azure DevOps, Jenkins. Leave behind documented patterns the customer team can own and extend.
Security and Identity
Configure and troubleshoot enterprise authentication and identity controls — SSO (SAML, OIDC), SCIM provisioning, OAuth 2.0, API key and token management, secrets vaults, and RBAC. Communicate credential handling clearly to security and compliance stakeholders.
AI and Agentic Platform Activation
Help customers adopt AI-powered and agentic platform capabilities. Demonstrate and align how well-governed APIs and automation layers reduce token waste, improve agent accuracy, and enable safe AI tooling at scale. Connect platform features to real engineering productivity outcomes.
Technical Consulting and Stakeholder Engagement
Run structured technical discovery. Define scope, success criteria, and delivery milestones. Communicate clearly with both engineering teams and executive stakeholders. Translate implementation outcomes into measurable business value — velocity, quality, cost, and risk reduction.
Engineering Quality Awareness
Bring knowledge of engineering quality frameworks — DORA metrics, shift-left testing, QA maturity models, contract testing, and governance scoring. Use this lens to show customers where current practices create risk and where automation creates measurable improvement. Connect the platform to outcomes engineering leaders care about: deployment frequency, change failure rate, mean time to recovery, and test coverage.
Customer Self-Sufficiency
Build reusable assets, templates, and playbooks. Leave every engagement with documented ownership and the customer team capable of running and extending what you built together.
Thought Leadership and Voice of the Customer
When you encounter a friction point — a missing pattern, a recurring customer pain, a product gap — document it so the next person does not have to solve it from scratch. Build reusable knowledge: runbooks, root-cause logs, and playbooks that make the whole team faster. Bring recurring customer challenges to Product and Engineering with enough specificity to drive a real fix — so a problem one customer faces today does not become a problem every customer faces next quarter.
About You
10+ years in a technical customer-facing role — Customer Success Engineer, Solutions Engineer, Solutions Architect, or Implementation Engineer
Development or engineering background: you have built things with code, not just configured tools. Prior hands-on development experience is a strong differentiator.
Hands-on CI/CD experience: you have personally built, modified, or debugged pipelines using tools such as GitHub, GitLab CI, Azure DevOps, Jenkins, or CircleCI
Strong API fluency: REST APIs, API specifications, authentication flows (OAuth 2.0, SAML, OIDC, JWT, API keys), and automated testing
Enterprise identity and security knowledge: SSO, SCIM, RBAC, secrets management, and AuthN/AuthZ patterns
Fluency in one hyperscaller AWS/Azure/GCP etc
Technical depth
Scripting and automation in Python, Node.js, or similar — including calling APIs and building workflow automations
Cloud and infrastructure reasoning: containers, permissions, secrets, and deployment environments
Familiarity with engineering quality frameworks: DORA metrics, contract testing, shift-left QA, and test coverage models
Ability to build beyond a product's UI: scripts, integrations, pipelines, and tooling that solve real customer problems
AI and agentic experience
Practical experience using LLMs or generative AI tools in technical work — scripting, automation, documentation, or integration
Familiarity with agentic frameworks, MCP, or similar approaches to governing AI-driven workflows
Sound judgment about AI outputs: you validate, test, and do not ship generated work without review
Consulting and developer mindset
You find genuine fun in building new things — a novel architecture problem excites you more than it frustrates you
You ask clarifying questions before proposing a solution and scope a manageable first outcome
You define what "done" means, hold to it, and document your decisions clearly
You are equally comfortable in a conversation with a CTO and in a terminal window debugging a pipeline failure
You are customer-obsessed — you naturally want to see the person across the table succeed
What Success Looks Like
Customers are onboarded, identity-configured, and have a working API foundation within 30–60 days of contract close
Initial implementations become repeatable patterns, not one-off deliveries
Customer teams can operate and extend what you built — without calling you back
Technical outcomes are connected to business value and communicated to executive sponsors
Problems you encounter are documented and fed back so the product and team improve continuously
What Else?
In addition to Postman's pay-on-performance philosophy, and a flexible schedule working with a fun, collaborative team, Postman offers a comprehensive set of benefits, including full medical coverage, flexible PTO, wellness reimbursement, and a monthly lunch stipend. Along with that, our wellness programs will help you stay in the best of your physical and mental health. Our frequent and fascinating team-building events will keep you connected, while our donation-matching program can support the causes you care about. We’re building a long-term company with an inclusive culture where everyone can be the best version of themselves.
At Postman we value in person collaboration. We are in office 5 days a week for all roles based out of our hubs in San Francisco Bay Area, Boston, Austin, New York City, Tokyo and London. For roles based in Bangalore, employees currently work in the office three days a week and will transition to five days per week by the end of the year. We were thoughtful in our approach which is based on collaboration and grounded in feedback from our workforce, leadership team, and peers. The benefits of our in office model will be shared knowledge, brainstorming sessions, communication, and building trust in-person that cannot be replicated via zoom.
Our Values
At Postman, we create with the same curiosity that we see in our users. We value transparency and honest communication about not only successes, but also failures. In our work, we focus on specific goals that add up to a larger vision. Our inclusive work culture ensures that everyone is valued equally as important pieces of our final product. We are dedicated to delivering the best products we can.
Equal Opportunity
Postman is an Equal Employment Opportunity and Affirmative Action Employer. Qualified applicants will receive consideration for employment without regard to race, color, religion, sex, sexual orientation, gender perception or identity, national origin, age, marital status, protected veteran status, or disability status. Headhunters and recruitment agencies may not submit resumes/CVs through this website or directly to managers. Postman does not accept unsolicited headhunter and agency resumes. Postman will not pay fees to any third-party agency or company that does not have a signed agreement with Postman.
