cswork / libraryOpen practice workspace

Interview guides · Wai Global

Wai Global Software Engineer Interview Guide

Wai Global Software Engineer interview guide: reported rounds, questions and how candidates describe the process.

The 60-second brief

A Software Engineer at Wai Global plays a pivotal role in designing, building, and maintaining the core systems that drive the company's business operations. Operating in a highly dynamic environment, engineers here are responsible for translating complex business requirements into scalable, high-performance software solutions. Whether you are optimizing a database, refining a user interface, or building robust backend services, your work directly impacts the reliability and efficiency of the company's digital ecosystem. At Wai Global, engineering teams are structured to foster collaboration and rapid innovation. As a Software Engineer, you will work on diverse technical stacks that span modern frontend frameworks, robust backend architectures, and high-throughput data layers.

This guide is scoped to a Software Engineer candidate at Wai Global.

Focus areas

  • Angular
  • Full Stack Development
  • JavaScript

The Wai Global interview process

Wai Global candidates report 4 rounds over 3-5 weeks. The stages below are what candidates describe, not a published process.

Online Assessment

Initial assessment to establish a technical baseline.

What to demonstrate

  • Initial assessment to establish a technical baseline
  • Depth in Angular

How to prepare

  • Answer aloud and timed: Explain the lifecycle hooks in Angular and describe a scenario where you would use ngOnInit versus ngAfterViewInit.
  • Answer aloud and timed: How does change detection work in Angular, and how can you optimize it for high-performance applications?

Technical Discussion

In-depth technical conversations to evaluate coding skills and architectural thinking.

What to demonstrate

  • In-depth technical conversations to evaluate coding skills and architectural thinking
  • Depth in Angular

How to prepare

  • Answer aloud and timed: What are the differences between flexbox and grid layouts in CSS? Provide an example of when you would choose one over the other.
  • Answer aloud and timed: How do you handle asynchronous data streams in JavaScript using RxJS Observables?

Leadership Evaluation

Meet with senior engineering leadership for behavioral and cultural alignment discussions.

What to demonstrate

  • Meet with senior engineering leadership for behavioral and cultural alignment discussions
  • Depth in Angular

How to prepare

  • Answer aloud and timed: Describe the process of optimizing a web application's loading time and performance.
  • Answer aloud and timed: How do you design a secure, versioned, and scalable REST API from scratch?

Terms Negotiation

Negotiate terms with HR following the technical and leadership evaluations.

What to demonstrate

  • Negotiate terms with HR following the technical and leadership evaluations
  • Depth in Angular

How to prepare

  • Answer aloud and timed: Explain the concept of multi-threading. How do you handle thread safety and prevent race conditions in C# or Java?
  • Answer aloud and timed: Describe your approach to implementing comprehensive error handling and logging across a distributed backend system.

Where candidates lose points

Brush up on web basics

Even if you are applying for a full-stack or backend role, ensure you have a solid grasp of core web technologies like JavaScript, HTML, and CSS, as cross-functional knowledge is highly valued.

Be ready to talk about error handling

Do not just explain how your code works when everything goes right. Interviewers frequently ask how you handle exceptions, validate inputs, and log errors in production environments.

Naming no test cases at all

State what you would test before being asked: empty input, a single element, all elements equal, the maximum permitted size, and the input that exercises the branch you just wrote. It costs thirty seconds and is much of what separates someone who has shipped code from someone who has only solved puzzles.

Questions & practice

Explain the concept of multi-threading. How do you handle thread safety and prevent race conditions in C# or J

Medium · Backend & API Engineering

Explain the concept of multi-threading. How do you handle thread safety and prevent race conditions in C# or Java?

Approach

  1. Say what the runtime actually does before reasoning about the code.
  2. Name what is shared across threads and what owns each piece of state.
  3. Identify the window where an invariant is briefly untrue.
  4. 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?

What is the difference between synchronous and asynchronous programming, and how does it impact server resourc

Medium · Backend & API Engineering

What is the difference between synchronous and asynchronous programming, and how does it impact server resource utilization?

Approach

  1. Say what the runtime actually does before reasoning about the code.
  2. Name what is shared across threads and what owns each piece of state.
  3. Identify the window where an invariant is briefly untrue.
  4. 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?

Diff a projection against the primary without per-row point reads

