Cyber engineer reviewing code and software tests at home, with a $400 per task remote contract label

Mercor Cyber Engineer Job: Remote Contract at $400 per Task

Please Share
Pin Share
Mercor Cyber Engineer Job: Remote Contract at $400 per Task
Mercor Cyber Engineer Job: Remote $400-per-Task Contract
workfromhomes
Remote IT & Cybersecurity Jobs

Mercor Cyber Engineer Job: Remote Contract at $400 per Task

$400 per taskRemote contract3+ years experienceEstimated 5 hours per task
Illustrative image for a Cyber Engineer role advertised by Mercor at $400 per task.

The Mercor Cyber Engineer job offers experienced security professionals remote contract work creating and reviewing code-security tasks for AI evaluation. The advertised compensation is $400 per task, with an estimated average of five hours per task. Applicants need at least three years of relevant professional experience, along with strong coding and technical writing skills.

This opportunity may suit you if your work already involves understanding vulnerable code, explaining how a security issue behaves, and checking whether a fix actually solves the problem. The work connects practical software security with the evaluation of AI systems.

Below, you will find the verified job details, a realistic explanation of the pay, and practical ways to prepare your application. The preparation advice and illustrative examples are our editorial guidance; Mercor has not published the specific assessment questions or a detailed task rubric in this listing.

Listing checked: November 17, 2026. Availability and requirements may change. Review the current official Mercor Cyber Engineer listing before applying.

Referral disclosure: Global Work From Homes may earn a referral payment if you apply through our Mercor referral link and qualify for eligible paid work. Using the link does not guarantee selection or income.

On this page

Job snapshot

DetailWhat the listing says
Company posting the opportunityMercor
PositionCyber Engineer (3+ Years Experience)
EngagementContract
Work arrangementRemote
Advertised compensation$400 per task
Estimated average handling timeFive hours per task
ExperienceThree or more years of relevant professional experience
Relevant backgroundsApplication security, vulnerability research, penetration testing, or secure software engineering
Core strengthsCoding and clear technical writing
Screening formatRecorded assessment with typed answers and camera/screen recording; no AI interviewer
Location restrictionsNo specific country or state restriction is stated in the supplied role description
Weekly hours and project durationNot specified in the role description
Application deadlineNot specified in the role description

View the role and start your application on Mercor.

What the work involves

Mercor describes work centered on building and reviewing realistic code-security tasks used to evaluate AI systems. The responsibilities include finding vulnerabilities, documenting reproducible exploits in controlled environments, and validating fixes and regression tests.

For an experienced engineer, those activities form a connected chain of evidence: identify the weakness, demonstrate the behavior, explain its cause, and verify the correction. A reviewer needs enough information to judge each link without relying on the author’s confidence alone.

Analyze the code and explain the underlying issue

A useful security finding connects an observable problem to the implementation that causes it. A warning from a scanner can help direct attention, but a convincing explanation should establish what the code does and why the behavior matters.

For example, an engineer might examine whether an application consistently checks a user’s permission before returning a resource. The valuable part of the analysis is the reasoning about the trust boundary, the affected operation, and the conditions needed for the issue to occur.

That example illustrates the kind of reasoning relevant to software security. It does not identify a vulnerability that Mercor has confirmed will appear in this project or assessment.

Make the behavior reproducible

Another reviewer should be able to understand the starting conditions and reproduce the reported result in the designated test environment. Good documentation explains the setup, the expected behavior, the observed behavior, and any limitations of the evidence.

Reproducibility also requires discipline about scope. A test that works only because of an undocumented local setting may tell a different story when another person runs it. Keep relevant configuration details close to the finding so reviewers can distinguish an application weakness from an environment problem.

Validate the correction and regression coverage

A code change can remove one symptom while leaving the underlying issue in place. Useful validation explains why the correction addresses the original cause, then checks whether legitimate behavior still works.

Regression coverage should make the security requirement observable. Ideally, the relevant check exposes the problem in the vulnerable version and passes after the correction. Additional checks can cover nearby conditions where a superficial fix might fail.

This is why clear writing matters alongside coding: another engineer must be able to assess both your implementation and your reasoning.

