summer-2027-internships is four files and a spreadsheet, and its newest dated row predates its last commit

Four files, one table, and a workbook

The entire repository is four entries: a README, a contributing guide, a licence and a spreadsheet. There is no source code, no site, no build and no release history, which is also why a language detector finds nothing to report. The product is the Markdown table in the README plus a downloadable workbook called internship_tracker.xlsx, announced in a short informal note. The instruction for the workbook is to download it, upload it to Google Sheets, bookmark it, and it works in Excel too. In other words, the tracking layer is a spreadsheet the reader owns rather than a form inside the project, and nothing about it is validated by the repository. Everything else in the repository is convention: a scope section, a legend, a note asking for contributions, and the table itself, sorted newest first, with five columns for company, role, location, apply link and the added date.

The newest dated row sits two weeks before the last commit

Two dates matter here and they do not line up. The Added column carries the date a role was posted, newest at the top, and in the visible rows the dates run from the twenty-first of July 2026 at the top down to the fourteenth of July by the time the page reaches the Hudson River Trading entry, where the table stops mid-row. The most recent commit to the repository is dated the third of August 2026. The author writes that he wants to keep the list active and update it daily, and the file also carries a star prompt asking readers to star the repository to save it and get updates when new roles are added. So the top of the visible table is roughly two weeks older than the last change to the file, and the newest entries below the fold carry whatever dates the portals did expose.

Greenhouse is named as the date problem and is also the main source

There is a note explaining the Added column. The author tried pulling a posted date from each job portal, but a lot of them, naming greenhouse and smaller career sites among them, do not show one publicly, so only some rows are dated and the rest stay a dash. Readers who have a date for one of the undated rows are asked to open a pull request and it will be merged. The tension is visible in the table itself. Most of the visible apply links point at greenhouse boards, covering Chicago Trading Company, The Trade Desk, Databricks, Neuralink, Point72, Five Rings twice, Old Mission and Hudson River Trading, and greenhouse is the first portal named as the reason a row cannot be dated. Other rows come from Ashby, SmartRecruiters, a Workday board, and company career sites of their own.

A four marker legend, two of them about eligibility

The legend explains four inline markers used in the role column. One marks a posting as closed. One marks a role that does not offer sponsorship. One marks a role that requires United States citizenship. The fourth marks a posting that states no term or year, described as a rolling or evergreen requisition where the term has to be confirmed before applying. Two of those four are eligibility rather than status, which is the part a reader scanning a table for a summer programme cares about most, and none of them is enforced by anything except somebody reading the posting and marking the row. The visible rows use them sparingly. Kearney and Company carries the citizenship marker on a remote IT audit internship, Unison at GE Aerospace carries both the no-sponsorship and the citizenship marker, and Neuralink's BCI applications internship carries the no-term marker, which is the one that undercuts the premise of a list organised by term.

One company fills three rows and two links carry a placeholder

Three consecutive rows belong to Solar Turbines, a Caterpillar business, all in San Diego and all routed through the same Workday board host: an IT internship, a business analyst internship and a solutions platforms engineering internship, each titled only with the year 2027 and no term. Two of those three addresses contain a literal XMLNAME segment sitting where the requisition title would normally appear, and the third uses a dashed placeholder form instead of a title. That is what an unrendered template variable looks like in a link a reader is meant to click, and it is the kind of defect the dead link contribution process is meant to catch. Scope is enforced by hand elsewhere too: one visible role is titled for the 2026 to 2027 span rather than a summer term, and three more carry only a year.

Three scope lines, and Canada conditional on stars

The scope is stated in three lines. Software engineering, data and machine learning, hardware, quant and product roles. Positions based in the United States, with United States based remote work accepted. Summer 2027 and the off-season terms of fall, winter and spring. Anything outside that is declared out of scope, and the contributing guide is the reference for adding a role. The about section explains the rest. The author is United States based, built the list for himself, and says that if it ever gets more stars he is open to changing it based on what people need, including adding Canada. He would rather hand the list to someone who can keep it going than let it go inactive.

The author says when he intends to stop

The maintenance note is unusually blunt about the end state. The author has turned down offers to buy the repository, on the grounds that it would only get worse under some company's website with labels and ads, and he says he is doing his part until the big repositories start posting 2027 roles officially. At that point, in his words, it gets almost unmaintainable for one person. Until then he intends to keep going, and the contribution process is the safety valve: a dead link goes into an issue and gets removed, a missing role goes in as an issue or a pull request, and the maintainer calls that the biggest help anyone can give. So the update loop is entirely crowdsourced, including the least glamorous part of it, dating the postings that portals refuse to date.

Editorial conclusion

Treat this as a lead list rather than a source of truth. Every row is a link into someone else's applicant tracking system, and the author says so himself when he explains that many portals never publish a posted date. It is worth using if you want breadth across quant, hardware, product and software roles in one table, and worth ignoring if you need verified terms or sponsorship answers, because those are flagged by hand and the author asks readers to send corrections back as issues. Before you act on a row, open the posting and confirm the term, since an evergreen entry carries a marker precisely because the list could not date it.

Frequently asked questions

Official sources

1. Issues
2. License: MIT
3. README
4. sndsh404/summer-2027-internships on GitHub