Staff Software Engineer

Bloomreach is building the world’s premier agentic platform for personalization.We’re revolutionizing how businesses connect with their customers, building and deploying AI agents to personalize the entire customer journey.

And we're building all of that on the intelligence of a single AI engine, **Loomi **, so that personalization isn't only autonomous…it's also consistent.From retail to financial services, hospitality to gaming, businesses use Bloomreach to drive higher growth and lasting loyalty. We power personalization for more than 1,400 global brands, including American Eagle, Sonepar, and Pandora.

We want you to join us full-time as a Staff Backend Engineer. You will work remotely first (from Central & Eastern Europe), but we are more than happy to meet you in our nice offices in Bratislava, Brno or Prague. The Pulsar team builds platform and admin services that all Bloomreach SaaS products rely on. In your first year, you’ll develop features used by thousands of customers and deliver fast, consistent, and high-energy (but low-drama) product releases. We all work remotely from the US, India, and Europe.

Examples of our services:

Why you’ll love your work

Your typical day

Your day begins with review of a teammate’s GitLab merge request. It has already been reviewed by Claude, but you’ll think deeply about the business problem, alternative solutions, and future needs.

Then you spend a few undisturbed hours “in the flow,” working on a technical design doc for a new project. Once you’ve completed a draft, you send it to another teammate for feedback, then decide to jump on a Zoom call to talk it over and refine it.

After lunch, you join the team for a quick standup via Zoom to discuss current work and the plan for the next few days. You mention that you’re finishing up a small improvement to improve the logging and alerting for one of our components that requires high uptime. A teammate offers to review your changes. It has some complex behavior, so you walk through it together and make a few improvements.

Soon, the new unit tests are green. With a few keystrokes, you create a merge request, spin up a dev instance, and deploy your change. After some quick smoke tests, you and your teammate decide to merge the change. Your improvement will be deployed in production with the release in a few days.

Next, you respond to a Slack request for advice on integrating with the authorization API. You draft a short tech design doc that links the API spec, code examples, and optimization tips. You discuss it on the team channel, and your manager forwards it to another team that’s also starting a new service.

Your day ends with a chat with a product manager about questions that came up while drafting the tech design. With their feedback, you refine the proposal to deliver the core feature more quickly, while the product manager will work with customers and decide how much more to invest. Tomorrow, you’ll break down the tasks in Jira and decide what you’ll complete yourself and what you’ll ask teammates to complete….

Our tech stack(s)

Our expectations

The ideal candidate’s experience