Frontend / UI Engineer

$70–100/hr

rate as listed

Workload: ~15h/week
Engagement: Project-based
Location: Worldwide
Field: STEM and Coding

Create frontend coding tasks from screenshots, mockups, diagrams, and screen recordings, then build reference implementations and objective grading criteria. The work is remote and project-based, with a public GitHub profile required for verification of hands-on engineering experience.

The work

You will translate visual material, such as screenshots, UI mockups, diagrams, and workflow recordings, into multi-step frontend coding tasks. Each task needs clearly identified code and artifacts, expected behavior, reproducible success criteria, and a working reference implementation. You may also review other contributors’ tasks, test their technical accuracy, and flag work that cannot be graded reliably.

What the platform screens for

The screening emphasizes verifiable frontend experience and precise evaluation judgment. A public GitHub profile with substantial contributions is essential. Strong frontend engineering with React, TypeScript, or similar technologies is expected, including the ability to read, modify, debug, and validate real application code. Experience with UI, graphics, SVG, or Canvas is especially valuable, while prior data labeling, AI evaluation, or rubric-based review experience is preferred but not required. Strong written English is required for explaining behavior and verification steps.

Working model

The role is fully remote and structured around project-based tasks that are paid after approval. A typical task is described as taking about eight hours. The listing presents the work as task-based rather than scheduled shifts, but it does not explicitly guarantee fully asynchronous scheduling or a fixed volume of work.

Pay band: $70–100/hr

What they look for

React
Typescript
FrontEnd
UI Design
Graphic OSS Contributions
Product/UI design
GitHub
Debugging

Included with this listing

Interview prep — 10 questions

Matched to what this platform's screening actually measures. Answer each out loud in 60–90 seconds: claim → concrete example → implication.

What it tests: This tests whether your claimed experience can be matched to commits, merged pull requests, or maintained repositories that a reviewer can inspect.
A strong answer: Name a specific public repository or pull request, describe your technical ownership, and distinguish your code from collaborators’ work. Include the interface behavior, architecture, or debugging decisions visible in the contribution history.
Where people lose it: Candidates lose points by discussing a private employer project or linking a profile whose visible activity consists mainly of forks, tutorials, or minor edits.

Summary, eligibility guidance and screening preparation are prepared by Sidequest from the platform's posting. Check the source listing before applying.

STEM AND CODING on Sidequest

What stem and coding AI work pays

Rates by specialty, the platforms hiring, and every open role in this field.