Associate Scientist - RNA
BioSpace · Watertown, MA · Yesterday
Healthcare$71k–$187k/yrFull-time
We need to produce HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions). Also must not include sections with filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes Pay: "Actual compensation will depend on a candidate’s education, experience, skills, and geographic location. The anticipated wage for this position is $71,250 - $187,000 Full-time equivalent employees also will be eligible for a company bonus (depending, in part, on company and individual performance)." So we have Pay info. Benefits: "In addition, Lilly offers a comprehensive benefit program to eligible employees, including eligibility to participate in a company-sponsored 401(k); pension; vacation benefits; eligibility for medical, dental, vision and prescription drug benefits; flexible benefits (e.g., healthcare and/or dependent day care flexible spending accounts); life insurance and death benefits; certain time off and leave of absence benefits; and well-being benefits (e.g., employee assistance program, fitness benefits, and employee clubs and activities)." So Benefits section exists. Schedule: Not explicitly mentioned; maybe implied full-time but not stated. The posting says "Full-time equivalent employees also will be eligible for a company bonus". It doesn't give schedule details like hours. So we should not create Schedule section unless stated. So we will include About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Possibly also "About the company" but not required headings. The headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We'll include those with content.
We need to extract content:
About the role: The description of role: "Orna Therapeutics, Inc., a wholly owned subsidiary of Eli Lilly and Company, is an innovative biotechnology startup based in Watertown, MA, committed to developing groundbreaking therapies for diseases that current approaches cannot address. With our pioneering circular RNA technology, developed at MIT, we are at the forefront of advancing the next generation of RNA therapeutics. Our innovative expression and delivery platform positions us to tackle complex diseases, including B cell-driven autoimmune disorders, B cell malignancies, sickle cell disease, and beyond. We are seeking an exceptional analytical development Scientist to join our team - RNA Production, Research, and Optimization (PRO). This position will report to an Advisor and focus on onboarding, optimizing, troubleshooting, and performing a range of analytical assays for the characterization of in vitro-transcribed RNA. An ideal candidate would have extensive hands-on molecular biology experience, particularly with common analytical techniques and cell-based assays. The candidate should also be familiar with statistics and data handling/reporting relevant to analytics. This position will require one who learns and adapts quickly, follows established protocols, and is comfortable in a dynamic and collaborative environment. The candidate will be expected to document all experiments in detail and share results both orally and in writing."
That's about the role.
Responsibilities: Likely the duties: "focus on onboarding, optimizing, troubleshooting, and performing a range of analytical assays for the characterization of in vitro-transcribed RNA", "document all experiments in detail and share results both orally and in writing". Also maybe "learns and adapts quickly, follows established protocols, comfortable in dynamic collaborative environment". But those are more qualifications. We'll list responsibilities as bullet points.
Requirements: Might be basic qualifications: "Expertise in analytical chemistry, biochemistry, biology, molecular biology or a related field and either: M.S. with 1+ years relevant industry experience OR B.S. with 6+ years relevant industry experience Qualified applicants must be authorized to work in the United States on a full-time basis. Lilly will not provide support for or sponsor work authorization or visas for this role, including but not limited to F-1 CPT, F-1 OPT, F-1 STEM OPT, J-1, H-1B, TN, O-1, E-3, H-1B1, or L-1."
Qualifications: Could be the "Additional Skills/Preferences" list: hands-on experience with ELISA, HPLC, CE, protein experience, strong technical background in biochemistry, hands-on experience with nucleic acids, firsthand experience with cell culture and cell-based reporter assays, knowledge of ELN data tracking, coding experience a plus, proven track record of successful method development including fit-for-purpose assay validations.
Skills: Could be overlapping with Additional Skills/Preferences. But we need to avoid duplication. Perhaps we treat "Skills" as the technical skills list, and "Qualifications" as education/experience. However the instructions: Use headings as given; we can decide what goes where. We need to preserve all substantive info; we can split.
Let's map:
- About the role: company description and role overview.
- Responsibilities: onboarding, optimizing, troubleshooting, performing analytical assays for IVT RNA characterization; documenting experiments; sharing results orally/written.
- Requirements: basic qualifications (education/experience, work authorization).
- Qualifications: maybe "Additional Skills/Preferences" (preferred skills). But we also have Skills heading; maybe we put the list of hands-on experience etc under Skills, and Qualifications could be education/experience? But we already used Requirements for that. Actually Requirements often includes education/experience; Qualifications could be preferred qualifications. Let's assign:
Requirements: Basic Qualifications (education/experience, work auth).
Qualifications: Additional Skills/Preferences (preferred).
Skills: maybe we could combine with Qualifications? But we need to avoid empty sections. Could put technical skills under Skills, and preferred experience under Qualifications. However the Additional Skills/Preferences list includes both technical skills and experience. Might be better to put that under Skills, and Qualifications could be something else like "Proven track record of successful method development" etc. But that's also part of Additional Skills/Preferences.
Given the headings list, we can decide to put:
- About the role: company + role overview.
- Responsibilities: duties.
- Requirements: basic qualifications (education/experience, work auth).
- Qualifications: Additional Skills/Preferences (preferred skills/experience).
- Skills: maybe we could list specific technical competencies like ELISA, HPLC, CE, SDS-PAGE, nucleic acids, cell culture, ELN, coding, method development. But that duplicates Qualifications. To avoid duplication, we could omit Skills section if content would be duplicate. But we need to include sections only when posting has real specific content for it. If we already put that content under Qualifications, we could still have Skills with maybe a subset? But risk of duplication. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid duplication, but better to avoid redundancy. However we must include all info; if we put it under Qualifications, it's still preserved. So we could omit Skills section if we feel it's redundant. But we need to decide if there is distinct content for Skills beyond what's in Qualifications. The posting includes "Additional Skills/Preferences" which is a list of skills/experience. That could be considered Skills. The "Basic Qualifications" is education/experience. So we could map:
- Requirements: Basic Qualifications (education/experience, work auth).
- Skills: Additional Skills/Preferences (hands-on experience with ELISA, HPLC, CE, protein experience, biochemistry background, nucleic acids, cell culture, ELN, coding, method development).
- Qualifications: maybe we could put "Proven track record of successful method development, including fit-for-purpose assay validations." but that's also in Additional Skills/Preferences. Hmm.
Alternatively, we could treat Qualifications as the education/experience (basic) and Skills as the technical skills list. Requirements could be something else like "Must be authorized to work in the US" etc. But the heading list includes Requirements, Qualifications, Skills. Usually Requirements are mandatory, Qualifications are preferred, Skills are abilities. Let's assign:
- Requirements: Basic Qualifications (education/experience, work auth).
- Qualifications: Additional Skills/Preferences (preferred skills/experience).
- Skills: maybe we could list "hands-on experience with common analytical techniques... protein experience... strong technical background in biochemistry... firsthand experience with cell culture... knowledge of ELN... coding experience... proven track record..." but that's same as Qualifications. To avoid duplication, we could split the list: some items under Qualifications (preferred experience) and some under Skills (technical abilities). But the instruction says do not create sections with filler; we can still have both if they have distinct content. Let's see if we can separate:
Additional Skills/Preferences list:
- Hands-on experience with common analytical techniques in the field such as ELISA, HPLC, and CE, including troubleshooting, operating, and development of analytical methods for biomolecules.
- Protein experience including techniques such as CE, SDS-PAGE, etc. is preferred.
- Strong technical background in biochemistry, with hands-on experience working with nucleic acids and other biomolecules.
- Firsthand experience with cell culture and cell-based reporter assays, including fluorescence, luminescence, and flow cytometry would be a major plus.
- Knowledge of ELN data tracking and analysis.
- Coding experience is a plus.
- Proven track record of successful method development, including fit-for-purpose assay validations.
These are all skills/experience. Could be considered Skills. Qualifications could be something else like "Extensive hands-on molecular biology experience, particularly with common analytical techniques and cell-based assays." but that's also in role overview. Hmm.
Maybe better to follow typical job posting structure: About the role (overview), Responsibilities (duties), Requirements (mandatory), Qualifications (preferred), Skills (maybe technical skills), Benefits, Pay. We'll allocate:
- About the role: company description and role overview (as earlier).
- Responsibilities: bullet list of duties: onboarding, optimizing, troubleshooting, performing analytical assays for IVT RNA characterization; documenting experiments; sharing results orally/written.
- Requirements: Basic Qualifications (education/experience, work auth).
- Qualifications: Additional Skills/Preferences (preferred skills/experience) - but we could call this Qualifications.
- Skills: maybe we could list specific technical competencies like ELISA, HPLC, CE, SDS-PAGE, nucleic acids, cell culture, ELN, coding, method development. But that's essentially same as Qualifications. To avoid duplication, we could put under Skills a concise list of the techniques: ELISA, HPLC, CE, SDS-PAGE, nucleic acids, cell culture (fluorescence/luminescence/flow cytometry), ELN, coding, method development. While Qualifications could contain the descriptive statements about experience level, etc. But the posting doesn't have separate descriptive statements for qualifications beyond the basic ones. The "Additional Skills/Preferences" is essentially the skills list. So maybe we treat Qualifications as the basic qualifications (education/experience) and Skills as the additional skills list. Then Requirements could be something else like "Must be authorized to work in the US" but that's also part of basic qualifications. Hmm.
Let's examine the headings list again: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to include sections only when posting has real specific content for it. So we need to decide content for each.
We have:
- About the role: yes.
- Responsibilities: yes (duties).
- Requirements: we have basic qualifications (education/experience, work auth). That's definitely requirements.
- Qualifications: we have "Additional Skills/Preferences" which are preferred qualifications. So yes.
- Skills: we could maybe list the specific technical skills (like ELISA, HPLC, CE, SDS-PAGE, nucleic acids, cell culture, ELN, coding, method development). But those are already in Additional Skills/Preferences. However we could still have a Skills section that enumerates them as bullet points, while Qualifications could contain the descriptive statements about experience level (e.g., "Expertise in analytical chemistry, biochemistry, biology, molecular