As a Software Engineer at Outfit7, you are at the heart of one of the world’s most recognizable mobile gaming companies. Your work directly impacts the experiences of millions of users globally, as you contribute to the development and optimization of the iconic Talking Tom and Friends universe. This role is not just about writing code; it is about engineering high-performance, scalable solutions that power engaging, fun, and technically sophisticated mobile entertainment. You will work in a fast-paced, collaborative environment where technical excellence meets creative problem-solving. Whether you are optimizing game engines, developing backend infrastructure, or implementing new gameplay features, your contributions will directly influence product stability and user retention. We value engineers who are passionate about gaming, curious about emerging technologies, and capable of balancing rapid iteration with long-term code quality. ##### Tip Being a gamer or having a genuine interest in the mobile gaming industry is highly regarded during the interview process. Be ready to discuss your favorite titles and why they succeed from a technical and design perspective.
Initial Screening
reportedThe first step involves a review of the candidate's application and background.
What to demonstrate
- The first step involves a review of the candidate's application and background
- Depth in Debugging / finding bugs
How to prepare
- Be able to walk your CV end to end in two minutes, and say why this company specifically.
- Have your salary expectations, notice period and location constraints ready, and ask for the rest of the loop in writing.
Technical Assessment
reportedCandidates will demonstrate their core engineering skills through a technical assignment.
What to demonstrate
- Candidates will demonstrate their core engineering skills through a technical assignment
- Depth in Debugging / finding bugs
How to prepare
- Answer aloud and timed: How would you optimize a rendering loop for a mobile device with limited hardware resources?
- Answer aloud and timed: Describe a situation where you had to debug a complex performance issue. What was your process?
HR Interview
reportedAn interview with HR to assess interpersonal maturity and cultural fit.
What to demonstrate
- An interview with HR to assess interpersonal maturity and cultural fit
- Depth in Debugging / finding bugs
How to prepare
- Answer aloud and timed: What are the most critical factors to consider when scaling a backend service for a high-traffic game?
- Answer aloud and timed: Given a simple class with functions, how would you refactor it to improve readability and performance?
Leadership Interview
reportedOccasional engagement with leadership to evaluate long-term potential within the company.
What to demonstrate
- Occasional engagement with leadership to evaluate long-term potential within the company
- Depth in Debugging / finding bugs
How to prepare
- Answer aloud and timed: How do you approach finding bugs in a pre-existing, unfamiliar codebase?
- Answer aloud and timed: Explain your thought process when you encounter a technical requirement that seems impossible to implement within the deadline.
PracHub editorial advice for the preparation topics above.
Review your assignment code
If you submit a take-home task, be prepared to defend every decision you made, including why you chose certain data structures or patterns.
Be curious
Ask questions about the team’s current challenges and the tech stack. It shows you are already thinking like a team member.
Communicate your thought process
During live technical sessions, do not code in silence. Explaining your logic allows the interviewer to provide guidance and see how you handle feedback.
Research our games
Have a clear opinion on our current titles. Understanding the "user" side of our products makes you a much more compelling candidate.
Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.
What are the key differences between memory management in C++ and managed languages?
What are the key differences between memory management in C++ and managed languages?
Approach
- Say what the runtime actually does before reasoning about the code.
- Name what is shared across threads and what owns each piece of state.
- Identify the window where an invariant is briefly untrue.
- Distinguish a value from a reference to it, and say which one you handed out.
Follow-up
- What happens if two callers reach this at the same time?
- Where could this allocate more than you expect?
Given a simple class with functions, how would you refactor it to improve readability and performance?
Given a simple class with functions, how would you refactor it to improve readability and performance?
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
How do you approach finding bugs in a pre-existing, unfamiliar codebase?
How do you approach finding bugs in a pre-existing, unfamiliar codebase?
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
Explain your thought process when you encounter a technical requirement that seems impossible to implement wit
Explain your thought process when you encounter a technical requirement that seems impossible to implement within the deadline.
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
Can you explain the logic behind your solution for the take-home assignment?
Can you explain the logic behind your solution for the take-home assignment?
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
Stop tag and share joins from fanning out a page
resource_tag is (resource_id, tag_id) with PK (resource_id, tag_id); resource_share is (resource_id, shared_with_user_id, permission). The tagged-and-shared listing inner-joins resource to both, filters tenant_id, tag_id = ANY($2) and shared_with_user_id = $3, orders by updated_at DESC and takes 50. Pages come back with fewer than 50 distinct resources and the total in the header is far too high. Explain the row multiplication, rewrite both the page query and the count query so each is correct, and name the index each one needs. PostgreSQL 16.
Approach
- Do the arithmetic against the predicates that are actually there. An inner join emits one row per matching child row, and both joins are filtered: tag_id = ANY($2) admits only the requested tags, shared_with_user_id = $3 admits one user's share rows. So a resource holding three of the requested tags and shared with $3 once yields three rows, not one — the multiplier is its count of matching tags times its share rows for that single user, and that second factor is 1 unless the table admits duplicate (resource_id, shared_with_user_id) pairs. LIMIT 50 then limits rows rather than resources, and COUNT(*) counts pairs — the header is the product, not the population.
- Reject DISTINCT as the fix. It deduplicates after the product has been built, so the planner must materialise and sort the fanned-out set before the LIMIT can apply, and it leaves any SUM or AVG in the same select list wrong.
- Rewrite both filters as semi-joins, keeping resource as the only row source: AND EXISTS (SELECT 1 FROM resource_tag rt WHERE rt.resource_id = r.resource_id AND rt.tag_id = ANY($2)) and the same shape against resource_share. A semi-join stops at the first match per resource and preserves the driving index order, so ORDER BY updated_at DESC, resource_id DESC LIMIT 50 still stops after 50 rows.
- Count with the same predicates and no join at all: SELECT count(*) FROM resource r WHERE r.tenant_id = $1 AND r.status = 'active' AND EXISTS (...) AND EXISTS (...). Nothing multiplies a resource, so the number is the population.
Follow-up
- The filter changes from 'any of these tags' to 'all of these tags'. Rewrite it and state what it costs relative to the ANY form.
- A resource can be shared with the same user twice under different permissions. Does your count change, and should it?
Replace offset paging on the resource feed with keyset
resource holds resource_id, tenant_id, owner_user_id, title, body_ref, version, status ('draft','active','archived','deleted'), created_at, updated_at, deleted_at, with an index on (tenant_id, status, updated_at DESC, resource_id DESC). The listing endpoint returns active resources for one tenant, newest update first, 50 per page, today with LIMIT 50 OFFSET n. Tenants reach page 400 and rows are created while they read. Write the keyset query, define what the cursor carries and how it is encoded, and say which part of the index each predicate uses. Assume PostgreSQL 16.
Approach
- Name the two failures separately. OFFSET 20000 makes the server produce and discard 20,000 rows, so page cost grows with depth rather than with page size. Independently, any write that changes how many rows sort above the offset moves the window between two fetches, and the direction decides which anomaly you get: an insert lands at the head of updated_at DESC and pushes already-returned rows down past the boundary, so they are returned a second time; a delete above the offset, or a row whose updated_at is bumped above the cursor, pulls rows up and one is never returned at all. Nothing in the response reveals either.
- Write the seek: WHERE tenant_id = $1 AND status = 'active' AND (updated_at, resource_id) < ($2, $3) ORDER BY updated_at DESC, resource_id DESC LIMIT 50. The row-value comparison is one index range rather than a disjunction, and both columns are NOT NULL, which is what makes that comparison well defined.
- Map each predicate onto the index: tenant_id and status are equality on the leading columns, (updated_at, resource_id) is the range, and the ORDER BY matches the index order so no Sort node appears and the scan stops after 50 rows. The DESC in the definition only matters for mixed directions — a plain ascending btree on the same columns is read backwards for this query.
- Put both sort columns in the cursor and nothing the client can tamper with into another tenant: base64 of (updated_at, resource_id), validated server-side, with tenant_id taken from the principal.
Follow-up
- The client asks for 'jump to page 400'. What do you offer instead, and what does the honest version cost?
- Sort order becomes user-selectable across four columns. How many indexes is that, and which would you refuse to add?
Can you explain the pros and cons of using specific design patterns in a game engine context?
Can you explain the pros and cons of using specific design patterns in a game engine context?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
How would you optimize a rendering loop for a mobile device with limited hardware resources?
How would you optimize a rendering loop for a mobile device with limited hardware resources?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
What are the most critical factors to consider when scaling a backend service for a high-traffic game?
What are the most critical factors to consider when scaling a backend service for a high-traffic game?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
How do you ensure your code remains testable and scalable as a project grows?
How do you ensure your code remains testable and scalable as a project grows?
Approach
- Fix the scope first: who calls this, how often, and what they do when it fails.
- Name the read and write paths separately; they rarely have the same bottleneck.
- Choose a partition key and say what query it makes expensive.
- State the consistency you need, and where you are willing to be stale.
Follow-up
- What breaks first when traffic grows ten times?
- How does this behave when that dependency is down for an hour?
Describe a situation where you had to debug a complex performance issue. What was your process?
Describe a situation where you had to debug a complex performance issue. What was your process?
Approach
- Establish what changed and when, before forming any theory.
- Pick a bisection that eliminates candidates whichever way it turns out.
- Check the instrumentation before believing the symptom.
- Separate the trigger from the cause; the deploy is rarely the bug.
Follow-up
- What would you look at first, and what would it rule out?
- How would you tell a cause from a coincidence here?
Built from the rounds and topics Outfit7 candidates report.
Prepare, practise & reflect
One practical outcome each day. Spend longer where you need it.
0 / 7 done01Map the Outfit7 loop
- Write out the reported sequence: Initial Screening, Technical Assessment, HR Interview, Leadership Interview.
- For each round, write one sentence on what it is judging, from the description above, and mark the one you are least ready for.
Deliverable: A one-page map of the 4 reported rounds, with the weakest marked.
02Work Debugging / finding bugs
- Spend the session on Debugging / finding bugs, which Outfit7 candidates report being tested on.
- Write one worked example in Debugging / finding bugs and time yourself on it.
Deliverable: One timed worked example in Debugging / finding bugs.
03Work C++
- Spend the session on C++, which Outfit7 candidates report being tested on.
- Write one worked example in C++ and time yourself on it.
Deliverable: One timed worked example in C++.
04Work Take-home assignments
- Spend the session on Take-home assignments, which Outfit7 candidates report being tested on.
- Write one worked example in Take-home assignments and time yourself on it.
Deliverable: One timed worked example in Take-home assignments.
05Answer out loud: Technical and Domain Knowledge
- Answer aloud, timed: What are the key differences between memory management in C++ and managed languages?
- Answer aloud, timed: Can you explain the pros and cons of using specific design patterns in a game engine context?
Deliverable: Spoken answers to 2 reported Technical and Domain Knowledge question(s), under time.
06Answer out loud: Problem-Solving and Coding
- Answer aloud, timed: Given a simple class with functions, how would you refactor it to improve readability and performance?
- Answer aloud, timed: How do you approach finding bugs in a pre-existing, unfamiliar codebase?
Deliverable: Spoken answers to 2 reported Problem-Solving and Coding question(s), under time.
07Answer out loud: Behavioral and Culture Fit
- Answer aloud, timed: Describe a time you had a conflict with a team member. How did you resolve it?
- Answer aloud, timed: Why do you want to work for Outfit7 specifically, rather than another tech company?
Deliverable: Spoken answers to 2 reported Behavioral and Culture Fit question(s), under time.
Expand any day for tasks and deliverables. Your progress is saved on this device.
Behavioural rounds judge the decision you made and what it cost.
Describe a time you had a conflict with a team member. How did you resolve it?
Describe a time you had a conflict with a team member. How did you resolve it?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
Why do you want to work for Outfit7 specifically, rather than another tech company?
Why do you want to work for Outfit7 specifically, rather than another tech company?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
Tell us about a project you are particularly proud of and your specific role in its success.
Tell us about a project you are particularly proud of and your specific role in its success.
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
How do you handle constructive criticism regarding your code or technical designs?
How do you handle constructive criticism regarding your code or technical designs?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
What is your preferred way of staying updated with the latest advancements in software engineering?
What is your preferred way of staying updated with the latest advancements in software engineering?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
- 01
Describe a time you had a conflict with a team member. How did you resolve it?
- 02
Why do you want to work for Outfit7 specifically, rather than another tech company?
- 03
Tell us about a project you are particularly proud of and your specific role in its success.
- 04
How do you handle constructive criticism regarding your code or technical designs?
How difficult are the technical assignments?
The assignments are designed to be practical. They are not intended to be "trick" questions; rather, they are opportunities to show how you structure your code and solve real-world game development problems.
Outfit7 Software Engineer candidate reports ↗What is the significance of the HR and leadership interviews?
These stages are vital for assessing culture fit. We want to ensure that you will be a positive, collaborative addition to our team and that you align with the long-term vision of Outfit7.
Outfit7 Software Engineer candidate reports ↗How long does the process take?
The process typically spans 1 to 2 months. We value thoroughness, so please be prepared for a multi-stage process that includes internal reviews after each step.
Outfit7 Software Engineer candidate reports ↗Is there a possibility to work remotely?
Our policies regarding remote and hybrid work vary by location and team. We encourage you to discuss this during your initial screening to get the most accurate information for your specific branch.
Outfit7 Software Engineer candidate reports ↗What topics does Outfit7 test in interviews?
Outfit7 interviews most often cover Data Science, SQL, Bug reporting, UI/UX Design Test Tasks, and Debugging / finding bugs. The exact emphasis depends on the specific role you apply for.
Outfit7 Software Engineer candidate reports ↗Sources & methodology 3 sources ↗
No official company page is cited. Rounds and questions come from candidate reports and PracHub editorial material; each source shows the date it was read.
- 01Outfit7 Software Engineer candidate reports ↗
Company-reported rounds, questions and FAQ.
Candidate reports · Accessed 2026-09-22 - 02PracHub Software Engineer practice ↗
PracHub practice material, not company-reported.
PracHub page · Accessed 2026-09-22 - 03PracHub preparation framework ↗
PracHub preparation guidance.
PracHub page · Accessed 2026-09-22
Explore related engineering environments and compare the preparation focus.
Discord Software Engineer Interview Guide
Database practice for Discord candidates: how an index changes a query plan, and which anomalies survive a given isolation level, since read committed still permits non-repeatable reads.
Zebra Technologies Software Engineer Interview Guide
What Zebra Technologies asks Software Engineer candidates, from reported rounds and questions.
Viasat Software Engineer Interview Guide
What Viasat asks Software Engineer candidates, from reported rounds and questions.
Verily Software Engineer Interview Guide
What Verily asks Software Engineer candidates, from reported rounds and questions.