At JetBrains, code is our passion. Ever since we started back in 2000, we have been striving to make the strongest, most effective developer tools on earth. By automating routine checks and corrections, our tools speed up production, freeing developers to grow, discover, and create.

The Data Office department is responsible for the data associated with products, AI tools, marketing, financials, sales, and all other domains at JetBrains. Our department provides up-to-date, transparent, and reliable data, as well as data services.

As part of our exciting growth strategy, we are seeking an experienced, detail-focused, and self-motivated DevOps Engineer to drive solutions that help teams be more independent, reducing the need for constant DevOps intervention while keeping systems reliable, scalable, and secure. As a DevOps engineer on our team, you will be responsible for services required to process and manage data inside JetBrains.

Our technological stack includes:

Cloud providers: AWS is our primary cloud provider. The most commonly used services include, but are not limited to, S3, Glue, API Gateway, Kinesis, EMR, RDS, and IAM. In addition to these, we also occasionally use GCP.
Containerization: We currently use ECS, with a plan to migrate to Kubernetes in the near future. All new tools in the stack are deployed on top of Kubernetes.
Monitoring and logging: Prometheus is our choice for monitoring, paired with Grafana and related tools like Loki and Grafana Dashboards.
Databases: Our main database engine is Postgres, but we also work with MySQL and MS SQL where needed.
Distributed data processing: We use Spark and ClickHouse.
Infrastructure as code: We prefer an infrastructure-as-code approach and use Terraform for managing infrastructure.
Languages: Most of our infrastructure code is written in Python, Go, or Bash, but due to the department’s specific context, it’s useful to be able to read Kotlin, Java, or Scala.
CI/CD: Our CI/CD pipelines are mostly handled by JetBrains TeamCity, but we have plans to migrate part of the workloads to GitHub and GitHub Actions. As part of the Kubernetes migration, we have also introduced Argo CD.

We will be happy to have you on our team if you:

Are a great communicator who can work with engineers, product teams, and management.
Can adapt to different audiences and know how to explain things differently depending on whether you're speaking to junior or staff-level engineers.
Are able to drive initiative and align stakeholders, pushing for best practices among both junior and senior colleagues.
Understand people and are aware of personal differences, with the ability to provide and receive feedback effectively.
Are comfortable with competing priorities and able to work across multiple teams with different needs.
Are a systemic thinker who can see the bigger picture and understand how changes impact architecture long term.

What technical skills we are looking for:

Automation and coding: Strong scripting and programming skills (Python, Go, and Shell preferred). Experience with Java, Kotlin, and Scala would be a nice bonus.
Distributed data processing: Experience with Spark, Hadoop, or Trino, or their cloud counterparts like Glue, Athena, or BigQuery.
High-scale databases: Experience with ClickHouse would be desirable.
Remaining data stack: Experience with database management systems, streaming engines (Kafka, Kinesis Firehose, and Dataflow), orchestrators (Airflow and Dagster) would be beneficial.
GitOps and CI/CD: Familiarity with modern deployment pipelines and continuous integration practices.
Infrastructure as code or configuration management: Experience with Terraform, Pulumi, Ansible, Chef, or similar tools.
Cloud expertise: Experience with AWS or GCP preferred.
Security: Security-first mindset, experience with hardening cloud infrastructure, and an understanding of web application security concepts and WAF.
Containerization: Hands-on experience with Docker, ECS, or Kubernetes.
Troubleshooting: Strong debugging and problem-solving skills across infrastructure and services.
IdP: Familiarity with IdP solutions, like Okta or Google Workspaces, as well as an understanding of the concepts surrounding it would be desirable.

How we work:

Iterate, don’t overengineer: Focus on practical solutions rather than unnecessary complexity.
Automate where possible: Think in terms of "how do I never have to do this again?"
Take ownership: If something breaks, don’t just point fingers – fix it. Our general rule is to leave things in a better state than you found them in.
Be proactive, not reactive: Identify and solve issues before they become problems.
We have a bias toward action: It’s better to try and fail than to do nothing.
Be honest and open: If something goes wrong on the infrastructure side, own it and fix it.
Take a rotational approach: We believe in reducing the bus factor and building a well-balanced team. That means you won’t just be working on what you know best – you’ll rotate across different tasks and skill sets. One day, you might be improving CI/CD pipelines; the next, troubleshooting cloud infrastructure or optimizing Kubernetes clusters. This encourages growth, keeps work interesting, and ensures no single person becomes a bottleneck.