Selected skill statements from exact requisitions
This table includes only skill statements coded from exact requisition records, not general career-page descriptions. A role can appear more than once when it contains different kinds of statements. The classification is our reading of the cited wording and should be checked against the full source.
| Requisition | Skill or evidence | Classification | Scope | Sources |
|---|---|---|---|---|
| Citadel Securities — Quantitative Trader Intern (US), Trading and Research | Coding mathematical models | required | The description asks for expertise translating models into code, with Python, R and C++ as examples. | |
| Citadel Securities — Quantitative Trader Intern (US), Trading and Research | AI/LLM or agentic workflow experience | preferred | Described as highly desirable, not a mandatory condition in the wording reviewed. | |
| Capital One — Business Analyst Intern R244322 | SQL and Python | learning | Presented as skills interns have the opportunity to learn; not coded as mandatory prior experience. | |
| Dominion Energy — Intern — Power Contracts & Origination | Excel and PowerPoint | required | Listed among the role’s software and communication qualifications. | |
| Dominion Energy — Intern — Electric Transmission Services | Microsoft Office | required | Excel, Word, PowerPoint and Outlook proficiency is requested in the role qualifications. | |
| Florida Power & Light / NextEra Energy — Summer Intern — Finance/Accounting | Excel | preferred | Excel experience appears in preferred qualifications, not coded as a mandatory requirement. | |
| Johnson & Johnson — Clinical Operations Intern R-098089 | Microsoft Office and languages | required | Office proficiency, local-language competency and advanced English are listed qualifications. |
This is not a frequency ranking of market demand. The six requisitions were selected for useful contrasts, and absence from the table does not mean a skill is absent from the internship market.
Read the words surrounding the tool name
A posting may require experience with a tool, prefer it, say interns will learn it or describe the team's work using it. Those are different statements. A keyword search that counts them all as mandatory will misread the opportunity.
For each qualification, record the original category, your evidence and any ambiguity. Do not treat a blank structured Required Skills field as proof that no requirements exist when the narrative qualifications contain them. Conversely, do not turn a learning opportunity into a reason to reject yourself before reading the rest of the posting.
Examples can also differ from exclusive lists. A phrase naming several programming languages may illustrate suitable experience rather than require mastery of every language; preserve the exact context before interpreting it.
Demonstrate the task rather than decorating the résumé
Map a skill to something you actually did. For spreadsheet analysis, show a model with defined inputs and a reconciliation. For programming, explain a test, a bug and the change that fixed it. For communication, explain the audience and the decision your document supported.
A course or independent exercise is valid evidence when labelled accurately. Do not describe a tool you watched in a video as professional experience, or list a programming language you cannot use to explain your project. Keep examples small enough to inspect and specific enough that a reviewer can ask follow-up questions.
Where you have adjacent experience, state the connection and the learning gap. That is different from pretending the gap does not exist.
What the coding does not measure
This resource is built from the same small research cohort used by our other comparison pages. Purposive sample of 24 named program or requisition records reviewed September 16, 2026. It mixes explicitly dated 2027 programs with general program descriptions and undated-cohort requisitions. It is not a vacancy census, employer ranking, eligibility determination or estimate of market-wide pay or disclosure. Unknown values remain unknown. Records from one employer or program family are not independent observations.
A row represents the named program or requisition, not an employer-wide policy. Repeated employers, shared program pages and different country scopes remain visible. The sample was selected to investigate useful differences, not randomly sampled to estimate what all internships offer. The downloadable JSON preserves field-level source references and explicit missing values.
The unit in the table is a coded statement within a requisition. Several statements from one role are not independent openings. No skill popularity, hiring probability or causal effect on selection is estimated. General program-level statements are retained in the full dataset but excluded from this exact-role table.
Choose one missing capability to practice
After checking the mandatory conditions, choose a bounded preparation task that addresses the actual work. Define its output, complete it, test it and explain it. Avoid collecting unrelated certificates simply to make the application longer.
Use a question queue for ambiguous requirements and keep other suitable applications moving. A strong project does not waive a stated degree or location condition, while an unmet preference is not automatically a mandatory rejection.
Before submitting, read the exact role once more. Check that the résumé examples, links and dates are accurate and that you have not borrowed a requirement or salary from a different program at the same employer.