1. LandOffer
  2. Blog
  3. All articles
  4. Work With Indies Review: Find Paid Programming Work and Check Location Restrictions

Job search

Work With Indies Review: Find Paid Programming Work and Check Location Restrictions

Three current public role checks and an original controller-contract evidence packet show how to assess geography, compensation basis and specialist fit.

10 min readLandOffer team

Work With Indies can help a programmer discover paid work at smaller game studios, but the useful lead is the complete engagement described inside a listing. A remote label does not establish your permitted location. An annual salary figure on a contract also does not promise a year of income; the stated term and payment basis determine what the listing actually offers. Read the engine, geography, duration and payment basis together before preparing an application.

We inspected public programming listings, application destinations and site information on October 20, 2026. Three selected roles show different boundaries: a one-month Unity contract requesting a proposed rate, a Quebec-only remote employee role, and a US-only six-month Unreal engagement. This review involved public reading, with no account, email, application, purchase or employer conversation.

A game developer inspects a character-controller prototype beside an indie studio job board with location markers.

Keep a broader baseline through recent roles on LandOffer.ai and studio career pages. This review does not estimate the board's share of available programming jobs or show that a role is exclusive to it. The useful part of this visit was the detail in three leads: it let us distinguish a potential specialist contract from a location mismatch and an older US opening.

Work With Indies organizes opportunities around independent games. Its Programming & Development category gives a more focused starting point than searching every occupation at every games company. That focus can expose smaller teams and specific production problems, including controller polish, multiplayer implementation and building a prototype.

The site's About page describes reviewing and improving job posts, including editing and formatting. That is a public description of its editorial work. We did not audit the review process, verify studio finances or establish whether every advertised position remains available. A carefully presented listing still needs a current employer and role check.

The category also cannot establish your personal fit. Someone who develops Unity tools may lack console hardware experience; a backend engineer may understand networking without having shipped multiplayer gameplay. Look for the engineering output the studio needs, then compare your own contribution to that output. Interest in independent games is useful context, not a replacement for the requirements.

Separate location labels from the permitted work arrangement

The Skymap Games listing made the distinction clear. Its header said Quebec and Remote; the body specified Montreal, fully remote, applicants residing anywhere in Quebec, and legal authorization to work in Canada. We followed its public application destination and found the same location and compensation language on the Skymap-branded Parallel careers page. The match covers what was readable on that date; it does not establish that an application would be reviewed.

The studio description also mentioned Manchester, New Hampshire, and broader company benefits. Those company facts did not turn this particular opening into a US-remote role. The role-specific Quebec requirements and Canadian benefits were more useful than the headquarters address when deciding whether a US resident should continue.

For the Happiest Dark Corner contract, the board displayed Anywhere and Remote. The body requested the applicant's time zone and weekly availability, but did not settle US contracting eligibility, required overlap or access to development hardware. We recorded those fields as unresolved. “Anywhere” was a discovery label, not a verified agreement covering every country.

Windy Games was more explicit: remote in the US, US candidates only, with core hours written as 10:00–2:00 EST. Before relying on that schedule, clarify whether the studio means Eastern local time through daylight-saving changes. We did not infer sponsorship, payroll classification or state-specific eligibility from the US label.

Worked audit of three programming leads

These are three deliberately selected public listings, not a representative sample or a measured success rate. We checked the visible body rather than treating a title or a search snippet as the complete job. Dates below are board labels, not verified employer requisition creation dates.

Lead inspected Engineering and engagement evidence Location evidence Completed review decision
Happiest Dark Corner, Unity Character Controller Developer; October 15 One-month remote contract; controller, animation, camera and DualSense work; applicant proposes a rate Anywhere label; studio in Bahrain; time zone and availability requested Keep as a conditional specialist lead; fixed pay, eligible contracting location and hardware access remain unresolved
Skymap Games, Multiplayer Engineer (Unity); October 13 Full-time mobile multiplayer work; C#; CAD 80,000–120,000 per year; three years of games/Unity experience and mobile shipping evidence Quebec residents with Canadian work authorization; same restriction on the external careers page Exclude from a US-resident-only search; remote work does not remove the provincial requirement
Windy Games, Senior Unreal 5 Programmer; September 1 Six-month employment contract; C++/Unreal internals; prototype and vertical slice; five years and a shipped PC/console title US candidates only; specified Eastern core hours Potential US lead for an experienced Unreal programmer; verify current intake and written engagement terms before applying

The Unity controller listing asked for practical PS5 development and DualSense experience as essential requirements. A desktop-only Unity project does not demonstrate those requirements. If that is your experience, do not spend time packaging it as proof of console work. Look for an opening whose essential requirements you can support truthfully. Its requested deliverables included integrated source, configurable effects, documentation, remaining issues and a handover session. Those details tell a candidate what evidence would matter.

The Skymap listing and its external careers destination both described the same mobile multiplayer role. That establishes a readable, matching destination during our visit. We did not submit a form or verify an employer response, available headcount or the application system's behavior after submission.

The Windy listing remained readable with an Apply link during the check. Its September date warranted a current-availability check. We did not infer closure from the age alone or infer an active recruiting process from the page still loading. An accessible page and a button alone do not prove that hiring continues, especially when an older role appears beside newer category entries.