Hard · reconciliation · range hashing · throttling

The listing projection has drifted and some rows show a stale version. The primary holds 40,000,000 resource rows across 12,000 tenants while serving 1,200 writes and 14,000 reads per second. The obvious repair, reading each resource row and comparing its version against the projection, is correct and would eventually finish. Explain precisely why it is unacceptable here, then give a diff that finds the differing rows, state its complexity, and make it safe to run against a live primary. Replication lag is usually under 100 ms and is not bounded.

Approach

  1. Quantify the naive cost rather than calling it slow: 40,000,000 point reads at even 0.5 ms each is over five hours serialised, and the only lever is concurrency, which is exactly what you cannot spend. The primary's pool is sized for the write path, and 40,000,000 random reads evict the buffer cache that sustains the 85 percent cache hit rate, so the audit degrades the system it is auditing.
  2. Replace random access with one ordered pass per side. Both sides can be read in (tenant_id, resource_id) order, which is a sequential scan on each and a merge join in O(n) time and O(1) memory. For a dense diff that is the whole answer, and it reads the primary once instead of 40,000,000 times.
  3. For the expected sparse case, compare range hashes instead of rows: partition the key space, compute per range an order-independent aggregate over hash(resource_id, version), compare aggregates, and descend only into ranges that differ. With d differing rows and branching factor B, at most d ranges mismatch per level, so the drill-down examines O(d log_B(n/d)) ranges and reads full rows only in mismatching leaves.
  4. Aggregate with a sum modulo 2^64 or a multiset hash, never XOR. XOR is order-independent but self-cancelling, so two rows wrong in the same way, or a row duplicated on one side, leave the range aggregate matching and the range is declared clean.

Follow-up

  • The diff reports 900 stale rows. How do you decide between patching those rows and rebuilding the projection from resource_revision?
  • Same job, but the projection lives in a search index that cannot be scanned in key order. What changes?

How do you optimize a slow-running SQL query? Explain the role of indexes and execution plans.

Medium · Object-Oriented Programming & Database M

Approach

  1. Name the grain you start from and join outward from it.
  2. Check whether any join is one-to-many before aggregating, or the sums inflate.
  3. Say which index the query would use, and what makes it unusable.
  4. Handle the rows that do not match: that is usually the actual question.

Follow-up

  • How does the query change if that join becomes one-to-many?
  • What happens to this when the table is ten times larger?

Describe the differences between inner joins, left joins, and outer joins in SQL, and how they affect query pe

Medium · Object-Oriented Programming & Database M

Describe the differences between inner joins, left joins, and outer joins in SQL, and how they affect query performance.

Approach

  1. Name the grain you start from and join outward from it.
  2. Check whether any join is one-to-many before aggregating, or the sums inflate.
  3. Say which index the query would use, and what makes it unusable.
  4. Handle the rows that do not match: that is usually the actual question.

Follow-up

  • How does the query change if that join becomes one-to-many?
  • What happens to this when the table is ten times larger?

