Job search
How to Use gamedevmap to Find US Studios That Job Boards Miss
A bounded Austin directory-to-employer audit and completed tools-engineer shortlist explain company discovery without claiming exclusive job-board coverage.
A job board begins with advertised vacancies. gamedevmap begins with organizations: developers, publishers and other parts of the game-development ecosystem. That makes it useful for building a company list you might not have thought to search, then following each company to its own hiring route.
“Job boards miss” here means an additional discovery method, not a measured claim of exclusive vacancies. We did not compare a defined set of job-board searches. This guide follows an actual US directory search and three company checks made on October 20, 2026; a directory row is never counted as an open job.

Use company discovery alongside current vacancies. Recently posted roles on LandOffer.ai provide another starting point for comparing the actual responsibilities, geography and application routes you find.
Start with the directory’s unit: an organization
gamedevmap’s public explanation describes a curated directory of game-development organizations. It includes developers, publishers and several ecosystem categories. Its stated exclusions include tool vendors and service providers without primary authorship; inclusion is discretionary. Do not interpret those criteria as an independent audit of every company’s current business.
An organization can appear because it develops games, publishes other teams’ games or supports the ecosystem. That tells you something about where to investigate, but not whether it needs your particular skill today. A company may be active with no public openings, or have a general application route without a named programming vacancy.
A directory location is also not a hiring-location promise. It can describe an office or organizational presence. A role can have a different schedule, permitted geography or remote-work condition. Establish those from the employer’s current job description rather than carry the map’s city into an assumption about eligibility.
First build a company list. Move an entry into your application shortlist only after finding a role and assessing its conditions.
Reproduce a bounded US search
In the native browser, we selected United States in Browse by Country / Region. The US results exposed state and type controls. We then selected Texas and Austin using the displayed selectors and read the resulting company table.
That sequence is reproducible without treating the whole database as your to-do list. Choose a geography you can realistically consider, inspect the available organization types and begin with a small group of companies. Save the country, state, city and organization type with your notes so you can repeat the search and explain each inclusion.
For this guide, we deliberately selected Retro Studios, Devolver Digital and Lost Boys Interactive from the Austin results. The selection compares different kinds of hiring evidence; it is not random and does not represent every Austin studio or US game employer.
A type filter can narrow the list, but keep the company’s own description in view. Directory categories can be broad, company ownership can change and a business can perform several kinds of work. The next stage resolves those distinctions rather than assuming the table has already done so.
Worked company audit: three entries produce three hiring states
We followed the directory’s company website destinations, then inspected official careers routes. These are point-in-time public checks, not verification of unfilled headcount or a test of application submission.
| Directory discovery | Official route inspected | Completed result |
|---|---|---|
| Retro Studios (Nintendo), listed as a developer in Austin | Retro website → Nintendo’s Retro careers page → named engineering role | A specific programming opportunity to evaluate, with its own requirements and on-site condition. |
| Devolver Digital, listed as a publisher in Austin | Official site → Jobs page | The rendered page said “No Open Positions.” Keep as company research, not an active programming lead. |
| Lost Boys Interactive (Embracer Group), listed as a developer in Austin | Current studio site → careers page | Careers showed General Application, not a named programming vacancy; the current company description also required updating the ownership note. |
Retro’s site linked to Nintendo’s careers site. There we found Tools Engineer — Systems, identified as Retro Studios, Austin, on-site. The description covered tools, applications, libraries and plugins for content creation, with lifecycle ownership and technical leadership. That named employer page supplied the programming responsibilities and work-location condition needed for a role-level review.
Lost Boys’ current website described game development and co-development partnerships, and said it had returned to independent founder-led ownership. That differed from the parent-company wording in the directory entry. The difference does not establish that the studio is inactive or unsuitable. It shows why an ownership label should be rechecked before identifying the employer.
The company’s careers page listed a remote General Application. That is a route for expressing interest, not evidence of a particular programming team, seniority level or immediate opening. We did not submit to it or test whether it produces contact.
Devolver’s page supplied a different answer again: no open positions were displayed on the inspected jobs page. That is a current page observation, not a claim about every company in its portfolio or every future opportunity. A publisher’s catalog should not be converted into programming vacancies at the publisher itself.
The audit ends with one named role to evaluate and two company records with different follow-up states. It does not end with three jobs.
Check the work behind the company category
A developer may build its own title, work on licensed IP or support another studio’s production. A publisher may handle distribution, funding, marketing or other functions while a separate team writes the game. A co-development studio can offer substantial engineering work, but its client/project arrangement may differ from owning a product internally.
Use these distinctions to identify the engineering work you want. If you want gameplay implementation, read for gameplay systems and the team’s code ownership. If you want tools, read for content workflows, editor integrations and support responsibilities. If you want backend services, identify the actual systems rather than infer them from a game genre.
Verify the hiring organization as well as its engineering work. Parent ownership, studio branding and the application entity can differ. Keep the current official wording and the careers destination together so a later conversation concerns the right organization.
If a site fails to load, record that as an unavailable check. It does not prove the company closed. If you find credible current closure or acquisition information, reconcile the company record before treating an old name as an active employer. This review does not label a company inactive merely because one automated request failed.
Worked candidate shortlist: tools experience meets a concrete route
Mara is a fictional engineer living near Austin who can consider on-site work. They have eight years building C# internal applications, including WPF interfaces and asset-validation tools used by a simulation team. They have maintained build workflows and documented tools for artists, but have not shipped a commercial console game.
Mara uses the three audited companies to complete a shortlist. The candidate facts and decisions are invented; they are not an employer evaluation or a claim that the candidate meets every requirement.
| Company or route | Mara’s completed decision | Evidence or unresolved condition |
|---|---|---|
| Retro’s named tools opening | Prioritize a full requirements review and prepare tools-lifecycle examples | Austin on-site is acceptable; related tools and WPF work are relevant, while seniority and game-production experience need an honest comparison. |
| Devolver jobs page | Keep in a company watchlist, not an application queue | No open positions were displayed during this check. |
| Lost Boys general application | Keep as a separate, optional expression-of-interest decision | No specific programming vacancy, team or scope was established. Mara has not chosen to submit a general profile. |
| Directory ownership label | Update the research note before using it in an application discussion | Current Lost Boys site describes independent founder-led ownership. |
The Retro description preferred 10–15 years in game development or a related industry and listed WPF and build-system experience among preferred areas. Mara does not rewrite eight years as twelve, or describe simulation tools as a shipped console title. They prepare a factual comparison and decide whether their actual scope supports an application after reading the full current role.
Their completed project note reads:
Built and maintained a C# WPF asset-validation tool for a simulation content team. I gathered workflow requirements, implemented validation rules, documented the tool and handled later changes from users. I also maintained build-workflow integration. I have not shipped a commercial console game.
That note describes Mara’s tools ownership and makes the missing console-shipping experience explicit. Mara can attach a permitted example or describe the design decisions in an interview, while keeping private assets and internal links out of shared materials.
Mara also finishes the next action: review the named Retro role’s full requirements and current application route, then make an application decision. They do not count Devolver’s company record or Lost Boys’ general pool as additional active tools vacancies. No application was submitted for this guide.

