Editorial practice groupings, not verified official interview questions or endorsements.
Public Shopee prep guide
Prepare with five practice prompts shaped by public frontend interview accounts from Ho Chi Minh City, mainland China, Singapore campus hiring and Taipei, 2020 to 2025: a Promise written without using Promise after event-loop and async questions, a recursive multi-level hover menu in React, a function cache keyed by its arguments beside flatten, deep clone and new, an HTTP, caching, cookie and security hour, and a 90-minute written test with CSS specificity and centring questions.
This guide uses public, self-reported interview accounts, most of them written in Chinese between 2020 and 2022, together with Shopee's own hiring page and a reprinted campus posting, to create realistic constraints. It does not claim access to private interview material, a fixed interview format, or the stack of every Shopee team.
Study priorities
The public accounts reward engineers who can write JavaScript fundamentals from memory and explain the web platform precisely: a Promise implemented without Promise, a function cache, flatten, deep clone and new, then HTTP caching, cookie attributes, CSRF, XSS and CORS answered with the right headers and status codes. Networking and security questions appear in these frontend accounts more often than in most other companies' public loops, sometimes as a whole round, and one or two LeetCode easy-to-medium problems sit in most technical rounds outside Taipei. Each prompt below starts with the clarifying questions a strong candidate asks, then the behaviours a strong answer covers, then the miss that usually ends the round.
The shape differs by region. The 2025 Ho Chi Minh City account ran a two-hour frontend round in clear parts (CSS, JavaScript, a React build, an algorithm), a CS-fundamentals round, a behavioural interview a week later and a final conversation before the offer. Mainland-China loops run per department as a first and second technical interview plus HR, sometimes all on one day, and a second department can re-interview a candidate another has turned down. Singapore campus loops start with an online assessment and continue in video rounds of 60 to 90 minutes. Taipei ran a 30-minute HR call, a 90-minute written test and same-day panels with a product manager and a tech lead, where, in the candidate's words, communication mattered a lot. Practise narrating your decisions, not only typing them.
Reported interview process
Shopee's How we hire page lists five steps (Apply, Getting to Know You, Putting Your Skills to the Test, Meet the Hiring Manager, Preparing to Join Us) and says the number of rounds varies depending on the role and seniority. Public frontend accounts describe three shapes: a 2025 Ho Chi Minh City loop with an HR call, a two-hour frontend round, a CS-fundamentals round, a behavioural interview a week later and a final conversation; Singapore campus loops from 2020 to 2022 with an online assessment, video rounds of 60 to 90 minutes and an HR call; and mainland-China campus and social-hire loops run in Chinese, with a written test for some campus roles, two technical interviews per department and an HR conversation.
The Singapore experienced-hire loop that English searches point at (an HR call, a coding test on HTML, CSS and JavaScript, two technical rounds heavy on verbal JavaScript, an engineering-manager round and an offer in about two weeks) rests on search snippets only and gets no table. Taipei has two accounts and no table: a 2021 frontend loop with a 30-minute HR call, a 90-minute junior-level written test and same-day panels with a product manager and a tech lead, and a 2023 senior software-engineer loop of HR, a manager round on technology, a peer round and a senior-manager chat. Most full-text accounts are from 2020 to 2022 and written in Chinese, and on 2026-10-21 the Shopee job board listed no frontend-titled opening in Singapore or South-East Asia. Sources last checked Oct 2026.
One full account (Viblo, February 2025, an offer) carries this table; the stage order rests on it alone.
| Stage | What happens | Who | Evidence |
|---|---|---|---|
| HR call | Personal details, expected salary and whether the candidate is willing to move to Saigon. | All candidates | One public report, 2025 |
| Frontend technical round | About two hours in clear parts: CSS (the position values), JavaScript (the event loop, promises, async/await, a Promise written without using Promise), a React build (a recursive multi-level hover menu) and an algorithm on mapping characters between two data sets. Practice: Create a deferred promise | Front-end engineers | One public report, 2025 |
| CS-fundamentals round | Design a system based on the candidate's current work, then HTTP, TCP/UDP, WebSocket, how an API gateway and a load balancer work, and encryption, hashing and encoding. Practice: HTTP caching basics | Front-end engineers | One public report, 2025 |
| Behavioural interview | A week later: how the candidate had worked with a colleague who held a different view, and how it was resolved. Practice: Behavioural stories | All candidates | One public report, 2025 |
| Final conversation and offer | Future direction and expectations at Shopee compared with the previous job; the offer came a few days later. | Candidates who pass | One public report, 2025 |
One frontend first round (Nowcoder, September 2020) plus three campus loops in other tracks for the assessment and round shape. Singapore experienced hires get no table.
| Stage | What happens | Who | Evidence |
|---|---|---|---|
| Online assessment | A 70-minute test in the 2022 account: ten multiple-choice questions on operating systems and networking plus two array coding problems; twenty-odd multiple-choice questions plus one LeetCode problem in the 2021 account. | Campus candidates; backend and platform accounts | 2 public reports, 2021–2022 |
| Technical video rounds | One to three rounds of 60 to 90 minutes on a shared editor, each with one or two problems, CS fundamentals and a design-concept question; the frontend first round had a string-compression algorithm plus JavaScript versus CSS animation, specificity, React keys, HTTPS and man-in-the-middle attacks, and session versus cookie versus token. Practice: Cascade, specificity and !important | All campus candidates; frontend content from the 2020 first round | 4 public reports, 2020–2022 |
| HR call with a verbal offer | A verbal offer from HR about five weeks after applying, with cost-of-living and relocation material for overseas hires in the 2020 account; one 2022 loop ended in a rejection sixteen days after applying. | Candidates who pass | 2 public reports, 2020–2022 |
All loops in Chinese. The official line comes from a reprinted 2027 campus posting; the accounts are campus loops from 2019 to 2021 and social-hire loops from 2020 and 2022, each social hire re-interviewed by a second department.
| Stage | What happens | Who | Evidence |
|---|---|---|---|
| Application or referral, then a written test | The campus posting lists 网申/内推 (online application or referral), then 笔试 (a written test) that some roles skip (部分岗位不设笔试), before two to three technical rounds. | Campus candidates | Official page |
| First technical interview | JavaScript, CSS, HTTP and framework basics plus one or two small algorithms: event-loop and promise output questions, handwritten new, flatten and deep clone, XSS and CSRF, caching headers, CSS centring, binary search, set intersection or quicksort; the 2019 account says the interviewer guides the candidate's thinking. Practice: Implement the new operator | Front-end engineers, campus and social hires | 6 public reports, 2019–2022 |
| Second technical interview | React internals and diffing, HTTP/2 and status codes, webpack performance and async chunks, CDN questions, scenario questions such as a user reporting a button that cannot be clicked, project depth, and a second coding task such as a function cache; the 2019 account had three questions only. Practice: Memoization | Front-end engineers | 4 public reports, 2019–2022 |
| HR interview and offer | The posting lists an HR conversation (HR沟通) before the offer. In the social-hire accounts the loop runs per department, sometimes both technical rounds and HR on one day; a rejection after the first round can come back with feedback such as 算法有待加强 (algorithms need strengthening), and a second department can re-interview the same candidate. | All candidates | Official page and 2 reports |
Role lenses
These are preparation lenses derived from the departments the public accounts name (a seller platform, a supply-chain team, a digital bank and a team the account calls PFMS), not claimed team assignments. Choose the lens closest to the role and keep the reasoning framework-neutral.
The 2020 and 2022 mainland-China loops ran through seller-platform, supply-chain and PFMS teams and asked about webpack performance and async chunk loading, fifty SVG requests, what a CDN does, html2canvas and a schema-driven back-office form.
Practice focus: Bundle splitting and lazy loading, sprites and batching for many small assets, CDN caching with explicit invalidation, form state driven by a schema, and rendering work kept off the critical path.
The 2022 digital-bank first round was an HTTP and security hour: an HTTP message for a POST, strong versus negotiated caching, SameSite and CSRF, CORS, and carrying an ID number safely in a cookie, plus a Vue scenario: a vertically centred dialog created on demand through a createDialog call rather than injected as a component.
Practice focus: Cookie and token placement with its trade-offs, HTTPS and TLS reasoning, CORS with credentials, escaping and a Content Security Policy, and idempotent requests for actions that move money.
Representative practice prompts
For each prompt, clarify the contract, explain ownership and trade-offs, implement or write out the smallest credible slice, and test the failure cases. Each prompt links to the public report it is modelled on and to a practice page; quoted Chinese and Vietnamese phrases are glossed in English.
Prompt 1
The 2025 Ho Chi Minh City account describes the JavaScript part of a two-hour frontend round: the interviewers went deep into the event loop, promises and async/await, then set one exercise, "code một Promise nhưng không được dùng Promise" (write a Promise without using Promise). Implement a MyPromise class with a constructor that takes an executor, then and catch methods that chain, and callbacks that run asynchronously, and be ready to predict the output of promise and setTimeout snippets before you start.
Practice version modelled on a reported round: Public report: Viblo frontend engineer account, Ho Chi Minh City, February 2025
Whether you understand the state machine behind a promise (pending, fulfilled, rejected, settled once), how then returns a new promise and adopts returned values, why callbacks must run asynchronously, and whether you can predict microtask and macrotask order.
Common miss: Calling then callbacks synchronously when the promise is already settled, or letting a second resolve overwrite the first value; both break the ordering questions the same round asked about.
Practice the deferred promise with resolve and reject controls (free)Prompt 2
From the same 2025 account: build a multi-level menu in React where hovering an item drops down its sub-menu, and a sub-menu with children of its own keeps opening, described by the candidate as a recursion exercise. Take a nested array of items with an optional children array, render one component that renders itself for each child, and keep only the hovered path open.
Practice version modelled on a reported round: Public report: Viblo frontend engineer account, Ho Chi Minh City, February 2025
Recursive component design over nested data, where the open state lives, hover handling that does not close the menu while the pointer travels into the sub-menu, stable keys, and keyboard access.
Common miss: A sub-menu that closes as soon as the pointer leaves the parent label because the leave handler sits on the label rather than on the item with its sub-menu, and a children list rendered with index keys so hover state jumps between items.
Practice recursion over nested nodes with the indented tree filter (free)Prompt 3
A 2020 Juejin record of two mainland-China loops lists the handwritten tasks: a cache wrapper where f2 = cache(f1) returns the earlier result at once for the same arguments (f1("abc", 123, {b: 3}) took 1000 seconds to return 10; f2 with the same call returns 10 in 0 seconds), 拍平数组 (flatten an array), 深复制 (deep clone) and "new 的实现" (implement new). A 2022 Nowcoder social-hire account got 函数缓存 (a function cache) again in a second round. Implement each in plain JavaScript and say what each one does with its edge cases.
Practice version modelled on a reported round: Public report: Juejin frontend interview record, mainland China, March 2020
Closures and key derivation for a cache, recursion over nested arrays and objects, how the prototype chain and this binding work inside new, and whether you name the edge cases (object arguments, cycles, dates and functions in a clone, a constructor that returns an object) without being prompted.
Common miss: A cache keyed by arguments.join(",") that treats {b: 3} as "[object Object]", a deep clone that loops forever on a cyclic reference, and an implementation of new that forgets the constructor may return an object of its own.
Practice memoisation keyed by arguments (Premium)Prompt 4
The 2022 Nowcoder account lists its digital-bank frontend first round in order: given the URL and return body of a POST, write the HTTP message; strong versus negotiated caching; from HTTP to cookies and the SameSite attribute, then on to CSRF and XSS; cross-origin requests, which the candidate extended to simple versus preflighted requests; and how to keep an ID number safe when it must travel in a cookie. The 2020 Juejin record asks about the HTTPS and TLS handshakes, symmetric versus asymmetric encryption, the HttpOnly and Secure flags and the status codes behind each cache type, and the 2020 Singapore campus first round asks how HTTPS prevents a man-in-the-middle attack and how a session, a cookie and a token differ.
Practice version modelled on a reported round: Public report: Nowcoder frontend social-hire interview, mainland China, April 2022
Precise web-platform knowledge stated from memory: the shape of an HTTP response, cache headers and their status codes, cookie attributes and the attacks they limit, CORS mechanics, and transport-security reasoning for sensitive data.
Common miss: Describing CSRF as a form of XSS, naming 304 for a strong cache hit, or answering the ID-number question with "use HTTPS" alone when the interviewer is waiting for cookie flags, encryption of the value and a reason not to store it in the cookie at all.
Review HTTP caching basics (free)Prompt 5
A 2021 Taipei account reproduces its 90-minute onsite written test, which the candidate rated junior level: sort an array and remove duplicates in decreasing order; the rules of CSS specificity; shallow versus deep copy; how to manage CSS in a large application; three ways to centre horizontally and vertically; optimise or debug a class component; and the console output of setTimeout inside a var loop. The same-day panels then asked about cookie details, localStorage and sessionStorage, whether computing load belongs on the frontend or the backend, and how the browser renders HTML, CSS and JavaScript. The 2020 mainland-China campus first round asked for the centring methods and the caching headers as well. Answer all seven in writing with a clock running, then explain each answer aloud.
Practice version modelled on a reported round: Public report: GoodJob frontend engineer written test and panels, Taipei, January 2021
Fast, correct fundamentals on paper: array methods, the specificity algorithm, copy semantics, CSS organisation at scale, layout techniques, class-to-hooks judgment and closure behaviour in loops, plus the ability to explain each answer to a product manager and a tech lead the same day.
Common miss: Sorting with the default comparator, which orders numbers as strings, or answering the loop question with 0 1, 1 2, 2 3 because the shared var binding was not run through in your head.
Practice inline centring (free)Public mini walkthrough
Treat this as a representative exercise, not a description of the reported one. Work from the contract toward the microtask, and say each decision out loud.
A constructor that takes an executor and calls it at once with resolve and reject; then(onFulfilled, onRejected) and catch(onRejected) that return new promises. Say what you are leaving out: finally, the static helpers, thenable adoption.
Three states (pending, fulfilled, rejected), one value or reason, and a guard so only the first resolve or reject counts; a throw inside the executor rejects.
While pending, push each then call's handlers into two arrays; on settlement, drain the arrays in order.
Each then creates a new promise; a handler's return value resolves it, a thrown error rejects it, and a missing handler passes the value or the reason through.
Schedule handler execution with queueMicrotask (or setTimeout if told to), even when the promise is already settled, so the ordering matches the native behaviour you were asked to predict.
Resolve twice, reject after resolve, throw in a handler, a then without handlers, a handler returning one of your own promises, and the output order against a native Promise.
Actionable preparation
Every day ends with code, a test, a written answer, or a question you can use in the real process.
Event loop and promises: microtask and macrotask order, promise-chain output questions, setTimeout inside a var loop, catching errors with async/await.
Deliverable: A Promise written without Promise, with a test list you can retype from memory.
Handwritten utilities: a function cache keyed by arguments, flatten, deep clone, new, valid brackets, a publish-subscribe function.
Deliverable: Six implementations with edge cases written as tests.
React builds: the recursive multi-level hover menu, keys and one-way data flow, a class component moved to hooks, a component with data fetching.
Deliverable: The hover menu with keyboard access and a note on where the open state lives.
HTTP and security: an HTTP message for a POST response, strong versus negotiated caching with 200 and 304, cookie attributes, CSRF versus XSS, simple versus preflighted CORS requests, the HTTPS handshake, session versus cookie versus token.
Deliverable: A one-page answer sheet with the status code or header named for each topic.
CSS and the browser: specificity, three ways to centre, the position values, display none versus visibility hidden, managing CSS at scale, how the browser renders a page.
Deliverable: The seven Taipei written-test questions answered in 90 minutes against a clock.
Algorithms: sort and dedupe, string compression (elephant-walk to e6t-w2k), count the smaller elements, binary search, the intersection of two sets with sorting and two pointers or a hash map, reverse a linked list in groups of k.
Deliverable: Solutions in JavaScript with the time complexity stated for each.
Mock loop and behavioural: a two-hour frontend round narrated in parts, a CS-fundamentals round that starts from a system you built, a story about a colleague who held a different view.
Deliverable: A list of the questions you will ask the recruiter about the language, the assessment, the rounds and the tools.
Preparation FAQ
No. They are FrontendAtlas practice versions modelled on rounds and tasks described in public, self-reported accounts and on Shopee's own hiring page. The wording, the data and the test cases are ours, and the quoted Chinese and Vietnamese phrases are the candidates' own words, glossed in English.
Mainland-China loops run in Chinese; the full-text accounts from there are written in Chinese about Chinese-language rounds. Singapore campus loops are reported in English by Taiwanese candidates: the 2022 account says its technical round was conducted entirely in English, and a 2021 platform-engineer account on PTT says its rounds were in English, while a commenter on that thread adds that a round may run in Chinese depending on the interviewer. The Vietnamese accounts do not say which language was used, and the Taipei written test mixes English and Chinese questions. Ask the recruiter.
Campus accounts describe one. Two Singapore campus loops in other tracks sat a proctored online assessment of 60 to 70 minutes, on Glider.ai in the accounts that name the platform: ten multiple-choice questions on operating systems and networking plus two array problems in 2022, and twenty-odd multiple-choice questions plus one LeetCode problem in 2021; campus accounts also describe a frontend variant with five JavaScript problems. In mainland China the reprinted campus posting lists a written test after the application and says some roles have none; the two social-hire accounts used here started with a technical interview. The 2025 Ho Chi Minh City loop had no assessment, and Taipei ran a 90-minute written test onsite instead. Confirm with the recruiter.
The Singapore and mainland-China accounts put one or two LeetCode easy-to-medium problems in each technical round: a string-compression task in the 2020 Singapore campus first round, binary search, the intersection of two sets and quicksort in a 2021 campus first round, and reversing a linked list in groups of k in the 2022 social-hire round, whose feedback was "算法有待加强" (algorithms need strengthening). The 2025 Ho Chi Minh City round ended with one algorithm on mapping characters between two data sets. The Taipei candidate wrote that algorithms were hardly required ("對於演算法倒是不太要求"). Expect the handwritten utilities to count as much as the algorithms.
On 21 October 2026 the Shopee job board listed no frontend-titled opening in Singapore or South-East Asia; its 80 Singapore engineering postings carried backend, graduate and intern titles, and the only frontend-titled roles were two full-stack Python and React positions in São Paulo. Mainland China hires frontend engineers through its campus cycle, whose 2027 posting appeared in April 2026. Check the board before you plan a week of preparation.
Free public practice
These public pages cover the promise, utility, event-loop, caching, cookie, security and CSS skills used by the practice prompts. They are supporting drills, not claimed Shopee questions.
Public interview reports and official context
These links support the public context used by the guide. Their notes state what each source can and cannot establish about preparation. Most full-text accounts are from 2020 to 2022 and written in Chinese; the quotes above are glossed in English.
One self-reported Frontend Engineer loop at Shopee Vietnam in Ho Chi Minh City, published in February 2025 by a preparation course in the candidate's own words and ending in an offer. It establishes the HR call, the two-hour frontend round split into CSS, JavaScript, a React build and an algorithm, the CS-fundamentals round, the behavioural interview a week later and the offer a few days after the final conversation; it names no interview language and cannot establish the current format.
One self-reported record of two mainland-China loops in March 2020, a seller-platform loop that ended at HR and a same-day supply-chain session that led to a job, with about sixty questions listed. It establishes the handwritten tasks (a function cache, flatten, deep clone, new), the promise output questions and the HTTP, caching and cookie questions of that year; the city is not stated and the loop is more than five years old.
One self-reported social-hire loop in April 2022 by a candidate with more than two years of experience in Guangdong: a digital-bank frontend first round that ended with "算法有待加强" (algorithms need strengthening), then a first and second round with a second department, which the account calls PFMS, that also ended in a rejection. It establishes the HTTP, caching, SameSite, CORS and cookie-safety questions, the k-group linked-list reversal and the function cache; it cannot establish the current format.
One self-reported frontend engineer loop in Taipei in January 2021 by a candidate with four years of experience who heard nothing afterwards. It establishes the 30-minute HR call, the 90-minute onsite written test with its seven questions, the same-day panels with a product manager and a tech lead, the behavioural questions, and the candidate's view that algorithms were hardly required and communication mattered; it is one loop from 2021.
One self-reported first round for a Singapore frontend campus role in September 2020, posted on Nowcoder in Chinese. It establishes the string-compression algorithm, the JavaScript versus CSS animation question, specificity, React keys, HTTPS and man-in-the-middle attacks, and session versus cookie versus token; it covers one round only.
One self-reported mainland-China campus loop from July 2020 with a first and a second technical round. It establishes the process-versus-thread, XSS, CSRF, keep-alive and HTTP/2 questions, the event-loop puzzle, the thousands-separator task, and the second round's React, diffing, 304 and "a user reports a button that cannot be clicked" questions; it cannot establish the current campus format.
One self-reported 2020 spring campus first round in mainland China. It establishes the caching headers (If-None-Match and If-Modified-Since), the centring question, Vue basics, the promise-chain output and the count-the-smaller-elements algorithm; a Shopee frontend employee corrects the candidate's caching answer in the comments.
One Taiwanese new graduate's Singapore backend campus loop from spring 2020, read for the campus shape only: an application on 23 March, an HR call on 14 April, three technical rounds of 90, 90 and 60 minutes on a shared editor with a design-concept question in each, and a verbal offer on 28 April. It is not a frontend loop and names no frontend question.
One Taiwanese new graduate's Singapore campus backend loop from January 2022, read for the campus shape only: a 70-minute online assessment with ten multiple-choice questions and two coding problems, one 90-minute technical round conducted entirely in English, and a rejection sixteen days after applying. It is not a frontend loop.
Official page, read in Chrome on 21 October 2026. It lists five steps (Apply, Getting to Know You, Putting Your Skills to the Test, Meet the Hiring Manager, Preparing to Join Us) and answers that "The number of rounds varies depending on the role and seniority."; it names no frontend format or question.
A reprint, on a third-party campus site, of a Shenzhen Shopee campus posting for 2027 frontend development engineers in Beijing, Shanghai and Shenzhen, posted in April 2026, with the process line "网申/内推 > 笔试（部分岗位不设笔试） > 2-3轮专业面试 > HR沟通 > Offer" (online application or referral, a written test that some roles skip, two to three technical rounds, an HR conversation, offer). The site states that it is a reprint; the line is the only official-origin frontend process description and applies to mainland China.
Published by Shopee
Shopee publishes these pages itself. They describe the process and expectations in the company's own words; they do not list interview questions, and FrontendAtlas is not affiliated with Shopee.
| Page | What it covers | Checked |
|---|---|---|
| How we hire | Shopee's five hiring steps: Apply; Getting to Know You (a conversation with a recruiter); Putting Your Skills to the Test (depending on the role, additional tasks or assessments such as a coding, technical or role-specific assessment); Meet the Hiring Manager (questions about experiences, hypothetical scenarios or role-specific cases); and Preparing to Join Us (the offer by phone or email). Its FAQ says the number of rounds varies depending on the role and seniority and that the recruiter shares the details. | Oct 2026 |
Full company practice
This public guide is complete enough to plan a focused week. Premium unlocks the memoisation drill, the deep clone drill, the React nested comments tree and the wider premium library of coding, concept and system-design practice.