YouTube Researcher

Please login or register as jobseeker to apply for this job.

TYPE OF WORK

Any

SALARY

$50 to $80 USD per approved topic

HOURS PER WEEK

TBD

DATE UPDATED

Jul 27, 2026

JOB OVERVIEW

WHO WE ARE
NIA Production is a YouTube conglomerate. We own, build, and operate our own channels in-house. Every channel we run is ours.
You can see our work at ----------

We are 90+ people strong and growing rapidly. Most of our team is hybrid and we hire globally. We move fast. We care about results, and we hire people who think the same way.

WHY THIS ROLE EXISTS
Every video we make starts with a case worth telling. Finding those cases is the bottleneck. Most of what looks promising falls apart on contact: the story is exaggerated, the footage does not exist, the clip has been deleted, or a competitor covered it two years ago.

Your job is to find real, unsettling, usable cases and prove they are real before anyone spends time on them. You are the filter that stops the rest of the team from building on sand.
You are not doing the deep dive. Once we green-light your finds, a separate researcher takes them further. Your value is in breadth, speed, and judgment: how much good raw material you can surface, how fast, and how reliably it survives scrutiny.
Our channels in this category, and the direct competitors we benchmark against:
Chilling Scares
Nick Crowley
Farrel McGuire
You will be expected to know this landscape well enough to tell instantly whether an idea has already been used.

HOW THIS ROLE WORKS
Each assignment follows the same cycle:
Brief. You receive a topic plus reference videos that establish the tone and style to match.
Scouting (24 hours). You deliver 35 to 40 segments per topic using our template. Rough but smart. For each one you prove four things: the case is real, it is genuinely unsettling, there is enough usable footage to build around, and your links plus timestamps let us verify it in minutes.
Green-light. We approve 30 or more segments from your batch.
Handoff. Approved segments go to our deep-dive researcher, who builds the full package. You may get short follow-up questions, then you move to the next topic.
Feedback. You act on notes fast, so each segment batch needs fewer feedback than the last.

RESPONSIBILITIES
Find the segments. Search across platforms and the less obvious corners of the internet to surface real clips and real cases. Not listicle material that has already circulated. Each topic needs 35 to 40 segments that are genuinely different from each other, so we get real options instead of one idea in eleven variations.
Check that they hold up. Three things have to be true before a segment reaches us: the story is real and traceable to a credible source, the footage still exists and can be downloaded, and no competitor has covered it. Screening against Nexpo, Nick Crowley, and Farrel McGuire is your job, not ours.
Judge whether it will work on screen. A strong story with 20 seconds of usable video is not a segment. You need at least 2 to 3 minutes of core footage, and you need to be able to say what the specific ---------- nt is that makes it land for a viewer.
Deliver it clean and on time. Submit in our template with links, timestamps, why it fits, why it is unsettling, and how it supports the narrative. Pass 100% of the checklist every time. Hit your dates, because production downstream is scheduled around them.

WHAT THIS ROLE IS NOT
Not deep-dive research. You are not building the full source package, the timeline, or the script beats. You prove a segment is worth that investment. Someone else makes it.
Not a writing role. No scripting, no narration, no drafting.
Not a volume game. You are paid per approved topic, so sending us twelve weak ideas to sort through is worse than useless. Filtering is the job.
Not passive. If a topic we assign is thin, say so early instead of delivering twelve mediocre segments and letting us find out.

REQUIREMENTS

Must-Have:
Strong internet research instincts. You know how to find things that are not on the first page of Google, including archived pages, deleted uploads, reverse image search, and old forum threads.
Basic source sense. You can tell a primary source from a repost of a repost, and you do not treat the second as the first.
Familiarity with this YouTube niche and its major channels, enough to recognize covered ground immediately.
An eye for what actually unsettles a viewer, and the ability to explain why in specific terms rather than saying a clip is creepy.
Reliable under a 24 to 36 hour clock. Clear written communication, no chasing required.

Nice-to-Have:
Any past research work where you had to verify information
Awareness of what footage is usable in an edit, not just what exists.
A real, pre-existing habit of going down internet rabbit holes, especially in the YouTube landscape. Hard to fake, obvious when it is genuine.

