New-Grad-Positions: 574 entry-level roles in a README with no salary column
A collection of full time roles in SWE, Quant, and PM for new grads.
At a glance
- What is it?
- The SimplifyJobs New-Grad-Positions repository is a daily-updated README table of 574 entry-level roles with an age column, a five-marker legend and no salary data, distributed through issues on the dev branch rather than releases.
- Who is it for?
- This repository is worth bookmarking for anyone applying to 2026 entry-level software, hardware, data, quant or PM roles, because the age column and the sponsorship legend compress what a career page buries. It is not a source for compensation, and it is not a data source for a tool you need to keep working, since the dev branch moves daily and there is no release or LICENSE file to pin.
- Can I use it commercially?
- Not without permission. GitHub finds no licence file in the repository, and without a licence all rights are reserved by default: you may read the code but not reuse it. Check the README, or ask the authors, before using it.
- Is it still maintained?
- Yes. The repository received new commits within the last day.
- What is it written in?
- GitHub does not report a main language for this repository.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- SimplifyJobs/New-Grad-Positions18,374 ★ · +647
| Repository | 2026-08-22 | 2026-11-15 |
|---|---|---|
| SimplifyJobs/New-Grad-Positions | 17.7k | 18.4k |
647 Stars in the last 85 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The whole artifact is a README table keyed by an HTML comment
There is no source directory, no package manifest and no build step here. The repository root holds .github/, CONTRIBUTING.md, README.md and archived/, and everything a reader consumes is the rendered README on the dev branch. That makes the file's internal structure load bearing. Downstream scrapers locate the table through a literal marker left in the HTML:
<!-- Please leave a one line gap between this and the table TABLE_START (DO NOT CHANGE THIS LINE) -->The comment instructs whoever edits the file to keep one blank line above it and to leave that exact line untouched, which means the table's position between the marker and the next heading is a contract rather than a formatting preference. Move the gap, reword the comment, or insert a section between the legend and the first category and anything slicing the file on that boundary silently starts returning nothing.
Contributions follow the same low-ceremony route: the README asks for an issue and points to CONTRIBUTING.md for the guidelines, so the data arrives as issue text and lands in the file through whatever review that file goes through.
Six categories that add up to 502, with Other sitting at zero
The index near the top of the file breaks the list into Software Engineering 324, Data Science, AI and Machine Learning 96, Hardware Engineering 111, Quantitative Finance 25, Product Management 18 and Other 0. Those six numbers total exactly 574, which matches the headline count, so the index is a complete census rather than a rounded summary. The empty Other bucket shows a taxonomy slot that nothing currently fills, and it is the kind of gap that quietly absorbs roles nobody has classified yet.
Distribution matters more than the total. Software engineering is just over half of everything listed. The repository description still reads "A collection of full time roles in SWE, Quant, and PM for new grads", which covers 324 plus 25 plus 18, or 367 of the 574 rows. Hardware engineering and data science together account for another 207 rows the description does not mention, so anyone filtering their expectations by the project's own summary line will underestimate what is there.
The year framing is looser still. The title reads 2026 New Grad Positions, while the introduction describes the list as covering entry-level software, tech, CS, PM and quant jobs for 2025 and 2026 new graduates.
Sponsorship, citizenship and closed postings live in a five-marker legend
Everything the list says about eligibility is compressed into five legend entries: a marker for roles that do not offer sponsorship, a marker for roles requiring U.S. Citizenship, a marker for a closed application, a marker for a FAANG+ company, and a marker for an advanced degree requirement of a Master's, PhD or MBA. No column carries any of this. A reader looking for a role that will sponsor has no field to sort on, so the filter is a per-cell glyph decoded against a legend they have to find and remember.
The closed marker is the one with the longest tail. A list with no retirement mechanism cannot quietly drop a dead posting, which is exactly why the legend has a closed entry, and the repository root also carries an archived/ directory. Either way, staleness is marked in place rather than removed, so a row's usefulness depends on you reading the marker and the age together.
The FAANG+ marker is a third signal nobody would guess from a job title, and it changes how you read a row that also carries a closed marker.
The Age column counts days since the row landed, not since the role opened
Five columns make up each row: Company, Role, Location, Application and Age. Age is the only time field in the entire file, and the values visible at the top of the table run from 0d to 3d. There is no posting date, no application deadline and no per-row refresh timestamp, so a 0d means the row appeared in the list that day, not that the employer opened the role that day. A posting that stays open for months ages with the list rather than with the employer.
The README states that the list is updated and maintained daily by Coder Quad and Simplify, and the 0d bucket is the visible evidence of that: the first entries in the software engineering table are 0d, followed by 1d, 2d and 3d rows. What the file offers no mechanism for is the other end. Nothing sorts by Age, nothing filters it, and no cell records when a posting closed, so a reader who wants this morning's roles has to walk the first rows themselves, and a reader who wants a role that is still open after two weeks has to open every employer link to find out.
Two application links per row, and the second one is a tracking URL
Each row's Application cell holds two anchors. The first goes to the employer's own applicant tracking system, and the second is a UUID path on simplify.jobs. Company names are links too, pointing at a per-company page with utm_source=GHList and utm_medium=company, while the employer links carry utm_source=Simplify and ref=Simplify.
Those employer destinations are not uniform. The visible rows reach Qualtrics' own careers site, two Greenhouse hosts (boards.greenhouse.io for Databricks and job-boards.greenhouse.io for Built Technologies), Ocado's careers site, Google's careers site, a MyWorkday tenant at unitytech.wd1 and a SuccessFactors page at careers.huntingtoningalls.com. A single vendor therefore hosts several unrelated boards, which means the domain alone tells you nothing about the posting.
The practical consequence is that the simplify.jobs UUID is the only stable handle for a posting inside this list. The ATS URLs are per-tenant, so anything you build on top has to store the second link, and every click from the table travels through a redirect carrying the campaign parameters attached to the row.
Locations arrive three ways, and the arrow row has no company at all
One posting can be one row with a collapsed location list, one row with a single location, or a row with no company name at all. Google's Software Engineer 2 – Early Career entry folds 12 locations into a details block, from Palo Alto, CA and Madison, WI to Sunnyvale, CA and Mountain View, CA. Most other rows carry a single place, such as Seattle, WA or London, UK. Qualtrics then has a second row that begins with an arrow glyph instead of a company link: Software Engineer 1 - XMD in Seattle, WA, listed under the company's Software Development Engineer 1 - Data Platform row.
The arrow row is the part that breaks tooling. It has no company cell, so it cannot be joined on the column every other row uses, and a script has to carry the company down from the row above. A script that skips rows without a company undercounts roles. A human reading it gets the information immediately, which is the trade the file makes: the format optimises for scanning in a browser and pays for it in parseability.
The location strings are free text as well, with abbreviations such as LA and NYC sitting in the same column as city and state codes and full country names, so anything downstream has to normalise them by matching the text.
No salary column, and two ad blocks share the file with the data
Salary is not among the five columns. Neither are team, level, interview stage, work model or years of experience. Every one of the 574 rows still sends you to the employer to learn what it pays, and for anyone who searched this list looking for new grad salaries, the field they wanted most is the one the format leaves out.
Two promotional blocks sit in the same file. One is for a browser extension that autofills job applications, described as working on millions of sites. The other points at SWEList on swelist.com, a service described as built by a community member that sends email alerts for new roles added to the repository, and the repository's only recorded homepage is that service. So the alerting path is a third-party project, not a feature of the repository itself.
Both blocks sit between the category index and the data, which means any consumer of the file has to skip them to reach the table. For a README whose value is being machine-readable, that is an avoidable cost, and it is the part that can change without notice.
The dev branch moves daily and there is no release to pin
The default branch is dev rather than main; no GitHub releases or Git tags were visible when checked. The last push was 2026-11-01, consistent with the README's claim of daily maintenance, but it also means the branch tip is a moving target by design. If you script against this README, a commit sha is the only reference that stays put, and you have to expect the row you cached yesterday to be edited, re-marked or reworded tomorrow.
The root directory lists no LICENSE file alongside .github/, CONTRIBUTING.md, README.md and archived/. The terms for reusing or republishing the compiled list are therefore not stated in the repository, and a fork inherits both the data and that silence. The archived/ directory exists; whether past cycles are kept there is something a reader has to check on the repository itself.
For a document rather than a program, that is a fair trade. You get a list that changes every day without waiting for a release, and you give up any promise about what yesterday's version said.
Editorial conclusion
This repository is worth bookmarking for anyone applying to 2026 entry-level software, hardware, data, quant or PM roles, because the age column and the sponsorship legend compress what a career page buries. It is not a source for compensation, and it is not a data source for a tool you need to keep working, since the dev branch moves daily and there is no release or LICENSE file to pin. Open the employer's posting before you apply, check whether the row carries the sponsorship or citizenship marker, and treat the 0d age as the day the row landed rather than the day the role opened.
Frequently asked questions
What are some good job titles for a fresh graduate in the New-Grad-Positions list?
The Role column shows employers labelling the same early-career band in different words: Software Development Engineer 1 - Data Platform, Software Engineer New Grad, Software Engineer 2 – Early Career, Software Developer New Grad - U-Accelerate, Software Engineer 1 and Innovation Software Engineer 1 - Marketplace. Reading across the list is the point of the repository, since no single company's naming tells you what else to search.
What are graduate positions in the New-Grad-Positions list?
The repository scopes itself to entry-level software, tech, CS, PM and quant jobs for 2025 and 2026 new graduates, while the README title reads 2026 New Grad Positions. Nothing in the repository defines the term beyond those categories and the job titles companies write in the Role column.
What are the new grad positions tracked in New-Grad-Positions?
The README presents 574 roles across six categories, from 324 software engineering rows down to an empty Other bucket, and the repository describes itself as a collection of full time roles in SWE, Quant and PM for new grads. The Age column marks the newest rows at 0d to 3d, and the list is stated to be updated and maintained daily by Coder Quad and Simplify.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/simplifyjobs-new-grad-positions)Star history chart for your README
[](https://hysenlabs.com/projects/simplifyjobs-new-grad-positions)Was this useful?