Senior Software Engineer

About the role

This role operates within the Ludios studio, a team focused on creating and publishing casual, free-to-play mobile games. You will apply strong C# engineering to solve architecture and performance challenges in a mobile gaming context, extending expertise into Unity and game systems.

Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.

Key facts

What you'll do

Reusable C# components are designed, built, and maintained to power application frameworks and core game mechanics for product and player audiences. Memory performance is optimized through dedicated resource handling and collection behavior to ensure smooth execution across diverse mobile hardware. Integration with backend APIs, local data storage, and real-time multiplayer networking is coordinated with cross-functional teams to scale solutions for millions of daily active users. Existing C# skills are converted into high-performance game engineering through dedicated mentorship, supporting live game operations in Unity.

Requirements

Around 5 years of professional C# experience with .NET frameworks is required, demonstrating maintainable code in production environments. Deep computer science fundamentals are required, including object-oriented programming, SOLID principles, data structures, algorithms, and design patterns. Experience with profiling tools, diagnosing memory leaks, handling concurrency, and reducing garbage collection overhead in mobile contexts must be shown. Curiosity and adaptability are required to learn a new industry and apply technical skills to interactive media and mobile applications. Effective English communication skills are required to collaborate with global stakeholders and align with distributed teams.

Practical notes

Work is hybrid, with office days Monday through Thursday and the option to work remotely on Friday, alongside 20 days of remote work per year from anywhere. Role may be subject to local regulations and requires a degree. Typical interview steps

Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.

Good to know

The role focuses on backend and systems programming in a games context, using C# and Unity. Team workflows are data-driven and centered on mobile free-to-play products. Engineers use profiling and performance optimization tools on a regular basis. The environment emphasizes rapid learning, clean architecture, and collaboration across distributed studios.

Questions to ask

Worth asking in any interview: how the team measures success, who the role works with daily, what the onboarding looks like, and what the company is trying to achieve this year. Asking what past hires did well is a strong final question. Keep the list short and pick the questions that matter most to you.

Career growth

Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.