Senior SWE-Bench: open-source benchmark that assesses agents as senior engineers
Senior SWE-BenchWe treat agents like senior engineers, so why evaluate them like junior engineers?01Senior engineers build features without over-specified requirementsSenior SWE-Bench feature tasks have realistic instructions that read like natural language messages rather than over-specified requirements. This presents a problem when metadata is missing, malformed, or incomplete—particularly for books with only ISBN-13s. As a result, incomplete records submitted via promise items or `/api/import` may fail to be enriched, leaving poor-quality entries in Open Library.
- ▪Senior SWE-BenchWe treat agents like senior engineers, so why evaluate them like junior engineers?01Senior engineers build features without over-specified requirementsSenior SWE-Bench feature tasks have realistic instructions that read like
- ▪This presents a problem when metadata is missing, malformed, or incomplete—particularly for books with only ISBN-13s.
- ▪As a result, incomplete records submitted via promise items or `/api/import` may fail to be enriched, leaving poor-quality entries in Open Library.
Hacker News (Front Page) files mainly under programming. We currently carry 993 of its stories. Top-voted stories on Hacker News.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Senior SWE-Bench |
| Canonical URL | https://senior-swe-bench.snorkel.ai/ |
| Publication time | Thu, 02 Jul 2026 02:55:16 +0000 |
| Retrieval time | 2026-07-02T03:29:45.693Z |
| Last seen | 2026-07-02T03:50:14.914Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | cfiV-jfnzulN |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Senior SWE-BenchWe treat agents like senior engineers, so why evaluate them like junior engineers?01Senior engineers build features without over-specified requirementsSenior SWE-Bench feature tasks have realistic instructions that read like natural language messages rather than over-specified requirements. To reliably evaluate these tasks, we introduce a validation agent which uses expert-designed recipes to write behavioral tests that adapt to submitted solutions.02Senior engineers solve bugs that require runtime investigation from behavioral reportsSenior SWE-Bench bug tasks reflect tricky user reports and focus on investigation, from starting services to debugging subtle runtime issues. They are sourced from PRs that needed significant runtime investigation to solve (e.g.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Senior SWE-Bench.
Discussion
0 commentsMore from Senior SWE-Bench
