A job listing’s technology section is usually the most concrete signal in the posting, more concrete than the title, but it still needs reading against what each name actually implies rather than taken at face value.
An engine name is the strongest signal, because it tells you something about the team’s actual day-to-day tools, not just its ambitions. A listing naming Unreal Engine points to a studio whose economics eventually track revenue past $1,000,000 in lifetime gross, per Epic’s own End User License Agreement, at which point a standard license owes a royalty, 5% of further revenue, reduced to 3.5% for a release on the Epic Games Store no later than anywhere else. A listing naming Unity points to a studio whose obligations instead scale with company revenue and funding rather than a single product’s earnings: Unity Personal stays free under $200,000 in trailing revenue or funding, Unity Pro is required above that, and Unity Enterprise, with custom pricing, is required past $25,000,000 in annual revenue. A listing naming Godot points to a studio under neither structure at all, since Godot’s MIT license lets a studio use, modify and ship commercially without paying anything or asking permission, the tradeoff for that freedom being no vendor to build on, no shared licensing pool of contractors already fluent in the engine’s specifics, and a smaller ecosystem of paid tools and marketplace assets than Unreal or Unity carry. A listing naming none of the three, describing a proprietary or in-house engine instead, usually signals a larger studio with a long-running franchise, deep enough pockets to have built and maintained its own tools rather than licensed someone else’s, and a technical stack that’s specific to that one studio rather than transferable the way Unreal or Unity experience is.
Cloud and backend mentions carry much less specific information than they look like they do, because the market for game backend infrastructure is concentrated among a small number of vendors serving nearly the whole industry. AWS’s own GameTech pages describe cloud infrastructure supporting titles across the size spectrum, citing Amazon GameLift’s server hosting scaling to “100 million concurrently connected users per game” and naming Fortnite, Roblox and League of Legends among titles built on its infrastructure, alongside dedicated partnerships with both Epic’s Unreal Engine and Unity for asset and build pipelines. A listing mentioning “AWS,” “cloud infrastructure” or “live services” is naming the same small set of vendors most of the industry already uses for the same purposes, dedicated game servers, matchmaking, player analytics, rather than something unique to that studio; it tells you the studio runs live services of some kind, which a “live game” or “games as a service” job title usually already implied, more than it tells you anything else about the specific technical work on offer.
What a stack section reliably won’t tell you is scope or seniority; a listing naming the same engine, the same cloud vendor and the same handful of tools can describe work ranging from a small maintenance patch team to the core engineering group building a franchise’s next major release, and that distinction usually lives in the job’s actual responsibilities section, not its technology list. Reading a listing’s stack well means treating it as a filter for what kind of technical environment you’d be working in, engine licensing model, in-house versus vendor tooling, live service or not, and reading everything else, scope, team size, seniority, from the rest of the posting instead.