--- title: How Prathyusha Ramanjaneyulu at Celonis Eliminated Dev... description: Prathyusha Ramanjaneyulu, a Senior Software Engineer at Celonis, shares how she solved the dev environment problem for 600 engineers. After trying full local... canonical: https://daily.dev/posts/how-prathyusha-ramanjaneyulu-at-celonis-eliminated-dev-environment-overhead-for-600-engineers-v8q7oalea twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: How Prathyusha Ramanjaneyulu at Celonis Eliminated Dev Environment Overhead for 600 Engineers | daily.dev og:description: Prathyusha Ramanjaneyulu, a Senior Software Engineer at Celonis, shares how she solved the dev environment problem for 600 engineers. After trying full local... og:url: https://daily.dev/posts/how-prathyusha-ramanjaneyulu-at-celonis-eliminated-dev-environment-overhead-for-600-engineers-v8q7oalea og:image: https://api.daily.dev/og/posts/V8q7oaleA.png og:image:alt: How Prathyusha Ramanjaneyulu at Celonis Eliminated Dev Environment Overhead for 600 Engineers og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # How Prathyusha Ramanjaneyulu at Celonis Eliminated Dev Environment Overhead for 600 Engineers **[MetalBear](https://daily.dev/sources/metalbear)** · 6 min read · 21 upvotes · 3 comments ## Summary Prathyusha Ramanjaneyulu, a Senior Software Engineer at Celonis, shares how she solved the dev environment problem for 600 engineers. After trying full local setups (weeks to configure) and shared VMs (1.5 days setup, 3+ hours/week maintenance, shared breakage), she evaluated Telepresence and mirrord. She chose mirrord because it impersonates a pod process rather than joining the cluster network, requires no daemon management, operates within the private network, and leaves no persistent cluster footprint. The result: environment setup dropped from days to 15 minutes, feedback loops shrank from an hour to seconds, and engineers stopped blocking each other thanks to mirrord's HTTP traffic filtering, queue splitting, and DB branching. At 600 engineers saving just one hour per week, that's 30,000 hours of capacity reclaimed annually. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What is the main architectural difference between mirrord and Telepresence for connecting to a Kubernetes cluster? Mirrord makes only the specific local process impersonate a pod inside the cluster, while Telepresence makes the entire workstation part of the cluster network. This narrower scope in mirrord reduces blast radius and configuration complexity, and avoids the daemon processes and per-user configuration that Telepresence requires the platform team to maintain. _Comparing Kubernetes dev-environment tools like mirrord and Telepresence is easier with daily.dev's technical breakdowns._ ### How much time did Celonis save on developer environment setup by switching to mirrord? Environment setup time dropped from weeks per engineer with an all-local setup, to about a day and a half with a shared VM, to around 15 minutes with mirrord, a 144x speedup over the shared VM approach. The time between writing code and knowing if it works also dropped from an hour to seconds. _Teams weighing dev-environment tooling changes can track real-world adoption stories on daily.dev._ ### How does mirrord let multiple engineers share the same staging Kubernetes cluster without interfering with each other's tests? Mirrord isolates each engineer's traffic and changes using features like HTTP traffic filtering, queue splitting, and database branching, so any number of engineers can test against the same staging cluster simultaneously without one person's broken change blocking everyone else, unlike a shared VM approach. _Engineers scaling shared staging environments can follow tooling patterns like this on daily.dev._ ## Community discussion Top comments from developers on daily.dev. **@erikandersoon** · 0 upvotes > The math here is staggering. 600 engineers × 1 hour/week × 48 weeks = 28,800 hours reclaimed annually. At a blended engineering cost of even $100/hour, that's nearly $3 million/year in productivity recovered. But the real win isn't the hours—it's the _flow state_. When your feedback loop is "make a change → run a test → wait an hour," you lose context every single time. When it's "change → test → seconds," you stay in the zone. That's where the real productivity lives. The fact that mirrord impersonates the pod process rather than joining the cluster network is the key architectural... ## Similar posts on daily.dev - [How We Shortened Development Feedback Loops From 30m to 30s](https://daily.dev/posts/how-we-shortened-development-feedback-loops-from-30m-to-30s-mq8rpnrxu) · monday Engineering · 2 upvotes · 1 comments - [Testing Is the New Bottleneck for AI-Driven Software Development](https://daily.dev/posts/testing-is-the-new-bottleneck-for-ai-driven-software-development-azhhistin) · MetalBear · 0 upvotes · 0 comments --- Tags: [#kubernetes](https://daily.dev/tags/kubernetes), [#microservices](https://daily.dev/tags/microservices) [View this post on daily.dev](https://daily.dev/posts/how-prathyusha-ramanjaneyulu-at-celonis-eliminated-dev-environment-overhead-for-600-engineers-v8q7oalea) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"How Prathyusha Ramanjaneyulu at Celonis Eliminated Dev Environment Overhead for 600 Engineers","url":"https://daily.dev/posts/how-prathyusha-ramanjaneyulu-at-celonis-eliminated-dev-environment-overhead-for-600-engineers-v8q7oalea","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/how-prathyusha-ramanjaneyulu-at-celonis-eliminated-dev-environment-overhead-for-600-engineers-v8q7oalea"},"datePublished":"2026-07-01T10:50:17.830Z","dateModified":"2026-09-13T20:02:22.984Z","description":"Prathyusha Ramanjaneyulu, a Senior Software Engineer at Celonis, shares how she solved the dev environment problem for 600 engineers. After trying full local...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/5e3d96278024b17f06066d2eac33e35c?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/5e3d96278024b17f06066d2eac33e35c?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"MetalBear","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"MetalBear","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/3165f5f876b147e2a160f4bf0fcaa13a","url":"https://daily.dev/sources/metalbear"},"commentCount":3,"discussionUrl":"https://daily.dev/posts/how-prathyusha-ramanjaneyulu-at-celonis-eliminated-dev-environment-overhead-for-600-engineers-v8q7oalea","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":21},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":3}],"keywords":"kubernetes,microservices","timeRequired":"PT6M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"MetalBear","item":"https://daily.dev/sources/metalbear"},{"@type":"ListItem","position":3,"name":"How Prathyusha Ramanjaneyulu at Celonis Eliminated Dev Environment Overhead for 600 Engineers"}]} {"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/how-prathyusha-ramanjaneyulu-at-celonis-eliminated-dev-environment-overhead-for-600-engineers-v8q7oalea","comment":[{"@type":"Comment","text":"The math here is staggering. 600 engineers × 1 hour/week × 48 weeks = 28,800 hours reclaimed annually. At a blended engineering cost of even $100/hour, that’s nearly $3 million/year in productivity recovered. But the real win isn’t the hours—it’s the flow state. When your feedback loop is “make a change → run a test → wait an hour,” you lose context every single time. When it’s “change → test → seconds,” you stay in the zone. That’s where the real productivity lives. The fact that mirrord impersonates the pod process rather than joining the cluster network is the key architectural insight—it’s non-invasive, leaves no footprint, and doesn’t require managing daemons. Telepresence’s intercept model is powerful but invasive; mirrord’s impersonation model is elegant. The HTTP traffic filtering, queue splitting, and DB branching features are the operational details that make this work at 600-engineer scale. This is how you scale dev environments from 10 to 600 engineers without losing your mind.","datePublished":"2026-07-05T19:32:07.674Z","url":"https://daily.dev/posts/V8q7oaleA#c-M092BAQtA","author":{"@type":"Person","name":"Erik Andersoon","url":"https://daily.dev/erikandersoon","image":"https://lh3.googleusercontent.com/a/ACg8ocIjscYXslkLRHxEihtWWVgTFELNg4TVNJzpD0qugegOqLsZAw=s96-c"}}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/how-prathyusha-ramanjaneyulu-at-celonis-eliminated-dev-environment-overhead-for-600-engineers-v8q7oalea#faq","mainEntity":[{"@type":"Question","name":"What is the main architectural difference between mirrord and Telepresence for connecting to a Kubernetes cluster?","acceptedAnswer":{"@type":"Answer","text":"Mirrord makes only the specific local process impersonate a pod inside the cluster, while Telepresence makes the entire workstation part of the cluster network. This narrower scope in mirrord reduces blast radius and configuration complexity, and avoids the daemon processes and per-user configuration that Telepresence requires the platform team to maintain. Comparing Kubernetes dev-environment tools like mirrord and Telepresence is easier with daily.dev's technical breakdowns."}},{"@type":"Question","name":"How much time did Celonis save on developer environment setup by switching to mirrord?","acceptedAnswer":{"@type":"Answer","text":"Environment setup time dropped from weeks per engineer with an all-local setup, to about a day and a half with a shared VM, to around 15 minutes with mirrord, a 144x speedup over the shared VM approach. The time between writing code and knowing if it works also dropped from an hour to seconds. Teams weighing dev-environment tooling changes can track real-world adoption stories on daily.dev."}},{"@type":"Question","name":"How does mirrord let multiple engineers share the same staging Kubernetes cluster without interfering with each other's tests?","acceptedAnswer":{"@type":"Answer","text":"Mirrord isolates each engineer's traffic and changes using features like HTTP traffic filtering, queue splitting, and database branching, so any number of engineers can test against the same staging cluster simultaneously without one person's broken change blocking everyone else, unlike a shared VM approach. Engineers scaling shared staging environments can follow tooling patterns like this on daily.dev."}}]} ```