Java Software Engineer

About Piano  

Piano’s Digital Revenue Optimization solution helps digital services grow revenue by better understanding and influencing their customers’ behavior. Piano unifies analytics, segmentation, and commercial personalization in one AI-driven application, enabling sites and apps to efficiently maximize the value of every user's visit. Headquartered in Amsterdam with offices in the Americas, Europe, and Asia-Pacific, Piano serves a global client base including the BBC, Deutsche Telekom, Nikkei, AXA and the Wall Street Journal.  For more information, visit piano.io. 

About Us 

We’re an engineering led office, building a high-performance real-time data platform with demanding reliability and performance requirements. Our systems must be fast, fault-tolerant, global, and transparent to debug, which is why we care deeply about writing clear, well-reasoned code rather than leaning on unnecessary abstractions. 

We’re looking for a Java Engineer who thrives in complex technical environments, enjoys challenging performance problems, and naturally questions how and why systems behave the way they do. If you get genuine satisfaction from debugging, discussing architecture choices, or exploring JVM internals just because you like it, you’ll fit right in here. 

What You’ll Do: 

Design, implement, and maintain high-performance Java-based services and components. 

Optimize system performance and latency, using profiling, benchmarking. 

Collaborate closely with product owners, architects, and engineers to design pragmatic, maintainable solutions.

Contribute to team goals, both by hands-on coding and by helping define technical direction.

Review code and mentor peers, encouraging clarity and thoughtful trade-offs in design.

Participate in full Software design life cycle, from design and implementation to testing, deployment, and monitoring. 

We are looking for you if: 

You are comfortable finding the answers to questions like: 

How does JVM selection impact performance? 

How does garbage collection, and data structure choices influence throughput and latency?

How do different concurrency models behave under load, and how can they be tuned?

You are comfortable saying things like: 

I don’t understand how this works, can you (..) 

I’m not sure, but this is my understanding (..) 

Let’s do this on the whiteboard instead. 

As an Engineer: 

Your primary goal is to learn and grow your skills. 

You value clarity and correctness over cleverness, because clear code is easier to reason about and debug under pressure. 

You’re open to defending your ideas and changing your mind when presented with new information. 

You take pride in helping others grow, code reviewing, and knowledge sharing.

You stay curious, you tinker, test, and learn, not becauseyou’retold to, but because you enjoy understanding how things really work. 

What We Offer: 

A team that values engineering excellence and curiosity.

Real influence on technical direction and system architecture.

A culture where asking questions is a strength.

A highly competitive compensation

Healthy work life balance, because enthusiasm for tech shouldn’t mean endless hours. 

Fuzzball and ping pong in the office