
Sign up to save your podcasts
Or


Join us as we explore what happens to narrow job titles when AI rewrites the learning curve! In this episode, Yinon Golan, VP R&D at Papaya, shares the view from the R&D chair: narrow roles were a by-product of company growth, and AI is bringing back the "kolboynik", Hebrew slang for the person who does a bit of everything, only this time with real expertise that is simply much wider. Discover why one feature at Papaya takes six different roles today, why he says DevOps is the team that "manages itself", and what is left for humans when the agent listens in on the Zoom call and the PR is ready by the end of it.
Yinon Golan on LinkedIn - https://www.linkedin.com/in/yinon-golan-11724028/
Miki Manor on LinkedIn - https://www.linkedin.com/in/mikimanor/
Ofir Stein on LinkedIn - https://www.linkedin.com/in/ofir-stein/
DevOps Leaders - https://www.linkedin.com/company/devops-leaders-il/posts/?feedView=all
Key takeaways:
Join our exclusive DevOps Leaders community with over 300 members, where we share knowledge and improve together.
What's your biggest challenge in the DevOps field? Drop it in the comments! Subscribe for weekly insights and updates on the latest in DevOps!
#DevOps #Podcast #Technology #AI #Papaya
Join us as we explore what happens to CI/CD when every developer commands an army of AI agents!
In this episode, Nir Koren, DevOps CI/CD Team Leader at SAP, shares how he went from the 2006 nightly build that one missing semicolon could break for almost 2,000 people to running pipelines for 200 microservices, and why, even when 100 developers become 100K agents, whoever pushes the code still owns it.
Discover how a security scan stayed switched off for two years, why AI that explains build failures hits a wall inside org-specific pipelines, and why Nir says the predictability of CI/CD is what protects business continuity.
Nir Koren on LinkedIn - https://il.linkedin.com/in/nirkoren
Miki Manor on LinkedIn - https://www.linkedin.com/in/mikimanor/
Ofir Stein on LinkedIn - https://www.linkedin.com/in/ofir-stein/
DevOps Leaders - https://www.linkedin.com/company/devops-leaders-il/posts/?feedView=all
Key takeaways:
* In 2006 SAP's nightly build ran 9-10 hours, and one missing Java semicolon left almost 2,000 people worldwide unable to work the next day. That pain is how Continuous Integration was born.
* CI forced the industry toward short, fast builds and then microservices, and Nir shares the counterpoint he quotes from Martin Fowler: if your codebase is manageable, don't go there.
* From Hudson to Jenkins: Kohsuke Kawaguchi's fork, why "org.hudson" still shows up in Jenkins stack traces, and the same license-fork pattern with Elasticsearch, Redis/Valkey and Terraform, now that an agent can rebuild proprietary software.
* Life after a startup acquisition: Gigya became SAP's Customer Data Cloud, with 200 microservices, about 400 repos, around 30 Kubernetes clusters and 600+ nodes, plus the compliance load a corporation brings.
* Control at scale: every Jenkins job is generated from a services database, so deleting a service deletes its jobs. No zombie jobs, and one pipeline file for everything.
* 100 developers become 100K agents, but whoever pushes is accountable. Production deploys that skip the full pipeline are blocked unless an emergency box is ticked and the manager is notified.* A developer switched off a security scan "just to get the build through", and it stayed off for two years until an external audit found it.
* The honest limits of AI in CI: great at npm errors, lost when the error hides in tens of thousands of Jenkins log lines. And the thought experiment: switch off the CI/CD platform and let the agents run, and Nir expects chaos.
Join our exclusive DevOps Leaders community with over 300 members, where we share knowledge and improve together.
What's your biggest challenge in the DevOps field? Drop it in the comments! Subscribe for weekly insights and updates on the latest in DevOps!
#DevOps #Podcast #Technology #AI #SAP
Join us as we explore what site reliability actually looks like at Fortune 1 scale! In this episode, Yoseph Reuveni, Sr. Director II of SRE at Walmart Global Tech, traces a career from an Israeli VC seat through Elbit, Amazon Prime Video, Bloomberg compliance and Jet.com, into running the only SRE function for a company with 35,000 engineers and 2.5 million employees. Discover how his team went from eight engineers staring at dashboards all night to a single person on the holiday bridge, why an EVP asked "how does one SRE beat all of you?" in a room with 600 engineers, and why he calls unit test coverage in the GenAI era "one big fiction."
Yoseph Reuveni on LinkedIn - https://www.linkedin.com/in/yosephreuveni/
Miki Manor on LinkedIn - https://www.linkedin.com/in/mikimanor/
Ofir Stein on LinkedIn - https://www.linkedin.com/in/ofir-stein/
DevOps Leaders - https://www.linkedin.com/company/devops-leaders-il/posts/?feedView=all
Key takeaways:
* The real difference between SRE and DevOps: DevOps upgrades the database, SRE asks what tier it is and whether the customer would even notice it going down.
* 300 SREs supporting 32,000 developers, versus Google's roughly 7,000 SREs for 30,000 developers.
* Walmart's "triplet" architecture: three US regions, each with a private data center plus Azure plus Google, 2 milliseconds apart, all active at once, with cost and capacity deciding where work runs.
* Holiday peaks run 100x a normal day and last for hours, not minutes. Microsoft built data centers so Walmart would have enough capacity.
* 5 billion metrics per second, a volume most monitoring products simply cannot ingest, which is what turned build-versus-buy into build.
* His first week produced a list of 60 things to fix. His boss made him pick three: automation, tech debt, and observability.
* Attacking problems by class, not by incident. One expired certificate becomes a program to eliminate every trust failure across Walmart.
* Adding a missing metric used to mean chasing a team for a year. Now it's two buttons, no code change, no deployment.
* Why AI made him a "master lazy" engineer, and why juniors shipping code they can't explain forced Walmart to require an architect's signature on any runtime change to a new resource.
* The best-selling item at Walmart on Black Friday two years ago: over 30 million bananas.
Join our exclusive DevOps Leaders community with over 300 members, where we share knowledge and improve together.
What's your biggest challenge in the DevOps field? Drop it in the comments! Subscribe for weekly insights and updates on the latest in DevOps!
#DevOps #Podcast #Technology #AI #Walmart
Join us as we explore where the line sits between developer freedom and total chaos in the agentic era! In this episode, Eyal Goldenberg, Director of SaaS Platform & DevOps at Cellebrite, shares how a company that lived on-prem since 1999 made the jump to SaaS, started its platform deliberately "not opinionated" — and learned the hard way why you have to get opinionated to move fast and safe once agents enter the picture. Discover his line on what really separates freedom from chaos ("just how much light you turn on in the room"), how his team built an SDLC fleet of 30+ agents and 40+ skills devs pull as versioned plugins, and why he bets DevOps — soon "AIOps" — is the role that survives and grows.
Eyal Goldenberg on LinkedIn - https://www.linkedin.com/in/eyal-goldenberg/
Miki Manor on LinkedIn - https://www.linkedin.com/in/mikimanor/
Ofir Stein on LinkedIn - https://www.linkedin.com/in/ofir-stein/
DevOps Leaders - https://www.linkedin.com/company/devops-leaders-il/posts/?feedView=all
Key takeaways:
We're recording live from the Platforma conference in Tel Aviv, featuring fascinating discussions on AI and more.
Join our exclusive DevOps Leaders community with over 300 members, where we share knowledge and improve together.
What's your biggest challenge in the DevOps field? Drop it in the comments!
Subscribe for weekly insights and updates on the latest in DevOps!
#DevOps #Podcast #Technology #AI #Cellebrite
Join us as we explore what it feels like to step out of the industry for seven months and walk back into a job that runs at a completely different speed! In this episode, Bat Hen Yosefov, DevOps Group Manager at Payoneer, shares how she returned from maternity leave straight into the AI agent era — where people now expect things in hours, not days or weeks — and why she calls it the coolest leave she's ever had.
Discover why she insists self-service "is service, it's not always self," the story of a Solution Engineer who told Claude to fix a secrets alert and watched it quietly wipe the pipeline ("he doesn't even know what a pipeline is"), and why she believes knowing the right questions to ask is now the difference between heaven and earth.
Bat Hen Yosefov on LinkedIn - https://il.linkedin.com/in/bat-hen-yosefov
Miki Manor on LinkedIn - https://www.linkedin.com/in/mikimanor/
Ofir Stein on LinkedIn - https://www.linkedin.com/in/ofir-stein/
DevOps Leaders - https://www.linkedin.com/company/devops-leaders-il/posts/?feedView=all
Key takeaways:
Coming back from a 7-month maternity leave into the AI era is a shock to the system — the pace went from days and weeks to hours, and "they talk to me in hours now"
A DevOps lead today manages a team of agents alongside developers — the agents genuinely speed up the work, but only if you can keep up with what they produce
Self-service is a misleading term: "it's service, it's not always self" — some teams wrap it, some hand everything to the developer, and the real platform work is in how you wrap it
Knowing the right questions to ask — and understanding the answers you get back — is now the difference between heaven and earth, for engineers and for kids learning today
The platform team's job is shifting toward "letting go" — wrapping quality gates so developers need far less interaction, even though that release work is the less fun part ("I'm DevOps, I'd rather build automation to do it")
The professional-fear dissonance: pushing developers to lean on you less can feel existential, but the backlog is endless and the same headcount can now deliver far more value, faster
Hiring has changed: she doesn't expect a candidate to know everything ("not everyone needs to know Kafka") — she asks whether they can learn and work with the material, because something new drops every two days
Bat Hen's open question for the next guest: how do you build organizational knowledge you can feed your agents — bringing the right information at the right time while it keeps learning and solving tomorrow's problems
We're recording live from the Platforma conference in Tel Aviv, featuring fascinating discussions on AI and more.
Join our exclusive DevOps Leaders community with over 300 members, where we share knowledge and improve together.
What's your biggest challenge in the DevOps field? Drop it in the comments!
Subscribe for weekly insights and updates on the latest in DevOps! #DevOps #Podcast #Technology #AI #Payoneer
Join us as we explore what it takes to re-architect the entire software development lifecycle when the pipeline now serves agents, not just developers! In this episode, Ariel Nackash, Head of DevOps at SecuriThings, shares why he joined a ~100-person startup at the exact moment it's trying to become an AI-native organization, and how he's rebuilding the SDLC for a world where agents do the bulk of the coding — while developers level up to architects and the final approval gate where code meets the main branch ("the human never leaves the loop"). Discover why an agentic pipeline has to absorb 10x the load, why splitting into autonomous vs. human-in-every-iteration cycles matters, and why Ariel bets DevOps teams won't disappear in 2027 — they'll become "Agentic Platform Engineers."
Ariel Nackash on LinkedIn - https://www.linkedin.com/in/ariel-nackash-8030601/
Miki Manor on LinkedIn - https://www.linkedin.com/in/mikimanor/
Ofir Stein on LinkedIn - https://www.linkedin.com/in/ofir-stein/
DevOps Leaders - https://www.linkedin.com/company/devops-leaders-il/posts/?feedView=all
Key takeaways:
SecuriThings is the only company that actually remediates and patches the vulnerabilities on the IoT/physical-security device itself — cameras, access controllers, and the thousands of unmanaged devices sprawled across enterprise data centers — not just detects them
The first problem in IoT security isn't patching, it's inventory: most orgs have no idea what devices, vendors, or firmware versions are even on their network, with unaddressed CVEs running live compute on managed networks
Physical security has no "IT team" to defend it — the wedge is connecting physical-security teams to IT, speaking in IT terms, and giving operators the single pane of glass they need for patching and compliance
Going AI-native isn't buying Claude and Cursor licenses and letting people play — it's designing a custom SDLC where the pipeline now serves agents alongside your developers
An agentic pipeline must absorb ~10x the load, handle new security risk, preserve quality, and stay tailored to the business — old problems, but far more extreme
Build for two cycle types: free, autonomous cycles that need little human involvement, and tighter iterative cycles where a human sits on every iteration
Developers don't disappear — they level up to architects who see the big picture, keep work custom to the business logic, and own the final approval gate where new code meets the main branch
Ariel's open question for the next guest: how do you build a self-maintaining, always-current knowledge layer (from Confluence, Git, posts) that stays accessible as context to agentic flows — efficient and learning, never solving yesterday's problems
We're recording live from the PlatforMa conference in Tel Aviv, featuring fascinating discussions on AI and more.
Join our exclusive DevOps Leaders community with over 300 members, where we share knowledge and improve together.What's your biggest challenge in the DevOps field? Drop it in the comments! Subscribe for weekly insights and updates on the latest in DevOps!#DevOps #Podcast #Technology #AI #SecuriThings
Join us as we explore how you actually break into DevOps — and thrive once you're there! In this episode, Romi Hemo, DevOps Engineer at HoneyBook, shares how she went from QA automation to owning production deploys by refusing to fear touching, breaking, or taking on more than her job asked. Discover how she "stole" her way into the role one task at a time, why her team tore out a pile of deploy scripts for a Go + Temporal "Deploy Service" running GitOps with Argo CD, and her bet that in the AI era "everyone is a builder" and it's all just prompts.
Romi Hemo on LinkedIn - https://www.linkedin.com/in/romi-hemo-9b39b2214/
Miki Manor on LinkedIn - https://www.linkedin.com/in/mikimanor/
Ofir Stein on LinkedIn - https://www.linkedin.com/in/ofir-stein/
DevOps Leaders - https://www.linkedin.com/company/devops-leaders-il/posts/?feedView=all
Key takeaways:
From QA automation to DevOps: the path was a strong infra/automation base, then "stealing" DevOps tasks one at a time until the move was obvious — value first, permission later.
Her two rules for breaking in: come in without fear (to try, to break — DevOps breaks a lot) and relentlessly create added value beyond your job description.
Tearing out messy, duplicated deploy scripts for a purpose-built "Deploy Service" in Go + Temporal — and surviving the over-engineering trap on the way ("how will I look in two years?").
The move from a Helm installer to GitOps with Argo CD: commit, push, and let Argo reconcile the cluster to desired state — plus using Port for production and staging deploys.
The payoff for developers: fewer failures, more visibility, more self-service capability, and far less getting blocked. * Working AI-native today — 4 parallel tasks and 4 Claude tabs open, more time on planning and less on the small stuff, but you have to watch what the agent actually wrote in the PR before giving it free rein.
Her prediction for the AI era: "everyone is a builder," the future platform is mostly text and prompts — "I just talk to Claude and it does everything I need."
We're recording live from the Platforma 2026 conference in Tel Aviv, featuring fascinating discussions on AI and more.
Join our exclusive DevOps Leaders community with over 300 members, where we share knowledge and improve together.
What's your biggest challenge in the DevOps field? Drop it in the comments!
Subscribe for weekly insights and updates on the latest in DevOps!
#DevOps #Podcast #Technology #AI #HoneyBook
Join us as we explore what happens when AI generates vulnerabilities faster than any human can review them! In this episode, Oren Efraim, Technology Leader at Check Point (and leader of the 10,000-member Node.js Israel community), explains why security has to become a first-class part of your platform — not a gate at the end. Discover why 2025's ~50,000 new vulnerabilities are heading toward 100,000, why Check Point's research shows 96% of exploited vulnerabilities aren't even new, and why a CVSS score of 9.9 tells you almost nothing without context.
Oren Efraim on LinkedIn - https://www.linkedin.com/in/orenefr/
Miki Manor on LinkedIn - https://www.linkedin.com/in/mikimanor/
Ofir Stein on LinkedIn - https://www.linkedin.com/in/ofir-stein/
DevOps Leaders - https://www.linkedin.com/company/devops-leaders-il/posts/?feedView=all
Key takeaways:
* The vulnerability flood is real: ~50,000 new vulnerabilities in 2025, heading to 70,000–100,000 as AI coding tools multiply the output
* Check Point's research bombshell: 96% of exploited vulnerabilities are NOT new — they already existed, and nobody patched them
* "Mythos" and the new class of AI models that can map your whole system and find advanced vulnerabilities only veteran security researchers used to catch
* Why a weapon in one person's hands is more dangerous than a weapon everyone has — the zero-day economics of AI-found exploits in open-source libraries
* We don't write code by hand anymore: bring a *different* model with no bias to security-review the code your first model wrote ("the suspect is also the victim")
* Why a 9.9 severity score means nothing without context — attack surface, networking, permissions, and business logic decide what's actually critical
* How to kill the security bottleneck: move from rigid context-free scanners to an agentic system that decides in context, so deployments don't stall
* Who owns the context? Developers know the logic, platform people know the exposure, product people know what the business can't afford to lose — plus detecting drift between what's defined and what's actually running
We're recording live from the Platforma 2026 conference in Tel Aviv, featuring fascinating discussions on AI and more.Join our exclusive DevOps Leaders community with over 300 members, where we share knowledge and improve together.
What's your biggest challenge in the DevOps field? Drop it in the comments!
Subscribe for weekly insights and updates on the latest in DevOps!
#DevOps #Podcast #Technology #AI #CheckPoint
What if, in five years, the system builds itself — a product manager describes what they want, an architect agent inspects the existing codebase, and the feature gets written without a traditional dev team in the loop? In this episode, Erik Parienty, Director of DevOps Engineering at Riskified, lays out that future and what it means for the people running infrastructure today. Erik has spent 7 years scaling Riskified's DevOps from a 6-person team through the company's IPO, and he's been in the field since long before the word "DevOps" existed — which gives him a rare long-lens view on what he calls the discipline's "second revolution."
Erik Parienty on LinkedIn - https://www.linkedin.com/in/erik-parienty
Miki Manor on LinkedIn - https://www.linkedin.com/in/mikimanor/
Ofir Stein on LinkedIn - https://www.linkedin.com/in/ofir-stein/
DevOps Leaders - https://www.linkedin.com/company/devops-leaders-il/posts/?feedView=all
Key takeaways:
The "second revolution": the first wave standardized CI/CD and Kubernetes — the next automates the entire SDLC and PDLC, from the product idea forward
The future org chart: a product manager talks to an architect agent that reads your system and decides whether to customize what exists or build something new
Stop blaming the model — Erik's reframe: "if you told it and it didn't do it, you don't understand it." The agent is a tool; agent literacy is the new Google search
The rise of the one-person company — why you no longer need to raise a round to build, and why (like the Google panic) revolutions create more work, not less
The FinOps cautionary tale: an agent insists your $2M Kubernetes cluster costs $50, because it pulled context from a random server tagged "kubernetes"
Where DevOps still wins: human adaptability. The communication skills we use with people are exactly what make someone good at operating agents
The coming open-source agent ecosystem — git clone a community-maintained agent, run it locally, and it just does the work, the way we run Karpenter and cluster-autoscaler today
The measurement problem nobody's solved: from counting lines of code at Amdocs to counting tokens — and what that says about productivity
What AI still can't touch — infrastructure. Root-cause analysis across distributed systems is the real frontier, well beyond today's self-healing watchdogs
We're recording live from the PlatforMa conference in Tel Aviv, featuring fascinating discussions on AI and more.
Join our exclusive DevOps Leaders community with over 300 members, where we share knowledge and improve together.
What's your biggest challenge in the DevOps field? Drop it in the comments! Subscribe for weekly insights and updates on the latest in DevOps!
#DevOps #Podcast #Technology #AI #Riskified
Join us as we explore what happens to your pipeline when AI turns every developer into a 10x builder! In this episode, Amit Daniel, Director of DevOps at DoorLoop, shares how a fast-moving Israeli proptech went from 40 to 300–500 pull requests a day — and how his team fought back against cloud costs that exploded 5-6x overnight. Discover why writing code fast is no longer the challenge but writing it efficiently is, where humans must stay in the loop when "the suspect is also the victim," and how DoorLoop built an internal platform that lets HR and Finance ship to production safely.
Amit Daniel on LinkedIn - https://il.linkedin.com/in/amit-daniel-%F0%9F%8E%97%EF%B8%8F-%F0%9F%87%AE%F0%9F%87%B1-58062a62
Miki Manor on LinkedIn - https://www.linkedin.com/in/mikimanor/
Ofir Stein on LinkedIn - https://www.linkedin.com/in/ofir-stein/
DevOps Leaders - https://www.linkedin.com/company/devops-leaders-il/posts/?feedView=all
Key takeaways:
From 40 to 500 PRs a day — the new SDLC bottleneck nobody planned for
How "Fusion Week" exposed a 5-6x cloud cost explosion, and the caching, test mapping, and right-sized runners that fixed it
Why security vulnerability reviews are non-negotiable when AI writes the code
"The suspect is also the victim" — where to place checkpoints when AI writes, plans, tests, and reviews itself
Why Claude investigates production incidents at DoorLoop, but never acts without human approval
Skills as your differentiator — tailoring AI to your business instead of getting generic reviews
Deploy By: the internal platform that turns HR, Finance, and Product into safe builders
We're recording live from the PlatforMa conference in Tel Aviv, featuring fascinating discussions on AI and more.
Join our exclusive DevOps Leaders community with over 300 members, where we share knowledge and improve together.
What's your biggest challenge in the DevOps field? Drop it in the comments! Subscribe for weekly insights and updates on the latest in DevOps!
#DevOps #Podcast #Technology #AI #DoorLoop