Explain the lifecycle hooks in Angular and describe a scenario where you would use ngOnInit versus `ngAfterV

Medium · Frontend & UI Development

Explain the lifecycle hooks in Angular and describe a scenario where you would use ngOnInit versus ngAfterViewInit.

Approach

  1. Clarify what is being asked and what a complete answer contains.
  2. State your assumptions explicitly before working the problem.
  3. Say what you would check first and why it is the highest-information step.
  4. 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 does change detection work in Angular, and how can you optimize it for high-performance applications?

Medium · Frontend & UI Development

Approach

  1. Clarify what is being asked and what a complete answer contains.
  2. State your assumptions explicitly before working the problem.
  3. Say what you would check first and why it is the highest-information step.
  4. 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 differences between flexbox and grid layouts in CSS? Provide an example of when you would cho

Medium · Frontend & UI Development

What are the differences between flexbox and grid layouts in CSS? Provide an example of when you would choose one over the other.

Approach

  1. Clarify what is being asked and what a complete answer contains.
  2. State your assumptions explicitly before working the problem.
  3. Say what you would check first and why it is the highest-information step.
  4. Work from the requirement backwards to the design.

Follow-up

  • What assumption would you test first?
  • How would you know your answer was wrong?

Describe the process of optimizing a web application's loading time and performance.

Medium · Frontend & UI Development

Approach

  1. Clarify what is being asked and what a complete answer contains.
  2. State your assumptions explicitly before working the problem.
  3. Say what you would check first and why it is the highest-information step.
  4. 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 design a secure, versioned, and scalable REST API from scratch?

Medium · Backend & API Engineering

Approach

  1. Fix the scope first: who calls this, how often, and what they do when it fails.
  2. Name the read and write paths separately; they rarely have the same bottleneck.
  3. Choose a partition key and say what query it makes expensive.
  4. 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 your approach to implementing comprehensive error handling and logging across a distributed backend s

Medium · Backend & API Engineering

Describe your approach to implementing comprehensive error handling and logging across a distributed backend system.

Approach

  1. Fix the scope first: who calls this, how often, and what they do when it fails.
  2. Name the read and write paths separately; they rarely have the same bottleneck.
  3. Choose a partition key and say what query it makes expensive.
  4. 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 dependency injection and inversion of control (IoC) contribute to writing testable backend code?

Medium · Backend & API Engineering

Approach

  1. Say who the caller is and what they do when the call fails halfway.
  2. Define the identity of a request so a retry cannot double-apply it.
  3. Separate accepted, pending, failed and confirmed; they are different facts.
  4. 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?

Explain the four pillars of Object-Oriented Programming (OOP) and give a practical example of polymorphism in

Medium · Object-Oriented Programming & Database M

Explain the four pillars of Object-Oriented Programming (OOP) and give a practical example of polymorphism in a real-world project.

Approach

  1. Clarify what is being asked and what a complete answer contains.
  2. State your assumptions explicitly before working the problem.
  3. Say what you would check first and why it is the highest-information step.
  4. 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 is the difference between an abstract class and an interface, and when would you use each?

Medium · Object-Oriented Programming & Database M

Approach

  1. Clarify what is being asked and what a complete answer contains.
  2. State your assumptions explicitly before working the problem.
  3. Say what you would check first and why it is the highest-information step.
  4. Work from the requirement backwards to the design.

Follow-up

  • What assumption would you test first?
  • How would you know your answer was wrong?

p99 jumped on one listing filter while p50 stayed flat

Medium · query planning · composite index · percentiles

After a release that added an owner_user_id filter to the resource listing, p99 rose from 90 ms to 1.9 s while p50 stayed at 40 ms. Traffic and row counts are unchanged. resource carries the index (tenant_id, status, updated_at DESC, resource_id DESC). The new query filters tenant_id and owner_user_id, orders by updated_at DESC, resource_id DESC, and takes 20 rows. On PostgreSQL, explain the shape of the regression, prove it from a query plan, and give the index you would add.

Approach

  1. Start from the shape. A flat p50 with a moved p99 means a subset of requests changed cost, not all of them, so the first job is naming the subset. Bucket the endpoint's latency by the tenant's row count; the natural hypothesis is that large tenants are a small share of requests and all of the tail.
  2. Get the plan for the new query on a large tenant with EXPLAIN (ANALYZE, BUFFERS). Expect an index scan over the tenant's range, a filter discarding most of it, then a Sort feeding the Limit, possibly reporting Sort Method: external merge Disk. Read actual rows on the scan node, not estimated.
  3. Explain why the existing index cannot serve it. A composite B-tree is seekable only as a left prefix, and with no equality predicate on status the scan cannot treat updated_at as an ordering, because rows in the tenant's range are ordered by status first. Everything matching must be read and sorted before LIMIT 20 can apply, so a tenant with 400,000 rows pays 400,000 rows to return 20.
  4. Add (tenant_id, owner_user_id, updated_at DESC, resource_id DESC). Equality on the first two columns leaves the index ordered by updated_at within that pair, so the plan becomes an index scan that stops after 20 rows with no Sort node. PostgreSQL can scan a B-tree backwards, so the DESC markers matter only if the two sort columns ever disagree in direction; keeping them explicit documents the order the keyset cursor depends on.

Follow-up

  • The endpoint paginates with OFFSET. What does page 500 cost with your index, and what does the keyset version cost?
  • How would you have caught this before release, given that a 10,000-row seed database produces the same plan shape at an unnoticeable cost?

Suggested practice checklist

Built from the rounds and topics Wai Global candidates report.

Day 1 — Map the Wai Global loop

  • Write out the reported sequence: Online Assessment, Technical Discussion, Leadership Evaluation, Terms Negotiation.
  • 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.

Day 2 — Work Angular

  • Spend the session on Angular, which Wai Global candidates report being tested on.
  • Write one worked example in Angular and time yourself on it.

Deliverable: One timed worked example in Angular.

Day 3 — Work Full Stack Development

  • Spend the session on Full Stack Development, which Wai Global candidates report being tested on.
  • Write one worked example in Full Stack Development and time yourself on it.

Deliverable: One timed worked example in Full Stack Development.

Day 4 — Work JavaScript

  • Spend the session on JavaScript, which Wai Global candidates report being tested on.
  • Write one worked example in JavaScript and time yourself on it.

Deliverable: One timed worked example in JavaScript.

Day 5 — Answer out loud: Frontend & UI Development

  • Answer aloud, timed: Explain the lifecycle hooks in Angular and describe a scenario where you would use ngOnInit versus ngAfterViewInit.
  • Answer aloud, timed: How does change detection work in Angular, and how can you optimize it for high-performance applications?

Deliverable: Spoken answers to 2 reported Frontend & UI Development question(s), under time.

Day 6 — Answer out loud: Backend & API Engineering

  • Answer aloud, timed: How do you design a secure, versioned, and scalable REST API from scratch?
  • Answer aloud, timed: Explain the concept of multi-threading. How do you handle thread safety and prevent race conditions in C# or Java?

Deliverable: Spoken answers to 2 reported Backend & API Engineering question(s), under time.

Day 7 — Answer out loud: Object-Oriented Programming & Database Management

  • Answer aloud, timed: Explain the four pillars of Object-Oriented Programming (OOP) and give a practical example of polymorphism in a real-world project.
  • Answer aloud, timed: What is the difference between an abstract class and an interface, and when would you use each?

Deliverable: Spoken answers to 2 reported Object-Oriented Programming & Database Management question(s), under time.

Behavioural preparation

Behavioural rounds judge the decision you made and what it cost.

How do you handle asynchronous data streams in JavaScript using RxJS Observables?

Medium · Frontend & UI Development

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. 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 database transactions to ensure data consistency and integrity under high concurrent write l

Medium · Object-Oriented Programming & Database M

How do you handle database transactions to ensure data consistency and integrity under high concurrent write loads?

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. 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?

Estimate work you have never done and defend the range

Hard · estimation · backfills · expand-contract

You are asked to estimate a change you have never attempted: add a column to a 100-million-row table, populate it, move reads across, and drop the old shape. Give a range with the assumptions that generate it, including batch size, the signal your backfill throttles on, and wall-clock hours, and name the three unknowns that would move the number most. Then describe a real estimate you gave under comparable ignorance: how you expressed its uncertainty, what you committed to, and how wrong you turned out to be.

Approach

  1. Decompose into independently deployable steps before estimating anything: add the column nullable, write both shapes, backfill in batches, verify, move reads, stop writing the old shape, drop it. That is four deploys spread over days, and the calendar estimate is dominated by them rather than by the loop's runtime.
  2. Do the arithmetic aloud for the part that has arithmetic in it: batch size times number of batches times per-batch duration, at a write rate the primary can absorb alongside roughly 1.2k writes per second of production traffic. The loop is throttled by replication lag and lock waits, not by how fast it can issue statements.
  3. Price the schema step by its lock rather than its statement duration. In PostgreSQL an ALTER TABLE taking ACCESS EXCLUSIVE waits for every open transaction on that table while later queries queue behind it, so a millisecond change issued during a thirty-second analytics query stalls that table for thirty seconds. Adding a nullable column with a non-volatile default avoids a rewrite from version 11; a new index wants CREATE INDEX CONCURRENTLY, which cannot run inside a transaction block and leaves an invalid index behind if it fails.
  4. Express the answer as a range whose endpoints each trace to a stated assumption, then name the cheapest experiment that collapses it, which is almost always running one real batch against the real table and multiplying.

Follow-up

  • How do you verify the backfill genuinely finished, given rows written by production traffic while it ran?
  • Where does the backfill resume from after a worker is killed mid-batch, and what makes that resume point trustworthy?