Apify
Platform Reliability Engineer
Part remote, part office, you need to live within commuting distance of a named location.
Hybrid · Prague
Employer listed it 3 months ago · Added yesterday
Been open since 3 months ago. Long-running listings are sometimes left up after the role is filled.
Salary
Not stated
Location
Hybrid · Prague
Timezone
Not stated
Contract
Full-time
Experience
Mid
Category
Software
This employer didn't state pay. Jobs like this usually pay around $165k–$255k a year, a typical range taken from 594 mid-level software roles on Nomaders that do state pay. It's a guide, not an offer.
Remote flexibility
Hybrid
This role is only partly remote, the employer expects time in the office around Prague, Brno, Hybrid, so you need to live within commuting distance.
What the employer says
- Source listing states candidate location: "Prague, Brno, Hybrid"
- Listing mentions "Hybrid"
What Nomaders makes of it
- Not suitable if you plan to move between countries
The quotes above are the employer's own words; the reading is ours. Always check the original listing and employment terms before working from another country.
About the role
Apify is the largest marketplace of tools for AI. 40,000+ Actors helping people and agents get real-time web data, track competitors, generate leads, or integrate their apps. Actors are built by a global creator community that now earns more than $1.2 million every month.
Join us to help people put the web to work. Apify can find missing children , protect consumers from fake discounts across the EU , and feed data to AI chatbots .
To support our mission, we're looking for a Platform Reliability Engineer with a developer's mindset. You've shipped code and you care what happens when it runs in production (speed, failures, recovery). You'll help us strengthen the way Apify monitors systems, handles incidents, and routes alerts, so engineering teams can ship with confidence. You won't be on-call. This role is focused on sustainable improvement, not after-hours emergency response.
What you'll be working on:
Monitoring & signals: Operate and improve our monitoring stack (Prometheus, Grafana, OpenTelemetry) - instrument services to expose the right metrics, define what we watch in production, and shape alerting so teams get actionable signals without the noise.
When things go wrong: Help define how we run incidents - clear communication, structured learning afterward, and supporting artifacts (status page, runbooks).
With the team: Work with platform and product engineers to make reliability standards practical - help teams adopt better tooling or practices when things change, and write documentation people actually use.
Who we're looking for:
You have hands-on experience choosing what to measure in production - not just reading dashboards, but picking signals that reflect the customer experience.
You're comfortable with incidents and alerts , from early detection through resolution and follow-up so similar issues are less likely to recur.
You have hands-on experience with Prometheus, Grafana, OpenTelemetry , or similar, and with alert-routing tools such as PagerDuty .
You read and write code: you can follow services and pipelines across the stack and collaborate on technical details with the teams building them.
You know what good post-incident culture looks like in practice - blame-free, learning-focused, and actually used to make things better - even if your past title never mentioned reliability.
You can write clear, concise guidance that teams adopt, and you work constructively toward sound decisions.
You're driven to automate repetitive tasks and improve developer workflows.
Nice to have:
Meaningful hands-on experience as an application or backend developer - you've built things that run in production and approach observability as someone who needs it as a "user," not just the person who sets it up.
Experience building and maintaining infrastructure on AWS (EC2, EKS, S3, CloudFormation, or similar), and hands-on experience with container technologies.
Some familiarity with CI/CD pipelines or release practices - enough to have an informed opinion on what makes deployments reliable and safe.
Don't worry if you don't meet all of the above criteria. We value diverse skills and experience and would love to hear from you.
Our tech stack
Infra: AWS Compute (Kubernetes (EKS), EC2, Lambda), Helm, ArgoCD, MongoDB, Redis, DynamoDB, S3, GitHub Actions
Monitoring: Grafana, Prometheus, OpenTelemetry, Mezmo, PagerDuty
Frontend: React.js, styled-components, Storybook, Chromatic, Cypress, Playwright
Requirements
The employer hasn't listed requirements separately, they're described in the role summary above and on the original listing.
Benefits
No benefits package published with this listing. Ask about it at first interview.
How to apply
- 1Check the flexibility label above, hybrid, matches where you plan to live and work.
- 2Tailor your CV to the role at Apify, mentioning your remote working experience.
- 3Apply directly on the employer's careers page using the button below. Nomaders never handles your application.
Found 1d ago. Last checked today. Always confirm the details on the original posting, salary and location can change after publication.
Listing sourced from Company boards.
Similar roles
Other open software roles with comparable remote rules.
Free to apply, no account needed.
Typically $165k–$255k · You'll be taken to the employer's careers page.