Technology & Gaming

Source: reference/verticals/tech-and-gaming.md · synced 2026-06-12

Vertical encyclopedia for the rubric and outreach engines. To be populated with Calibre’s domain expertise during the build phase.

Scope

Companies and roles across:

Software product companies (SaaS, infra, platforms)
Gaming studios (AAA, mobile, indie, publishers)
Fintech, climate tech, AI/ML companies
Tech-enabled scale-ups
Game services (LiveOps, publishing, art outsourcing, QA)

Adjacent: VC-backed start-ups, tech consultancies.

Sub-Functions

To be filled with Calibre’s input:

Engineering (backend, frontend, full-stack, mobile, infra, DevOps, ML)
Product management
Design (product, game, UX)
Data (engineering, analytics, science)
Game-specific (LiveOps, narrative, game design, art, animation, audio)
Go-to-market (sales, marketing, customer success)
Leadership (CTO, VPE, Head of Studio, etc.)

Common Titles (with seniority signals)

To be populated. Seniority signals differ between tech (IC track: Engineer → Senior → Staff → Principal) and management track (TL → EM → Director → VP).

Skills, Tools, Certifications

To be populated. Tech: language fluency (Python, TypeScript, Go, Rust, Java, C++), frameworks, cloud (AWS, GCP, Azure), data tools. Gaming: engines (Unreal, Unity, custom), game programming patterns, live service operations.

Industry Jargon

To be populated. Tech: SLO, MTTR, P95, DAU/MAU, NRR, ARR. Gaming: LiveOps, gacha, F2P, monetisation curve, retention curves, K-factor, time-to-fun.

Career Trajectories

To be populated. IC vs management track moves, startup-to-big-tech transitions, gaming-specific paths (publisher to studio, etc.).

Red Flags

To be populated.

Outreach Tone Notes

To be populated. This vertical is the most outreach-saturated — candidates ignore generic messages immediately. Specificity to their actual work (recent shipped projects, GitHub, tech blog posts) is essential.

This file is a stub. Replace with real content via interview session with Calibre and the Calibre team.