> Markdown version of [/jobs/ext/4636750-frontend-ui-engineer](https://www.wearedevelopers.com/jobs/ext/4636750-frontend-ui-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Frontend / UI Engineer

- **Company:** Pro Integrate
- **Location:** New York, NY, United States (Remote available)
- **Salary:** $145,600.0 - $208,000.0
- **Contract:** Permanent contract
- **Skills:** AI Evaluation, Reference Implementation, Software Debugging, Github, Design of User Interfaces, Human-Computer Interaction, Scalable Vector Graphics, TypeScript, ReactJS, Front End Software Development
- **Published:** November 8, 2026
- **Apply:** https://www.careerbuilder.com/job-details/frontend-ui-engineer-new-york-ny--a605415d-0d3f-46bb-b4a2-ca9af443b162

## About the Role

User Interface/Experience (UI/UX), User Interface/Experience (UI/UX), User Interface Design, Operational Support Systems (OSS), Product Design, GitHub, Mock Up, Debugging Skills, Graphics, SVG (Scalable Vector Graphics), React
Typescript
FrontEnd
UI Design
Graphic OSS Contributions
Product/UI design
GitHub
Debugging, 1. A public GitHub profile with substantial, verifiable contributions - commits, merged PRs, or repositories you maintain. This is essential.

 2. Strong frontend engineering:React, TypeScript, or similar,with experience shipping complex interfaces and interactions.
 3. Able to read, modify, debug and validate real application code.
 4. Experience with UI, graphics, SVG, or Canvas work is especially valuable.
 5. Product or UI designers with hands-on frontend implementation and public code contributions are also a fit.
 6. Strong written English, and the ability to explain expected behavior and reproducible verification steps.
 7. Prior data labeling, AI evaluation, or rubric-based review experience is a plus, not a requirement.

## Description

1. Design multi-step coding tasks grounded in visual material: screenshots, UI mockups, diagrams, or screen recordings of real workflows.
 2. Specify which code and artifacts the task involves, and what the expected behavior is.
 3. Define objective success criteria - how someone would verify the task was completed correctly, not just plausibly.
 4. Provide a working reference implementation.
 5. Review tasks built by other contributors for technical accuracy and verifiability.
 6. Flag tasks that turn out to be ambiguous or ungradable rather than submitting them.