Development cycles, process, and tooling
Sumeet Jain from Sublime Security
·
April 10, 2025
What happens when a fully remote team prioritizes speed, flexibility, and customer feedback?
In this episode of the Distributed podcast, host Jack Hannah talks to Sumeet Jain, Head of Engineering at Sublime Security, about how they manage one-week development cycles to stay agile and responsive to their customers’ needs. Sumeet shares how the team’s reliance on Slack and Notion streamlines workflows and minimizes friction, helping engineers stay connected even across time zones.
They also discuss how making work visible, listening to customers, and maintaining a balance between speed and quality are key to Sublime’s success in a fast-paced remote environment.
- Why a one-week development cycle gives Sublime a competitive edge
- How the team uses Slack and Notion to manage tasks and streamline communication
- The importance of making work visible to foster camaraderie in a remote team
- How prioritizing customer feedback drives development decisions
- Maintaining speed and focus while ensuring quality in a rapid delivery environment
- (00:00) – Kicking things off with Sumeet Jain
- (01:13) – Catching the software bug with a Penny Hardaway fan site
- (02:21) – Running a fully remote team across North America
- (03:20) – Why Sublime chose one-week engineering cycles
- (07:00) – Inside the Monday planning ritual and company alignment
- (11:39) – How customer feedback drives weekly priorities
- (14:08) – Rethinking under promise and over deliver culture
- (19:02) – Principles behind Sublime’s lightweight operations
- (22:59) – Using emoji reactions to create tasks in Slack
- (28:47) – Organizing work through “T channels”
- (34:01) – Sumeet’s favorite remote work gear and why air quality matters