Job search
Gun.io Review for Developers: Profile Screening, Client Matching, and Payment Terms
Review Gun.io profile screening, public client-matching descriptions and payment terms. Use a worked net 30 calendar before relying on advertised hourly income.
Gun.io is worth investigating when you can present concrete engineering work and want a screened client-matching route. A complete profile starts consideration; it does not establish approval, a client interview or a paid assignment. Read the communication and contract conditions alongside the advertised candidate rate. The FAQ describes net 30 from each billing week's end; payment is not immediate cash.
LandOffer publishes this review and offers recent technology listings. We checked Gun.io's public developer pages, expanded FAQ and website terms on October 13, 2026. We did not register, undergo screening, contact clients or test payments. Dante and Portia are fictional examples. Their completed preparation and arithmetic explain decisions without reporting approval, actual earnings or delivery of the provider's advertised guarantees.

A complete profile opens consideration rather than an assignment
The Find Work page describes completing a profile to 100%, senior-developer review, shortlisting, a conversation about experience, client interviews and contracts. It also says developers retain the rate they set and clients pay its fees. These are published descriptions, not an onboarding sequence or rate we tested in an account.
The FAQ adds screening, work-history and background review, and a live technical interview with a senior engineer. It says only approved profiles are presented as finalists. Completing the profile and receiving approval therefore need separate entries in your preparation record.
Keep the actual invitation's requirements when one arrives. We did not verify a fixed interview duration, question bank, retake policy or universal timeline. Prepare to explain your own work without assuming that a phrase on the public page removes technical evaluation or every client conversation.
A completed form supplies information. Technical fit still needs evidence of relevant work. Describe a contribution, a check and an ownership boundary beside the languages you list. Describe the system, contribution, checks and limits behind the skills you intend to claim.
You may spend useful preparation time before a match appears. That time should remain visible even if access involves no candidate-rate deduction under the public description. We did not measure how quickly useful introductions arrive or whether the available work fits a new candidate's schedule.
Read the public jobs as leads with information still missing
The Latest Jobs page showed examples including AI/backend infrastructure, senior React work, backend API integrations and full-stack work. The backend example mentioned Node.js, PostgreSQL and GraphQL. The descriptions emphasized substantive technical responsibility, but did not identify clients, job IDs, pay or dates in the reviewed public view.
The visible See All Jobs and application links pointed to account signup. We observed their destinations without following an intake or entering information. That public page helped identify work to investigate; it did not provide the full terms of an individual opportunity or establish that a developer had been shortlisted.
Do not fill the missing fields with an imagined client. A technology combination or business category cannot identify the company reliably. Keep employer or client identity pending until it is supplied through the appropriate process. An unnamed lead can still be worth investigating, with that information limit retained.
Read ownership words carefully. Contributing to an integration differs from being responsible for the whole architecture, operating it during incidents or deciding every interface boundary. If the brief expects broader independence than your evidence shows, identify the gap before presenting yourself as a complete match.
We did not independently verify testimonials, steady-work claims or candidate outcomes. We do not use them as a candidate acceptance probability or a promise of steady work. The useful first decision is whether the described responsibility and matching route deserve time in your search.
Dante completes an evidence and profile-state record
Fictional case: Dante has eight years of Node.js and PostgreSQL integration work. He implemented request handling, retry checks and exception reports in an existing team. He has no professional GraphQL work and has not independently owned the platform's whole architecture or incident coverage. He is interested in longer technical engagements but has no Gun.io account or proposed contract.
He completes this record against the actual public backend-integration example. It does not claim that the unknown client accepts his experience or that every listed technology has the same importance.
| Item | Dante's completed record | Next action |
|---|---|---|
| Integration contribution | Node request handling, retries and PostgreSQL checks he can explain | Select one permitted example for review |
| GraphQL | No professional evidence supplied | Keep the gap and clarify its importance in a real role |
| Architecture ownership | Component contribution within a team | Do not claim entire-platform responsibility |
| Profile | Facts and an original project summary prepared locally | Decide whether to begin the actual intake |
| Approval and client selection | Neither established | No finalist, interview or assignment recorded |
His original fictional project paragraph reads:
I implemented request handling for a Node integration and added retry checks to avoid processing the same request twice. I used PostgreSQL queries to investigate unmatched records and prepared exception reports for team review. Our lead decided the broader interface architecture, and operations shared incident coverage. I can explain my changes and checks; I have not claimed professional GraphQL experience or ownership of the entire platform.
The paragraph supports a conversation about responsibility. It does not invent a measured uptime improvement or disclose a client's private repository. For a real profile, Dante would use his own accurate work and artifacts he is entitled to share.
He also prepares one follow-up explanation: why the retry check used a stored request identifier, what happened when a duplicate arrived and which failure case the team still needed to investigate. These are fictional example topics, not Gun.io assessment questions or a script that guarantees approval.
Dante's completed choice is to investigate the matching route while preserving the GraphQL and ownership questions. If an actual role requires independent architecture and incident responsibility from arrival, he can exclude it under his current evidence. Another lead with narrower responsibility could justify a fresh review.
Keep the candidate rate and engagement scope together
Gun.io's Find Work page presents retaining 100% of the developer's stated rate, with fees charged to clients. A candidate rate and a client's total bill are therefore different figures in its public description. This review did not inspect a contract, bank payout, currency conversion or tax result.
The actual rate still needs to belong to an agreed engagement. A number entered into a profile is not paid income when there is no client agreement or logged work. Confirm what work is included, the allowed hours and the applicable payment process before depending on the figure.
Ask whether meetings, review, research and handoff are reportable time within the agreed hour limit. A deliverable estimate that excludes necessary coordination can exceed the commitment you intended to make. Identify the scope and reporting rule rather than assuming that every activity is billable under every agreement.
Also distinguish contract work from employment. The FAQ describes contract, contract-to-hire and salaried placement routes. A possible later hire should not repair missing terms in the initial engagement or be entered as an accepted employment offer. Evaluate the proposed relationship you would start with.
Weekly net 30 starts from each billing week's end
The developer-payment FAQ says each payment covers a week of logged time and is paid 30 days after that billing week ends. This is its documented schedule. We did not test a payout or establish the banking availability time for any candidate.
This distinction changes a cash-flow plan. Work performed early in a week has not reached the stated payment date when that week ends. A later week creates its own later date. Keeping those dates visible prevents the phrase weekly payments from becoming an assumption that money arrives immediately after each Friday.
Use the actual agreement to confirm how the billing week is defined, how hours are reported and what changes if time is disputed or corrected. The following example stipulates a Sunday week ending and calendar-day calculation solely for teaching. It does not establish that every private agreement uses those inputs.