Who should consider applying

The stated threshold is three or more years of professional experience in one of the relevant fields. Assess your fit using the responsibilities you have actually performed, including the depth of your involvement and the evidence you can discuss.

Application security engineers

Application security work can provide strong examples when it includes code review, vulnerability triage, remediation guidance, and verification with developers. Choose examples that show how you investigated a finding rather than simply forwarded an automated report.

You should be ready to explain a security decision in ordinary engineering language. Describe what could go wrong, which assumptions you tested, and why a particular change improved the behavior.

Penetration testers and vulnerability researchers

Relevant experience may include reproducing issues, separating confirmed findings from hypotheses, and writing reports that help another person act. Your strongest examples will also show an understanding of implementation details and remediation.

If your background is primarily testing, make your coding experience visible. Explain the scripts, test cases, or application changes you personally created. Avoid presenting a long list of tools as a substitute for technical depth.

Software engineers with security responsibilities

Secure software engineering is explicitly included in the listing. A developer who has implemented permission checks, addressed security defects, and written meaningful tests may have relevant experience even if their job title did not contain the word cybersecurity.

However, routine feature development alone does not establish security expertise. Use concrete examples to show how you identified risk, chose a mitigation, and verified the result.

Applicants still building experience

Personal labs and certifications can support an application, but they do not replace a published professional-experience requirement. Keep professional work, independent projects, and coursework clearly identified on your resume.

If your experience is mainly basic IT support or introductory cloud study, consider opportunities that match that background while you continue building software security skills. You can browse our Remote IT & Cybersecurity Jobs page for other roles.

Understanding the $400-per-task pay

The listing advertises a task fee. Dividing $400 by Mercor’s five-hour handling-time estimate gives $80 per hour as a comparison. It does not turn the contract into an hourly pay offer.

Your effective return depends on the time a task actually takes, the payment terms, and whether the work meets the applicable acceptance requirements. Time spent reviewing instructions or responding to requested changes can affect that calculation.

Illustrative total time for one $400 taskGross effective rate
Four hours$100 per hour
Five hours$80 per hour
Six hoursAbout $66.67 per hour
Eight hours$50 per hour

These are arithmetic examples, not Mercor forecasts or promised earnings. They assume the full $400 is payable for that task and exclude taxes or any applicable expenses.

Task availability matters as much as the headline rate

A high fee does not tell you how many assignments will be offered. The description does not establish a weekly minimum, a monthly workload, or a project end date.

For that reason, avoid multiplying the task fee into a projected salary before you understand the engagement. First establish how tasks are assigned, whether contributors can decline them, and what happens when available work slows.

Track your own total time during any paid engagement. A simple record of setup, implementation, documentation, and review time will give you a more useful basis for future decisions than the headline figure alone.

Remote eligibility and missing details

The role is advertised as remote, and its description does not specify a country or U.S. state. That does not establish that every applicant can receive a contract.

Mercor publishes a supported-countries list covering where it can onboard and pay experts. The United States and Ghana are listed at the time of this review. Payment-country support is separate from selection for this particular role, and applicants must still satisfy any requirements presented during application and contracting.

What the listing does not settle

The description does not name a required degree, a mandatory certification, a specific programming language, or an equipment allowance. It also does not provide a fixed weekly schedule, guaranteed task volume, or detailed payment-acceptance rules.

Treat those as unanswered questions. Their absence does not mean Mercor has waived them or that a particular arrangement will be available to you.

If your location, availability, or equipment affects your ability to work, resolve that point before committing to deliverables. You can save time by asking a precise question about your circumstances rather than assuming the word remote answers every practical concern.

How to apply

1. Open the specific Cyber Engineer listing

Use our Mercor Cyber Engineer referral application link, then confirm the title and compensation. If the listing has closed, return to Mercor’s opportunity search to look for an active role that fits your experience.

Keeping the exact role in view matters because different Mercor opportunities can have different screening formats and requirements. General advice about another listing may not apply here.

2. Prepare an accurate resume

Prioritize experience that demonstrates software security reasoning, hands-on coding, reproducible technical work, and clear documentation. Make dates and responsibilities easy to understand.

