As a Software Engineer at AppsFlyer, you are at the core of a global platform that processes billions of events daily. Your work directly impacts how the world’s largest brands measure, optimize, and protect their marketing investments. You will contribute to a high-scale, distributed environment where performance, reliability, and data integrity are not just requirements—they are the product itself. The role involves tackling complex engineering challenges, ranging from real-time data ingestion and processing to building robust APIs and SDKs that developers worldwide rely on. You will collaborate with cross-functional teams to translate business needs into scalable technical solutions, ensuring that AppsFlyer maintains its market-leading position. It is a fast-paced environment that demands both deep technical rigor and the agility to adapt to evolving industry standards. ##### Tip The engineering team at AppsFlyer values "doers" who are comfortable with ambiguity. Be prepared to discuss not just how you write code, but how you design systems for scale and how you troubleshoot under pressure.
Recruiter Screen
reportedInitial screening call with a recruiter to discuss the candidate's background and fit for the role.
What to demonstrate
- Initial screening call with a recruiter to discuss the candidate's background and fit for the role
- Depth in System design
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 Deep Dives
reportedA series of technical interviews focusing on algorithmic coding, system design, and behavioral discussions.
What to demonstrate
- A series of technical interviews focusing on algorithmic coding, system design, and behavioral discussions
- Depth in System design
How to prepare
- Answer aloud and timed: Write a function to process a large file using an HashMap.
- Answer aloud and timed: Solve a medium-level LeetCode style problem (e.g., hash-based questions, graph traversal using Dijkstra).
Behavioral Discussions
reportedInterviews with peers and leadership to assess cultural fit and behavioral competencies.
What to demonstrate
- Interviews with peers and leadership to assess cultural fit and behavioral competencies
- Depth in System design
How to prepare
- Prepare three examples from your own work, each with a decision you made and an outcome you can quantify.
- Re-read the description of the behavioral discussions above and write down what you would ask to confirm before it.
Final Decision
reportedFinal interviews and discussions leading to a decision on the candidate's application.
What to demonstrate
- Final interviews and discussions leading to a decision on the candidate's application
- Depth in System design
How to prepare
- Answer aloud and timed: Design a game like Damka (checkers) from an architectural perspective.
- Answer aloud and timed: How do you handle distributed systems and large-scale data challenges?
PracHub editorial advice for the preparation topics above.
Think out loud
Interviewers at AppsFlyer want to see your thought process. Even if you aren't sure of the final answer, explaining your logic is vital for a positive evaluation.
Prepare your own questions
Use the end of the interview to ask about the team’s current technical challenges or the company’s roadmap. This shows genuine interest and engagement.
Know your CV
Be prepared to dive deep into every project mentioned on your resume. You should be able to explain the "why" behind every technical choice you made.
Be honest about your limits
If you don't know an answer, it is better to admit it and explain how you would go about finding the solution rather than guessing.
Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.
Implement an LRU Cache from scratch.
Implement an LRU Cache from scratch.
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?
Write a function to process a large file using an HashMap.
Write a function to process a large file using an HashMap.
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?
Solve a medium-level LeetCode style problem (e.g., hash-based questions, graph traversal using Dijkstra).
Solve a medium-level LeetCode style problem (e.g., hash-based questions, graph traversal using Dijkstra).
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 would you handle race conditions in a React application?
How would you handle race conditions in a React application?
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?
Denormalise tenant onto revisions and backfill it live
resource_revision (revision_id, resource_id, version, actor_user_id, change_kind, patch, request_id, created_at) has 400M rows and no tenant column; tenant_id lives only on resource. Two reads need it: a tenant-scoped audit feed ordered by created_at DESC, and an offboarding purge. Both join back to resource today. Justify adding tenant_id to resource_revision against those two reads, name the anomaly the copy introduces and the constraint that prevents it, then give the ordered migration for a live table taking 1.2k writes/second — the lock each step takes, how the backfill is batched, and where each step stops being reversible. PostgreSQL 16.
Approach
- Justify from the access path rather than from taste. Without the column, the audit feed either scans resource_revision by created_at and discards other tenants' rows, or resolves the tenant's resource_ids first and probes with them — both proportional to the tenant's whole history rather than to one page. With (tenant_id, created_at DESC, revision_id DESC) it is a seek that stops at 50 rows, and the purge becomes a ranged delete instead of a join.
- Name the cost exactly: a second copy of a fact can disagree with the first. Make the disagreement unwritable rather than documented — add UNIQUE (resource_id, tenant_id) on resource so it can serve as a foreign-key target, then FOREIGN KEY (resource_id, tenant_id) REFERENCES resource (resource_id, tenant_id) on the revision table. A revision can then only ever carry its parent's tenant.
- Step one, expand: ALTER TABLE resource_revision ADD COLUMN tenant_id BIGINT NULL, with no default, so it is a catalogue change and no rewrite. It still needs ACCESS EXCLUSIVE for an instant, and that instant queues behind the longest open transaction on the table while every later query queues behind it — set lock_timeout to 2s and retry rather than wait.
- Step two, dual-write: deploy the writer that populates tenant_id on every new revision while reads still use the join. Reversible by redeploying the previous build, because nothing reads the column yet.
Follow-up
- The backfill is half finished and a rollback is required. What state is the table in, and what does the previous build do with a half-populated column?
- How do you verify the backfill actually finished, given rows are still being inserted while it runs?
Keep soft-deleted accounts from blocking re-registration
app_user holds user_id, tenant_id, email CITEXT, password_hash (NULL for SSO principals), email_verified_at, auth_version, status ('invited','active','suspended','deactivated'), created_at, updated_at, deleted_at. Two live accounts for one address inside a tenant must be impossible, but an address freed by a soft delete must be reusable, and the same tenant may delete and re-register it repeatedly. Write the uniqueness DDL for PostgreSQL 16, then the equivalent for MySQL 8 where partial indexes do not exist, and say what each permits once three deleted rows already hold that address.
Approach
- Start from what is actually unique: not (tenant_id, email), but (tenant_id, email) among live rows. PostgreSQL says that directly — CREATE UNIQUE INDEX app_user_live_email ON app_user (tenant_id, email) WHERE deleted_at IS NULL. A full constraint over the same two columns burns the address permanently the first time someone deletes an account.
- Keep case-insensitivity in the type or the index, never in the application: CITEXT as given, or UNIQUE (tenant_id, lower(email)) as an expression index where the extension is unavailable. A case-sensitive unique column is exactly how two accounts for one human appear.
- For MySQL 8 the predicate has to move inside the key: add a discriminator column that is a constant 0 while the row is live and is set to user_id on delete, with UNIQUE (tenant_id, email, deleted_marker). Live rows share the constant and still collide; deleted rows differ from each other and stop colliding.
- State the NULL variant and its dependency: leaving the marker NULL for deleted rows also works, because a unique index treats NULLs as distinct — true in MySQL, and true in PostgreSQL only under the default NULLS DISTINCT, which PostgreSQL 15 lets you reverse. Check the polarity against the three existing deleted rows: constant-on-live is what preserves the collision you want, and reversing it silently admits duplicate live accounts.
Follow-up
- A deleted account re-registers with the same address the next day. Do the old resource rows follow the new user_id, and how does the API keep the two principals apart?
- How do you honour an erasure request while resource_revision.actor_user_id still references this table?
Given a slow function that calls an external API, how would you optimize its performance?
Given a slow function that calls an external API, how would you optimize its performance?
Approach
- Say who the caller is and what they do when the call fails halfway.
- Define the identity of a request so a retry cannot double-apply it.
- Separate accepted, pending, failed and confirmed; they are different facts.
- Design the error taxonomy before the success shape; callers branch on it.
Follow-up
- What happens if the caller retries after a timeout?
- How does a client discover it is on an old version of this contract?
Design a URL shortening service.
Design a URL shortening service.
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?
Design a game like Damka (checkers) from an architectural perspective.
Design a game like Damka (checkers) from an architectural perspective.
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 the architecture of a project you led.
Describe the architecture of a project you led.
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?
How do you approach scaling a service when traffic spikes unexpectedly?
How do you approach scaling a service when traffic spikes unexpectedly?
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?
One customer endpoint stalls deliveries to every other destination
The egress service delivers about 1.5k webhooks/second across 40,000 destinations, with a per-destination concurrency cap of 4 and a 10-second connect-plus-read timeout. Throughput falls to 300/second, queue depth climbs, and p99 delivery latency for unaffected destinations goes from 200 ms to minutes, while the error rate barely moves. One tenant holds 900 destination rows whose URLs share a hostname that now answers in 9.5 seconds. Explain the mechanism with the arithmetic, then give the containment in the order you would apply it.
Approach
- Look at saturation before errors. A flat error rate with collapsing throughput says nothing is failing, things are waiting, so the first signal to pull is in-flight request count or pool wait time rather than the error counter. This is the distinction that decides the whole investigation.
- Group in-flight work by resolved host, not by destination id. The cap is keyed per destination row, so 900 rows sharing one hostname buy 3,600 concurrent slots against a single host, each held for 9.5 seconds. The bulkhead was never a bulkhead for that host, and grouping by the wrong dimension is why the dashboard looked healthy.
- Do the arithmetic in both directions. Required concurrency is arrival rate times latency, so 1.5k/second at 200 ms needs about 300 in flight, which is entirely consumed by 3,600 slow slots; conversely whatever concurrency is left sustains rate equals concurrency divided by 9.5 seconds, which is the 300/second you are seeing. Matching both numbers is what promotes this from a plausible story to the mechanism.
- Explain why the circuit breaker never helped. It opens on consecutive failures, and a 9.5-second response inside a 10-second timeout is a success. Slow is not failing, so an error-rate breaker cannot see this; you need a slow-call ratio, a deadline propagated from the caller's remaining budget, or a concurrency limiter.
Follow-up
- The host recovers to 80 ms. How long does the queue take to drain, and what does the drain do to the recovered host?
- Where should the 10-second timeout number actually come from?
Built from the rounds and topics AppsFlyer candidates report.
Prepare, practise & reflect
One practical outcome each day. Spend longer where you need it.
0 / 7 done01Map the AppsFlyer loop
- Write out the reported sequence: Recruiter Screen, Technical Deep Dives, Behavioral Discussions, Final Decision.
- 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 System design
- Spend the session on System design, which AppsFlyer candidates report being tested on.
- Write one worked example in System design and time yourself on it.
Deliverable: One timed worked example in System design.
03Work Coding interview problem solving
- Spend the session on Coding interview problem solving, which AppsFlyer candidates report being tested on.
- Write one worked example in Coding interview problem solving and time yourself on it.
Deliverable: One timed worked example in Coding interview problem solving.
04Work Architectural skills
- Spend the session on Architectural skills, which AppsFlyer candidates report being tested on.
- Write one worked example in Architectural skills and time yourself on it.
Deliverable: One timed worked example in Architectural skills.
05Answer out loud: Coding and Algorithms
- Answer aloud, timed: Implement an LRU Cache from scratch.
- Answer aloud, timed: Given a slow function that calls an external API, how would you optimize its performance?
Deliverable: Spoken answers to 2 reported Coding and Algorithms question(s), under time.
06Answer out loud: System Design and Architecture
- Answer aloud, timed: Design a URL shortening service.
- Answer aloud, timed: Design a game like Damka (checkers) from an architectural perspective.
Deliverable: Spoken answers to 2 reported System Design and Architecture question(s), under time.
07Answer out loud: Experience and Behavioral
- Answer aloud, timed: Describe a significant technical challenge you faced in your last role and how you solved it.
- Answer aloud, timed: Tell me about a time you had to make a difficult trade-off between speed and code quality.
Deliverable: Spoken answers to 2 reported Experience and Behavioral 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.
How do you handle distributed systems and large-scale data challenges?
How do you handle distributed systems and large-scale data challenges?
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?
Describe a significant technical challenge you faced in your last role and how you solved it.
Describe a significant technical challenge you faced in your last role and how you solved 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?
Tell me about a time you had to make a difficult trade-off between speed and code quality.
Tell me about a time you had to make a difficult trade-off between speed and code quality.
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 stay updated with new technologies and apply them to your work?
How do you stay updated with new technologies and apply them to your work?
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 are you interested in joining AppsFlyer?
Why are you interested in joining AppsFlyer?
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 are you looking for in your next career move?
What are you looking for in your next career move?
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
How do you handle distributed systems and large-scale data challenges?
- 02
Describe a significant technical challenge you faced in your last role and how you solved it.
- 03
Tell me about a time you had to make a difficult trade-off between speed and code quality.
- 04
How do you stay updated with new technologies and apply them to your work?
How difficult are the technical interviews?
They are generally considered fair but challenging. They focus on practical engineering skills rather than "trick" questions, so focus on foundational knowledge and clear communication.
AppsFlyer Software Engineer candidate reports ↗How should I prepare for the design interview?
Focus on understanding the trade-offs of different architectural patterns. Practice drawing diagrams and explaining your choices, such as why you chose a specific database or caching strategy.
AppsFlyer Software Engineer candidate reports ↗What is the company culture like?
AppsFlyer is often described as professional, welcoming, and fast-paced. They place a high value on learning, growth, and team collaboration.
AppsFlyer Software Engineer candidate reports ↗Can I use tools like ChatGPT or the internet during the interview?
Some interviewers encourage using available resources to solve complex problems, as it mimics real-world work. Always ask the interviewer for their preference before accessing external tools.
AppsFlyer Software Engineer candidate reports ↗What topics does AppsFlyer test in interviews?
AppsFlyer interviews most often cover SQL, Problem Solving, Mobile attribution, Stakeholder Management, and Stakeholder Communication (Technical). The exact emphasis depends on the specific role you apply for.
AppsFlyer 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.
- 01AppsFlyer 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.
Vercel Software Engineer Interview Guide
Debugging practice for Vercel software engineer prep built on a reproduction you trust, narrowing to the smallest failing input, and changing one variable per run so the result stays attributable.
Spotify Software Engineer Interview Guide
Timed practice for Spotify software engineer candidates who lose time to the clock: short problems taken end to end, then reviewed against a written rubric rather than a passing test run.
Shopify Software Engineer Interview Guide
Timed practice for Shopify software engineer candidates who lose time to the clock: short problems taken end to end, then reviewed against a written rubric rather than a passing test run.
Ramp Software Engineer Interview Guide
Systems practice for Ramp software engineer candidates, weighted toward payments and lending work: the load that actually arrives, the failure modes that matter there, and the invariants a partial outage must not break.