Read paid work as a specific compensation agreement

Two inspected roles disclosed amounts; the controller engagement requested a proposed rate. We did not establish a universal paid-only guarantee from the public posting interface. The employer posting page did not expose usable submission rules in our rendering. This review therefore evaluates the actual compensation information in these listings rather than promising that every board entry has a fixed, guaranteed payment.

Windy supplied an unusually useful distinction: an annual rate of USD 80,000–100,000 and USD 40,000–50,000 for the six-month term. The latter is the advertised term amount. Possible conversion to full-time was conditional; it did not extend the contract to twelve months or guarantee a subsequent offer. We did not calculate take-home pay, benefits value or an hourly equivalent from unspecified working weeks.

The listing also said the studio did not currently have a health plan, despite describing paid time off. That makes a benefits question concrete. A candidate comparing this engagement with another role should obtain the actual employment classification, benefits eligibility and payment schedule instead of assuming that an annualized figure buys the same package.

For the one-month Unity contract, the missing rate changes the next step. Before starting work, settle the approved scope, currency, payment timing, review process and handling of additional requests. A proposed rate belongs in a negotiation; it is not evidence that the studio accepted a number or funded a milestone. None of those terms was tested here.

Worked evidence packet for a one-month controller contract

Consider fictional Mira, a US-based Unity programmer with a shipped console game, permitted-to-share controller footage and direct PS5/DualSense implementation experience. Mira can reserve four weeks for a defined engagement. She uses the inspected controller listing to assemble a private evidence packet; this is an original example, not a real application or an employer-approved plan.

Mira's packet maps her contribution to the studio's requested output. She chooses one controller clip showing traversal and camera behavior, a separate clip demonstrating haptic events she implemented, and a short explanation of her own code ownership. She removes confidential repository links and unreleased footage. Each retained clip has a short contribution note so the reviewer can distinguish her controller code from animation or level work supplied by teammates. Her shipped credit supports experience, while the clips explain what she actually did.

Packet field Mira's completed entry Boundary or next decision
Controller evidence Shareable clip of ledge traversal, collision recovery and camera transitions; contribution described as her own movement and camera code Does not claim ownership of the whole game or reuse restricted studio assets
Console evidence Authorized clip and written account of implementing and tuning DualSense feedback on a shipped project No confidential development documentation or credentials included
Proposed delivery sequence First establish a reproducible baseline and priorities; then tune agreed movement/effects; finish with integrated source, remaining-issue list and handover Illustrative sequence only; studio must agree scope and acceptance criteria
Availability Four-week window and 25 hours per week available; US time zone stated in the private draft Does not assume those hours or overlap satisfy the studio
Commercial terms Rate and currency left for a deliberate quote after scope and hardware access are clarified No guessed employer budget, promised payment or invented accepted rate
Immediate outcome Evidence packet ready; eligibility, hardware arrangement, agreed scope and payment terms still open Hold any work commitment until the missing terms are resolved

The sequence gives Mira a useful first discussion without pretending she can estimate an unseen codebase. A controller defect may involve animation, physics, input or another system. She distinguishes investigating the baseline from promising every requested interaction will be fixed within one month. Additional scope needs an explicit decision rather than disappearing into “polish.”

Hardware is another practical boundary. Prior PS5 experience does not establish that Mira currently has authorized access to the required development environment for this project. Her private note asks who provides access and how validation will occur. She does not send restricted material to demonstrate readiness or assume a consumer console is the needed test setup.

Mira's outcome is a prepared, conditional application package. She has not applied, been shortlisted or won the contract. A different candidate without the essential console experience would reach a different result: keep the role as a signal about skill requirements and pursue a better-matched Unity opening rather than claim experience they do not have.

A controller test scene, four-week calendar and engineering notebook show a bounded delivery sequence ending in a handover folder.

Check freshness and the route before sharing an application

The site's terms describe listings lasting 45 days unless a shorter closing date is supplied. That publishing rule is not a promise that an employer continues recruiting for the entire period. We found the older Windy page still readable, so elapsed time should trigger verification rather than an automatic conclusion that a visible page is active or closed.

Check the current rendered page and destination. Our public controller page exposed an email application route; Skymap linked to a careers page; Windy linked to a Google form. We read the email destination without opening a composer and did not submit any application. Different routes call for separate checks of recipient identity and requested material. A form link and an email address are application destinations, not a recruiter introduction or a promise of feedback.

The website also offered a weekly email digest and community links. Browsing did not subscribe us to either. If you choose those channels, treat notification settings and information sharing as separate decisions. Read the privacy policy and the destination's own information before sending personal details; this review did not test retention, deletion or community moderation.

Use the board when smaller-studio programming work matches your target and you are ready to inspect concrete production responsibilities. The selected roles were useful because they exposed different work arrangements and specific technical requirements, not because every remote card qualified for the same candidate.

Keep the full engagement in your record: engine, contribution evidence, permitted location, duration, rate basis and application route. Resolve material gaps before committing work. Explore LandOffer.ai alongside studio career pages to keep other technical options available while you decide which indie opportunity deserves a tailored application.

Sources and Further Reading