Job search
Meridial by Invisible Review: Expert Projects, Statements of Work, and Geographic Eligibility
Two current technical listings and two completed fictional SOW decisions distinguish advertised rates, authorized scope, project duration, location and work actually received.
Meridial by Invisible is a public channel for finding expert AI-training projects, not a promise of assigned work. Review the specific project and its Statement of Work before committing: what you will deliver, the confirmed rate and payable activities, expected duration, payment terms and geographic eligibility. A remote label or an advertised hourly rate does not settle those details for an individual engagement.
LandOffer publishes this review and offers job-search tools. You can browse recent roles on LandOffer.ai alongside project-based opportunities, while keeping their arrangements distinct. This review checks public Meridial pages and two linked technical listings on October 21, 2026. We did not register, apply, assess, sign a SOW, upload a resume, contact the company or perform paid work. The completed decision examples are entirely fictional.

Find the current expert channel before evaluating the work
The Meridial FAQ identifies the service as an expert contractor marketplace powered by Invisible Technologies. Its public navigation points to a project board and a marketplace login. Someone searching an older Invisible name should follow the current official expert channel and its linked project, rather than assuming that every Invisible vacancy describes the same arrangement.
The FAQ describes profiles being reviewed against current project needs, with a match leading to project details. A profile can remain active when there is no current match. It expressly does not guarantee immediate engagements. Those are platform descriptions; we did not observe matching inside an account or measure how long it takes.
Meridial presents these opportunities as independent-contractor engagements rather than employment with Meridial or Invisible. Treat that as the channel’s stated arrangement, not an individual legal classification determination. A candidate seeking an employee role with company benefits should compare the actual arrangement before investing effort in this route.
The public board provides a starting point for investigating specialized project work. The limitation is that browsing or joining does not establish a paid assignment, a start date or a dependable weekly workload. Keep network membership, project interest, selection and an agreed engagement as separate stages.
Separate a public project rate from an agreed offer
The expert page says compensation is set per project and that each engagement is scoped through a Statement of Work describing the work, pay and expected length before commitment. It also says availability depends on client needs, expertise and geographic eligibility.
That supports using the SOW as a decision checkpoint. It does not supply the actual terms of a private engagement we have not seen. For example, the public statement that project time is paid should not be silently extended into a conclusion about every profile, confirmation, qualification or preparation activity. Establish which activities belong to the authorized project and how time is recorded before you rely on a calculation.
The public project board displayed both US-specific and worldwide-remote technical opportunities during this check. Those location labels help narrow the search; they are not a complete eligibility policy. We did not inspect an account-specific set of projects or confirm which opportunities a particular person would receive.
A rate range is also different from an agreed rate. Preserve its currency, unit and evaluation caveat. Keep the advertised range separate from your confirmed rate. Multiply it by hours only for a clearly labeled scenario, not an assumed full-time workload.
Two current technical listings, with their limits
The linked Coding Specialist project was labeled United States of America, contract, remote and mid-to-senior level. Its description involves challenging and evaluating model responses on coding subjects, checking reasoning and documenting failure traces. It describes technical education as ideal and also names professional software work, open-source contributions and other evidence of fit.
The listing displayed $8–$65 per hour, with the exact amount evaluated using experience, expertise and geographic location; it also warned that final offer amounts may differ from the listed range. It says contractors provide their own secure computer and internet, and company-sponsored health insurance and PTO do not apply. These are the listing’s statements, not a personal offer or a tested work experience.
The linked SWE-Bench AI Task Auditor project was labeled World Wide – Remote and freelance contract. Its scope is task evaluation and technical auditing: accuracy, reproducibility, tests, integration problems and actionable feedback. It asks for deep software-engineering experience, complex-codebase knowledge and familiarity with the relevant standards.
That page displayed $60 per hour, while still saying the exact rate is determined after evaluating experience, expertise and geography. Preserve both statements rather than converting the headline into an unconditional rate. It likewise excludes company-sponsored benefits. Its public page did not provide the full SOW, guaranteed hours or a complete country-and-state eligibility list.
For a developer, these examples show why domain and deliverable fit matter. Coding expertise does not automatically establish experience auditing difficult repository tasks. Conversely, a technically relevant project can still be unsuitable because the eventual authorized time, location or duration does not fit your circumstances.
Use a completed SOW record to decide how far to proceed
Write the project’s scope, pay basis, authorized time, expected dates and applicable location in one record. Mark each item as publicly advertised, confirmed in the engagement material or still unknown. End the record with a decision about whether to continue, pause or decline, so missing terms have a concrete consequence for your time.
Worked asset 1: a fictional hourly project with a bounded commitment
Everything in this example is invented, including candidate Nadia, the project and its SOW terms. DEMO-SOW-A is not a Meridial contract or quote. It illustrates the questions a person would need resolved, without representing the public coding listing as an offer.
| Decision field | Filled fictional record |
|---|---|
| Work scope | Code-evaluation review packets with written error explanations; no software implementation for a client. |
| Pay basis | USD32 per authorized project hour, including the calibration activity explicitly named in this invented SOW. |
| Authorized limit | Eight hours per week for an expected two-week project window. The limit is not a guarantee that eight hours will be available. |
| Location | The fictional project materials explicitly cover Nadia’s stated work location. No real Meridial country or state approval is implied. |
| Time and payment details | The example stipulates a defined time-recording process and written payment terms. No actual platform record or bank receipt exists. |
| Candidate decision | Continue reviewing this bounded engagement because the stipulated scope, paid activities and location are resolved; do not treat it as recurring employment or guaranteed income. |
The illustrative authorized-hour record contains 7.5 hours in week one and six in week two. Our actual local Decimal calculation gives 13.5 × $32 = $432 gross. The arithmetic ceiling under the assumed weekly limits is 16 × $32 = $512. Neither number is earned money or a forecast; both come from invented inputs and exclude any personal tax or other financial analysis.
We also checked an alternative record containing nine hours in the first week. The checker rejects that record against the assumed eight-hour authorization rather than silently reducing it to eight. The checker applies only our invented authorization rule. It does not establish whether additional work is payable under any actual agreement or applicable rule. It identifies a discrepancy that needs clarification before relying on the record or undertaking more work.
Nadia’s completed decision note is: “The fictional scope and eligibility conditions are sufficiently specified for further SOW review. Reserve only the agreed project window, keep the weekly limit visible and confirm any requested expansion before changing the commitment.” No actual signature, work or payment followed.

