Principal Software Engineer- Site Reliability

LIFE AT UIPATH

The people at UiPath believe in the transformative power of automation to change how the world works. We’re committed to creating category-leading enterprise software that unleashes that power.

To make that happen, we need people who are curious, self-propelled, generous, and genuine. People who love being part of a fast-moving, fast-thinking growth company. And people who care—about each other, about UiPath, and about our larger purpose.

Could that be you?

Your mission

We see boundless potential in the way we live. It drives the way we work. Our culture is our most valuable asset. It acts like a compass for us. We are fast, immersed, humble and bold. And thatʼs not just words on the walls. Eliminating time-consuming tasks means people get to do more of what they love. Itʼs an inspiring, high stakes challenge that motivates us, and this common passion bonds UiPath employees globally. We all strive every day to be better and to accelerate human achievement. We make software robots, so people donʼt have to be robots. Would you like to be part of this journey?

At UiPath's Site Reliability team, we build the platforms and systems the entire company depends on to deliver on our compliance and SLA promises to customers. These span services and tools that enforce cloud access policies, cost governance, observability, operational excellence, and reliability across UiPath. We are scaling each of these pillars, and building the next generation of capabilities on each, powered by AI.

This is a software engineering role. You will not be the person who identifies a reliability gap and files a ticket for another team to fix. You are the engineer who identifies the gaps across teams, designs the system that closes it, builds it, ships it, and drives its adoption — often by doing the integration work yourself rather than asking other teams to come to you. You build platforms that other engineers depend on in their critical path, and you hold yourself accountable to outcomes, not outputs.

You treat every system you ship as a product: you put it in front of users early, seek feedback aggressively, and iterate until it delivers real results. If adoption is slow, you donʼt blame the docs — you sit with the team, understand the friction, and remove it.

What you will be doing at UiPath As a Principal Software Engineer, you will