Technical Writer & QA Engineer:

- Location: Vancouver, BC, Canada (On - Site)
- Employment Type: Full-time, Permanent
- Experience Level: Junior/Intermediate

Company overview:

- Established in 2010, Omega Gaming (Malta) Ltd. was founded by a team of seasoned executives, project and product managers, and skilled software engineers. Building on our extensive industry experience and proprietary technology, we deliver the OMEGA CORE Management System — a comprehensive solution featuring:
- A comprehensive, managed back office for player and promotion management
- An open architecture for seamless integration of gaming products
- A robust player services module
- A secure, fully managed transaction server supporting diverse payment solutions
- The OMEGA CORE system also enables integration with jurisdictional regulators and incorporates full responsible gaming capabilities. Beyond infrastructure solutions, Omega Gaming develops cutting-edge games, gaming systems, and platforms tailored for the regulated online gaming industry.
- To ensure compliance with regulatory frameworks, Omega has successfully deployed multiple instances of the OMEGA CORE Management System and integrated various Payment Gateways, KYC Providers, and Affiliate Management Solutions.

About the role:

- We build a lot of software, and we're missing the person who makes it understandable and makes sure it works. That's two jobs that are really one instinct: catch what's wrong or unclear before a user does.
- You'll write the docs people actually rely on, and you'll test the product so the gaps show up in your hands, not theirs.
- This is B2B iGaming, so both halves carry real weight. OMEGA is a PAM (Player Account Management) platform; your docs are used daily by the operations teams at our clients — the casino and sportsbook operators who run their business on it — and by internal teams, from support to marketing. And your bugs aren't all equal:



a confusing guide costs a support ticket; a self-excluded player who can still place a bet is a compliance incident for our client. You're the person who catches both before they ship.
- We have plenty of developers. We need the person who turns what they build into something a wide range of people can understand and trust.

What you'll own:

- Documentation that's actually used. Operator-facing guides for our clients' operations teams, internal references, release notes, process docs — written clearly enough that a client operations manager, a support agent, an engineer, and a marketing teammate each get what they need.
- Writing for a wide audience. You adjust depth and language to the reader. The same feature reads one way for a client's operations team, another for our engineers, another for marketing — three versions that all land.
- Hands-on QA. Manual and exploratory testing, clear reproduction steps, and clean bug reports a developer can act on without a back-and-forth.
- Keeping docs and reality in sync. When the product changes, the docs change. You catch the drift before support tickets do.
- Being the early signal on quality. You're often the first person to use a feature the way a client's operations team — or one of their players — would, and you say so when it's not ready.
- Driving internal projects when they need an owner. From time to time you'll project-manage an initiative end to end — a product certification with a regulatory or compliance body, a product training rollout — keeping the plan visible, the people aligned, and the follow-ups closed.

Qualifications:

Essential:

- Strong technical writing. You make complicated things explicit,



and you write for the reader in front of you, not for yourself.
- QA and testing skills. You test like a careful, slightly suspicious user. You find the edge case, reproduce it reliably, and report it cleanly.
- Experience with both technical and business teams. You've worked directly with engineers and with business stakeholders, and you adapt your language to the target audience — engineer to exec to end user, you meet each where they are.
- Technical background. Enough to understand what you're documenting and testing, read a ticket, follow how the pieces fit, and not get hand-waved past a real problem.
- Productive with AI, skeptical of it. You use AI tools to draft, research, and test faster — and you treat the output as a starting point, not the truth. You verify against the real product and apply your own judgment before anything ships.
- Ownership and integrity. You take the work personally, you finish it, and you tell the truth about whether something's ready even when it's inconvenient. In a regulated space, that honesty isn't a nice-to-have — it's the job.

Preferred:

- Project coordination: driving alignment across teams, keeping people in the loop, spotting risk early.
- Familiarity with the mechanics this space runs on: bonuses and wagering requirements, responsible-gambling controls, KYC and age verification, odds and payouts.

Open to Graduates:

- Recent graduates are welcome to apply (an academic transcript is required).

Technical Writing Sample:

- Candidates must submit a technically oriented writing sample that demonstrates transparent, effective communication of complex topics.

What this role is not:

- A developer seat. Our dev bench is deep. This role makes what they build clear and correct.

Please Apply Here:

To be considered for the first stage of the interview process, please complete your application via the link below:

https://forms.gle/ZE1Df7REz8phaMmp6

📌 Technical Writer & QA Engineer (Vancouver)
🏢 OMEGA Systems
📍 Vancouver