Keep company discovery and job verification in separate records
For a company, record its directory name, location, type, website and current identity note. For a vacancy, record the exact employer role URL, title, location condition and date checked. A company can have several vacancies, and several directory entries can point to one organization’s broader careers system.
This separation helps with both duplication and changes. If another job board later surfaces the same employer role URL, update the existing opportunity instead of counting a new job. If the company changes ownership or careers provider, preserve the history while checking the new route.
A general application deserves its own label. It can be a legitimate way to express interest, but it does not supply the scope and timing of a named vacancy. Decide whether that route suits your search and what information you are willing to provide before using it.
Likewise, a game-pitch form, business-development contact, newsletter and recruitment application serve different purposes. Do not send a resume through a publisher’s pitch route because it happens to be prominent on the site. We used only public pages and did not contact any organization.
Make “additional discovery” measurable in your own search
You can evaluate the directory without claiming it contains exclusive opportunities. Begin with a bounded geography and record a small set of companies you had not already examined. For each, finish the website, identity and careers check.
Then distinguish the outcomes: named role worth reviewing, no current openings displayed, general application only, unresolved destination or company outside your target. The useful result is a better company map and a manageable set of verified next actions, even if some rows produce no application.
To measure what job boards actually missed, you would need a defined comparison: named boards, exact queries, location settings and a date window. This guide did not perform that experiment. A company newly discovered by one candidate is not necessarily absent from every job board.
The directory says it uses monthly data drops and community input. Treat that as its stated maintenance process, not a guarantee that each record reflects today’s ownership or hiring status. The observed ownership difference and three distinct careers results explain why a second-stage check remains necessary.
Use the map to find companies, then use evidence to choose roles
gamedevmap can broaden a US company-discovery routine beyond the vacancies currently visible in your usual search. Its geography and organization categories help you decide where to look; official company and careers pages determine what you can evaluate next.
Choose a region you can work in, select a few organizations and trace each to its current careers destination. Preserve developer, publisher and co-development distinctions. Keep a company with no displayed opening out of the active-job count, and compare a named role with your actual experience and location constraints.
For current vacancies alongside that research, browse recent LandOffer.ai roles. Whether a lead begins on a map or a board, verify the employer route before applying and keep the result at its actual level of certainty.
Sources and Further Reading
- gamedevmap and US directory results — directory scope and discovery route.
- Retro Studios careers and Tools Engineer — Systems — named programming route and role conditions.
- Devolver jobs — rendered no-open-positions observation.
- Lost Boys Interactive and careers — current identity, co-development context and general application route.
Checked October 20, 2026. No application, general-profile submission, account, contact or job-board exclusivity test. Mara is fictional. Company details and vacancies can change after the check.


