1. LandOffer
  2. Blog
  3. All articles
  4. Hitmarker vs. Work With Indies: Broad Game-Industry Roles or Small-Studio Projects?

Job search

Hitmarker vs. Work With Indies: Broad Game-Industry Roles or Small-Studio Projects?

Choose a game-job discovery source by the programming work you want, then compare distinct role identities and the engagement conditions each studio states.

10 min readLandOffer team

Start with Hitmarker when you want to explore programming work across studios, publishers, platforms and the wider games, esports and content industry. Start with Work With Indies when you specifically want to work on an independent game and examine its project brief. Then screen the actual responsibilities and engagement terms. Neither a Unity category nor an indie label establishes the programming work, location or contract you would accept.

This comparison uses official descriptions and public browser observations from October 13, 2026. We inspected real roles on both boards, original employer descriptions where identified, and a linked empty application form. We did not create profiles, subscribe, join communities or submit applications. The examples resolve source order and role screening; they do not measure interview rates, hiring speed or overall inventory completeness.

LandOffer publishes this comparison. You can also browse recent roles on LandOffer.ai, using the same work and location requirements. Choose the source that adds relevant employers or projects to your search, rather than treating every additional card as another usable opportunity.

Editorial illustration contrasting a broad game-industry search with a focused independent-game project search.

The two sources organize different searches

Hitmarker describes its scope as games, esports and content. Its public organization includes engineering alongside art, design, community and other functions. That breadth can help someone discover a platform team, a studio specialty or work supporting the wider industry. A software search still needs a narrower definition than “a job connected to games.”

Work With Indies describes a board and community focused on careers with independent game developers. Its Programming category groups opportunities across studios and engines. The Games With DNA example below names the game and immediate contribution, while leaving the agreed rate and exact engagement dates unanswered.

These are useful differences in focus, not guarantees about employment quality. Indie does not automatically mean a tiny team, creative control, stable funding or informal management. A large studio does not automatically provide a narrow specialty or permanent employment. Read the role's stated arrangement before making either assumption.

Both discovery paths were publicly readable during our review. We used Hitmarker's Unity page and selected its London location checkbox; the settled result showed 22 jobs. We also inspected Work With Indies' current Programming page, which displayed 16 entries. Those figures describe different public views, not an equivalent search experiment or counts of suitable programmer vacancies.

A Unity result can describe several kinds of work

Hitmarker's Unity category included art, management and programming. Its Software Engineering Manager, Web Platform description combined technical strategy for Unity's browser support with hiring, developing and managing engineers. If you want to implement gameplay without managing people, this role's responsibilities differ from that goal despite the familiar engine name. We read the board copy; we did not verify that role's original Unity requisition.

A second Hitmarker example, Senior Software Engineer, Match AI & Simulation, showed another distinction. The SEGA Careers original identified Sports Interactive, professional C++ and classical game AI as central requirements. Unity and C# were beneficial. The work involved football simulation, agent behavior and supporting tools; its London arrangement was hybrid, with remote work by exception.

An engine tag therefore should not become a qualification shortcut. A candidate with six years of C# gameplay work has not thereby demonstrated five years using C++ professionally or experience with behavior trees and simulation. Likewise, “remote by exception” does not mean an exception has already been approved for that applicant.

Work With Indies made a different project visible: Games With DNA's Unity Programmer. The advertised work concerned an existing branching-narrative game using Unity and NaniNovel. It was paid, full time, fully remote within the UK and approximately five months fixed term. The description requested relevant narrative experience and at least one shipped title as lead programmer. Familiarity with Unity alone would leave important evidence gaps.

Compare four role targets against one programmer's goal

Lewis is a fictional UK-based developer with six years of Unity/C# experience, branching-narrative work and one released game on which he served as lead programmer. He wants paid individual-contributor game programming, can consider a five-month project and intends to stay in the UK. He has not demonstrated the required professional C++ background for the simulation role.

The table uses four actual investigated targets. “Not seen” means absent from the specific saved view, not absent from an entire platform. Hitmarker's London filter also does not cover every UK remote listing. This is a completed screening example, not a ranking based on comparable total inventories.

Investigated role Hitmarker London view Indies Programming view Lewis's decision
Unity: Web Platform engineering manager Seen Not seen Exclude: he wants implementation work without people-management responsibility
Sports Interactive: Match AI & Simulation Seen under SEGA Not seen Exclude under his stated evidence: primary C++ and classical game-AI requirements remain unsupported
Games With DNA: Unity Programmer Not seen Seen Retain pending the rate, exact dates and written project scope
Skymap: Multiplayer Engineer, Unity Not seen Seen Exclude under the advertised Quebec residence condition

The four investigated targets are different work opportunities; none is a cross-board duplicate within this selected set. Lewis ends with one retained lead and three exclusions. He does not end with proof that Work With Indies has more suitable jobs overall. He has a concrete reason to investigate one indie project first.

Skymap demonstrates why the location screen stays separate. Its original employer page confirmed a remote multiplayer role for applicants residing in Quebec and authorized to work in Canada. Its Unity, C# and mobile networking requirements might interest a programmer elsewhere, but they do not override that geography. We read the public description without starting its application.

