Site Reliability Engineer (SRE) 

📢

The job offer is currently closed, but if you're interested and believe you would be a good fit, we encourage you to apply. We'll keep your application in mind for future opportunities.

Engineering culture

🚀
Ship early
and often
📦
Only one project
at a time
🧪
Testing is a first
class problem
🙋🏽‍♂️
Always be
recruiting
📨
Communicate openly and frequently



Follow the Engineering Twitter account for updates

Audiense is an equal opportunity employer, and we know it's our differences that makes us great, so we want to welcome people from all backgrounds to our family. We encourage black, brown, LGBTQ+, disabled, mums and dads to apply!

During the application process, please feel free to share with us your preferred pronouns (she/her/hers, he/him/his, they/them/theirs). Please also let us know if you need any reasonable adjustments for the application, or for the interview. Thanks!

We’re looking to hire a new team member to join us on the SRE Platform Team. 



Our mission in the SRE Platform Team is to enable other teams to deliver work with substantial autonomy and help to maintain the reliability of the software services provided by the business. 

We collaborate across software engineer teams to product design, deploy and maintain resilient, reliable and secure systems. We use a variety of tools, scripting languages, and processes to develop, automate, test, monitor systems and troubleshoot issues. Additionally, we are responsible for developing and maintaining metrics to measure the health and performance of systems and developing strategies to improve system reliability, security and performance.

Our main responsibilities include, among others:

  • Empowering other teams with the autonomy to deliver their own work independently.
  • Assisting other teams in designing the architecture of the Audiense platform.
  • The ongoing maintenance of the infrastructure to ensure system performance.
  • Analyzing and managing the costs of our AWS infrastructure.
  • Designing and implementing disaster recovery plans.
  • Managing and reviewing the teams' access permissions.

Our work culture is remote-first, and we have been working 100% remotely for more than eight years. Although we have an office in Córdoba, our teams (management, sales, customer service, marketing, product and engineering) are distributed across different cities: London, Málaga, Madrid, Córdoba, Barcelona, Vigo, Sevilla, Granada, Murcia, Chieti (Italy) ... 

Our mindset, workflows and communication assume that we are all remote. Almost everything is documented in Github: growth plans, learning path, architecture, protocols, onboarding, playbooks, design system, UX guidelines, etc. We invest everything in our power in automating our daily routines to be as autonomous as possible to allow us to work remotely efficiently.

You will be joining a cohesive team, (more than four years on average together), in a very collaborative environment in which you will feel cared for from the start of your onboarding.

Each team applies different agile methodologies, but all follow some basic principles. We prioritize the features that bring the most value to our customers and, instead of setting deadlines, we deliver small increments so that we always have a functional and deliverable version of the features. Whenever possible, we try to keep the number of parallel tasks to a minimum. We have a few meetings scheduled but will not miss the daily meetings, biweekly sprint planning and reviews. We have regular 1:1s with the team leader and the CTO, and we do not hesitate to jump on to a hangout, if a Slack or mail thread is getting lengthy. 

We believe in extreme programming as a development technique, so most of the time we do pair programming (yes, remotely) and TDD is our main tool for writing robust and testable code. Pair programming always helps us trust our code allowing for constant iterations. Once per sprint, we spend time on joint code review to detect possible glitches to prioritize. We do continuous integration, and we are in the process of extinguishing the branches to do trunk base development, there is a challenge here too.

We have a culture of continuous learning, and we encourage this to happen during working hours. As a team we have made a pact to follow a learning path, so by joining Audiense, you are committing to it too. If you have followed a similar path, we are eager to get to know you and learn from your experiences, if you haven’t, we are looking forward to supporting you with resources, time and mentoring so that we are aligned.

We are moving from a culture of silos towards a more t-shaped mentality. We are not looking for a specific tech expert in all the things we use but for someone that no matter what his/her vocation is, must be versatile enough to assume the tasks that provide the most value to our customers instead of the ones that better fit their skills.

We expect you to feel aligned with these values and this way of working, but we also know that every opinion matters and would be very open to you showing us how to improve. 

You can learn more about our culture on our engineering blog and Instagram account.

What are we looking for?

The ideal candidate for this position should have a few years of experience in systems engineering. However, we emphasize the projects you have worked on and the successes you have achieved in your career rather than the time you have been in the profession. We'd like to hear more about your involvement in some projects and how you contributed to their success. We care about attitude, restlessness and happiness in our day to day.

