Research 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.
We need to parse the posting.
Content:
- About The Company: a paragraph describing company, mission, data curation suite, benefits of curated data, research references, funding, investors, team, location (San Mateo, CA), office schedule (in office 4 days a week), internship timing (Summer 2027, May-August 2027). This is substantive.
- About The Role: description of day-to-day: bullet-like sentences: "Transform messy literature into practical improvements...", "Perform High-Risk, High-Reward Research.", "Conduct science driven by real-world needs.", "Science is more than just experiments...". These are prose sentences; could be list items.
- About You: Ideal candidates should have strong coding skills with experience with one of the following: list of topics: Data research, Data pruning/curation, Curriculum learning, Synthetic data generation, Dataset distillation, Effects of training data on model behavior, Embedding models, Semantic search, Efficient ML. Also: "We would love to have you if you have practical experience and/or publications related to training large vision (especially video), language, and multimodal models." Also: "Or teach us something new that you are passionate about that could improve data curation!"
- Benefits: list of benefits: 100% covered health benefits (medical, vision, and dental). 401(k) plan with a generous 4% company match. Unlimited PTO policy. Paid Parental Leave of 12 weeks, plus 6 months of WFH flexibility. Annual $2,000 wellness stipend. Annual $1,000 learning and development stipend. Daily lunches and snacks are provided in our office! Relocation assistance for employees moving to the Bay Area.
- No Pay or Schedule specifics given (except office schedule: "We are in office 4 days a week." That's schedule info. Should we include a Schedule section? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state schedule: "We are in office 4 days a week." So we can include a Schedule section with that detail. Also location: "This role is based in San Mateo, CA." Could be part of About the Company or separate? Probably keep within About the Company.
- No Pay mentioned, so omit Pay section.
- No duplicated lines.
We need to output only HTML fragment, no /, no markdown fences.
We need headings: Use
for section headings. Which sections? We have About the Company, About the Role, About You (maybe Qualifications/Skills?), Benefits, Schedule. The instruction list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map:
- About the Company: not in list but we can still use heading? The instruction says 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 similar style. Probably we can use About the Company as About the Company
. It's okay.
- About The Role: could be About the Role
or maybe Responsibilities. The posting says "About The Role". We'll use that.
- About You: could be About You
or Qualifications/Skills. We'll use About You.
- Benefits: Benefits
- Schedule: Schedule
We need to use - for any list of duties/requirements/benefits. So for Benefits we should use
- . For About You qualifications list also use
- . For About The Role duties maybe also list.
We need to preserve all substantive information. So we need to include all details.
Let's craft:
About the Company
Models are what they eat. But a large portion of training compute is wasted training on data that are already learned, irrelevant, or even harmful, leading to worse models that cost more to train and deploy. At DatologyAI, we’ve built a state of the art data curation suite to automatically curate and optimize petabytes of data to create the best possible training data for your models. Training on curated data can dramatically reduce training time and cost (7-40x faster training depending on the use case), dramatically increase model performance as if you had trained on >10x more raw data without increasing the cost of training, and allow smaller models with fewer than half the parameters to outperform larger models despite using far less compute at inference time, substantially reducing the cost of deployment. For more details, check out our recent research on synthetic data scaling (BeyondWeb) and pretraining with domain-specific data (The Finetuner’s Fallacy). We raised a total of $57.5M in two rounds, a Seed and Series A. Our investors include Felicis Ventures, Radical Ventures, Amplify Partners, Microsoft, Amazon, and AI visionaries like Geoff Hinton, Yann LeCun, Jeff Dean, and many others who deeply understand the importance and difficulty of identifying and optimizing the best possible training data for models. Our team has pioneered this frontier research area and has the deep expertise on both data research and data engineering necessary to solve this incredibly challenging problem and make data curation easy for anyone who wants to train their own model on their own data. This role is based in San Mateo, CA. We are in office 4 days a week. The internship is for Summer 2027 and will take place sometime between May and August 2027.
But we need to separate schedule maybe. However schedule info is in that paragraph. Could we keep schedule separate? The instruction: include a section ONLY when posting has real specific content. We have schedule info: "We are in office 4 days a week." So we could make a Schedule section with that sentence. Also location and internship timing could be in About the Company or separate. But we already have location and timing in About the Company paragraph. It's okay.
But we might want to avoid duplication: If we put schedule in its own section, we should remove from About the Company paragraph to avoid duplication. However the instruction says preserve ALL substantive information; we can move it to Schedule section and remove from About the Company. But we need to ensure we don't lose any info. Let's extract schedule sentence: "We are in office 4 days a week." Also location: "This role is based in San Mateo, CA." Internship timing: "The internship is for Summer 2027 and will take place sometime between May and August 2027." Those could stay in About the Company or we could make a separate section for "Location and Timing"? Not required. Probably keep them in About the Company.
Thus About the Company paragraph will exclude the schedule sentence. We'll put schedule sentence in its own Schedule
We are in office 4 days a week.
Now About the Role: we need to list duties. The paragraph includes four sentences each starting with a bold-like phrase. We can turn each into - . Let's do:
About the Role
- Transform messy literature into practical improvements. The research literature is vast, ambiguous, and constantly evolving. You will use your skills as a scientist to source, vet, implement, and improve promising ideas from the literature and your own creation.
- Perform High-Risk, High-Reward Research. We want our interns to focus on problems that have massive potential to transform how data is ingested into future ML models. Rather than making incremental changes to current algorithms, we want you to work on novel project ideas that could change how we view data.
- Conduct science driven by real-world needs. At DatologyAI, we understand that conference reviewers and academic benchmarks don’t always incentivize the most impactful research. Concrete customer needs and product improvements will guide your research.
- Science is more than just experiments. We expect our Research Scientist Interns to collaborate closely with engineers, talk to customers, and shape the product vision.
Now About You: we need to list qualifications/skills. The paragraph: "Ideal candidates should have strong coding skills with experience with one of the following: We would like to hire students with practical experience and/or publications related to any of the following research topics:Data researchData pruning/curationCurriculum learningSynthetic data generationDataset distillationEffects of training data on model behaviorEmbedding modelsSemantic searchEfficient MLWe would love to have you if you have practical experience and/or publications related to training large vision (especially video), language, and multimodal models.Or teach us something new that you are passionate about that could improve data curation!"
We need to split into list items. Let's create a list:
- Data research
- Data pruning/curation
- Curriculum learning
- Synthetic data generation
- Dataset distillation
- Effects of training data on model behavior
- Embedding models
- Semantic search
- Efficient ML
- Practical experience and/or publications related to training large vision (especially video), language, and multimodal models.
- Or teach us something new that you are passionate about that could improve data curation!
Also "Ideal candidates should have strong coding skills" is a general requirement; we could include as a separate bullet or as part of intro. We'll include as a bullet: "Strong coding skills."
Thus:
About You
- Strong coding skills.
- Data research
- Data pruning/curation
- Curriculum learning
- Synthetic data generation
- Dataset distillation
- Effects of training data on model behavior
- Embedding models
- Semantic search
- Efficient ML
- Practical experience and/or publications related to training large vision (especially video), language, and multimodal models.
- Or teach us something new that you are passionate about that could improve data curation!
Now Benefits: list.
Benefits
- 100% covered health benefits (medical, vision, and dental).
- 401(k) plan with a generous 4% company match.
- Unlimited PTO policy.
- Paid Parental Leave of 12 weeks, plus 6 months of WFH flexibility.
- Annual $2,000 wellness stipend.
- Annual $1,000 learning and development stipend.
- Daily lunches and snacks are provided in our office!
- Relocation assistance for employees moving to the Bay
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. We need to parse the posting. Content: - About The Company: a paragraph describing company, mission, data curation suite, benefits of curated data, research references, funding, investors, team, location (San Mateo, CA), office schedule (in office 4 days a week), internship timing (Summer 2027, May-August 2027). This is substantive. - About The Role: description of day-to-day: bullet-like sentences: "Transform messy literature into practical improvements...", "Perform High-Risk, High-Reward Research.", "Conduct science driven by real-world needs.", "Science is more than just experiments...". These are prose sentences; could be list items. - About You: Ideal candidates should have strong coding skills with experience with one of the following: list of topics: Data research, Data pruning/curation, Curriculum learning, Synthetic data generation, Dataset distillation, Effects of training data on model behavior, Embedding models, Semantic search, Efficient ML. Also: "We would love to have you if you have practical experience and/or publications related to training large vision (especially video), language, and multimodal models." Also: "Or teach us something new that you are passionate about that could improve data curation!" - Benefits: list of benefits: 100% covered health benefits (medical, vision, and dental). 401(k) plan with a generous 4% company match. Unlimited PTO policy. Paid Parental Leave of 12 weeks, plus 6 months of WFH flexibility. Annual $2,000 wellness stipend. Annual $1,000 learning and development stipend. Daily lunches and snacks are provided in our office! Relocation assistance for employees moving to the Bay Area. - No Pay or Schedule specifics given (except office schedule: "We are in office 4 days a week." That's schedule info. Should we include a Schedule section? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state schedule: "We are in office 4 days a week." So we can include a Schedule section with that detail. Also location: "This role is based in San Mateo, CA." Could be part of About the Company or separate? Probably keep within About the Company. - No Pay mentioned, so omit Pay section. - No duplicated lines. We need to output only HTML fragment, no /, no markdown fences. We need headings: Use
for section headings. Which sections? We have About the Company, About the Role, About You (maybe Qualifications/Skills?), Benefits, Schedule. The instruction list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map:
- About the Company: not in list but we can still use heading? The instruction says 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 similar style. Probably we can use About the Company as About the Company
. It's okay.
- About The Role: could be About the Role
or maybe Responsibilities. The posting says "About The Role". We'll use that.
- About You: could be About You
or Qualifications/Skills. We'll use About You.
- Benefits: Benefits
- Schedule: Schedule
We need to use - for any list of duties/requirements/benefits. So for Benefits we should use
- . For About You qualifications list also use
- . For About The Role duties maybe also list.
We need to preserve all substantive information. So we need to include all details.
Let's craft:
About the Company
Models are what they eat. But a large portion of training compute is wasted training on data that are already learned, irrelevant, or even harmful, leading to worse models that cost more to train and deploy. At DatologyAI, we’ve built a state of the art data curation suite to automatically curate and optimize petabytes of data to create the best possible training data for your models. Training on curated data can dramatically reduce training time and cost (7-40x faster training depending on the use case), dramatically increase model performance as if you had trained on >10x more raw data without increasing the cost of training, and allow smaller models with fewer than half the parameters to outperform larger models despite using far less compute at inference time, substantially reducing the cost of deployment. For more details, check out our recent research on synthetic data scaling (BeyondWeb) and pretraining with domain-specific data (The Finetuner’s Fallacy). We raised a total of $57.5M in two rounds, a Seed and Series A. Our investors include Felicis Ventures, Radical Ventures, Amplify Partners, Microsoft, Amazon, and AI visionaries like Geoff Hinton, Yann LeCun, Jeff Dean, and many others who deeply understand the importance and difficulty of identifying and optimizing the best possible training data for models. Our team has pioneered this frontier research area and has the deep expertise on both data research and data engineering necessary to solve this incredibly challenging problem and make data curation easy for anyone who wants to train their own model on their own data. This role is based in San Mateo, CA. We are in office 4 days a week. The internship is for Summer 2027 and will take place sometime between May and August 2027.
But we need to separate schedule maybe. However schedule info is in that paragraph. Could we keep schedule separate? The instruction: include a section ONLY when posting has real specific content. We have schedule info: "We are in office 4 days a week." So we could make a Schedule section with that sentence. Also location and internship timing could be in About the Company or separate. But we already have location and timing in About the Company paragraph. It's okay.
But we might want to avoid duplication: If we put schedule in its own section, we should remove from About the Company paragraph to avoid duplication. However the instruction says preserve ALL substantive information; we can move it to Schedule section and remove from About the Company. But we need to ensure we don't lose any info. Let's extract schedule sentence: "We are in office 4 days a week." Also location: "This role is based in San Mateo, CA." Internship timing: "The internship is for Summer 2027 and will take place sometime between May and August 2027." Those could stay in About the Company or we could make a separate section for "Location and Timing"? Not required. Probably keep them in About the Company.
Thus About the Company paragraph will exclude the schedule sentence. We'll put schedule sentence in its own Schedule
We are in office 4 days a week.
Now About the Role: we need to list duties. The paragraph includes four sentences each starting with a bold-like phrase. We can turn each into - . Let's do:
About the Role
- Transform messy literature into practical improvements. The research literature is vast, ambiguous, and constantly evolving. You will use your skills as a scientist to source, vet, implement, and improve promising ideas from the literature and your own creation.
- Perform High-Risk, High-Reward Research. We want our interns to focus on problems that have massive potential to transform how data is ingested into future ML models. Rather than making incremental changes to current algorithms, we want you to work on novel project ideas that could change how we view data.
- Conduct science driven by real-world needs. At DatologyAI, we understand that conference reviewers and academic benchmarks don’t always incentivize the most impactful research. Concrete customer needs and product improvements will guide your research.
- Science is more than just experiments. We expect our Research Scientist Interns to collaborate closely with engineers, talk to customers, and shape the product vision.
Now About You: we need to list qualifications/skills. The paragraph: "Ideal candidates should have strong coding skills with experience with one of the following: We would like to hire students with practical experience and/or publications related to any of the following research topics:Data researchData pruning/curationCurriculum learningSynthetic data generationDataset distillationEffects of training data on model behaviorEmbedding modelsSemantic searchEfficient MLWe would love to have you if you have practical experience and/or publications related to training large vision (especially video), language, and multimodal models.Or teach us something new that you are passionate about that could improve data curation!"
We need to split into list items. Let's create a list:
- Data research
- Data pruning/curation
- Curriculum learning
- Synthetic data generation
- Dataset distillation
- Effects of training data on model behavior
- Embedding models
- Semantic search
- Efficient ML
- Practical experience and/or publications related to training large vision (especially video), language, and multimodal models.
- Or teach us something new that you are passionate about that could improve data curation!
Also "Ideal candidates should have strong coding skills" is a general requirement; we could include as a separate bullet or as part of intro. We'll include as a bullet: "Strong coding skills."
Thus:
About You
- Strong coding skills.
- Data research
- Data pruning/curation
- Curriculum learning
- Synthetic data generation
- Dataset distillation
- Effects of training data on model behavior
- Embedding models
- Semantic search
- Efficient ML
- Practical experience and/or publications related to training large vision (especially video), language, and multimodal models.
- Or teach us something new that you are passionate about that could improve data curation!
Now Benefits: list.
Benefits
- 100% covered health benefits (medical, vision, and dental).
- 401(k) plan with a generous 4% company match.
- Unlimited PTO policy.
- Paid Parental Leave of 12 weeks, plus 6 months of WFH flexibility.
- Annual $2,000 wellness stipend.
- Annual $1,000 learning and development stipend.
- Daily lunches and snacks are provided in our office!
- Relocation assistance for employees moving to the Bay
About the Company
. It's okay. - About The Role: could beAbout the Role
or maybe Responsibilities. The posting says "About The Role". We'll use that. - About You: could beAbout You
or Qualifications/Skills. We'll use About You. - Benefits:Benefits
- Schedule:Schedule
We need to use- for any list of duties/requirements/benefits. So for Benefits we should use
- . For About You qualifications list also use
- . For About The Role duties maybe also list.
We need to preserve all substantive information. So we need to include all details.
Let's craft:
About the Company
Models are what they eat. But a large portion of training compute is wasted training on data that are already learned, irrelevant, or even harmful, leading to worse models that cost more to train and deploy. At DatologyAI, we’ve built a state of the art data curation suite to automatically curate and optimize petabytes of data to create the best possible training data for your models. Training on curated data can dramatically reduce training time and cost (7-40x faster training depending on the use case), dramatically increase model performance as if you had trained on >10x more raw data without increasing the cost of training, and allow smaller models with fewer than half the parameters to outperform larger models despite using far less compute at inference time, substantially reducing the cost of deployment. For more details, check out our recent research on synthetic data scaling (BeyondWeb) and pretraining with domain-specific data (The Finetuner’s Fallacy). We raised a total of $57.5M in two rounds, a Seed and Series A. Our investors include Felicis Ventures, Radical Ventures, Amplify Partners, Microsoft, Amazon, and AI visionaries like Geoff Hinton, Yann LeCun, Jeff Dean, and many others who deeply understand the importance and difficulty of identifying and optimizing the best possible training data for models. Our team has pioneered this frontier research area and has the deep expertise on both data research and data engineering necessary to solve this incredibly challenging problem and make data curation easy for anyone who wants to train their own model on their own data. This role is based in San Mateo, CA. We are in office 4 days a week. The internship is for Summer 2027 and will take place sometime between May and August 2027.
But we need to separate schedule maybe. However schedule info is in that paragraph. Could we keep schedule separate? The instruction: include a section ONLY when posting has real specific content. We have schedule info: "We are in office 4 days a week." So we could make a Schedule section with that sentence. Also location and internship timing could be in About the Company or separate. But we already have location and timing in About the Company paragraph. It's okay. But we might want to avoid duplication: If we put schedule in its own section, we should remove from About the Company paragraph to avoid duplication. However the instruction says preserve ALL substantive information; we can move it to Schedule section and remove from About the Company. But we need to ensure we don't lose any info. Let's extract schedule sentence: "We are in office 4 days a week." Also location: "This role is based in San Mateo, CA." Internship timing: "The internship is for Summer 2027 and will take place sometime between May and August 2027." Those could stay in About the Company or we could make a separate section for "Location and Timing"? Not required. Probably keep them in About the Company. Thus About the Company paragraph will exclude the schedule sentence. We'll put schedule sentence in its ownSchedule
We are in office 4 days a week.
Now About the Role: we need to list duties. The paragraph includes four sentences each starting with a bold-like phrase. We can turn each into - . Let's do:
About the Role
- Transform messy literature into practical improvements. The research literature is vast, ambiguous, and constantly evolving. You will use your skills as a scientist to source, vet, implement, and improve promising ideas from the literature and your own creation.
- Perform High-Risk, High-Reward Research. We want our interns to focus on problems that have massive potential to transform how data is ingested into future ML models. Rather than making incremental changes to current algorithms, we want you to work on novel project ideas that could change how we view data.
- Conduct science driven by real-world needs. At DatologyAI, we understand that conference reviewers and academic benchmarks don’t always incentivize the most impactful research. Concrete customer needs and product improvements will guide your research.
- Science is more than just experiments. We expect our Research Scientist Interns to collaborate closely with engineers, talk to customers, and shape the product vision.
About You
- Strong coding skills.
- Data research
- Data pruning/curation
- Curriculum learning
- Synthetic data generation
- Dataset distillation
- Effects of training data on model behavior
- Embedding models
- Semantic search
- Efficient ML
- Practical experience and/or publications related to training large vision (especially video), language, and multimodal models.
- Or teach us something new that you are passionate about that could improve data curation!
Benefits
- 100% covered health benefits (medical, vision, and dental).
- 401(k) plan with a generous 4% company match.
- Unlimited PTO policy.
- Paid Parental Leave of 12 weeks, plus 6 months of WFH flexibility.
- Annual $2,000 wellness stipend.
- Annual $1,000 learning and development stipend.
- Daily lunches and snacks are provided in our office!
- Relocation assistance for employees moving to the Bay
- . For About The Role duties maybe also list.
We need to preserve all substantive information. So we need to include all details.
Let's craft:
- . For About You qualifications list also use