About
Software engineer by foundation. Performance engineer by passion.
I’m Josef Lehner, a Senior Customer Success Engineer at IBM Austria. My background spans nearly 20 years across software development, performance engineering, technical sales, and customer success.
From building software to improving complex IT systems
I started my professional IT career in 2007 as a software developer. During more than ten years at msg, I helped design, build, optimize, and maintain enterprise applications using Java, JEE, SQL, Hibernate, Maven, and service-oriented architectures.
My work covered the complete application lifecycle: architecture and development, performance optimization, production go-live, maintenance, and troubleshooting. I worked on business-critical systems with many consumers and tens of thousands of concurrent users, analyzing challenges such as inefficient SQL access, N+1 queries, object churn, heap usage, request latency, and thread and connection pool behavior.
That experience shaped how I approach technology today. I still think like a developer: understand the system, reproduce the behavior, inspect the evidence, test assumptions, and solve the underlying problem rather than treating only the symptom.
Finding my passion in performance engineering
After software development, I spent nearly five years at Dynatrace as a Performance Engineer. I investigated performance regressions, scalability limits, CPU and memory behavior, garbage collection, resource leaks, and distributed-system bottlenecks in a multi-node cluster architecture.
Performance engineering taught me to connect application behavior with infrastructure, telemetry, architecture, and user experience. It also reinforced a principle that still guides my work: reliable decisions require evidence, not assumptions.
Helping customers turn technology into outcomes
Today, I work in a client-facing technical role at IBM Austria. As a Senior Customer Success Engineer, I help organizations improve the performance, reliability, efficiency, security, and economics of modern IT systems.
I work with customers and partners on architectures, demonstrations, technical deep dives, proofs of concept, deployments, adoption, and continuous optimization. My goal is not simply to explain what a product can do, but to understand the customer’s environment and help turn technology into measurable value.
What I work with
My work sits at the intersection of software engineering, observability, application performance, FinOps, cloud optimization, automation, security, and cloud-native platforms.
Why I write
I have wanted to create a technical blog for years, but kept postponing it. In 2027, I will look back on 20 years in professional IT. This site is my way of documenting what I have learned and giving something back to the community that supported me throughout that journey.
I write about problems I encounter in real projects, demos, labs, and troubleshooting sessions. Writing forces me to examine a topic more deeply, document what I learned, and turn a one-time solution into knowledge that I and others can find again later.
My goal is simple: publish honest, technically sound articles that help practitioners solve difficult problems, make better architectural decisions, and understand what is happening beneath the surface.
What you can expect here
- Hands-on troubleshooting stories, including the reasoning behind the solution
- Software and performance engineering lessons from real enterprise systems
- Technical deep dives into integrations, identity, architecture, and platform behavior
- Practical guidance on observability, FinOps, automation, and cloud optimization
- Experiences from customer projects, labs, demonstrations, and proofs of concept
- Configuration details, failure modes, and validation steps that are easy to overlook
I write for developers, engineers, architects, platform teams, FinOps practitioners, technical sellers, and technology leaders who value practical experience over marketing language. Where useful, I will share not only what worked, but also what failed, how I tested my assumptions, and what I learned along the way.
Let’s connect
If an article helps you, raises a question, or relates to a challenge in your organization, I would be glad to hear from you. The best place to connect is LinkedIn.