Independent career guide

Two Backend Listings, Two Ways Work Gets Accepted

Compares what two backend AI training listings ask you to clarify about accepted work and payment before applying.

Written and reviewed with AI assistance. No individual human or specialist review. Examples are educational; dated sources do not confirm current vacancies.

On this page

Two backend listings sat in the inventory when this companion was put together, each describing different work and different ways of saying how a task gets paid and approved. This companion does not repeat the main overview of backend work; it narrows in on one practical decision — who decides a piece of work is accepted, and what you should ask about that before you say yes. Main backend-engineer guide covers the broader picture.

The two descriptions below were read in full on the date given in Sources. They are a snapshot of what those specific listings said on that date — not confirmation that the same jobs, pay, eligibility, or interview process are current today. Treat anything here as a starting point for your own check of the current listing, not as current fact.

What each listing documents

Senior Backend Engineer. The description says this role builds reinforcement learning environments that test a model’s ability to design, deploy, troubleshoot, secure, scale and recover cloud infrastructure. The deliverables named are reproducible environments, deterministic validation tests, golden reference solutions, intentionally defective variants and failure scenarios, and documentation of each environment’s architecture, edge cases and operational flow. The description also says the expert refines environment specifications and acceptance criteria together with technical leads.

Backend C#/.NET Developer. The description says this role designs, develops and maintains backend services and APIs in C# and .NET, working with cross-functional teams to define technical requirements, optimizing existing processes, troubleshooting production and staging issues, and documenting technical specifications and architecture. It does not say who reviews that work, by what criterion, or what happens to work that is sent back.

The decision this companion adds

Both descriptions ask for documentation and both mention working with other people on the team, but only one of them says anything about how a finished piece of work gets judged. The Senior Backend Engineer description ties pay to tasks that meet project specifications and names a process for refining acceptance criteria with technical leads — worth asking about directly, even though the description does not spell out the exact criteria. The Backend C#/.NET Developer description does not mention acceptance criteria, a reviewer, or a payment unit; it names a goal of reliable, secure code, not a review process.

That gap is the practical thing to resolve before you accept either kind of work: find out, in writing, who looks at what you submit and what they check it against. Not knowing this before you start risks spending time on work that does not end up counting toward anything.

Payment: what each description states, and what it leaves open

  • Advertised range: neither description’s page metadata states a pay figure.
  • Paid unit: the Senior Backend Engineer description states that pay is output-based, tied to tasks that meet project specifications; the Backend C#/.NET Developer description does not state a paid unit at all.
  • Minimums: the Senior Backend Engineer description states a weekly submission minimum, with the number left out here; the Backend C#/.NET Developer description does not state one.
  • Availability: the Senior Backend Engineer description states a weekly-hours figure for the contractor role type, also left out here; the Backend C#/.NET Developer description states only that the role is a contract, without stating an hours figure.
  • Acceptance criteria: the Senior Backend Engineer description says criteria are refined with technical leads but does not spell them out; the Backend C#/.NET Developer description does not mention acceptance criteria.
  • Effective time versus task price: because the Senior Backend Engineer role pays per completed task, extra time spent correcting a task that was sent back changes how much that task works out to per hour of your time — it does not change the task’s agreed price. The description does not say what happens procedurally to a corrected and resubmitted task, which is worth asking about directly. The Backend C#/.NET Developer description does not state a paid unit, so this trade-off cannot be assessed from what is written.

Ask micro1 for the payment conditions in writing before accepting work.

Four questions worth sending in writing

  1. What exact unit is payment calculated on for this specific role — per task, per hour, or something else — and does that match what the listing says?
  2. Who reviews a submission, and what specific standard do they check it against?
  3. If a submission is returned, is it corrected and resubmitted, rejected outright, or something else — and does that affect the weekly minimum?
  4. What is the minimum expected output for this role, and over what period does it apply?

Clarification messages (illustrative)

The examples below are illustrative exercises created for this guide, not published micro1 assignments or interview questions. They are drafts you could adapt, not required wording, and none of them carries a score or a right answer.

Message for the Senior Backend Engineer listing, about defective variants: “Before I start building failure scenarios, could you confirm what happens if my intentionally defective variant also fails a validation test it wasn’t designed to fail? Does that count against the task, or is it treated as a finding to document?”

Message for the same listing, about acceptance criteria: “The listing mentions refining acceptance criteria with technical leads. Is there a baseline specification I should work from for my first submission, or is that defined per task?”

Message for the Backend C#/.NET Developer listing, about review: “Could you tell me who reviews completed backend work on this contract, and whether there’s a defined process — a pull request review, a staging check — before a task is considered finished?”

A short checklist before you apply

  • Reread the listing’s own deliverable list and note anything you would need to ask about rather than assume.
  • Write down, in your own words, what “accepted” means for that specific listing, based only on what it states — not on how similar work has worked elsewhere.
  • Draft your own version of the four questions above, naming the listing and role title.
  • Keep a copy of whatever answer you get in writing, separate from the chat thread, before you accept any task.

This companion covers only the two backend listings read for it, on the date in Sources, and only the question of what counts as accepted work and how that connects to pay. It does not cover interview format, eligibility, or the broader scope of backend work — for that, see the main guide.

Browse all expert opportunities

Opens micro1. You apply and are vetted by micro1, not by this site.

Sources

  • The Senior Backend Engineer description says the expert builds reinforcement learning environments testing a model's ability to design, deploy, troubleshoot, secure, scale and recover cloud infrastructure, lists reproducible environments, deterministic validation tests, golden reference solutions, intentionally defective variants and failure scenarios, and documentation as deliverables, states that acceptance criteria are refined with technical leads, and states that compensation is output-based per task meeting project specifications with a stated weekly minimum submission requirement and a stated weekly-hours figure for the contractor role type (the specific numbers are not reproduced in the article) — visible in the listing on 2026-10-01 — https://jobs.micro1.ai/post/c2684826-73f6-4abb-9511-e89bf5c69e14 (checked 2026-10-01)
  • The Backend C#/.NET Developer description says the role is a contract position that designs, develops and maintains backend services and APIs in C# and .NET, works with cross-functional teams, optimizes existing processes, troubleshoots production and staging issues, and documents technical specifications and architecture; it does not state a paid unit, a minimum, acceptance criteria, a reviewer, or a weekly-hours figure — visible in the listing on 2026-10-01 — https://jobs.micro1.ai/post/f55c5e8b-d0e2-427c-b84f-7642e66e263f (checked 2026-10-01)

Programme terms, eligibility rules and reference pages change. Each claim above is dated; verify it on the page it cites before acting on it.