About the role
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. We're taking autonomous search mainstream, making product discovery more intuitive and conversational for customers, and more profitable for businesses. We’re making conversational shopping a reality, connecting every shopper with tailored guidance and product expertise — available on demand, at every touchpoint in their journey. We're designing the future of autonomous marketing , taking the work out of workflows, and reclaiming the creative, strategic, and customer-first work marketers were always meant to do. And we're building all of that on the intelligence of a single AI engine — Loomi AI — 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 Software Backend Engineer (medior level). 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 . For candidates at the P2 / Software Engineer II level, starting monthly
compensation begins at 2 900 € gross , with the final offer tailored for each candidate based on their skills and experience. Stock options and a comprehensive
benefits package are also included. 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: Central services to publish Model Context Protocol APIs for external AI agents Multi-product customer provisioning and licensing orchestration Integrated user management, authentication, and authorization High-availability, centralized configuration management Tools for new customer integration & product tuning Why you’ll love your work Technical Variety: Cloud-native services with diverse tech stacks offer learning and experimentation. Impact: Our services are used by customers and teams across the company – engineers, product managers, services consultants, and even executives. Autonomy: Senior engineers design, build, and deploy complete projects and are experts in our services. Teamwork: Your teammates are also high performers and will support you with learning our systems, brainstorming & design review, and running high-reliability production deployments. Your typical day Your day begins with review of a US 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 changes to the user management APIs to support a UX improvement that a designer suggested yesterday. Soon, all your 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 send a link to a frontend engineer who is collaborating with our team. After lunch, you join your team for a quick standup via Zoom to discuss current work and the plan for the next few days. A teammate offers to review your new code. It has some complex behavior, so you walk through it together and make a few improvements. The frontend engineer confirms over Slack that your API changes provide what they need. You merge it, which automatically retests and deploys to a staging environment. The UI changes and a few more integration tests from the QA team will be merged in a day or two. Your improvement will be in production in a few weeks. 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