Where you can substantiate them, include results that show the effect of your work. A specific remediation example is often more informative than several broad claims about being passionate, detail-oriented, or familiar with security tools.

3. Complete the requested profile and authorization information

The public application view shows resume, work-authorization, and recorded-assessment steps. Follow the instructions actually presented in your account, since the platform can update its process.

Use consistent employment dates and contact details. If a question requires clarification, explain the relevant fact directly rather than selecting an answer you cannot support.

4. Complete the recorded assessment

This role specifies typed answers with camera and screen recording, and says there is no AI interviewer. Prepare a stable computer setup and read the assessment’s instructions before beginning.

The listing does not disclose the exact duration or full question set. Do not assume an unrelated Mercor interview guide describes this assessment accurately.

5. Check the submission state

After completing the required steps, review the status displayed in your account and retain any confirmation you receive. An application submission does not itself establish an offer or an assignment.

For a broader introduction to the platform, read our Mercor review. The specific job listing remains the source for this opportunity’s terms.

Preparing for the recorded assessment

Preparation should help you demonstrate your own existing skills. The suggestions below are practice activities, not a prediction of Mercor’s questions or an account of its private scoring criteria.

Revisit a complete security investigation

Choose a past issue you are permitted to discuss. Practice explaining the original behavior, the relevant code, the evidence you gathered, and how the correction was validated.

Pay attention to the point where suspicion became a confirmed finding. If a colleague challenged your conclusion, what observation would resolve the disagreement? That question can reveal gaps in an otherwise polished explanation.

Also review an example where your first hypothesis was wrong. Explaining how you changed course can demonstrate more useful judgment than describing every investigation as immediate and straightforward.

Practice concise written reasoning

Write a short technical explanation for an engineer who has not seen your project. Start with the observed behavior, identify the relevant condition, and connect the proposed change to a testable result.

Then remove claims that your evidence does not establish. For instance, a demonstrated permission failure in one operation does not automatically prove that every endpoint has the same problem. Clear boundaries make a report more credible.

Aim for enough detail that a reviewer can follow the reasoning without a separate conversation. That is different from including every command or every abandoned debugging step.

Review testing and verification fundamentals

The OWASP Web Security Testing Guide provides a public resource for web application security testing. The OWASP Application Security Verification Standard provides security requirements relevant to application design and verification.

Use these resources to revisit areas where you have practical experience and identify concepts you need to refresh. Neither is described as a mandatory Mercor syllabus in the listing.

Check your recording setup

Test your camera, display-sharing permissions, and internet connection before starting. Close unrelated applications and personal notifications so they do not interrupt your work or appear in the recording.

Mercor’s assessment guidance explains that AI-generated answers and external collaboration are prohibited unless expressly allowed. Read the rules displayed for your assessment and complete the work independently. Any accommodation request should be raised through Mercor’s stated process before the assessment where possible.

Building a useful security work sample

A well-chosen sample can help you explain your experience, even when an application does not request a portfolio. Use material you own or have permission to share. The following is an illustrative practice structure, not a required submission for this role.

Example: a permission-check regression

Imagine a small local application with two test accounts and separate private resources. Your practice project examines whether one account can access a resource belonging to the other.

The useful engineering story is the authorization rule: which account should be allowed to perform which operation? Once that rule is explicit, the investigation, correction, and tests can all be judged against the same expectation.

Document the result in a compact format:

  • Scope: The local application, relevant component, and test accounts.
  • Expected behavior: The permission rule that should govern access.
  • Observed behavior: What the vulnerable version actually allows.
  • Cause: The implementation condition responsible for that difference.
  • Correction: The change and why it enforces the intended rule.
  • Verification: Evidence from the original failing case and legitimate access cases.
  • Limitations: Behaviors or components your sample does not evaluate.

Make the sample easy to assess

Include clear setup instructions, a small amount of relevant code, and readable tests. A focused example with a convincing explanation is easier to review than a large repository with no obvious starting point.

You should also be able to discuss tradeoffs. Why was this check placed at that boundary? Could a different legitimate workflow be affected? What evidence would suggest the fix needs further work?

