Let's keep in touch

orNew to LinkedIn? Join nowBy clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.I have an extensive background from software development to cloud environments and DevOps…“I had the pleasure of working with Jaakko, who joined one of our engineering domains to provide expertise in infrastructure and engineering practices. At the time, our domain consisted of several squads focused on post-launch improvements — specifically in stability, time to value, and overall efficiency. From the very beginning, Jaakko integrated seamlessly with our teams. He collaborated closely with domain and team leads to identify key improvement areas and developed a clear, actionable roadmap. His impact was both immediate and measurable:

• Reduced service running costs by ~15–20%.
• Enhanced Infrastructure-as-Code (IaC) quality through improvements in CDK usage, reducing risk in stack layouts and resource utilization.
• Built an observability library now adopted across multiple domains.
• Developed reusable patterns and modules that significantly reduced toil and increased deployment speed—by extending existing Pkl modules, he enabled teams to roll out GHA workflows centrally, cutting update times by about 50%.
• Created a clear migration path for teams to move from CDK to Terraform.
• Addressed skill gaps by developing utilities and guidance documentation that empowered engineers to work more efficiently and independently. Jaakko was consistently reliable, proactive, and a trusted partner in every initiative. I valued his honest feedback, collaborative approach, and ability to translate complex technical challenges into practical solutions. He worked effectively with all parts of the business, building strong relationships across teams and earning high respect from everyone in engineering. Jaakko’s combination of technical expertise, communication skills, and genuine enthusiasm made him a standout contributor—and a pleasure to work with.”“Jaakko is an engineer of amazing range: we collaborated on a lot of different projects, and he felt right at home no matter what it was. From data analysis and system design to SRE and CI/CD down to nitty-gritty typescript and bash, he always saw potential problems from a mile away and built beautiful, insightful and robust solutions. He was able to instantly grasp inner workings of complex systems and mentor people from other teams on how to best improve their architecture to achieve their goals. And the best part is that he did all that while being the most pleasant upbeat person you could imagine, always brightening up your day and helping you learn and grow. Any team would benefit tremendously from having him on board, and if you get an opportunity to work with him, don't miss it!”3 people have recommended JaakkoScaleOps19K followersSpark on Kubernetes looks great on paper. But in production? That's where things break. Spark assumes static executor sizing. Kubernetes expects dynamic workloads. Add the JVM blind spot, where Kubernetes can’t see heap usage, off-heap allocations, or GC pressure, and you get the classic failure mode: executors look healthy to Spark but get killed by cgroup memory limits. That’s not optimization. That’s firefighting. In our latest blog post, Konstantin Zelmanovich breaks down why this happens and how the ScaleOps platform fixes it. If you’re running Spark in K8s and tired of memory guesswork, this one’s for you. Read the full breakdown 🔗 https://lnkd.in/dkQTvi_WSajjad TariqExceptional IT Training
• 3K followersKubernetes adoption debate persists; early stage choices matter. Trend: Public discussions (Hacker News threads, community posts) show many startups still wrestle with whether Kubernetes is right at early stage. Why it matters: Choosing K8s too soon creates complexity; choosing it too late makes migration costly. Pick patterns that match team maturity. Question: What’s the 90-day checklist to know whether K8s is the right first platform for your team? 🔁 Repost if platform choice is a tradeoff, not a fad 🔔 Follow me for pragmatic infra decision guides 🌟 Takeaway: Solve for the team you have, not the org you hope to beDanny TippleDanOps
• 17K followersDid a LinkedIn search earlier for a Staff/IC Engineer with deep Kubernetes experience ✅ With the word “expert” in the profile headline or summary
• 857 results. Out of those… only 3 women. Then I removed the ego word and instead searched using proper context around what they actually worked on, delivered, improved… 🎯 117 results – 41 of them women. Maybe this shows something powerful:
• Those shouting "expert" loudest… often aren’t.
• Meanwhile, a lot of women in tech seem far more likely to describe impact, ownership, delivery - rather than just claiming a title.
• And isn’t that exactly what great engineering leadership and management is built on? Less “I’m an expert”, more “Here’s what I delivered and how it helped the team/product”. If that’s the trend, it’s no surprise so many women naturally transition into leadership roles - they’re already communicating like leaders.Scala Teams1K followersSome of the toughest bugs aren’t caused by broken code, they’re caused by changing facts. In the second post of our Learning Scala series, we explore immutability and why it matters for building reliable, scalable systems. When values drift over time, downstream processes break: prices get overwritten, orders are miscalculated, workflows misfire. Functional programming and Scala make immutability practical and expressive, so your systems behave as intended even under concurrency, distribution, and continuous change. This post covers real-world examples and how immutability turns architectural discipline into everyday code. Follow the series to see how Scala makes reliable systems easier to build and reason about. Read the post here: https://lnkd.in/gYiriZpX #Scala #FunctionalProgramming #TechLeadershipLMNTRIX12K followers🐛 What's worse than a 10.0 CVSS score? Nothing, it doesn't get any worse. 🤯 Researchers have revealed a critical 13-year-old bug in Redis (CVE-2025-49844, aka “RediShell”), rated at CVSS 10.0, that allows authenticated users to run malicious Lua scripts which can manipulate the garbage collector and trigger use-after-free vulnerabilities. 🩹 In effect, this flaw breaks out of the Lua sandbox and enables remote code execution on the Redis host. The flaw affects all Redis versions supporting Lua scripts. Redis has released patches in versions 6.2.20, 7.2.11, 7.4.6, 8.0.4, and 8.2.2 on October 3, 2025. ⚔️ Actionable threat intelligence not only involves knowing what bugs exist in the wild, but also how threat actors actively exploit them. SIEM alerts certainly do not provide such critical context, but LMNTRIX XDR does. To find out more, visit us here 👉 https://lmntrix.com/ #LMNTRIX #XDR #MDR #MXDR https://lnkd.in/gch5EQx3SoftwareMill6K followersSafe resource usage is coming to #Scala Our very own Adam Warski has written an insightful piece on the upcoming Scala 3.8 release. It’s the perfect moment to experiment with capture checking - but first, let's take a look how it works. 🔗 Adam walks you through the concept in his latest article: https://lnkd.in/dqF4dtbh #CaptureChecking #Scala38 #ScalaReleaseWe’re unlocking community knowledge in a new way. Experts add insights directly into each article, started with the help of AI.Agree & Join LinkedInBy clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.orNew to LinkedIn? Join nowBy clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.