Suggested rewrite: Led a cross-functional initiative that improved [business outcome] by [measurable result], demonstrating experience relevant to this role...
Senior Backend Engineer
- Remote from
- Europe
- Salary
- EUR 50k–75k / yr
- Department
- Software Engineering
- Employment
- Full Time
- Experience
- Senior
- Published
- Apply before
- 12 Dec 2026
- Listing views
- 21
- Application actions
- 1
Make your next move.
Prepare your resume, explore your fit, and draft a cover letter for this opportunity.
About this role.
Hey there!
We’re Fever, the world’s leading tech platform for culture and live entertainment.
Our mission? To democratize access to culture and entertainment. With our proprietary cutting-edge technology and data-driven approach, we’re revolutionizing the way people engage with live entertainment.
Every month, our platform inspires over 300 million people in +55 countries (and counting) to discover unforgettable experiences while also empowering event creators with our data and technology, helping them scale, innovate, and enhance their events to reach new audiences.
Our results? We’ve teamed up with major industry leaders like Netflix, F.C. Barcelona, and Primavera Sound, presented international award-winning experiences, and are backed by several leading global investors! Impressive, right?
To achieve our mission, we are looking for bar-raisers with a hands-on mindset who are eager to help shape the future of entertainment!
Ready to be part of the experience?
Now, let’s discuss this role and what you will do to help achieve Fever’s mission.
Behind the user-friendly iOS and Android apps and webpage that work across the world is the engineering team. We are in charge of creating, developing, improving, and maintaining all Fever services so that more people can have an amazing experience.
About the role
Location: Spain – 100% Home office friendly
What are we looking for:
We are looking for a Senior Software Engineer to join the Engineering team with outstanding software development talent proven by great work results/experience. Somebody who cares about code quality and not just getting things done, but getting things done right.
If you’re smart, have great energy, can’t think about a system without a CI/CD pipeline, and you want to thrive in a fast-paced environment, we are in sync.
What would you do at Fever?
During your first month at Fever (Onboarding period):
- You’ll join a structured onboarding program designed to help you ramp up smoothly. During this period, you will:
- Meet your buddy and team, and get to know Fever’s culture and ways of working.
- Set up your local environment and become familiar with our Python-based stack, CI/CD pipelines, and cloud infrastructure.
- Learn about our architecture and observability tools while contributing small improvements and fixes.
- Have your first code running in production and a clear understanding of our delivery flow and processes.
- By the end of the onboarding, you’ll be ready to join your long-term squad and start contributing to larger initiatives.
After 3 months at Fever:
- You’ll be confidently collaborating and delivering at full speed. You will:
- Design and implement end-to-end features within your squad.
- Participate in architectural discussions and propose improvements across our services and APIs.
- Work with event-driven systems and focus on performance, reliability, and scalability.
- Collaborate closely with Product, Data, and other Engineering teams to enhance our platform and developer experience.
By your 6th month at Fever:
- You’ll be fully established as a key contributor in your team. You will:
- Take ownership of core components and help evolve their architecture.
- Lead by example through code reviews, design sessions, and mentoring.
- Contribute to best practices in areas like scalability, observability, and system design.
- Drive continuous improvement and have a visible impact on how we build high-performing services at scale.
- Become an expert in your domain, using business context and technical excellence to drive strategic initiatives forward
About you
Must have skills:
- Strong knowledge of best practices, testing, and design patterns
- You are proficient in business English
- You know how to deliver code from development to production
- Experience with RESTful APIs (implementation and consumption)
- Knowledge of relational databases and SQL
- Experience with event streaming platforms such as Kafka or RabbitMQ
- Handling services with high concurrencies and high volume requests.
We use these technologies, so it would be a plus if you have experience in:
- Django/Flask
- PostgreSQL and Redis
- AWS, Docker, and Kubernetes
Benefits & Perks
- 23 days of vacation plus half a day on your birthday
- Private medical insurance sponsored by the company
- 40% discount on Fever Marketplace
- Flexibility to work from home
- English & Spanish conversational classes
- Wellhub (former Gympass) membership
- Possibility to receive part of your salary in advance with Payflow
- Flexible remuneration with Cobee
- Budget for engineering events and trainings
- Young and international environment
- Attractive compensation package consisting of base salary and the potential to earn a significant bonus for top performance.
- Base Salary: 50K – 75K EUR
- Total Compensation: 67K – 90K EUR (Including Base, Variable, and Stock Options)
About the process
Fever aims to provide the best and fastest possible experience to our candidates. This is how it would look like:
- Talent Interview – 1h: An intro to Fever, our culture and a conversation about your background and experience.
- Technical Interview – 2h: A deep dive into your technical expertise through a system design discussion and a short coding exercise, giving you the chance to walk us through your reasoning and problem-solving approach — and ask us anything about your day-to-day at Fever.
- Manager Interview – 1.5h: A conversation about how you communicate context and trade-offs, own outcomes, quantify impact, and think about reliability, scale, and system design decisions.
Thank you for considering joining Fever. We cannot wait to learn more about you!
If you want to learn more about us: Fever’s Blog | Tech.Eu |TechCrunch
Fever is committed to creating an inclusive and diverse workspace where everyone’s background and ideas count. Our main goal is to find the best possible talent regardless of place of birth, racial or ethnic origin, gender, gender identity, religion, opinion, sexual orientation, disability, pregnancy, marital status, age or caring responsibilities. We encourage everyone to apply!
If you require any kind of accommodation during the selection process please contact our Talent team so we can help you by providing a welcoming and seamless journey.
If you want to know more about how Fever processes your personal data, click here Fever – Candidate Privacy Notice
This job listing has been manually reviewed by the Jobicy Trust & Safety Team for compliance with our posting guidelines, including verification of the company's legitimacy, accuracy of job details, clarity of remote work policy, and absence of misleading or fraudulent content.
Role DNA
A quick view of the complexity, pace, ownership and collaboration implied by the job description.
Pace & Pressure
5/5Autonomy Level
4/5Communication Load
4/5Salary analysis
Estimated compensation compared with the broader EU market for similar roles.
Core skills
Skills and capabilities most closely associated with this opportunity.
Sample interview questions
I would begin by defining traffic patterns, latency targets, consistency requirements, and failure modes. I would keep services stateless where possible, use horizontal scaling and caching appropriately, optimize database access, and introduce asynchronous processing for non-blocking workloads. I would also add load testing, observability, rate limiting, and capacity planning before production rollout.
I would design consumers to be idempotent, use durable message handling, and define retry and dead-letter-queue strategies. I would monitor consumer lag, processing failures, and duplicate delivery while ensuring messages carry enough context for safe replay. For critical workflows, I would use transactional or outbox-style patterns to reduce inconsistencies between database writes and event publication.
I rely on clear design boundaries, automated unit and integration tests, static analysis, meaningful code reviews, and reliable CI/CD checks. I prefer small, observable releases with feature flags when risk is high. I also document important architectural decisions and use production feedback to improve testing and operational practices.
I would first confirm the regression through metrics and compare the affected release with prior behavior. I would inspect latency percentiles, error rates, database query performance, cache hit rates, infrastructure utilization, and distributed traces to identify the bottleneck. After validating a hypothesis, I would implement and measure a targeted fix, then add monitoring or tests to prevent recurrence.
I translate options into user impact, delivery time, operational risk, cost, and long-term maintainability. I present a concise recommendation, explain what assumptions it depends on, and make uncertainties explicit. This helps stakeholders make informed decisions without requiring them to absorb unnecessary implementation detail.
Apply now.
Follow the employer’s application method and review Jobicy’s safety guidance before sharing personal information.
Continue on the employer website
Protect your personal information and never pay to secure an interview or job offer. .
