Staff Software Engineer - Pulsar Team
bloomreach • Czechia • Slovakia
Posted: March 6, 2026
Job Description
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:
- 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 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)
- Languages & Frameworks: Java / Spring, Python, Go – occasionally TypeScript, Angular, React
- Data: Postgres, MySQL, MongoDB, Redis, Kafka
- Cloud: AWS & GCP (RDS, Redshift, Pub/Sub, BigTable, DataFlow, etc), Docker & Kubernetes (via EKS & GKE)
- Tools: Jira, Gitlab CI/CD, Prometheus, Grafana, OpenSearch
Our expectations
- Flexible intelligence: Stretch your technical skills in a distributed cloud environment, making changes across systems built with various tech stacks to meet challenging requirements.
- Drive: Rapidly ship product improvements that affect thousands of users in a low-drama and high-trust way.
- Security & Reliability: Balance risks and benefits of change with discipline and agility.
- Communication: Organize technical work and maintain trust/respect across multiple teams, geographic regions, and departments.
- Knowledge Sharing: Proactively share expertise, guide less experienced team members, and document work for long-term sustainability.
The ideal candidate’s experience
- Active user of AI coding tools such as Cursor and Claude Code
- Developed backend services with Python using a variety of data systems (5+ years)
- Understands web security principles (OWASP), Authentication, and Authorization practices
- Designed APIs for a SaaS product
- Operated services in production on public cloud infrastructure
- Some experience with Java / Spring or Go
- Exposure to web frontend development (Angular / React)
#LI-KP1
Additional Content
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:
- 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 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)
- Languages & Frameworks: Java / Spring, Python, Go – occasionally TypeScript, Angular, React
- Data: Postgres, MySQL, MongoDB, Redis, Kafka
- Cloud: AWS & GCP (RDS, Redshift, Pub/Sub, BigTable, DataFlow, etc), Docker & Kubernetes (via EKS & GKE)
- Tools: Jira, Gitlab CI/CD, Prometheus, Grafana, OpenSearch
Our expectations
- Flexible intelligence: Stretch your technical skills in a distributed cloud environment, making changes across systems built with various tech stacks to meet challenging requirements.
- Drive: Rapidly ship product improvements that affect thousands of users in a low-drama and high-trust way.
- Security & Reliability: Balance risks and benefits of change with discipline and agility.
- Communication: Organize technical work and maintain trust/respect across multiple teams, geographic regions, and departments.
- Knowledge Sharing: Proactively share expertise, guide less experienced team members, and document work for long-term sustainability.
The ideal candidate’s experience
- Active user of AI coding tools such as Cursor and Claude Code
- Developed backend services with Python using a variety of data systems (5+ years)
- Understands web security principles (OWASP), Authentication, and Authorization practices
- Designed APIs for a SaaS product
- Operated services in production on public cloud infrastructure
- Some experience with Java / Spring or Go
- Exposure to web frontend development (Angular / React)
#LI-KP1