Software Benchmark Engineer (Remote)
Joblet-AI
- Local
- Remoto
- Contratação
- Freelance
- Publicada
- (horário de Brasília)
- Fonte
Candidatar-se no site original (LinkedIn) nenhum clique aindaQuantas vezes alguém abriu o anúncio original a partir do Vagas Front-end desde que a vaga entrou no site. Dá uma noção da concorrência, mas não inclui quem viu a vaga direto na fonte (LinkedIn, Gupy...), e a mesma pessoa pode contar mais de uma vez.
Descrição
• Role Title: SWE Coding Benchmarks & RL Environments
• Role Type: Contractor
• Location: Remote
What the work involves
1. Writing realistic engineering tasks on full-stack web apps: the kind of problem a real team has in its backlog, on codebases that grow as each task builds on the last.
2. Writing the tests that decide whether a solution is correct.
3. Going beyond the UI: new services and APIs, a backend in another language (Go, Rust, Java), gRPC, rate limiting — drawing on systems you've actually built.
4. Sharing what you've seen work in other projects and flagging what should change in ours.
The apps are TypeScript (React, Node, SQLite, Playwright). Use AI tools as much as you like to write code and tests.
What we're looking for
1. Solid professional software engineering experience, backend and frontend.
2. You've built and debugged real systems, and you care about testing them well.
3. Clear written communication, and comfort working independently from written docs.
4. 10–20+ hours a week, starting soon.
How it works
A short screener, a brief AI interview, and a paid work trial on the codebase you'd keep working on. US and Canada preferred for timezone overlap; exceptional candidates elsewhere are welcome. LinkedIn and GitHub required.
What You’ll Do
1. Writing realistic engineering tasks on full-stack web apps: the kind of problem a real team has in its backlog, on codebases that grow as each task builds on the last.
2. Writing the tests that decide whether a solution is correct.
3. Going beyond the UI: new services and APIs, a backend in another language (Go, Rust, Java), gRPC, rate limiting — drawing on systems you've actually built.
4. Sharing what you've seen work in other projects and flagging what should change in ours.
Apply Now!