LuisaE/opportunities: a curated map of student CS programs

A list, and the README says so first

The repository is named opportunities, it is described as a list of CS and Finance exploratory programs, underclassmen internships, interview prep, scholarships, part-time internships, mentorship programs, and more, and the homepage is a GitHub Pages site at luisae.github.io.

What makes the opening of the README notable is that it is a disclaimer rather than a description. It says it is possible that some of those opportunities are not available anymore, or the deadlines are completely wrong, and then in bold: double check the deadlines.

That warning is the defining characteristic of the project and it sets expectations properly. A list of opportunities is a list of facts about the world outside the repository, and those facts decay. Programs close, cohorts fill up, and application windows move. Any list that claims otherwise is either smaller than this one or less honest.

The primary language is recorded as SCSS, which reflects the shape of the repository. The top level entries are README.md, a _config.yml, an assets directory and a PDF called getting-tech-internship-latest.pdf. The _config.yml and the assets directory are the marks of a Jekyll site, so the README is the source and the rendered site is the product. The PDF is the guide described later in the document, shipped alongside it.

There are no GitHub releases and the licence is recorded as unknown. For a document that is a defensible position, since the list of links belongs to the employers rather than to the author, but it does mean you should not assume you may fork and republish it.

Fourteen sections, ordered by who the opportunity is for

The table of contents in the README lists fourteen areas, and the ordering is the interesting part because it is organised around the reader rather than around the topic.

It opens with CS underclassmen internships, then CS internship alternative, part-time internships, and for rising seniors and seniors. After the internship cluster come CS exploratory programs, CS conferences and scholarships, coding interview resources, CS Mentorship, CS Scholarships, CS Research, CS REU, then Finance and consulting exploratory programs, and finally a bonus section on resume and tips.

So the first four sections are about the job market itself, split by career stage. A freshman or sophomore reading this is directed to underclassman internships, a student who is not eligible for those is pointed to the alternative section, and the part-time section covers work that fits around a course schedule. The rising seniors and seniors section collects the programs that only open to students about to graduate, which is a real and separate application cycle.

The middle block is the non-internship half of the pipeline. Exploratory programs are the multi-week training programmes such as the ones described for New Technologists and Duolingo Thrive. Conferences and scholarships are the travel-and-network side. Coding interview resources is a study aid rather than an opportunity, and it sits in the list because it serves the same reader at the same moment. Mentorship is the ongoing support path, and research plus REU cover the academic route, with REU meaning research experience for undergraduates.

The final two sections widen the scope. Finance and consulting exploratory programs are the banking and consulting equivalents of the technology programmes, and the resume and tips section is the only part of the document that is advice rather than a list.

For a reader, this structure means you can find the section that matches your stage in about five seconds, which is more than most opportunity lists manage.

What a single entry looks like

The entries are tables with three columns, a name, a description and an approximate deadline, and the format is consistent enough that you can scan a column of deadlines down a page.

A representative row looks like this in the source:

