Data Journalism Summer Intern
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to parse the posting.
Content:
- About Us: description of FT.
- Our Internships: description of internship program, expectations, pay $22 per hour for 40 hours per week, runs June 7, 2027 - Aug 13, 2027, must be authorized to work in US, etc.
- Role Overview: description of team.
- Key Responsibilities: bullet list.
- Required Skills/experience: bullet list.
- Please Submit Your Application By October 26th By 5pm Eastern Time And Be Sure To Include The Following Documents In Your Application: Resume, cover letter, two relevant clips. Also note about AI usage, etc. Those are application instructions; we need to remove application instructions per instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should drop the application instructions (deadline, documents, AI usage, etc). Also remove "Our commitment to a fair and inclusive workplace", "Accessibility" sections? Those are EEO/equal-opportunity boilerplate; should be removed. So we keep only substantive info: About Us, Internships description (including pay, schedule, location expectations), Role Overview, Key Responsibilities, Required Skills/experience.
We need to decide sections: maybe "About the role" (could combine About Us and Role Overview?), but instructions: use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose appropriate headings based on content.
We have:
- About Us: description of FT. Could be under "About the role"? Actually "About the role" is more about the role, but we have "Role Overview". Could use "About the role" heading for Role Overview. And maybe "About the company" not needed? But we could include "About Us" as a heading? The instruction list includes "About the role" as example, not "About Us". But we can still use
for any section heading; they gave examples but not exclusive. Probably we should use headings that match content: "About the FT" maybe not needed. However we need to preserve all substantive information. We could include a
about FT under a heading like "About the FT". But they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should follow that pattern. Probably better to use "About the role" for Role Overview, and maybe include FT description as a paragraph under that or separate "About the company". But they said "Prefer a few substantive sections over many thin ones." So we could combine FT description and role overview into one section "About the role". Or we could have "About the FT" as a paragraph without heading? But they want headings for sections. Let's think: The posting includes "About Us" and "Role Overview". Could combine them under "About the role". That would be substantive.
Then we have "Key Responsibilities" -> heading Responsibilities.
Then "Required Skills/experience" -> heading Skills (or Requirements). They gave Requirements, Qualifications, Skills. We could use "Skills" heading for the list.
We also have Pay and Schedule: The internship pays $22 per hour for 40 hours per week and runs from June 7, 2027 - Aug 13, 2027. Also expectation: "We expect our interns to be in the office a minimum of three days a week." That's schedule info. So we should include Pay and Schedule sections.
Benefits: Not mentioned besides pay; maybe no benefits specifics. So we should not create Benefits section unless stated.
Thus sections: About the role (combining FT description and role overview), Responsibilities, Skills, Pay, Schedule.
We need to output HTML fragment with headings and appropriate
or
- .
Let's extract substantive content:
About Us paragraph: "The Financial Times is one of the world’s leading business news organisations, recognised internationally for its authority, integrity, and accuracy. At the FT, curiosity thrives and ambitious thinking is rewarded. Here, you’re given the chance to reach millions, create work that matters and deliver impartial journalism in a polarised world. In our warm, collaborative culture, you’ll connect with a diverse community of experts who support your growth, career aspirations and wellbeing. The FT has a record paying readership of 1.6 million, more than 1.4 million of which are digital subscriptions. It is part of Nikkei Inc., which provides a broad range of information, news, and services for the global business community. We have offices in more than 35 countries, including London, New York, Hong Kong, Beijing, Manila, Sofia, San Francisco, and Tokyo."
Role Overview paragraph: "You will work closely with all members of the FT’s US data journalism team. We are a small, interdisciplinary group working across the paper — on data visualisation, data analysis, news writing, enterprise stories, narrative features, interactive features and visual stories. All this work is strung together by our keen interest in the quantitative and the empirical. Our team fulfils a dual role: enhancing existing reporting with sharp analysis and visualisation, and pitching and producing our own original work. We are looking for candidates with a proven interest in data journalism and some experience with data and data graphics."
Combine them maybe as two paragraphs under About the role.
Key Responsibilities list:
- Source, collect and clean data for news stories and other pieces
- Create data graphics and perform analyses, often on deadline
- Collaborate with US data team members, and our data colleagues in London, on larger projects
- Work closely with beat reporters to conceive and create effective graphics
- Pitch and produce original pieces for editors in New York and London
Required Skills/experience list:
- Some experience creating clear and engaging graphics (ie. Flourish, Datawrapper, ggplot2)
- Some experience analysing datasets in a journalism context
- Strong writing and communication skills; experience reporting and writing news is an advantage
- Familiarity with sources of US data, especially financial, economic and political data
- Programming fluency, in a language of your choice, is an advantage
- Specific knowledge of business, economics and financial markets is an advantage
Pay: "$22 per hour for 40 hours per week"
Schedule: "runs from June 7, 2027 - Aug 13, 2027" and "We expect our interns to be in the office a minimum of three days a week."
We could put both in Schedule section, or separate Pay and Schedule sections as per instruction. They said "never create Pay/Schedule/Benefits sections unless the posting actually states them." So we can have Pay and Schedule sections.
Thus:
About the role
... FT description ...
... Role Overview ...
Responsibilities
- ...
...
Skills
- ...
...
Pay
$22 per hour for 40 hours per week
Schedule
Runs from June 7, 2027 to August 13, 2027. Interns are expected to be in the office a minimum of three days per week.
We need to preserve all substantive information; we should not lose any detail. Ensure we keep the exact phrasing? Not required to quote exactly but preserve info. We can rephrase slightly but must not lose detail. Let's keep close.
Check for any other substantive info: "Before applying, please ensure you will be available on these dates." That's application instruction; remove. "Applicants must be authorized to work in the US." That's a requirement; should we keep? It's a requirement for eligibility. It's substantive. Should we include under Skills or Requirements? Could be under Skills or maybe a separate Requirements section. Since we have Skills section, we could add that as a bullet under Skills. But the instruction says we can have Requirements section. Might be better to have a Requirements section for eligibility (work authorization). However they said "Prefer a few substantive sections over many thin ones." So we could incorporate that into Skills section as a bullet. Or we could have a Requirements section. Let's see: The posting also mentions "This program offers the opportunity to connect and collaborate across the FT — in the US and globally. You’ll develop ideas that help drive our growth, present your work to US leadership, and gain valuable insights from across the business. Plus, you’ll be paired with a dedicated Buddy to provide mentorship and support throughout your experience." That's also substantive about internship program; we could include under About the role or maybe a separate Benefits? But it's not benefits; it's program details. Could be included in About the role paragraph.
We need to preserve ALL substantive information. So we must include that info somewhere.
Let's list all substantive paragraphs from the posting:
- About Us (FT description)
- Our Internships: description of program, expectations (minimum three days a week), opportunity to connect across FT, develop ideas, present work to US leadership, gain insights, paired with Buddy, pay $22/hr for 40 hrs/week, runs June 7 2027 - Aug 13 2027, must be authorized to work in US.
- Role Overview: description of team, work, looking for candidates with interest in data journalism and some experience.
- Key Responsibilities: bullet list.
- Required Skills/experience: bullet list.
- Application instructions (deadline, documents, AI usage) - remove.
- Commitment to fair workplace - remove.
- Accessibility - remove.
Thus we need to keep: FT description, Internship program details (including expectations, opportunity, Buddy, pay, schedule, work auth), Role Overview, Responsibilities, Skills.
We can structure:
About the role: combine FT description + Role Overview + Internship program overview (maybe except pay/schedule). But we need to keep pay and schedule separate sections.
Thus About the role paragraph(s) will include FT description, Role Overview, Internship program details (except pay/schedule). Let's extract Internship program details:
"We are looking for passionate and motivated students who are interested in pursuing a career in media to join our team! We expect our interns to be in the office a minimum of three days a week. This program offers the opportunity to connect and collaborate across the FT — in the US and globally. You’ll develop ideas that help drive our growth, present your work to US leadership, and gain valuable insights from across the business. Plus, you’ll be paired with a dedicated Buddy to provide mentorship and support throughout your experience."
Also "Before applying, please ensure you will
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting. Content: - About Us: description of FT. - Our Internships: description of internship program, expectations, pay $22 per hour for 40 hours per week, runs June 7, 2027 - Aug 13, 2027, must be authorized to work in US, etc. - Role Overview: description of team. - Key Responsibilities: bullet list. - Required Skills/experience: bullet list. - Please Submit Your Application By October 26th By 5pm Eastern Time And Be Sure To Include The Following Documents In Your Application: Resume, cover letter, two relevant clips. Also note about AI usage, etc. Those are application instructions; we need to remove application instructions per instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should drop the application instructions (deadline, documents, AI usage, etc). Also remove "Our commitment to a fair and inclusive workplace", "Accessibility" sections? Those are EEO/equal-opportunity boilerplate; should be removed. So we keep only substantive info: About Us, Internships description (including pay, schedule, location expectations), Role Overview, Key Responsibilities, Required Skills/experience. We need to decide sections: maybe "About the role" (could combine About Us and Role Overview?), but instructions: use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose appropriate headings based on content. We have: - About Us: description of FT. Could be under "About the role"? Actually "About the role" is more about the role, but we have "Role Overview". Could use "About the role" heading for Role Overview. And maybe "About the company" not needed? But we could include "About Us" as a heading? The instruction list includes "About the role" as example, not "About Us". But we can still use
for any section heading; they gave examples but not exclusive. Probably we should use headings that match content: "About the FT" maybe not needed. However we need to preserve all substantive information. We could include a
about FT under a heading like "About the FT". But they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should follow that pattern. Probably better to use "About the role" for Role Overview, and maybe include FT description as a paragraph under that or separate "About the company". But they said "Prefer a few substantive sections over many thin ones." So we could combine FT description and role overview into one section "About the role". Or we could have "About the FT" as a paragraph without heading? But they want headings for sections. Let's think: The posting includes "About Us" and "Role Overview". Could combine them under "About the role". That would be substantive.
Then we have "Key Responsibilities" -> heading Responsibilities.
Then "Required Skills/experience" -> heading Skills (or Requirements). They gave Requirements, Qualifications, Skills. We could use "Skills" heading for the list.
We also have Pay and Schedule: The internship pays $22 per hour for 40 hours per week and runs from June 7, 2027 - Aug 13, 2027. Also expectation: "We expect our interns to be in the office a minimum of three days a week." That's schedule info. So we should include Pay and Schedule sections.
Benefits: Not mentioned besides pay; maybe no benefits specifics. So we should not create Benefits section unless stated.
Thus sections: About the role (combining FT description and role overview), Responsibilities, Skills, Pay, Schedule.
We need to output HTML fragment with headings and appropriate
or
- .
Let's extract substantive content:
About Us paragraph: "The Financial Times is one of the world’s leading business news organisations, recognised internationally for its authority, integrity, and accuracy. At the FT, curiosity thrives and ambitious thinking is rewarded. Here, you’re given the chance to reach millions, create work that matters and deliver impartial journalism in a polarised world. In our warm, collaborative culture, you’ll connect with a diverse community of experts who support your growth, career aspirations and wellbeing. The FT has a record paying readership of 1.6 million, more than 1.4 million of which are digital subscriptions. It is part of Nikkei Inc., which provides a broad range of information, news, and services for the global business community. We have offices in more than 35 countries, including London, New York, Hong Kong, Beijing, Manila, Sofia, San Francisco, and Tokyo."
Role Overview paragraph: "You will work closely with all members of the FT’s US data journalism team. We are a small, interdisciplinary group working across the paper — on data visualisation, data analysis, news writing, enterprise stories, narrative features, interactive features and visual stories. All this work is strung together by our keen interest in the quantitative and the empirical. Our team fulfils a dual role: enhancing existing reporting with sharp analysis and visualisation, and pitching and producing our own original work. We are looking for candidates with a proven interest in data journalism and some experience with data and data graphics."
Combine them maybe as two paragraphs under About the role.
Key Responsibilities list:
- Source, collect and clean data for news stories and other pieces
- Create data graphics and perform analyses, often on deadline
- Collaborate with US data team members, and our data colleagues in London, on larger projects
- Work closely with beat reporters to conceive and create effective graphics
- Pitch and produce original pieces for editors in New York and London
Required Skills/experience list:
- Some experience creating clear and engaging graphics (ie. Flourish, Datawrapper, ggplot2)
- Some experience analysing datasets in a journalism context
- Strong writing and communication skills; experience reporting and writing news is an advantage
- Familiarity with sources of US data, especially financial, economic and political data
- Programming fluency, in a language of your choice, is an advantage
- Specific knowledge of business, economics and financial markets is an advantage
Pay: "$22 per hour for 40 hours per week"
Schedule: "runs from June 7, 2027 - Aug 13, 2027" and "We expect our interns to be in the office a minimum of three days a week."
We could put both in Schedule section, or separate Pay and Schedule sections as per instruction. They said "never create Pay/Schedule/Benefits sections unless the posting actually states them." So we can have Pay and Schedule sections.
Thus:
About the role
... FT description ...
... Role Overview ...
Responsibilities
- ... ...
Skills
- ... ...
Pay
$22 per hour for 40 hours per week
Schedule
Runs from June 7, 2027 to August 13, 2027. Interns are expected to be in the office a minimum of three days per week.
We need to preserve all substantive information; we should not lose any detail. Ensure we keep the exact phrasing? Not required to quote exactly but preserve info. We can rephrase slightly but must not lose detail. Let's keep close. Check for any other substantive info: "Before applying, please ensure you will be available on these dates." That's application instruction; remove. "Applicants must be authorized to work in the US." That's a requirement; should we keep? It's a requirement for eligibility. It's substantive. Should we include under Skills or Requirements? Could be under Skills or maybe a separate Requirements section. Since we have Skills section, we could add that as a bullet under Skills. But the instruction says we can have Requirements section. Might be better to have a Requirements section for eligibility (work authorization). However they said "Prefer a few substantive sections over many thin ones." So we could incorporate that into Skills section as a bullet. Or we could have a Requirements section. Let's see: The posting also mentions "This program offers the opportunity to connect and collaborate across the FT — in the US and globally. You’ll develop ideas that help drive our growth, present your work to US leadership, and gain valuable insights from across the business. Plus, you’ll be paired with a dedicated Buddy to provide mentorship and support throughout your experience." That's also substantive about internship program; we could include under About the role or maybe a separate Benefits? But it's not benefits; it's program details. Could be included in About the role paragraph. We need to preserve ALL substantive information. So we must include that info somewhere. Let's list all substantive paragraphs from the posting: - About Us (FT description) - Our Internships: description of program, expectations (minimum three days a week), opportunity to connect across FT, develop ideas, present work to US leadership, gain insights, paired with Buddy, pay $22/hr for 40 hrs/week, runs June 7 2027 - Aug 13 2027, must be authorized to work in US. - Role Overview: description of team, work, looking for candidates with interest in data journalism and some experience. - Key Responsibilities: bullet list. - Required Skills/experience: bullet list. - Application instructions (deadline, documents, AI usage) - remove. - Commitment to fair workplace - remove. - Accessibility - remove. Thus we need to keep: FT description, Internship program details (including expectations, opportunity, Buddy, pay, schedule, work auth), Role Overview, Responsibilities, Skills. We can structure: About the role: combine FT description + Role Overview + Internship program overview (maybe except pay/schedule). But we need to keep pay and schedule separate sections. Thus About the role paragraph(s) will include FT description, Role Overview, Internship program details (except pay/schedule). Let's extract Internship program details: "We are looking for passionate and motivated students who are interested in pursuing a career in media to join our team! We expect our interns to be in the office a minimum of three days a week. This program offers the opportunity to connect and collaborate across the FT — in the US and globally. You’ll develop ideas that help drive our growth, present your work to US leadership, and gain valuable insights from across the business. Plus, you’ll be paired with a dedicated Buddy to provide mentorship and support throughout your experience." Also "Before applying, please ensure you will