Skip to main content

Internship Requirements

All internships added to the list must meet the following requirements:

Valid Categories

Internships must be in one of these categories:
  • Software Engineering - Software development, computer engineering, full-stack, frontend, backend, mobile development
  • Product Management - Product manager, associate product manager (APM), product analyst roles
  • Data Science, AI & Machine Learning - Data science, machine learning, AI research, data engineering, analytics
  • Quantitative Finance - Quantitative trading, quantitative research, fintech engineering
  • Hardware Engineering - Hardware design, embedded systems, firmware, FPGA, circuit design
  • Other - Any other tech-related internships that don’t fit the above categories

Location Requirements

Internships must be:
  • Located in the United States
  • Located in Canada
  • Remote (work from anywhere)

No Duplicates

The internship must not already exist in the list. Before submitting:
  1. Search the README for the company name
  2. Check if the specific position already exists
  3. If it exists but needs updating, use the Edit Internship template instead

Formal ATS Required

Companies must use a formal Applicant Tracking System (ATS) such as:
  • Workday
  • Greenhouse
  • Ashby
  • Lever
  • iCIMS
  • Other recognized ATS platforms
Any company using non-ATS platforms such as Google Forms, Typeform, or other surveys must be verified/approved on Simplify.

Automatic README Updates

A script automatically processes contributions and internships from Simplify, adding them to the appropriate README.

Categorization

Internships are automatically placed into the appropriate category section:
  • Software Engineering
  • Product Management
  • Data Science, AI & Machine Learning
  • Quantitative Finance
  • Hardware Engineering
  • Other

Special Indicators

The system automatically adds indicators to help students identify special requirements or notable companies:
IndicatorMeaning
🔥FAANG+ companies (Google, Meta, Apple, Amazon, Microsoft, etc.)
🎓Roles requiring advanced degrees (Master’s/MBA/PhD)
🛂Roles that don’t offer sponsorship
🇺🇸Roles requiring U.S. citizenship

README Table Format

When your contribution is approved, it appears in the README table:

Markdown Format

| Company | Role | Location | Application | Age |
| --- | --- | --- | :---: | :---: |
| 🔥 **[Google](https://google.com)** | Software Engineering Internship 🎓 | San Francisco, CA | <a href="..."><img src="..." alt="Apply"></a> | 2d |

Rendered Output

When rendered, the table looks like:
CompanyRoleLocationApplicationAge
🔥 GoogleSoftware Engineering Internship 🎓San Francisco, CAApply button2d

Table Columns

  • Company: Company name with FAANG indicator (🔥) if applicable, linked to company page
  • Role: Job title with degree indicator (🎓) if advanced degree required
  • Location: City, state/province, and country or “Remote”
  • Application: Apply button that links to the job posting
  • Age: How long ago the posting was added (e.g., “2d” for 2 days ago)

Best Practices

Multiple Positions at Same Company

Please make a new submission for each unique position, even if they are for the same company.
If a company has multiple internship positions (e.g., Software Engineering and Data Science), submit separate issues for each one.

Accurate Information

Ensure all information is accurate:
  • Use the exact job title from the posting
  • Include all listed locations
  • Link directly to the application page (not the careers homepage)
  • Select the most appropriate category
  • Correctly indicate degree requirements

Clear Edit Reasons

When editing an internship:
  • Explain why you’re making the change
  • Provide context if the reason isn’t obvious
  • Include sources if you have them (e.g., “Company announced on Twitter that applications closed”)

Questions and Support

If you have questions about the guidelines or need help with a contribution, create a miscellaneous issue.

Build docs developers (and LLMs) love