PUBGM NS Creator Review Test — Candidate Onboarding Guide
This is a short briefing to help you take the review test fairly, even if you have not previously worked inside the NextStar program. Please read it before starting.
What is NextStar?
NextStar is a creator incentive program for PUBG MOBILE. Content creators sign up, choose a task (“brief”) published each week, make a short video about it, and submit it via the Creator Hub platform. If the submission meets the brief’s requirements, the creator is rewarded based on the views the video gets.
Each submission goes through a reviewer (the role you are applying for). The reviewer’s job is to decide whether a submitted video meets the brief’s requirements, and choose one of four decisions.
Your role in this test
You will be shown 40 real submissions from Myanmar creators. For each one, you will see:
- The task brief / requirements (what creators were asked to make a video about)
- The submission time, platform, view count and like count
- The caption exactly as the creator wrote it — including Burmese. Read it.
- A button to open the video (you must click it — the brief, the caption and the hashtags together are still not enough to decide)
You then pick one of 4 decisions, and for anything other than Approve you write down why. The test takes ~1 hour; budget about 60–90 seconds per item if you take it seriously.
Your written reasons matter as much as your decisions
For Return, Reject and Escalate you must pick a reason and write a short explanation, the same way the real Creator Hub console works. We read those explanations. Naming the specific thing you saw in the video (“the promoted set never appears”, “the caption insults another country”) counts for far more than the decision button alone — and a correct-looking decision with an empty reason counts for very little.
The 4 decision keys
This is the most important part. Each decision has different consequences for the creator. Please read carefully.
| Key | What it does to the creator | Use when |
|---|---|---|
| ✅ Approve 通过 |
The work counts, and the creator is rewarded based on its views. | It does what this task asked for, and there is no violation. |
| ↩️ Return 退回 |
The creator gets your reason and must submit the work again before it can be reviewed. You cannot flip a returned work to Approve yourself. | It is PUBG MOBILE content, but it is not what this particular task asked for — so there is somewhere else for it to go, or something the creator can add and come back with. |
| ❌ Reject 驳回 |
The work earns nothing, its data is not recorded, and the creator cannot move it to another task. | There is nothing to salvage — see the list in section 4. Use it when the work should not be on the platform at all, not when it is merely in the wrong place. |
| ⤴️ Escalate 上报主管 |
Nothing happens to the work yet. It goes to your immediate manager with your note. | The work does not break a rule, but whether it should be published publicly is a call above your level. You neither approve it nor kill it yourself. |
Key distinction: Return vs. Reject
This is the single most important judgment in the role, and the one most reviewers get backwards.
- Return = “this belongs somewhere else, or needs one more thing.” The content itself is fine.
- Reject = “this should not exist here.” There is no other task it could go to.
Do not treat either one as the safe default. Rejecting fixable work destroys a creator’s effort for no reason; returning a real violation quietly lets it through. Both directions are mistakes, and we look at both.
Escalate is not a “skip” button
Escalate is for the narrow case where the content is legitimate but publishing it is a judgment call that is not yours to make. It is not a place to park items you did not want to look at properly — the note you write is read, and “not sure” is not a note.
Task categories
Every task sits in one of three tracks, and the track decides what content is eligible at all:
| Track | What qualifies |
|---|---|
| Classic / Main | Any PUBG MOBILE content — no mode restriction. This is the catch-all. |
| WOW | WOW Mode (World of Wonder) content only. |
| METRO | Metro Royale content only. |
Within a track, a task is either a General Task (any content for that track) or a specific task — a set to promote, an event to cover, a feature to demonstrate, a piece of official material to work from. For a specific task, “it is good PUBG MOBILE content” is not the question. The question is whether it does the thing this brief asked for. The brief is shown beside every submission; read it before you decide.
What is Reject-level
- No PUBG MOBILE content at all, or the task slot used to advertise something else
- Abuse, slurs, harassment, or national / ethnic provocation
- Adult, suggestive, or otherwise brand-unsafe content
- Suspected unfinished or unreleased material (placeholder text still on screen)
- Internal platform exposed — Creator Hub back-office screens, the task board, internal messages. The public Creator Hub short link (sg.creatorhub.pubgmobile.com/t/…) in a caption is an official promo link and is not a violation.
- The link does not open, so the content cannot be verified
Calls reviewers commonly get wrong
- AI-generated content is acceptable, as long as PUBG MOBILE elements are in it.
- Beta builds are public and are not a leak. Unfinished placeholder assets are.
- A low view count is never a reason to reject. Plenty of valid submissions get a few hundred views.
- A caption that copies the brief text, or leaves a placeholder unreplaced, is a minor issue — mention it if you like, but it is rarely the real problem with a submission.
- For an item or set promotion: merely wearing it while playing is not the same as showcasing it. And judge by the series, not the single piece.
What to look at on each submission
Review each submission in two stages:
Stage 1 — Read the brief, then read the caption
Work out what the task actually asked for before you form an opinion about the video. Then read the caption in full. Captions are shown in the creator’s own language; a submission can look perfectly normal and still say something in the caption that no reviewer should let through.
Stage 2 — Watch the video
Hashtags, thumbnails and view counts tell you almost nothing. Several of these submissions have perfect hashtags, the right track, and good numbers, and are still not what the task asked for — or should not be on the platform at all. The only way to see that is to watch.
Stage 3 — Decide, then say why
Pick the action, pick the reason, and write the specific fact that drove it. If you spotted more than one problem, say so — we would rather read two sentences than guess what you noticed.
You can revisit any question via the question grid on the left. Changing your mind is fine — the system tracks it but does not penalize you.
When you’re unsure — please ask
If anything about a brief, a tag, a mode, or the SOP feels unclear, message the recruiter on WhatsApp. We expect questions, and reviewers who clarify uncertainty are valued more than reviewers who guess silently.
Common things people ask about:
- “I don’t recognize this mode / this event — what is it?”
- “Is this a Return or a Reject? I can argue it both ways.”
- “The brief is ambiguous on point X — how should I read it?”
- “I don’t speak the language in this caption well enough to be sure.”
There is no penalty for asking. There is, in real reviewer work, a cost for not asking — because guessing wrong on hundreds of submissions per day silently harms creators.
About this test (transparency)
- Length: 40 submissions, ~60 minutes.
- You can pause and come back. Your progress is saved.
- These are real submissions with real outcomes. Roughly half of them are fine — this is not a test where everything is secretly broken, and rejecting your way through it scores badly.
- If a video will not open for you, decide what a reviewer should do with a submission that cannot be verified (section 4 covers it), say so in your explanation, and tell us afterwards.
- Behavior signals are recorded. This is not to catch you doing anything wrong — it is so we understand each candidate’s review style (some people walk linearly, some jump around; both are fine). What we look for is whether the candidate engages with the content rather than rubber-stamping.
One ask before you start
This role exists because creators put real effort into their submissions, and a careless reviewer can unfairly destroy that work. The best reviewers we have are not the ones with the most experience — they are the ones who slow down on ambiguity, use the whole toolkit rather than one favourite button, and ask before guessing.
Take your time. Ask questions. Use all 5 keys when appropriate. We are not measuring speed; we are measuring care.
Good luck, and thank you for taking the time.
Ready? Start the test
Open your track and begin. Sign in with any Google account — your email is your identity. Use the link your recruiter sent you.
T-REX Esports · PUBGM NextStar · LATAM Creator Community Manager