Game Play Tester & Use-Case Developer
Budget: $250 – $750 USD
We are developing a browser-based action/building game and are looking for an experienced gamer to help us refine gameplay through structured testing and documentation.
This role does not require programming experience.
We need someone who understands how games are supposed to feel, function, and flow — and can clearly document where reality differs from design intent.
What You’ll Be Doing
You will:
Play early builds of the game extensively
Document intended gameplay use cases (what should happen)
Identify inconsistencies, friction points, and broken mechanics
Compare expected vs actual behavior
Suggest improvements from a gamer’s perspective
Record short screen captures when helpful
Write structured reports for the programming team
What We Need From You
Formal Gaming Experience (Required)
You must have:
Competitive or structured gaming experience
Experience in multiplayer, shooter, building, or strategy games
Strong understanding of game mechanics, flow, pacing, and player psychology
Ability to articulate why something feels “off”
Examples of relevant experience:
Competitive FPS games
Fortnite-style building mechanics
Arena-style PvP games
Survival / sandbox games
Game balancing and meta awareness
Core Skill: Use Case Thinking
We need someone who can document scenarios like this:
Expected Behavior:
When a player presses the wall-build key while aiming at valid terrain, a wall should place instantly and snap to grid alignment.
Actual Behavior:
Wall sometimes places partially inside terrain, sometimes delays 300–500ms, occasionally fails without feedback.
Impact:
Breaks build rhythm. Makes combat unreliable.
Severity: High (combat-critical mechanic)
This type of documentation is exactly what we’re looking for.
Deliverables
Structured Use Case Documentation (Word doc or google doc)
Bug / Behavior Reports
Gameplay Flow Reports
Friction Analysis (What breaks immersion?)
“Feels Wrong” Documentation (even if not technically broken)
Suggested Improvement Notes
Ideal Candidate
Competitive gamer mindset
Detail-oriented
Strong written communication
Analytical thinker
Comfortable explaining gameplay systems clearly
Not afraid to critique mechanics
What This Is NOT
Not a coding job
Not graphic design
Not story writing
Not casual playtesting
This is structured, professional-level gameplay analysis.
Bonus If You Have
QA testing background
Experience writing bug reports
Experience in early access or alpha builds
Game design education or training
Familiarity with documenting reproducible steps
This role does not require programming experience.
We need someone who understands how games are supposed to feel, function, and flow — and can clearly document where reality differs from design intent.
What You’ll Be Doing
You will:
Play early builds of the game extensively
Document intended gameplay use cases (what should happen)
Identify inconsistencies, friction points, and broken mechanics
Compare expected vs actual behavior
Suggest improvements from a gamer’s perspective
Record short screen captures when helpful
Write structured reports for the programming team
What We Need From You
Formal Gaming Experience (Required)
You must have:
Competitive or structured gaming experience
Experience in multiplayer, shooter, building, or strategy games
Strong understanding of game mechanics, flow, pacing, and player psychology
Ability to articulate why something feels “off”
Examples of relevant experience:
Competitive FPS games
Fortnite-style building mechanics
Arena-style PvP games
Survival / sandbox games
Game balancing and meta awareness
Core Skill: Use Case Thinking
We need someone who can document scenarios like this:
Expected Behavior:
When a player presses the wall-build key while aiming at valid terrain, a wall should place instantly and snap to grid alignment.
Actual Behavior:
Wall sometimes places partially inside terrain, sometimes delays 300–500ms, occasionally fails without feedback.
Impact:
Breaks build rhythm. Makes combat unreliable.
Severity: High (combat-critical mechanic)
This type of documentation is exactly what we’re looking for.
Deliverables
Structured Use Case Documentation (Word doc or google doc)
Bug / Behavior Reports
Gameplay Flow Reports
Friction Analysis (What breaks immersion?)
“Feels Wrong” Documentation (even if not technically broken)
Suggested Improvement Notes
Ideal Candidate
Competitive gamer mindset
Detail-oriented
Strong written communication
Analytical thinker
Comfortable explaining gameplay systems clearly
Not afraid to critique mechanics
What This Is NOT
Not a coding job
Not graphic design
Not story writing
Not casual playtesting
This is structured, professional-level gameplay analysis.
Bonus If You Have
QA testing background
Experience writing bug reports
Experience in early access or alpha builds
Game design education or training
Familiarity with documenting reproducible steps