# In Focus: Jay Dihenkar

DevFeed: [In Focus: Jay Dihenkar](<https://devfeed.tech/articles/in-focus-jay-dihenkar-20087.md>)

Original publisher: [Read original article](<https://lambda.blinkit.com/in-focus-jay-dihenkar-3cd0456a9efa?source=rss----42df4a1e8725---4>)

Author: Jacob

Published: 2023-02-23T03:01:29Z

Content type: opinion

Language: en

Sources: [Grofers](<https://devfeed.tech/sources/grofers.md>)

Topics: [release engineering](<https://devfeed.tech/topics/release-engineering.md>), [SRE](<https://devfeed.tech/topics/sre.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Resilience](<https://devfeed.tech/topics/resilience.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [observability](<https://devfeed.tech/topics/observability.md>), [developer-productivity](<https://devfeed.tech/topics/developer-productivity.md>), [Automation](<https://devfeed.tech/topics/automation.md>), [Scalability](<https://devfeed.tech/topics/scalability.md>), [systems](<https://devfeed.tech/topics/systems.md>)

Tags: [automation](<https://devfeed.tech/tags/automation.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [culture](<https://devfeed.tech/tags/culture.md>), [developer](<https://devfeed.tech/tags/developer.md>), [developer-productivity](<https://devfeed.tech/tags/developer-productivity.md>), [devops](<https://devfeed.tech/tags/devops.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [observability](<https://devfeed.tech/tags/observability.md>), [people-at-blinkit](<https://devfeed.tech/tags/people-at-blinkit.md>), [quick-commerce](<https://devfeed.tech/tags/quick-commerce.md>), [release-engineering](<https://devfeed.tech/tags/release-engineering.md>), [resilience](<https://devfeed.tech/tags/resilience.md>), [scalability](<https://devfeed.tech/tags/scalability.md>), [site-reliability-engineer](<https://devfeed.tech/tags/site-reliability-engineer.md>), [sre](<https://devfeed.tech/tags/sre.md>), [systems](<https://devfeed.tech/tags/systems.md>)

## AI overview

An interview with Blinkit Staff Engineer Jay Dihenkar about his journey from release engineering to site reliability engineering. He discusses CI/CD, developer productivity, production incident debugging, automation, monitoring and alerting, infrastructure costs, application reliability patterns, and challenges in scaling quick-commerce logistics.

## Source excerpt

A conversation with engineers who help run Blinkit Jay Dihenkar is a Staff Engineer at Blinkit. He joined us in December 2020 and has helped different teams manage and streamline their build and release processes. He is currently working towards continuously improving the reliability, scalability, observability, developer productivity, and other such aspects of a software system critical for ensuring that the system can meet the needs of its users and stakeholders over time. Tell us something about yourself and your journey in Blinkit so far. I started out as an engineer on the Release Engineering team, working on goals of Software Quality/Stability and streamlining release processes (Continuous Integration/Continuous Deployment or CI/CD). I help make an impact by improving developer productivity while safeguarding the production ecosystem against failures. I later transitioned into the Site Reliability Engineering (SRE) team, where we focused on improving the reliability and resilience of our systems. Being a site-reliability engineer requires one to develop a deep understanding of how the various components of a system work together and how to optimize them. Overall my journey in Blinkit is one of continuous learning and improvement. If you were to describe your experience as a Blinker in one word, what would that be? Growth. Being here is all about continuous learning in a fast-paced environment. What does a typical day at work look like for you? On a typical day, I work on the following domains (though not everything on a single day!): debugging complex problems sprung out of production incidents, putting automation in places where required, setting up monitoring and alerting, as well as responding to alerts, release engineering and developer productivity (CI/CD), System Infrastructure Cost, Working toward implementing Application Reliability Patterns and so on... What are the biggest challenges facing quick commerce today? I believe the "Logistics infrastructure"