Senior Entomologist
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Search Firm Representatives", EEO statements, etc. Also remove "Colossal is proud to be an equal employment opportunity workplace..." etc. Also remove "Colossal is proud to be named a Best Place to Work..." etc. Also remove "What Colossal Offers Full-Time Employees:" but we need to keep benefits list. However the benefits list is under that heading; we can keep benefits as a section with heading Benefits and list items.
We need to decide sections: About the role (intro paragraph), Responsibilities (list), Requirements (maybe education/experience?), Qualifications (maybe required skills?), Skills (maybe preferred skills?), Benefits (list). The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content accordingly.
We have:
- About the role: introductory paragraph describing role, contract, etc.
- Responsibilities: the bullet list under "Key Responsibilities:" (many items). We'll put each as
- .
- Requirements: maybe education and experience? Or required skills? The posting has "Required Skills and Abilities:" list. Could be Skills section. But we also have "Education and Experience:" separate. Could treat as Qualifications. Let's decide:
We can have:
- About the role (intro)
- Responsibilities (list)
- Required Skills (maybe under Skills heading)
- Education and Experience (maybe under Qualifications heading)
- Preferred Skills and Certifications (maybe under Skills as well? but we could split: Skills for required, Preferred Skills under Skills? Might be redundant. Better to have Skills for required, and maybe Qualifications for education/experience. Preferred skills could be under Skills as well but we could add another section? The instruction says prefer few substantive sections over many thin ones. Could combine required and preferred skills under Skills heading, but we need to preserve detail. Could have two sublists? But we need to use
- for any list. Could have one list with both required and preferred? Might lose distinction. Better to have Skills heading for required skills, and Qualifications heading for education/experience, and maybe another heading for Preferred Skills? But we only have allowed headings list; we could add "Preferred Skills" as a heading? Not in the list but we could still use
for any section heading; the list is examples, not exclusive. The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are examples but not strict. However to be safe, we can stick to those headings. We can map:
- About the role: intro.
- Responsibilities: responsibilities list.
- Requirements: required skills and abilities? Or maybe education/experience? Let's see: Requirements could be the required skills and abilities. Qualifications could be education and experience. Skills could be preferred skills and certifications. Benefits: benefits list.
Thus:
About the role: paragraph.
Requirements: list of required skills and abilities.
Qualifications: education and experience paragraph (maybe also list? It's a paragraph with bullet-like sentences). Could format as - for each requirement? The text: "Ph.D. in Entomology, Behavioral Ecology, or a closely related field required; emphasis in experimental statistics or ecological biochemistry a plus.15 or more years of progressive research experience in entomology or insect ecology, with a substantial portion in a lead scientist or principal investigator role.Demonstrated track record of leading multi-year, multi-site research programs from design through publication.Experience in academic, federal, or industry research environments; adjunct or teaching experience in entomology or wildlife ecology a plus.Proven ability to mentor and supervise technicians, students, and early-career scientists."
We could break into list items.
Skills: preferred skills and certifications list.
Benefits: list under "What Colossal Offers Full-Time Employees:" (Medical, dental, vision coverage; Excellent paid time off...; Flexible spending accounts (FSA); Company matched 401k retirement plan; Paid parental leave at 100% salary for up to 12 weeks; Education reimbursement; An opportunity to help us return the Earth to a healthier state; The team at Colossal is committed... etc). The latter part about culture maybe not a benefit but we can include as prose? Might be considered boilerplate? It's describing culture, maybe keep as prose under Benefits? But we should keep substantive info. The benefits list includes those items; the culture statements maybe not needed but could be considered part of Benefits? Might be fluff. Safer to include only the concrete benefits: Medical, dental, and vision coverage; Excellent paid time off and company holidays; Flexible spending accounts (FSA); Company matched 401k retirement plan; Paid parental leave at 100% salary for up to 12 weeks; Education reimbursement; An opportunity to help us return the Earth to a healthier state. The rest about team culture maybe not needed but could be considered part of Benefits? It's not a concrete benefit. I'd omit.
Now we need to remove boilerplate: EEO statements, Search Firm Representatives, Best Place to Work lists, etc.
Now produce HTML fragment.
Structure:
About the role
... paragraph ...
Responsibilities
- ...
...
Requirements
- ...
...
Qualifications
- ...
...
Skills
- ...
...
Benefits
- ...
...
Make sure no extra sections.
Now craft the About the role paragraph: combine first paragraph(s) before "Key Responsibilities:":
"We are seeking a contract Senior Entomologist to serve as the scientific lead for Colossal Biosciences’ New World Screwworm (NWS; Cochliomyia hominivorax) Biobanking Program, a multi-phase effort to establish a secure, traceable genetic baseline for NWS populations across North and Central America before, during, and after gene drive deployment. This role will design and execute the standardized fitness-validation battery for fresh and cryopreserved (thawed) screwworm cohorts, lead the field collection strategy across active outbreak regions, and oversee live-colony rearing in partnership with COPEG and USDA-APHIS. The Senior Entomologist will act as the central point of scientific accountability for the program — from protocol design and field deployment through data analysis, interpretation, and reporting to federal and partner stakeholders. This is a 6 month contract position that includes collections trips. You do not need to be based on-site in Dallas but do need to be available for travel."
That's the About the role.
Now Responsibilities list: each bullet after "Key Responsibilities:" until "Required Skills and Abilities:" start.
Let's extract each bullet:
- Serve as scientific lead for the NWS Biobanking Program, owning experimental design, protocol standardization, and interpretation of results across Phase 1 (Fitness Validation), Phase 2 (Biobanking), and Phase 3 (Embryology Production) as activated.
- Design, implement, and quality-control the nine-trait fitness battery — mating latency, copulation duration, fecundity, egg hatch rate, larval viability (1st–3rd instar and 3rd instar–pupa), adult eclosion and sex ratio, flight performance, and host-seeking latency — across CF-Gen1, CT-Gen1, CF-Gen2, and CT-Gen2 cohorts.
- Establish and enforce strict standardization of temperature, humidity, photoperiod, age at testing, diet, handling, and observer methods so that cryopreservation-associated fitness effects can be distinguished from normal biological variation.
- Lead statistical analysis of fitness data, including calculation of Hedge’s g effect sizes and percent-difference comparisons relative to the CF-Gen1 baseline, and determine whether observed effects persist, recover, or change across generations.
- Direct the mobile field collection team across priority outbreak regions in Panama, Costa Rica, Nicaragua, Honduras, Guatemala, Belize, and southern Mexico, targeting 600–900 individuals from confirmed breeding populations.
- Oversee field collection methods including wound sampling from naturally infested animals, Swormlure-4 baited trapping, rotted-liver bait stations for gravid females, and controlled oviposition on heated substrates to meet live-material targets (2,500+ fertile eggs, 1,200+ larvae, 280+ mated pairs).
- Coordinate with local veterinarians, livestock facilities, COPEG operations, and ongoing eradication efforts to secure site access, maintain cross-border coordination, and ensure enhanced biosecurity protocols in active outbreak zones.
- Oversee live-colony rearing, larval diet preparation, pupation, and eclosion procedures in coordination with COPEG animal care protocols and Arthropod Containment Level 3 (ACL-3) requirements.
- Develop sample chain-of-custody, labeling, metadata, and quality-assurance procedures for live and non-live genetic material entering the biobank in accordance with established biobanking standards.
- Prepare detailed protocols, standard operating procedures, equipment specifications, and training materials for laboratory technicians and field personnel.
- Deliver weekly progress updates and monthly scientific reports to program leadership; prepare data summaries, statistical analyses, and technical narratives for federal and partner stakeholders and regulatory review.
- Provide entomological guidance to embryology, cryopreservation, and cell-culture teams on screwworm developmental biology, reproductive behavior, and host-seeking ecology to support colony reconstitution and restoration success metrics.
- Support post-intervention monitoring design, including documentation of genetic bottlenecks, founder effects, and population dynamics during range expansion.
- Contribute to peer-reviewed publications, technical reports, and presentations that communicate program findings to the scientific and regulatory communities.
Now Required Skills and Abilities list:
- Deep expertise in insect behavioral ecology, host selection, and developmental biology, with demonstrated ability to design and run rigorous laboratory behavioral and life-history assays.
- Strong foundation in experimental design and applied statistics, including effect-size analysis, power analysis, and interpretation of variance in behavioral and reproductive traits.
- Hands-on experience with insect field sampling and monitoring methods, including baited and pheromone trapping, sentinel or bait-station collection, and standardized arthropod survey techniques.
- Experience establishing and maintaining live insect colonies under controlled environmental conditions, including diet formulation and rearing standardization.
- Proven ability to lead interdisciplinary research teams and to coordinate across scientific, operations, and external partner organizations.
- Strong written and verbal communication skills; ability to author protocols, technical reports, and peer-reviewed manuscripts and to present findings to executive and government stakeholders.
- Working knowledge of biosafety, containment, and animal-care compliance requirements for arthropod research facilities.
- Willingness and ability to travel to and work in field settings across Central America and southern Mexico, including active livestock outbreak zones.
Now Education and Experience (Qualifications):
- Ph.D. in Entomology, Behavioral Ecology, or a closely related field required; emphasis in experimental statistics or ecological biochemistry a plus.
- 15 or more years of progressive research experience in entomology
for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Search Firm Representatives", EEO statements, etc. Also remove "Colossal is proud to be an equal employment opportunity workplace..." etc. Also remove "Colossal is proud to be named a Best Place to Work..." etc. Also remove "What Colossal Offers Full-Time Employees:" but we need to keep benefits list. However the benefits list is under that heading; we can keep benefits as a section with heading Benefits and list items. We need to decide sections: About the role (intro paragraph), Responsibilities (list), Requirements (maybe education/experience?), Qualifications (maybe required skills?), Skills (maybe preferred skills?), Benefits (list). The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content accordingly. We have: - About the role: introductory paragraph describing role, contract, etc. - Responsibilities: the bullet list under "Key Responsibilities:" (many items). We'll put each as
- for any list. Could have one list with both required and preferred? Might lose distinction. Better to have Skills heading for required skills, and Qualifications heading for education/experience, and maybe another heading for Preferred Skills? But we only have allowed headings list; we could add "Preferred Skills" as a heading? Not in the list but we could still use
for any section heading; the list is examples, not exclusive. The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are examples but not strict. However to be safe, we can stick to those headings. We can map: - About the role: intro. - Responsibilities: responsibilities list. - Requirements: required skills and abilities? Or maybe education/experience? Let's see: Requirements could be the required skills and abilities. Qualifications could be education and experience. Skills could be preferred skills and certifications. Benefits: benefits list. Thus: About the role: paragraph. Requirements: list of required skills and abilities. Qualifications: education and experience paragraph (maybe also list? It's a paragraph with bullet-like sentences). Could format as
- for each requirement? The text: "Ph.D. in Entomology, Behavioral Ecology, or a closely related field required; emphasis in experimental statistics or ecological biochemistry a plus.15 or more years of progressive research experience in entomology or insect ecology, with a substantial portion in a lead scientist or principal investigator role.Demonstrated track record of leading multi-year, multi-site research programs from design through publication.Experience in academic, federal, or industry research environments; adjunct or teaching experience in entomology or wildlife ecology a plus.Proven ability to mentor and supervise technicians, students, and early-career scientists."
We could break into list items.
Skills: preferred skills and certifications list.
Benefits: list under "What Colossal Offers Full-Time Employees:" (Medical, dental, vision coverage; Excellent paid time off...; Flexible spending accounts (FSA); Company matched 401k retirement plan; Paid parental leave at 100% salary for up to 12 weeks; Education reimbursement; An opportunity to help us return the Earth to a healthier state; The team at Colossal is committed... etc). The latter part about culture maybe not a benefit but we can include as prose? Might be considered boilerplate? It's describing culture, maybe keep as prose under Benefits? But we should keep substantive info. The benefits list includes those items; the culture statements maybe not needed but could be considered part of Benefits? Might be fluff. Safer to include only the concrete benefits: Medical, dental, and vision coverage; Excellent paid time off and company holidays; Flexible spending accounts (FSA); Company matched 401k retirement plan; Paid parental leave at 100% salary for up to 12 weeks; Education reimbursement; An opportunity to help us return the Earth to a healthier state. The rest about team culture maybe not needed but could be considered part of Benefits? It's not a concrete benefit. I'd omit.
Now we need to remove boilerplate: EEO statements, Search Firm Representatives, Best Place to Work lists, etc.
Now produce HTML fragment.
Structure:
About the role
... paragraph ...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Skills
- ... ...
Benefits
- ... ...
- for each requirement? The text: "Ph.D. in Entomology, Behavioral Ecology, or a closely related field required; emphasis in experimental statistics or ecological biochemistry a plus.15 or more years of progressive research experience in entomology or insect ecology, with a substantial portion in a lead scientist or principal investigator role.Demonstrated track record of leading multi-year, multi-site research programs from design through publication.Experience in academic, federal, or industry research environments; adjunct or teaching experience in entomology or wildlife ecology a plus.Proven ability to mentor and supervise technicians, students, and early-career scientists."
We could break into list items.
Skills: preferred skills and certifications list.
Benefits: list under "What Colossal Offers Full-Time Employees:" (Medical, dental, vision coverage; Excellent paid time off...; Flexible spending accounts (FSA); Company matched 401k retirement plan; Paid parental leave at 100% salary for up to 12 weeks; Education reimbursement; An opportunity to help us return the Earth to a healthier state; The team at Colossal is committed... etc). The latter part about culture maybe not a benefit but we can include as prose? Might be considered boilerplate? It's describing culture, maybe keep as prose under Benefits? But we should keep substantive info. The benefits list includes those items; the culture statements maybe not needed but could be considered part of Benefits? Might be fluff. Safer to include only the concrete benefits: Medical, dental, and vision coverage; Excellent paid time off and company holidays; Flexible spending accounts (FSA); Company matched 401k retirement plan; Paid parental leave at 100% salary for up to 12 weeks; Education reimbursement; An opportunity to help us return the Earth to a healthier state. The rest about team culture maybe not needed but could be considered part of Benefits? It's not a concrete benefit. I'd omit.
Now we need to remove boilerplate: EEO statements, Search Firm Representatives, Best Place to Work lists, etc.
Now produce HTML fragment.
Structure: