Teq Vault is still early. That means volunteer roles, remote collaboration, and credit on the products and IP you help improve — not a traditional payroll career page. If you care about finding the bug that only appears on one Android skin, or the lore inconsistency that breaks immersion on a second reading, this is for you.
Applications are reviewed as capacity allows. Strong reports, clear reproduction steps, and specific feedback matter more than a long resume. Successful testers and proofreaders often move into tighter circles of the project as the studio grows.
Game Tester
Stress-test mobile builds of Quetiemals, Forge & Ruin, and future titles. Identify mechanics-level bugs, balance issues, and provide UI/UX feedback across Android builds.
- Detailed bug reporting with reproduction steps
- Gameplay balance and difficulty feedback
- UI/UX and accessibility feedback
- Early access to unreleased builds
IP Proofreader
Review manuscripts across the Eyuforyia mythos and our standalone novels. Ensure grammatical precision and maintain narrative consistency across six finished books and expanding lore documents.
- Grammar, syntax, and style analysis
- Cross-book lore consistency checks
- Tone and voice alignment per IP
- Access to unpublished manuscript drafts
Software Beta Tester
Put TeqXus AI and TeqDocs through their paces. Test AI response quality, PDF rendering, document workflows, and edge cases across browsers, devices, and operating systems.
- Cross-browser and cross-device testing
- AI response quality and accuracy feedback
- PDF, Markdown, and Word document edge cases
- Free Pro access during testing period
The Circuit-Level Standard
"We don't just fix typos or find glitches — we optimize the infrastructure of immersion. If you have an engineering mindset for creativity and care deeply about quality, we want you in the Vault."
Game testers focus on mechanics, balance, and device-specific issues across live and in-development titles. Proofreaders work through manuscripts and in-game text for clarity, consistency, and lore fidelity. Software beta testers exercise TeqXus and TeqDocs under real conditions — browsers, files, edge cases, and AI response quality.
All roles are remote. At this stage they are volunteer, with product and IP credit where contribution is material. Expectations are written into each application path so you know what “good” looks like before you apply.