Software Engineering Researcher (Research Coding Tasks)

What You'll Do8

• Convert a recent paper with released code into a self-contained coding challenge an AI agent can attempt.
• Remove the code that carries the paper's central contribution and package the rest as the task scaffold.
• Write a task statement an agent can follow without seeing the hidden answer.
• Define held-out workloads and a pass threshold for every metric the paper reports.
• Build a reference solution that stays out of the agent's reach.
• Supply a second solution that clears the bar, proving the target is reachable.
• Review agent attempts against your thresholds and judge the outcome.
• Keep the evaluation setup reproducible so another engineer can rerun it from scratch.

Requirements6

• Published software engineering research at ICSE, FSE, ASE, ISSTA or a comparable venue.
• A PhD in computer science or a neighboring field, finished or underway.
• Public code for at least one paper, shared through GitHub or an artifact link.
• Preferred: first-author papers that report measured gains over a baseline.
• Preferred: hands-on work with Docker and benchmark setups others can reproduce.
• Preferred: depth in test generation, program repair, static analysis or mining software repositories.

Who Should Apply

Researchers who publish in software engineering and ship the code behind their results. The role suits a PhD candidate or graduate who wants their own paper rebuilt as an agent benchmark and can set pass thresholds that hold up under review.

Salary Insight