blog.postman.com Open in urlscan Pro
162.159.129.53  Public Scan

Form analysis
2 forms found in the DOM

GET /

<form class="form-inline my-lg-0" method="get" action="/">
  <label htmlfor="search-lc" class="search-label">
    <svg class="nav-search__icon" width="16" height="16" viewBox="0 0 16 16" fill="#6b6b6b" xmlns="http://www.w3.org/2000/svg">
      <path fill-rule="evenodd" clip-rule="evenodd"
        d="M9.87147 9.16437C10.5768 8.30243 11 7.20063 11 6C11 3.23858 8.76142 1 6 1C3.23858 1 1 3.23858 1 6C1 8.76142 3.23858 11 6 11C7.20063 11 8.30243 10.5768 9.16437 9.87147L9.89648 10.6036L9.64648 10.8536L13.5758 14.7829C13.8101 15.0172 14.19 15.0172 14.4243 14.7829L14.7829 14.4243C15.0172 14.19 15.0172 13.8101 14.7829 13.5758L10.8536 9.64648L10.6036 9.89648L9.87147 9.16437ZM6 10C8.20914 10 10 8.20914 10 6C10 3.79086 8.20914 2 6 2C3.79086 2 2 3.79086 2 6C2 8.20914 3.79086 10 6 10Z">
      </path>
    </svg>
  </label>
  <input class="form-control" id="search-lc" type="search" placeholder="Search Postman Blog" aria-label="Search" name="s" autocomplete="off" spellcheck="false" dir="auto" value="">
</form>

POST https://blog.postman.com/wp-comments-post.php?wpe-comment-post=mktgproduction

<form action="https://blog.postman.com/wp-comments-post.php?wpe-comment-post=mktgproduction" method="post" id="commentform" class="comment-form" novalidate="">
  <p class="comment-notes"><span id="email-notes">Your email address will not be published.</span> <span class="required-field-message">Required fields are marked <span class="required">*</span></span></p>
  <p class="comment-form-author"><label for="author">Your name</label><br><input class="form-control" id="author" name="author" aria-required="true"></p>
  <p class="comment-form-email"><label for="author">Your email</label><br><input class="form-control" id="email" name="email"></p>
  <p class="comment-form-comment"><label for="author">Write a public comment</label><textarea class="form-control" id="comment" name="comment" aria-required="true"></textarea></p>
</form>

Text Content

 * Product
   
   GETTING STARTED
   
   What is Postman? Customer Stories Download Postman →
   
   API PLATFORM
   
   Collaborate in Workspaces Organize with Collections Explore the API Client
   Build Postman Flows Work smarter with Postbot Browse API Tools
   
   ENTERPRISE SOLUTIONS
   
   Enterprise Essentials API Test Automation Internal API Management
 * What is Postman? API Repository Tools Governance Workspaces Integrations Get
   Started Free →
 * Pricing
 * Enterprise
 * Resources and Support
   
   LEARNING
   
   Learning Center Docs Postman Academy White Papers Breaking Changes Show
   Templates Tutorials Webinars State of the API Report Guide to API-First
   
   COMMUNITY AND EVENTS
   
   Blog Community Postman Supernovas Student Program Events Postman Swag
   
   SUPPORT
   
   Support Center Reseller Support Postman Status Release Notes Contact Us
 * Public API Network

Contact Sales Sign In Sign Up for Free Launch Postman
Blog

 * Learning Center
   
   Learn about how to get started using Postman, and read more in the product
   docs.

 * Labs
   
   Flows, gRPC, WebSockets! Learn about the latest cutting-edge features brewing
   in Postman Labs.

 * Open Technologies
   
   Invest in the knowledge, specifications, standards, tooling, data, people,
   and organizations that define the next 50 years of the API economy.

 * Collection Format
   
   Understand the specification behind Postman Collections. Check out the docs
   and support resources!

 * Blog
   
   The Postman blog is your hub for API resources, news, and community. Learn
   about the Postman API Platform and much more.


 * AI
 * API-First
 * Product Updates
 * Company News
 * Tutorials




HOW POSTMAN USES POSTMAN: E2E TESTING, FEEDBACK LOOPS, AND COLLABORATION

Melinda Gutermuth
November 21, 2023· 5 mins

We love hearing from our community about how you’re using Postman to improve
your API development experience—it truly continues to inspire us. But have you
ever wondered how we might be using Postman internally as we’re building the
Postman API Platform and optimizing our own workflows? In this first post of our
new blog series, “How Postman uses Postman,” we’re taking a look inside one of
our engineering teams to see how they’re using Postman to build Postman.

Today, we’re chatting with Postman Senior Engineer Divyanshu Singh, of the
Workspaces squad. Divyanshu is based in Bangalore, India.

