Site Reliability Engineer
First seen by Alion on Nov 2, 2026.
Site Reliability Engineer (14:00–22:00 CET)
Communications Service Providers (CSP) are the biggest, most important clients of AVSystem. We build, test, launch and operate systems for our telco customers and make a living by keeping them relevant, reliable and remarkable.
Our products (UMP, CEM, BSAP and DHCP) manage hundreds of millions of devices in 100+ large deployments worldwide, for operators like T-Mobile, Play and Vodafone, also through our cloud offering. The SRE team runs them on Kubernetes in GCP and AWS, on bare metal and VMs in operators' data centres, and in air-gapped on-prem environments. Every operator brings its own customizations, and years of per-operator projects left debt in our tooling, processes and infrastructure. You'll spend part of your time untangling and simplifying it, which takes discipline.
Running the commands was never the hard part of this job. Deciding which ones to run was, and owning the result: whether a change is safe on an operator's network, what to fix first when two customers call at once, and when a workaround can wait until morning. We are looking for an engineer who takes those decisions and carries them, with whatever tools write the scripts this year.
Your hours
This role works a fixed afternoon schedule: 14:00–22:00 CET, Monday to Friday, so our operators in the US and Latin America have an SRE inside their working day, and planned work that fits these hours goes to you, whichever time zone the operator is in. Those hours are your normal working time, not overtime. You'll spend your first weeks in daytime hours next to the team, then move to the afternoon schedule. Each day starts with a handover from the daytime team and ends with a written note for the morning.
Requirements
A few years running production Linux systems as an SRE, DevOps engineer or sysadmin, with solid Linux (Ubuntu, RHEL) and networking (TCP/IP, DNS, TLS, routing) fundamentals: from a shell, you can tell what a host is doing and why.
Python or Go good enough to write automation your teammates can read, test and maintain. Bash for the small things.
Working knowledge of Kubernetes, at least one public cloud (GCP, AWS or Azure), and Ansible or Terraform.
Hands-on monitoring, alerting and logging work with the Prometheus stack and Loki, which we run, or with Zabbix, Splunk or ELK.
Daily, hands-on use of coding agents (we run Claude Code), the judgment to tell when their output is wrong, and the habit of not running in production what you could not explain to a colleague.
Fluent spoken English (you will often run calls with our customers' teams on your own, native speakers included) and proficiency in Polish.
A huge plus if you have
Set up and run MongoDB, Redis or Kafka.
Tuned or debugged JVM applications and distributed systems.
Supported customers in another time zone, or worked shifts.
Readiness to travel to our customers in the US from time to time.
Not for you if
you need your weekday evenings free.
you think customer calls are someone else's job.
your first move on a slow service is a restart, not a graph.
you would rather repeat a manual task than automate it.
you want every runbook written before you touch a system.
Responsibilities
Own problems end to end: frame them, choose the approach, direct agents and teammates through the implementation, verify the result, and run it in production.
Learn the telco domain on purpose: how an operator runs its access network, what our products do in it, and what a failed rollout costs the operator.
Work with our US and Latin American customers during their day, from calls and troubleshooting with their engineers to resolving production issues, and run any operator's planned work (upgrades, migrations, configuration changes) that fits your hours.
Build and maintain automation that removes toil from the team's week.
Find and fix performance and reliability problems, including in our product code, and lead the blameless postmortems that keep them from coming back.
Improve our observability stack (Prometheus, Loki, Grafana) and the Service Level Indicators the team watches.
Work with development teams on feature design, so they ship features we can operate.
After onboarding, join our additionally paid 24/7 on-call rotation.
How we hire
A call with our recruiter, partly in English, with a few short technical questions.
Three technical conversations with the SRE team, online: Linux troubleshooting on a live VM, a short Python exercise, and system design.
A conversation with the team's manager.
We send the meeting link and the format of each stage before every interview. Take a break whenever you need one.
What we offer
Remote work from anywhere in Poland, with occasional visits to our Kraków office.
Our goal is to inspire people more than manage them. We want our teams to do what is best for our products. This, in turn, generates a sense of responsibility which drives us to do great work.
A dream team is one in which all of your colleagues are extraordinary at what they do and highly effective working together. We model ourselves on a professional sports team, not a family. A family is about unconditional love. A dream team is about pushing yourself to be the best possible teammate. Dream teams are about performance, not seniority or tenure.
Our customers depend on the reliability of our products to generate revenue in their business. The telco industry is ever-growing and needs us to support that growth.
Open-source contribution opportunities.
A team of highly skilled and humorous colleagues.
Access to the best tools and equipment available in the market.
A Claude Code Premium seat from day one and the model access the work needs. We don't ration tokens; we look at what shipped.
A MacBook Pro / ThinkPad with 2 monitors.
Company events and team building activities.
Multiple career paths and employee development options – we want you to develop into a tech lead in the future, but we’ll support you in getting another dream role in site reliability, management, product development or sales.
Training and conferences.
Onsite gym and chillout space.
Multisport card.
Medical care.
Kitchen full of snacks and treats (including Good Lood ice cream).
Car parking area and bike room.
A relaxed work atmosphere – no dress code, no open space.
Tech stack
- Linux
- Networking
- Python
- Go
- Kubernetes
- Ansible
- Terraform
- Prometheus
- MongoDB
- Kafka