Lewis saves the DNA lead with its title, project, board URL and linked application destination. The other entries remain useful evidence of why he excluded them. If he later broadens his responsibilities or location, he can reassess the actual terms instead of remembering only that one board “worked better.”

Count role identities before counting additional opportunities

The Hitmarker London view also showed two Match AI & Simulation cards, one labeled SEGA and another Sports Interactive. The inspected SEGA original identified Sports Interactive as the studio. This is a reason to investigate the underlying identity, not immediately count two independent vacancies or declare the cards confirmed duplicates.

We did not resolve the second card's original requisition. A candidate should retain it as a possible related copy until the employer identity and destination are clear. Adding a different company label or board identifier to the same title is insufficient evidence of a second opening.

For a personal search, count a role once after checking the employer, team, title and available requisition or application URL. Attach each discovery source to the existing role record so a second board link does not create another application task for the same opening. Keep distinct teams or requisitions separate even when their titles resemble each other. This prevents an apparent increase in source coverage from becoming unnecessary application work.

The career pages versus job boards guide explains the wider discovery-to-employer relationship. Here, the practical comparison is what each game-focused source adds to the particular programming search. A raw board count does not supply that answer.

Turn a five-month project into a concrete work brief

Lewis's retained DNA opportunity now needs a second decision: whether its engagement and delivery expectations are workable. The listing identifies an existing codebase, a public demo and weekly task reviews with the producer. Those details help him prepare questions. They do not establish the final contract, payment schedule or acceptance process.

His completed preparation record separates published facts from unanswered terms. The questions below are illustrative and unsent; no producer or studio owner supplied answers during this review.

Area Lewis's saved evidence Unanswered question and preparation
Existing project Unity/NaniNovel codebase with a public demo Which versions and modules will he inherit? Prepare a relevant branching-state example and describe his actual contribution
Remaining delivery Narrative implementation, gameplay variables, smaller mechanics and asset integration Which deliverables must be completed within the engagement, and what falls outside scope?
Review and acceptance Weekly tasks reviewed with the team and producer Who approves completed work, how is acceptance recorded, and who decides when priorities change?
Duration and payment Paid full-time work, approximately five months; linked form asks for a monthly rate Confirm exact dates, agreed rate, payment timing and the written engagement terms

The record gives Lewis specific scope, review and payment questions to resolve with this team. It identifies the missing decisions without inventing unfavorable conditions. The available evidence does not establish funding problems, unpaid work or crunch; it also does not settle commercial terms that were not published.

Lewis can show a narrative feature, a state or variable bug he fixed, and the checks he performed. He can explain his shipped title and the boundaries of his lead contribution. He should avoid claiming experience with a particular plugin version or ownership of the whole game unless his actual work supports it.

He would also ask what happens when a dependency arrives late or the team changes a feature during the fixed period. That question follows from the delivery arrangement, rather than a judgment about indie studios generally. A written scope and review process help both sides understand the work being discussed.

Editorial illustration of a fixed-term game project with its known work scope beside unanswered rate, timing and acceptance conditions.

A different programmer can reasonably start with Hitmarker

Nina is a second fictional candidate. She has six years of professional C++, classical game-AI experience and an interest in football simulation. She can meet the London hybrid arrangement. The inspected Sports Interactive role gives her a specific reason to start with Hitmarker's broader studio and engineering coverage, then assess the original employer requirements.

That does not establish a complete match or an interview prediction. It identifies relevant work that Lewis's Unity/C# background did not demonstrate. Nina does not need to replace her simulation goal with a narrative contract simply because the latter is remote. The better starting source changes when the desired work and available evidence change.

The wider Hitmarker scope can also include programming near the commercial side of games. For example, the inspected Scopely playable-ads listing described interactive advertising work. The matching employer description identified the Forge team and a Barcelona hybrid arrangement. A developer interested in that output could investigate it; someone focused on gameplay for a particular title might make a different choice.

Keep both sources when they add different relevant targets. Reduce attention to a source when repeated checks produce no new usable roles for your current constraints. That is a judgment from your own search record, not evidence that the platform lacks worthwhile work for other programmers.

Read the application boundary for the specific lead

The settled Hitmarker manager and playable-ads pages displayed a sign-in-to-apply link. We did not sign in or test a profile, saved search or application. Publicly reading the description was a different action from entering an account workflow.

The DNA listing linked to an empty Google Form whose title matched the Unity position and repeated the UK restriction. It asked about relevant experience, availability and expected monthly rate. It also requested a resume URL viewable by anyone. We read the form without supplying answers or changing file-sharing permissions. A request for a public link deserves a deliberate choice about which resume copy to expose; it is not proof that a private file will be readable by the recipient.

For your next session, choose one programming target and read its full description. Record the main deliverable, employer or project, location and any unanswered engagement term before preparing the evidence that job requests. If you need another discovery source, browse recent roles on LandOffer.ai and apply the same screening before adding an application to your queue.

Sources and Further Reading