Divyanshu, what do you do at Postman?
I’m a senior engineer at Postman. I’ve been here for four and a half years, and
I’ve seen the organization grow massively in terms of the product as well as the
company. I work closely with the engineering team of our developer product
vertical and am part of the Workspaces squad.

What were you doing before you joined Postman?
Luckily, Postman was my first job straight out of engineering college at Manipal
Institute of Technology. So I was studying engineering before this.


GETTING TO KNOW THE WORKSPACES SQUAD

What does your team do?
When my team started over four years ago, it was called the Collaboration squad.
We aim to enable more seamless collaboration in a variety of ways. This includes
our users’ real-time presence, their commenting experience across Postman, the
activity feed of various parts of Postman, and, most importantly, the heart and
soul of Postman—Postman Workspaces.

Do you have any fun stories about your team?
Our team began with just two people. We had a running joke that we kept playing
chess while dividing up work during initiatives. Then we gradually increased our
team’s head count to four people. And that’s when we converted this analogy from
chess to a carrom board! In the last 1.5 years, we’ve scaled the team to 11
folks, and it’s been a great journey.


HOW THE WORKSPACES SQUAD USES POSTMAN

Exactly how does your team use Postman while working on Postman?
We have been leveraging Postman for tons of engineering workflows. Some of the
most important ones are:

 * End-to-end testing: We implemented an end-to-end testing structure with the
   use of Postman Collections, test scripts, and scheduled monitors. We have
   this structure set up for each of our microservices, which runs every six
   hours. Apart from this, we also have hooks defined to make sure they are run
   on each deployment for our staging and production environments. This has
   helped us identify various issues being shipped before they reach our users.
   It has also helped us gain confidence in shipping things without the fear of
   breaking workflows.
 * Postman Collections: We keep Postman Collections as a reference and source of
   truth for what is available through our various microservices. All our
   endpoints are present in these collections with the right set of examples.
   This helps any new engineer onboard to the service super quickly.
 * CI/CD: We set up contract tests on various microservices with the use of
   Newman, Postman Collections, and mocks in our CI/CD pipelines. This makes
   sure that with each commit, we ensure that we are not breaking any
   consumer-facing contracts.
 * Comments: We use comments as a feedback mechanism in the early stages of API
   development. This creates a feedback loop between the producer and the
   consumer early on in the development cycle, which leads to less back and
   forth between the producer and consumer.
 * Version control: We use features like fork and merge, along with pull
   requests, to make any new changes to the current system. The workflow that
   our team follows is to create a fork from the original collection, make new
   changes, raise a PR, get it reviewed, and get feedback through comments.
 * Watching: We also use the watch functionality on workspaces and collections
   so that we’re notified of any relevant changes made to the elements of our
   interest.

Was your team’s internal use of Postman a remedy for one-off challenges, or have
you implemented it as an ongoing practice?
No, these are not one-off challenges we solved but better practices our team now
follows. We are trying to cultivate an API-first culture within the team, and
these are the foundational stepping stones for that.

How did you (or your manager) get team buy-in for implementing these practices?
Getting the team’s buy-in was pretty easy, as everyone has a deep focus on the
quality of the product, and having testing automated with our microservices gave
everyone confidence about the changes we were shipping.


WHAT DIVYANSHU HAS LEARNED FROM USING POSTMAN

What’s something you’ve worked on recently?
I’ve been working on optimizing our DocumentDB performance and cost optimization
over the past few months, where we were able to bring performance up by 35% and
cost down by around 50%.

What are your favorite productivity tips for working with Postman?
Do explore the shortcuts for Postman—they can be a game changer. Use Postbot to
write test scripts and pre-request scripts, which can save a ton of time.


MORE ABOUT DIVYANSHU

Without revealing any secrets, what’s something you’re excited about working on
or exploring for the future of Postman?
Having scaled products from 0-1 and validated them within Postman, I’m really
excited about scaling these products from 10-100 and solving for the challenges
that come with this new level of scale, especially engineering ones. Also,
making workspaces even more seamlessly collaborative, where more value is
provided to the users as they have the best multiplayer experience.

Do you have any hobbies outside of work that you want to share?
I’m an avid runner and into racquet sports (tennis and badminton) and strength
training. I’m also really into different types of coffee and am always ready to
grab a freshly brewed cup.


THE BOTTOM LINE

Divyanshu and the rest of the Workspaces squad focus on Postman’s built-in
collaboration features—including commenting, the activity feed, and, of course,
workspaces. By making extensive use of Postman’s collaboration tools within
their own team, the squad has achieved some major milestones along their
API-first development journey.

Thanks for sharing your thoughts and experience, Divyanshu!

Interested in becoming a Postmanaut by joining our team? Check out our Careers
page.