RESULTS
Success in this role is measured by:
Your approval rate climbs and holds. Most of what you send is usable, rather than most of it being filtered out by us.
Nothing you submit is later found to have been covered by a competitor.
Nothing you flag falls apart when the deep-dive researcher picks it up, whether that is a claim that does not check out or footage that turns out to be unusable.
Your segments are diverse enough that we can pick 5 to 7 without them overlapping.
Your turnaround dates hold consistently, so nothing downstream waits on you.
The amount of feedback you need decreases topic over topic.

APPLICATION

We require a simple test project to gauge fit for the role. It is one topic, and it is the only reliable way for us to see how you actually hunt, since a CV cannot tell us whether you can find what is not on the first page of Google.

VIEW OTHER JOB POSTS FROM:
SHARE THIS POST
facebook linkedin
  BENCHMARKS  
Loading Time: Base Classes  0.0011
Controller Execution Time ( Jobseekers / Job )  0.0185
Total Execution Time  0.0204
  GET DATA  
No GET data exists
  MEMORY USAGE  
1,513,024 bytes
  POST DATA  
No POST data exists
  URI STRING  
jobseekers/job/YouTube-Researcher-1696978
  CLASS/METHOD  
jobseekers/job
  DATABASE:  onlinejobs (Jobseekers:$db)   QUERIES: 13 (0.0109 seconds)  (Hide)
0.0004   SELECT *
                                
FROM exrates
                                WHERE rate_name 
'USD-PHP' 
0.0004   SELECT *
FROM `employer_jobs`
WHERE `job_id` = 1696978
 LIMIT 1 
0.0004   SELECT *
FROM `employers`
WHERE `employer_id` = 861643
 LIMIT 1 
0.0008   SELECT COUNT(*) AS `numrows`
FROM `t_thread` `t`
LEFT JOIN `t_thread_misc` `miscON `t`.`id` = `misc`.`thread_id`
WHERE `t`.`job_id` = 1696978
AND `misc`.`idIS NULL 
0.0004   SELECT e.business_namee.logoe.websitee.rebill_datee.date_added member_datehitsDATEDIFF('2026-08-12',ej.date_added) duration_daysDATEDIFF('2026-08-12',e.rebill_date) duration_rebillej.*, e.deactivate FROM employers eemployer_jobs ej WHERE e.employer_id ej.employer_id AND
                                   ((
e.user_level >= '500' AND ej.date_added <= e.rebill_date)
                                   OR 
e.employer_id '' OR (ej.date_approved <> '2000-01-01' and DATEDIFF('2026-08-12',ej.date_added) <= 14 ))
                                   AND 
e.deactivate != AND ej.deleted AND job_id '1696978' 
0.0004   SELECT *
FROM `employer_jobs_skills` `ejs`
LEFT JOIN `skills_categories` `scON `ejs`.`skill_id` = `sc`.`id`
WHERE `job_id` = 1696978 
0.0007   UPDATE employer_jobs SET hit_counts '***Jul-27-2026=920***Jul-28-2026=103***Jul-29-2026=29***Jul-30-2026=22***Jul-31-2026=11***Aug-01-2026=11***Aug-02-2026=13***Aug-03-2026=5***Aug-04-2026=15***Aug-05-2026=7***Aug-06-2026=8***Aug-07-2026=8***Aug-08-2026=2***Aug-12-2026=1' WHERE job_id'1696978'  
0.0005   UPDATE employer_jobs SET monthly_hits '***Jul-2026=1085***Aug-2026=70' WHERE job_id'1696978'  
0.0007   SELECT date_sent FROM jobseeker_sent_emails WHERE jobseeker_id '' AND job_id '1696978' AND status LIKE 'sent%' ORDER BY id DESC  
0.0003   SELECT *
FROM `employer_jobs_skills` `ejs`
LEFT JOIN `skills_categories` `scON `ejs`.`skill_id` = `sc`.`id`
WHERE `job_id` = 1696978 
0.0050   SELECT COUNT(*) AS `numrows`
FROM `employer_jobs`
WHERE `employer_id` = '861643'
AND `date_added` >= '2022-06-08' 
0.0004   select from teasers 
0.0004   SELECT FROM skill_categories WHERE skill_cat_id='' 
  HTTP HEADERS  (Show)
  SESSION DATA  (Show)
  CONFIG VARIABLES  (Show)