Portia completes a hypothetical work and payment calendar
Separate fictional case: Portia considers an invented engagement starting Monday, November 2, 2026, at an agreed illustrative rate of $90 per paid hour. Assume 24 valid logged hours in the first week, 18 in the second and no work in the third. No real client, agreement, invoice or payment exists in this exercise.
| Fictional week ending | Assumed paid hours | Gross calculation | Date 30 calendar days later |
|---|---|---|---|
| November 8, 2026 | 24 | 24 × $90 = $2,160 | December 8, 2026 |
| November 15, 2026 | 18 | 18 × $90 = $1,620 | December 15, 2026 |
| November 22, 2026 | 0 | 0 × $90 = $0 | No earnings to expect for this week |
The two working weeks total 42 hours and $3,780 gross under the invented assumptions. That amount is not cash available on November 15. The first calculated payment date falls 36 days after the fictional start, because the first week's ending comes six days after that start and the example then adds 30 days.
Portia records work completed, time recorded, expected payment date and money actually received separately. The example has calculated dates and gross amounts but no received cash. It excludes taxes, bank or currency costs and any additional processing delay; it is neither take-home income nor a recommended rate.
The zero-hour week also matters. A weekly payment cadence does not manufacture earnings for a period with no payable time. Portia does not copy 24 hours into every future row or count a recurring engagement that has not been agreed. Her planning record shows the gap directly.
Before relying on a real proposal, she checks whether she can cover the initial interval and whether the actual billing and payment terms match the assumptions. If she needs a different start or cannot manage the delay, that constraint deserves a conversation before acceptance. A high hourly number cannot resolve a missing payment date.
Portia's calendar has two hypothetical gross amounts, two calculated dates and a zero-hour week; received cash remains zero in the exercise. It demonstrates what she must clarify and what she must not call received. It does not report that Gun.io has paid her or promise that a new developer will obtain these hours.
Read the actual agreement and communication boundaries
The FAQ directs pre-contract client communication through Gun.io and describes direct contact after contracts are in place. It describes an initial client hour block, with recurring work as a goal. Follow the applicable instructions for an actual engagement instead of treating an introduction as permission to move it elsewhere or assuming a renewal is guaranteed.
The public website terms were dated March 26, 2020 and expressly concerned the public site, preserving separate agreements. They were not the consultant contract discussed in the FAQ. We did not inspect a candidate's signed terms, so this review cannot determine a real person's exact payment or relationship obligations from that page alone.
Portia prepares this unsent fictional clarification:
Before I decide on this proposed engagement, please provide the applicable consultant and project terms. Please confirm the candidate rate, authorized hours, what time is reportable, billing-week ending, payment-date calculation and expected banking availability. I also need the communication route and the process for corrected hours or a changed scope. No recurring hours or later employment have been agreed in my current record.
This inquiry defines the information needed for a decision. It does not claim that the provider accepted the conditions or that a public FAQ overrides the actual agreement. A useful response resolves the specific rate, scope and calendar questions instead of offering only a broad assurance about handling administration.
Decide whether this route fits your search
Gun.io can be relevant when its screened matching model and technical work suit the experience you can explain. It remains a route to investigate, with approval, client selection and engagement terms still to establish. Keep your existing direct search if it already supplies suitable work and clear conditions.
Dante has an accurate project account and explicit technical gaps before intake. Portia has a concrete work-versus-cash calendar before relying on a contract. Neither needs an invented match or a testimonial to reach a useful next step.
Open one public lead, identify its actual responsibilities, or compare a role from LandOffer's recent technology listings. Prepare a truthful responsibility summary and identify the agreement facts that would change your decision. Record a completed profile, approved candidate, client conversation, contract and received payment only when each event actually occurs.


