> Markdown version of [/jobs/ext/2099327-software-engineering-evaluation-specialist](https://www.wearedevelopers.com/jobs/ext/2099327-software-engineering-evaluation-specialist). 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). --- # Software Engineering Evaluation Specialist - **Company:** Búsqueda Avanzada - **Location:** Valencia, Spain - **Salary:** €93,600.0 - €166,400.0 - **Contract:** Permanent contract - **Skills:** Java (Programming Language), Artificial Intelligence, JIRA, Bash Shell, Cron, Extract Transform Load (ETL), Cursor (Graphical User Interface Elements), Software Debugging, Linux, DevOps, Python (Programming Language), Nginx, Node.Js, NumPy, Scientific Computating, SciPy, Software Engineering, Pytorch, Prompt Engineering, Backend, Git, Pytest, Production Code, Docker, Golang - **Published:** August 18, 2026 - **Apply:** https://www.adzuna.es/contact-us.html ## About the Role + 3+ years of production software development in one backend stack - Python, Go, Node.js, Java, or Rust. Depth in one stack beats breadth. + Python + pytest fluency - required regardless of primary stack. The task harness is pytest-based even when the broken app is in another language. Fixtures, parametrize, monkeypatch, timeouts, conftest.py. + Docker authoring - reproducible Dockerfiles, pinned dependencies, multi-stage builds when needed, non-root user. + Linux & Bash - comfort debugging inside containers (strace, lsof, journalctl); shell beyond set -euo pipefail. + AI coding agent experience - Claude Code, Cursor, Roo Code, or similar, on non-trivial work. You can cite a specific time the AI was confidently wrong and how you caught it. + English - B2+ written., + Domain depth in Security, System Administration (nginx / systemd / cron), Scientific Computing (NumPy / PyTorch / SciPy), DevOps, or Git internals. ## Description + Invent a realistic developer scenario - a real bug, a broken ETL, a missing feature - not a toy problem. + Build a reproducible Docker environment with pinned dependencies. + Write a pytest that verifies outcomes, not specific commands - deterministic, non-flaky, and does not leak the fix. + Write an instruction.md that reads like a Jira ticket a developer would receive. + Write a reference solve.sh proving the task is solvable. + Calibrate difficulty so current state-of-the-art agents solve the task 20-60% of the time. + Iterate based on feedback from expert QA reviewers. + Later: review other authors' tasks as a QA reviewer. Not in scope + Data labeling, prompt engineering. + Production code to ship - you design problems and verification for AI agents. + Leetcode puzzles - scenarios must look like real developer work. + Not every candidate task ships - quality over quantity., Apply * Pass qualification (90-minute sample-task screen + short behavioral interview) * Join a project * Complete tasks * Get paid. Time commitment + Onboarding: ~10 hours per first task. + Steady state: ~5 hours per task, 2-4 parallel tasks per author. + Realistic weekly load: 8-20 hours. Higher volume available for top performers. + You choose when and how to contribute; tasks must be submitted by the deadline and meet acceptance criteria. ## Related Videos - [Improving quality with Agentic AI with Rovo Dev and Xray](https://www.wearedevelopers.com/videos/2005-improving-quality-with-agentic-ai-with-rovo-dev-and-xray) - [From Punch Cards to AI-assisted Development](https://www.wearedevelopers.com/videos/611-from-punch-cards-to-ai-assisted-development) - [From clicks to cribs - How to find your dream home with web scraping](https://www.wearedevelopers.com/videos/767-from-clicks-to-cribs-how-to-find-your-dream-home-with-web-scraping) - [How a Small Team Shrank a Microsoft Monorepo by 94%](https://www.wearedevelopers.com/videos/1236-how-a-small-team-shrank-a-microsoft-monorepo-by-94) - [The AI-Ready Stack: Rethinking the Engineering Org of the Future](https://www.wearedevelopers.com/videos/1706-the-ai-ready-stack-rethinking-the-engineering-org-of-the-future) - [Is your backend a hodgepodge of queues, event stores and cron jobs? Durable Execution to the Rescue.](https://www.wearedevelopers.com/videos/744-is-your-backend-a-hodgepodge-of-queues-event-stores-and-cron-jobs-durable-execution-to-the-rescue) ## Related Articles - [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers) - [Dev Digest 131 - AI'm not sure about OSS](https://www.wearedevelopers.com/magazine/472-dev-digest-131-ai-m-not-sure-about-oss) - [How We Built a Worry-Free System That Runs for 10+ Years – And What We’d Do Again](https://www.wearedevelopers.com/magazine/751-how-we-built-a-worry-free-system-that-runs-for-10-years-and-what-we-d-do-again) - [Dev Digest 121 - AI goes offline](https://www.wearedevelopers.com/magazine/456-dev-digest-121-ai-goes-offline) - [Dev Digest 137 - AI'm not sure about this](https://www.wearedevelopers.com/magazine/485-dev-digest-137-ai-m-not-sure-about-this) - [Is Software Engineering Over-Saturated?](https://www.wearedevelopers.com/magazine/418-is-software-engineering-over-saturated)