+19
Tags: Collaboration Engineering Postman Culture Testing Version Control
Workspaces

Melinda Gutermuth

 * 
 * 
 * 

Melinda Gutermuth is a technical lead at Postman. View all posts by Melinda
Gutermuth.

What do you think about this topic? Tell us in a comment below.




COMMENT CANCEL REPLY

Your email address will not be published. Required fields are marked *

Your name


Your email


Write a public comment





Δ

This site uses Akismet to reduce spam. Learn how your comment data is processed.


YOU MIGHT ALSO LIKE


ACCELERATE YOUR API-FIRST JOURNEY WITH POSTMAN’S NEW ENTERPRISE SOLUTIONS

The Postman Team· 5 mins

Since launching Postman Enterprise in 2018, we’ve collaborated closely with
Fortune 100 and FTSE 100 companies worldwide, including Paypal, Meta’s WhatsApp,
Axis…

Read more →


MANAGE ELEMENT TAGS PROGRAMMATICALLY WITH THE POSTMAN API

David Espi Hernandez· 3 mins

Postman Enterprise users can now add tags to collections, workspaces, and APIs.
Tags help improve organization, collaboration, documentation, discoverability,
and productivity. You…

Read more →


MANAGE PUBLICLY EXPOSED POSTMAN API KEYS

Suhas Gaikwad· 2 mins

Postman API keys provide access to the Postman user’s and team’s data. When
Postman API keys are exposed in Postman public elements,…

Read more →


POSTMAN NAMED BEST API PLATFORM

Postman is the #1 place where developers come to work with APIs. See why we’re
top-ranked in G2’s first-ever evaluation of API Platforms.

Read more →

© 2023 Postman, Inc.


PRODUCT

 * What is Postman?
 * API Repository
 * Tools
 * Governance
 * Workspaces
 * Integrations
 * Enterprise
 * Plans and pricing
 * Download the app
 * Support Center


COMPANY

 * About
 * Careers and culture
 * Press and media
 * Contact us
 * Partner program


LEGAL AND SECURITY

 * Terms of Service
 * Trust and Safety
 * Privacy policy
 * Cookie notice
 * Privacy choices


API CATEGORIES

 * App Security
 * Payments
 * Financial Services
 * DevOps
 * Developer Productivity
 * Data Analytics
 * Communication
 * Artifical Intelligence


SOCIAL

 * Twitter
 * LinkedIn
 * GitHub
 * YouTube
 * Asset 2
   Twitch

We use cookies on your device to enhance your navigation experience, analyze
usage to improve our site, and customize our marketing efforts. You can learn
more about cookies in ourCookie Notice.
Reject All Cookies Accept All Cookies
Manage Cookies




PRIVACY PREFERENCE CENTER

When you visit any website, it may store or retrieve information on your
browser, mostly in the form of cookies. This information might be about you,
your preferences or your device and is mostly used to make the site work as you
expect it to. The information does not usually directly identify you, but it can
give you a more personalized web experience. Because we respect your right to
privacy, you can choose not to allow some types of cookies. Click on the
different category headings to find out more and change our default settings.
However, blocking some types of cookies may impact your experience of the site
and the services we are able to offer.
More information
Allow All


MANAGE CONSENT PREFERENCES

STRICTLY NECESSARY COOKIES

Always Active

These cookies are necessary for the website to function and cannot be switched
off in our systems. They are usually only set in response to actions made by you
which amount to a request for services, such as setting your privacy
preferences, logging in or filling in forms. You can set your browser to block
or alert you about these cookies, but some parts of the site will not then work.

Cookies Details‎

FUNCTIONAL COOKIES

Functional Cookies

These cookies enable the website to provide enhanced functionality and
personalisation. They may be set by us or by third party providers whose
services we have added to our pages. If you do not allow these cookies then some
or all of these services may not function properly.

Cookies Details‎

TARGETING COOKIES

Targeting Cookies

These cookies may be set through our site by our advertising partners. They may
be used by those companies to build a profile of your interests and show you
relevant adverts on other sites. If you do not allow these cookies, you will
experience less targeted advertising.

Cookies Details‎

PERFORMANCE COOKIES

Performance Cookies

These cookies allow us to count visits and traffic sources so we can measure and
improve the performance of our site. They help us to know which pages are the
most and least popular and see how visitors move around the site. All
information these cookies collect is aggregated and therefore anonymous. If you
do not allow these cookies we will not know when you have visited our site, and
will not be able to monitor its performance.

Cookies Details‎
Back Button


COOKIE LIST



Search Icon
Filter Icon

Clear
checkbox label label
Apply Cancel
Consent Leg.Interest
checkbox label label
checkbox label label
checkbox label label

Confirm My Choices