| [Microsoft Explore](https://careers.microsoft.com/students/us/en/usexploremicrosoftprogram) | Explore Microsoft is a 12-week summer internship program specifically designed for first and second year college students. The program is rotational and allows you to gain experience in our different software engineering roles (SWE + PM). Phone interview + Onsite. | No fixed deadline, apply early. |

The description column is written in the employer's own words, taken from the programme page, and it includes the details a candidate actually needs: the length of the programme, the selection process, and who the programme is aimed at. In this case, a 12 week rotational internship for first and second year students, with a phone interview and an onsite.

The deadline column is where the honesty lives. Most entries give a month rather than a date, and the qualifiers are varied and specific. Microsoft Explore has no fixed deadline and says apply early. Google ASDI lists October. Uber STAR lists October. Palantir Path lists September. New Technologists lists February. Two Sigma lists early December. Dropbox Launch lists December with a question mark, and that single question mark is doing real work: it tells you the author was not certain and did not want to hide that.

The Jane Street Immersion Program and the Visa Sophomore Internship Program have empty deadline cells, which is arguably more honest than a guessed month.

The descriptions also carry the eligibility criteria explicitly. Uber STAR is a 12 week paid internship for undergraduate freshmen and rising sophomores, and it says students who identify with a group historically underrepresented in the technology industry are encouraged to apply, naming Black, Hispanic, Native American, students with disabilities and veterans. Duolingo Thrive is for second-year students from underrepresented communities, Google ASDI has a focus on providing development opportunities to students from groups historically underrepresented in tech, and Palantir Path says the same. If that is a filter you need, the list applies it consistently across employers, which is more useful than reading each programme page.

What the list points you to instead of duplicating

The repository is explicit about scope in two places, and both are about not duplicating other people's work.

The first is summer internships. For Summer SWE internships the README directs you to the Summer 2027 CS Internships list on SimplifyJobs, and the same redirect appears in the underclassmen section with a check on not being a freshman or sophomore. So the most contested category, the general software engineering internship for students, lives elsewhere, and this repository covers the programmes that list is not designed to capture.

The second is deadlines. The README points to Carleton's Career Center Calendar for more opportunities and deadlines. A career centre calendar is a live, maintained feed of events, whereas a table in a markdown file is a snapshot. Directing readers to the live source for the volatile half of the information is the right call.

There is a third artefact, the getting-tech-internship guide, which is a Google Doc rather than a link out to something generic. The README says it is written and reviewed by Carleton College students, class of 2022 and 2023, as a guide for other Carleton students on finding tech internships or new grad positions, and that their contacts are listed at the end of the document. The repository ships it as a PDF, getting-tech-internship-latest.pdf, so the guide is available even if the live document moves.

The pattern across all three is the same. This repository holds the specific, structured programme list, and it points to other people for everything else: the broad internship list, the live deadline feed, and the narrative advice. For a student who wants one place to look, that division makes sense, since a general career page cannot be a list and a list cannot be advice.

What the repository cannot tell you

The limits follow from the format, and they are worth being concrete about.

The first is staleness. The README states the possibility outright: some opportunities may not be available anymore, or the deadlines may be completely wrong. A markdown table has no mechanism for detecting a closed programme, and no automated check is described that would query each employer's page. The repository is not archived and the last push was on 2026-09-18, so somebody is maintaining it, but the maintenance is manual and the correctness of any single row depends on when it was last checked.

The second is scope. The list is aimed at students, and the audience is stated in the repository description as computer science students and the topics as computer-science-students, opportunities and software-engineering. There is no listing for contract roles, no alumni network, and no information about what a role is like once you are in it. It answers what exists and roughly when to apply, not what to expect.

The third is that the finance and consulting entries are a different shape. The Finance and consulting exploratory programs section sits at the end and, in the portion of the document visible here, does not yet show its entries. The exploratory programme model in banking, with its own timeline and its own application mechanics, is not the same as the technical programme model, and the earlier sections are built around the technical one.

The fourth is that a link is not a relationship. The list tells you a programme exists and roughly when to apply. It does not tell you the acceptance rate, the compensation, whether the internship converts to a return offer, or whether the alumni recommend it. Those questions need the employer, a current student, or the career centre.

Finally, the resource comes from one institution's perspective. The guide is written and reviewed by Carleton College students for Carleton students, and the repository is hosted under the LuisaE organisation. The list itself is broader than that, but the angle of the advice is not neutral, and the career centre calendar it points to is Carleton's.

How to use a list like this without wasting a weekend

The practical advice follows from the structure, and it is short.

Work one section, not the whole document. A student who is a first year student should read the underclassmen internships section and the exploratory programs section, and ignore the rest. A rising senior should read the senior section, the research and REU sections, and the interview prep resources. Reading all fourteen is how a deadline passes unnoticed.

Then treat the deadline column as a hint about when to look, not as the date to submit. A month listed in the table tells you the application window opens around then, and you should open the employer's page at that point rather than trust the table.

Cross-check the two entries that matter most to you, and only those, against the employer's own careers page. That is the point at which the table's value is highest, because the programmes it covers are the ones you will actually apply to.

Use the career centre calendar for breadth and the repository for structure. The calendar tells you what is happening this week, which is a different question from what a given programme is.

And if you are not a student, the list still has one use, which is as a template for how a student-facing opportunity list should be written. The table format with a stage-first organisation, the explicit eligibility language, the approximate deadlines with their qualifiers, and the honest note at the top are all things you can copy into a similar list for your own institution or your own organisation. The entries themselves are the least reusable part, and the structure is the most.

Editorial conclusion

Adopt this list as a starting index if you are a computer science student looking for internships, scholarships or research and you want one page to scan rather than dozens of career pages. Do not treat it as an authoritative source or a template for your own project, since the entries go stale and the licence is unstated. Verify first that the specific program is still open, because the README itself says the deadlines may be wrong, and cross-check the applications that matter against the employer's own page before you spend an evening on them.

Frequently asked questions

Official sources

1. Issues
2. LuisaE/opportunities on GitHub
3. Project website
4. README