I've spent the last 15 years building backend systems and coping with the challenges they bring. What really excites me is building microservices and figuring out how to make them run smoothly in production. I get genuinely excited about a good API design, data processing pipelines, and making distributed systems that actually solve real business problems.
On the DevOps side, I've become pretty passionate about deployment strategies, monitoring, and scaling systems. AWS has been my playground for years, and I've gotten really comfortable with infrastructure as code, Kubernetes orchestration, and embracing the whole GitOps philosophy.
What I love about having both backend and DevOps experience is that I see the complete picture - from the first line of code to that satisfying moment when everything runs smoothly in production. This perspective helps me write better code and work more effectively with teams. I'm naturally curious and love diving deep to understand why things break (and then fixing them). While I enjoy collaborating with others, I'm also comfortable owning entire projects from start to finish.
I'm drawn to Core/Platform backend roles where I can tackle engineering challenges that ripple across multiple teams. There's something deeply satisfying about building the foundational systems that make everyone else's job easier and more reliable, creating the infrastructure that speeds up development cycles and makes systems more robust.
Salt Security (2022-Present) - Backend Developer, DevOps/SRE
In this fast-growing security startup, I've been the go-to person for infrastructure scaling and keeping systems stable when everything's growing rapidly. What I'm most proud of is leading the development of edge solutions for remote agents - basically making sure our security agents can reliably connect and communicate from anywhere in the world. I've shaped how we handle network connectivity, built observability frameworks that actually help us understand what's happening, and streamlined our deployment processes. The best part? My work directly impacts how well our distributed security agents perform for clients everywhere.
Change Healthcare (2021-2022) - DevOps Lead, Backend Engineer
At Change Healthcare, I was the DevOps Lead responsible for making developers' lives easier. I spent my time designing CI/CD pipelines that actually worked - the kind that let teams deploy with confidence instead of holding their breath. I became the Terraform and CloudFormation person, building cloud infrastructure that was predictable and manageable. I also got everyone excited about GitOps (okay, maybe not everyone, but most people!). On the backend side, I built serverless applications in Go and Node.js, focusing on healthcare data processing that needed to be both scalable and secure - because healthcare data doesn't mess around.
ITMyWay (2014-2019) - Backend Developer
This was where I really got my hands dirty with serverless applications across different cloud platforms. I was juggling Java solutions on Salesforce and Python projects on GCP - basically learning that each cloud has its own personality. I built these large-scale data processing systems that had to handle data coming from everywhere, which meant getting really good at batching, queuing, and scheduling to keep everything flowing smoothly. One of the things I'm most proud of from this period is convincing the team to adopt Git workflows and CI/CD practices - it took some convincing, but once everyone saw how much easier their lives became, there was no going back.
4P-Tech (2010-2014) - Member & Tech Lead
Working in a software cooperative was eye-opening - it taught me how to navigate technical decisions when everyone has a voice in the process. As both a member and Tech Lead, I learned to balance pushing for technical innovation with what the collective thought was best for business. We made decisions together about everything, which meant I had to get really good at explaining technical concepts and building consensus around our direction. I developed information systems, mobile apps for Android/iOS, and API integrations, all while managing our AWS infrastructure. The cooperative structure meant every technical decision was a group discussion, which actually made me a better communicator and taught me to consider multiple perspectives before moving forward.
Drorsoft (2020) - DevOps Consultant & Technical Mentor
I spent some time helping other teams get their DevOps practices on track - implementing CI/CD pipelines, designing cloud infrastructure, and sharing the DevOps practices that actually work in the real world. What I really enjoyed was the teaching side of things - running workshops on Python and JavaScript, doing one-on-one mentoring sessions, and helping developers understand web development fundamentals. There's something really satisfying about seeing someone's face light up when a concept finally clicks.
Dror Israel (2007-2010) - Head of IT
This was my introduction to managing IT - keeping 500 users happy and productive. I handled everything from NT domain administration to crawling under desks to fix network issues. The big project that really tested me was migrating resources from our on-premises to Azure - this was back when cloud services were still pretty new, so it felt like we were pioneering something. I also built a bunch of custom information systems, mobile apps, and websites for different departments. What I learned here was how to work closely with non-technical stakeholders and translate their needs into actual working systems.
Over the years, I've gotten comfortable with quite a few tools. Here's what I've been working with lately:
Languages: Go, Python, Node.js, Java
Containerization: Docker, Kubernetes, ECS
Databases: PostgreSQL, MySQL, DynamoDB, Redis
Messaging: Kafka, RabbitMQ, SQS
Cloud: AWS (Lambda, Fargate, EC2, RDS, MSK), GCP, Azure
Infrastructure: Terraform, CloudFormation
CI/CD: GitLab, GitHub Actions, ArgoCD, GitOps
Observability: Prometheus, Grafana, Datadog
AI: Claude Code, AWS Kiro, Bedrock
"Domain-Driven Design" by Eric Evans - This book completely changed how I approach modeling complex business problems. It taught me to think about software architecture in terms of the actual business domain, which makes everything more maintainable and understandable.
"Designing Data-Intensive Applications" by Martin Kleppmann - My go-to reference for anything involving distributed systems. Whenever I'm designing data storage or building scalable applications, I find myself coming back to the concepts in this book.
My journey with technology started early - I was learning Pascal at my Bar Mitzvah and spending way too much time scripting IRC clients. But the experiences that really shaped who I am came from volunteering in youth movements, where I learned that the best part of knowing something is helping others learn it too.
After serving as a combat medic in the army, I got my B.Ed degree from Beit-Berl College, which reinforced my love for teaching and mentoring - skills that have been incredibly valuable in engineering leadership.
Now I'm 40 with a partner and two kids, and when I'm not debugging systems, you'll probably find me rock climbing, cycling, hiking, or skiing. I speak Hebrew and English fluently, and I'm always up for learning something new (whether it's a programming language or a new climbing route).
Email: marxus@gmail.com
LinkedIn: https://www.linkedin.com/in/marxus/
Phone: +972-54-6734595