Back 
It took me some time to realize that DevOps was my true calling, and I still wonder whether it was pure coincidence or fate.
When I was 24, my fascination with foundational concepts led me to major in philosophy at Tel Aviv University. Needing a part-time job, I joined the university’s Tech Support Center, where I quickly discovered I enjoyed solving technical problems. As interesting as philosophy was, I wanted something more stable, so I enrolled in an IT college for a while, where I discovered my passion for systems engineering and eventually secured an internship with great potential.
I dedicated myself entirely to the role, continuing to learn and develop my skills after work. Just two months later, at that same company, I was offered an opportunity to join the Linux and Cloud Department. It was a challenge—I had never worked with Linux systems before, and cloud computing was unfamiliar territory. But I quickly fell in love with Linux-based architecture, intricate networking, and virtualization.
I consistently took on the most complex issues instead of chasing quick wins. That approach built the foundation for how I think today and sharpened the debugging skills I still rely on. Throughout my career, my motivation has come from three things: a genuine passion for what I do, a drive for problem-solving, and a service-oriented mindset.
Whenever I face a technical challenge, I remind myself that there’s a person on the other side relying on the outcome. Whether it’s an organization trusting me with its infrastructure, a development team looking for guidance, or a colleague who needs help, I view each of them as a customer.
That mindset shapes how I approach every project.
Learning by Solving Problems
My curiosity naturally led me to transition into my next role as an Integration Engineer at a large cyber defense corporation.
Shortly after joining, the entire integration team resigned together to launch their own startup. Suddenly, I was supporting R&D, managing the data center, and handling customer deployments without documentation or a team to guide me.
I embraced it as a personal challenge. I learned directly from developers, mapping out their workflows and how our systems interacted. That experience gave me a deep understanding of the product and helped me become the senior integrator and technical focal point, bridging the gap between Integration and DevOps teams.
Working alongside DevOps inspired the eventual career step that brought me to Tipalti. I’ve been at Tipalti for three and a half years, starting as a Senior DevOps Engineer and now as a DevOps Tech Lead.
What I love about this role is that no two days are the same. Some days I spend hours helping teammates solve problems, while others I dive deeply into technical projects and proofs of concept. Success in this role requires adaptability—balancing technical productivity, supporting the people around me, and championing initiatives I truly believe in.
Using Technology for DevOps Success
One of the initiatives I’m proudest of at Tipalti actually started during my parental leave after my first child was born. During my final week away, I noticed I had registered for the DevOpsDays conference. I love attending conventions, speaking with people who build great solutions to everyday problems, and learning about new technologies, so I decided to go.
That’s where it clicked for me.
- The Challenge: At the time, our platform was already operating at a high level. We had standardized our Kubernetes deployments and optimized our CI/CD pipelines, but as we continued to scale, we saw an opportunity to make resource optimization even smarter. Managing resources across hundreds of microservices is complex because every application behaves differently and constantly evolves.
We had already invested in developer enablement through guidelines, study sessions, and alerts, but manual tuning still required ongoing attention from engineering teams. It became clear that optimizing at this level had outgrown manual tracking. I wanted to explore how automation could help us scale. - The Solution: When I returned to work, I discussed the opportunity with my managers and secured approval to run a proof of concept with an automated resource-optimization platform. I approached the testing phase carefully, validating the platform against our needs. At the same time, I built a Helm chart tailored to our workflows to make implementation simple and repeatable.
I also completed a deep dive into the scaling algorithm, why it made certain decisions, and how it handled our edge cases. We started the rollout with two engineering teams, and once they saw how it was optimizing at scale, adoption grew naturally. - The Result: The impact was significant. We eliminated much of the manual effort involved in managing resource requests and limits, enhanced performance by removing unnecessary CPU throttling, and reduced cluster costs by approximately 30%. The platform also increased stability through automated self-healing and new alerts for potential memory issues.
Most importantly, it freed both DevOps and developers from a task that had outgrown manual effort. Everything runs seamlessly, allowing developers to focus on high-impact innovation rather than managing infrastructure.
Building Systems Others Can Own
As I’ve grown into a Tech Lead and since becoming a father, I’ve noticed my definition of success has changed.
Earlier in my career, I wanted to build great systems. Today, I want to build systems that other people can own. A successful initiative shouldn’t depend on the person who created it. The best platforms continue evolving because developers feel empowered to contribute, improve them, and make them their own.
We have incredibly talented developers at Tipalti, and one of the most rewarding parts of my role is creating opportunities for them to shine. Seeing different people solve the same problem in completely new ways never stops being fascinating. That’s why platform engineering, self-service infrastructure, CI/CD, and AI-powered workflows excite me so much. The whole point of DevOps is empowering developers: giving them more control over their own applications and infrastructure so they can focus on writing code and solving problems.
For me, this connects directly back to what has motivated me throughout my career: a passion for the work, problem-solving, and a service-oriented mindset. I enjoy understanding how things work, finding better solutions, and helping others succeed.
Today, technology is moving faster than ever, but the qualities that matter most haven’t changed. Hard work is still essential because effort is always within your control. Curiosity matters just as much. Don’t accept an answer simply because AI generated it. Ask why. Challenge it. Understand the reasoning behind it. And most importantly, learn.
Looking back, I’m grateful I chose Linux and networking more than a decade ago, long before DevOps became an industry buzzword. The tools will continue to change, but service, problem-solving, and hard work will always be the foundation.
Stay tuned for our next Employee Spotlight as we continue to highlight the brilliant minds driving innovation at Tipalti.
