Postman
Enterprise Solutions Engineer
About this role
Postman is seeking an Enterprise Solutions Engineer to enhance their enterprise sales efforts and support customers in adopting API-first development practices. The ideal candidate will have substantial experience in enterprise sales and be proficient in JavaScript and the Postman platform.
What you'll do
- Drive enterprise sales and nurture customer relationships
- Conduct technical demos and workshops for prospective customers
- Address technical questions and provide solutions for customers
- Understand customer workflows and recommend best practices
- Share customer feedback and act as an advocate
- Maintain and develop customer sandbox environments
What they're looking for
- 8+ years in enterprise sales/solutions engineering
- 4+ years of software development experience
- Deep understanding of APIs and data platforms
- Experience with enterprise SaaS sales processes
- Strong communication and listening skills
- Familiarity with developer tools and methodologies
- Team-oriented and able to collaborate effectively
- Ability to engage with diverse audiences
Benefits
- Full medical coverage
- Flexible PTO
- Wellness reimbursement
- Competitive equity package
- Remote work options
- Sales performance incentives
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
Postman
Postman provides an API platform that helps customers adopt API-first development practices and execute API workflows in the cloud. The company is hiring Enterprise and Corporate Solutions Engineers to support customer adoption, as well as Backend Engineers and Customer Success Engineers to build and scale its platform infrastructure.
View all jobs at PostmanLikely interview questions
- Walk us through your experience with enterprise SaaS sales. Can you describe a complex deal you closed and how you navigated technical objections?
- Tell us about your hands-on experience with APIs. What types of APIs have you produced or consumed, and how would you explain API-first development to a non-technical executive?