If you cannot share employer code, an independently created demonstration can show your reasoning without exposing the original implementation. Label it as a demonstration and keep its claims proportional to what it proves.

Presenting your experience clearly

Your resume and application should make it easy to connect your professional history to this work. Organize examples around the decisions you made and the outcomes you verified.

Describe your contribution

Instead of a broad statement such as “responsible for application security,” explain the component you reviewed, the issue you investigated, and your part in correcting it. Distinguish your contribution from the team’s overall result.

A useful structure is: action, scope, evidence, result. For example, describe a review you performed, the class of behavior you investigated, how you confirmed it, and how you verified the remediation. Include numbers only when you have records or another reliable basis for them.

Connect coding with communication

Select examples that show you can move between implementation details and clear explanation. A strong sample might combine a focused change, a regression test, and a report that explains their relationship.

If you have worked with developers, describe how you resolved disagreement about a finding or clarified an ambiguous requirement. Review work often depends on making technical judgment understandable to another person.

Cloud administration, networking, and general IT support can provide valuable context. However, the most relevant evidence here concerns code security and the stated professional-experience threshold.

Give your strongest matching work the most space. Keep training and certifications visible without allowing them to obscure what you have actually implemented, investigated, or verified in a professional setting.

Questions to resolve before accepting work

Once you are being considered for an engagement, focus on the terms that affect how you will deliver and be paid. The short listing leaves several practical points open.

QuestionWhy the answer matters
What constitutes one complete task?Establishes the boundaries of the deliverable.
What are the acceptance criteria?Explains how completion and payment eligibility are assessed.
How are revision requests handled?Helps you understand the total work involved.
Is setup or onboarding compensated?Clarifies the time commitment before production tasks.
How often are tasks available?Helps you assess whether the opportunity fits your schedule.
What environment and tools are provided?Establishes what you must prepare and which resources you may use.
What are the payment timing and currency?Gives you the information needed to plan around the engagement.

Ask about the circumstances that would affect your decision, then review the written terms. For a task-based contract, understanding scope and acceptance is especially useful before comparing the fee with another opportunity.

Application checklist

  • Confirm that you meet the three-year professional-experience requirement.
  • Identify relevant code-security work you can explain in detail.
  • Update your resume with accurate dates and specific contributions.
  • Separate professional experience from labs, coursework, and certifications.
  • Check location and payment eligibility through Mercor’s current guidance.
  • Prepare your computer for typed answers and camera/screen recording.
  • Read the assessment’s rules before starting.
  • Complete every step requested in the application.
  • Review the displayed submission status.
  • Clarify task scope, acceptance, revisions, and payment terms before accepting work.

For other opportunities, visit our AI Training & Evaluation Jobs page or Find Remote Jobs hub.

Frequently asked questions

Is the Mercor Cyber Engineer job remote?

Yes. Mercor labels the opportunity remote. The role description does not specify a country or state, so check the current listing, payment-country support, and any eligibility questions presented during application.

Is the pay $400 an hour?

No. The advertised rate is $400 per task. Mercor estimates five hours per task, which works out to $80 per hour for comparison if a task takes exactly that long and the full fee is payable.

Can a beginner qualify for this role?

The listing requires at least three years of relevant professional experience. It is aimed at experienced applicants; personal labs or introductory certifications should not be represented as professional employment.

Is an AI interviewer part of the application?

The role description explicitly says there is no AI interviewer. It specifies a recorded assessment with typed answers and camera/screen recording. Follow the instructions for this particular assessment.

Does Mercor name a required programming language?

The description calls for strong coding skills but does not name a specific language. Present the languages you use confidently and the security work you have performed with them. Check for any additional requirements in the application.

Is the referral offer an applicant bonus?

The listing’s “up to $250” referral offer concerns eligible referrers. It is separate from the applicant’s $400 task compensation. Mercor’s referral policy describes earnings sharing, eligibility, and caps; signing up alone does not establish a payout.

Where can I apply?

Open the Mercor Cyber Engineer application through our referral link, review its current terms, and complete the requested steps. If the opportunity is closed, explore other active listings through Mercor.

Sources

Leave a Reply

Your email address will not be published. Required fields are marked *