Keep geographic eligibility attached to the engagement
A network’s international reach does not establish that every project accepts every location. The public pages say geography affects availability, and the two inspected listings use different location labels. The application pages also ask for current residence and, where applicable, US state information. We read those public fields but entered nothing.
Keep residence, the location where work will be performed and any proposed change visible in your own review. Do not assume that a worldwide-remote title settles project restrictions, permission to work while traveling or individual authorization questions. This review supplies no immigration, tax or employment-law conclusion.
Worked asset 2: a fictional location change that stops commitment
Candidate Cal and DEMO-SOW-B are also wholly fictional. This is a separate example, not a second real Meridial offer. The invented draft describes a ten-calendar-day technical-audit project at USD45 per authorized hour, with a total ceiling of 20 hours. It supplies neither guaranteed hours nor a settled answer about a planned work-location change.
Cal intends to work initially in one US state and later in another. The fictional record does not identify those states as eligible; the applicable project confirmation is missing. Revision activity is also undefined. The complete decision ledger is:
| Item | Current fictional evidence | Decision and remaining owner |
|---|---|---|
| Technical task | Audit repository tasks and write reproducible findings; relevant experience stipulated. | Technical fit can be considered, but it does not clear the other conditions. |
| Duration | Expected ten calendar days. | Keep separate from available hours and payout timing; no extension or continuing assignment assumed. |
| Rate and ceiling | USD45 hourly, maximum 20 authorized hours. | Arithmetic ceiling is $900; expected hours remain unknown. Budget no income from this unresolved engagement. |
| Changed work location | No project-specific confirmation for the later location. | Hold commitment and work until the project’s authorized contact clarifies the applicable scope. |
| Revisions | Draft does not state which revision activities are authorized project time. | Request the missing definition through the appropriate project process before relying on the scope. No request was actually sent. |
| Final choice | Two material conditions unresolved. | Do not accept or begin this fictional engagement; retain the unanswered items rather than treating the remote label as approval. |
The local record check keeps unknown values unknown and returns a hold. It calculates the $900 ceiling without converting it into guaranteed pay. A separate local check enumerated all eight true/false combinations of location, paid-scope and payment confirmations. Only the all-confirmed combination passed our fictional review gate; missing answers in Cal’s record remained unknown rather than becoming true. That is our teaching decision rule, not Meridial’s actual selection algorithm or a legal eligibility test.
Cal’s outcome is a completed do-not-commit-yet decision, not a claim that the project is unsuitable for everyone. A later written answer might change the choice. Until then, expertise, an attractive rate and network access cannot fill the missing engagement terms.
Treat payment descriptions as a starting point for verification
The FAQ says earnings are processed every two weeks. That is the public cadence description, not an observed bank-arrival time or a guarantee that a short project produces a payment immediately when its expected window ends. We did not examine a real payout statement or a person’s account.
Before commitment, retain the actual payment basis and applicable conditions with the SOW: how authorized work is recorded, when it becomes payable and what happens when scope changes. If an actual listing, agreement and project instruction conflict, resolve that discrepancy through the authorized project channel before relying on the most favorable wording. Do not invent a universal contract priority rule from this public review.
Meridial is worth investigating when your expertise matches a visible project and you can evaluate a project-based arrangement. It is a weaker fit if you need guaranteed weekly work or employee benefits that these contractor listings expressly exclude. Before allocating time, attach the current official project to your scope, rate, duration, location and payment record. Leave unresolved terms open, and keep employee roles separate when that is the arrangement you need.
Explore LandOffer.ai to organize the next opportunity while keeping advertised rates, agreed terms and work actually received distinct.
Sources and Further Reading
- Meridial: Become an expert, current public page checked October 21, 2026; per-engagement scope, rate, duration and geographic boundary.
- Meridial FAQ, current public page checked October 21, 2026; brand identity, matching, contractor description and payout-processing cadence.
- Meridial open projects, public board checked October 21, 2026; observed links and location labels, not account-specific eligibility.
- Coding Specialist project, 4629100101, current employer-linked public listing checked October 21, 2026.
- SWE-Bench AI Task Auditor project, 4969230101, current employer-linked public listing checked October 21, 2026.