Being a good fit is important and we would like the following:

  • We love technology, and we like to improve our platform with the most appropriate tools for each use. We need you to have a positive attitude to learn new things in an effective way.
  • Our production environment is managed according to availability and reliability standards. We need you to pay attention to details in order to maintain these standards properly.
  • We are everything in the cloud. We need you to have knowledge about cloud-based platforms, such as AWS, GCP, Azure, etc.
  • For us, infrastructure is code. We try to automate as much as possible. We need you to have some understanding of building code for infrastructure automation using Terraform, Ansible, Puppet or similar
  • We work on Linux; it is the basis of everything we use. We need you to be fluent in managing Linux systems. Also, containers and container orchestration technologies would be a bonus
  • The team works as a whole, so you must be proactive or be able to suggest solutions as well as take ideas on board.

Our stack as we develop in SRE is extensive: Python, RabbitMQ, Redis, OpenSearch, RedPanda (Kafka-like), PMM, Docker, Kubernetes, AWS (EC2, ECS, EKS, EMR, SNS, SQS, API Gateway, Lambda, Codebuild, Cloudwatch, ...), Jenkins, Icinga, Grafana, Graphite, among others. However, mastering them all, at this moment, is not a requirement. The principles behind them are more important to us.

Speaking of our data, we have a variety of MySQL clusters, Aurora MySQL, MongoDB, Solr and OpenSearch on several use cases and a lot of data volume. We are not afraid to apply the best technology to each use.

Despite being remote, we value pair programming as a fundamental practice, and in fact, I'd say that it's because we're remote that it's so important. We spend part of the week pairing, so we hope you feel comfortable with this practice. We also collaborate with other teams to remain aligned with product evolution and developmental requirements and to learn from incidents through postmortems.

We spend a lot of time and effort helping each other to keep learning, so it is very important that you are interested in learning and practicing the skills necessary to practice our profession. Practice, practice, practice!

Working remotely has many advantages but also requires extra effort when it comes to communication and responsibility. The following skills are essential: self-management, fluid communication, respect and inclusiveness.

What we offer?

Recruitment process

To apply, simply email [email protected] introducing yourself and explaining why you fit the profile we are looking for. Your CV will also be helpful, but it will not be the most important thing.

If you pass the initial filter of applications, we will contact you directly. Your first interview will be with the Head of the SRE team. It will be a simple first touch interview to ensure we are both on the same page. 

If successful in the first interview, you will have a second meeting with some of the SRE Platform Team members. In addition to discussing our work and any points that need more detail, we will propose a test to validate your skills and experience. The best way to do this is to do a pair programming session with our team to solve a simple but real problem. 

The interview will help us validate if we are on the same page, especially if you enjoy how we work, the challenge and the team. This meeting is an excellent opportunity to ask your future teammates questions directly. We will compensate you for the time you spend with us. 

If you need any reasonable adjustments for any of these meetings, we could adapt them to your needs.

Lastly, you'll have a quick chat with Alfredo Artiles, our CTO, whereby you can ask any final questions that you may have. 

If we finally convince you to join our team, this will be the ideal onboarding process:

  • Over the first few days, you will be assigned an onboarding buddy, who will help you set up your computer as needed and mentor you for the following months. He will explain all the workflows we have become familiar with, and I hope you will too.
  • From day one, you will become a part of the team working mainly in pairs: taking part in the production environment maintenance, solving tasks from the current sprint, making changes to the cloud environment and developing new tools to assist other teams.
  • After a few months, you will join the on-duty call alert process assisted by other team members and deal with support requests from other teams.
  • As our development flow is adapted to pair programming, your contribution will be very progressive, and you will always have someone to revert to with any questions you may have.

About Audiense

The Company

At Audiense, we help marketers and consumer researchers by identifying relevant audiences, discovering amazing actionable insights, and informing their strategies to grow their business.

Our software enables our customers to analyze and understand their target audience, identify particular individuals that influence their behavior, and make better marketing decisions.



We want everyone to be able to identify and understand any audience, no matter how specific or unique it is, to conduct social audience analysis.

Our Proposal

Audiense is an audience intelligence platform that combines rich social data sources with the world’s leading cognitive and machine learning to provide social consumer segmentation and cultural insights. It enables you to understand the audiences that matter to your business better, as well as fueling a variety of use cases, including buyer personas, social listening, influencer marketing, or advertising.

We help marketers, and consumer researchers identify relevant audiences, provide actionable insights and inform their strategies for growing their businesses.

Share this job offer