Scientist I - Neuromodulation Anatomy: Multimodal Data Integration
Allen Institute · Seattle, WA · 1 mo ago
Engineering$86k–$107k/yrFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no invention, no summarizing away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove EEO statements etc. Must keep essential functions, responsibilities, requirements, qualifications, benefits, pay, schedule if present.
Let's parse the posting.
Content:
- Intro paragraph about Allen Institute mission etc. That's "About the role"? Actually it's about the institute and the Neural Dynamics accelerator. Could be considered "About the role" or maybe "About the Institute". The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections are present.
We have:
- Description of goal: "The goal of the Neural Dynamics accelerator is to understand how the brain generates flexible behavior..." That's about the role/project.
- Then: "We are seeking an exceptional scientist to join the Neuromodulation, specifically to create a comprehensively map of the structural organization of neuromodulatory systems in the mouse brain."
- Then details about neuromodulators, project brings together transcriptomic, morphological, connectivity datasets.
- Then: "The scientist will work closely with experimentalists and develop and apply advanced statistical, computational, ML and AI methods to analyze multimodal data including single cell transcriptomics, single neuron reconstructions, input and output connectivity, and in vitro and in vivo physiology."
- Then: "A central biological question is how neuronal properties measured across these modalities align to define functionally relevant cell types."
- Then: "This role offers substantial scope to think deeply about this question and develop conceptual and quantitative frameworks to address it."
- Then: "The scientist will lead the project’s multimodal integration and analysis efforts in close collaboration with experimental and computational teams across the Allen Institute."
- Then: "They will be expected to produce foundational knowledge and openly shared datasets on the structural organization of neuromodulation."
- Then: "For an example of this approach to integrating multimodal neuronal data, see Su et al. Nature 2026."
- Then: "At the Allen Institute, we believe that science is for everyone – and should be open to everyone. We are dedicated to combating biases and reducing barriers to STEM careers more broadly. We also believe that science is better when it includes different perspectives and voices. We strive to make the Allen Institute a place where everyone feels like they belong and are empowered to do their best work in a supportive environment. We are an equal-opportunity employer and strongly encourage people from all backgrounds to apply for our open positions." This is EEO boilerplate; we should remove.
- Then "Essential Functions" list: bullet points.
- Then "Required Education And Experience": list.
- Then "Preferred Education And Experience": list.
- Then "Physical Demands": description.
- Then "Work Environment": description.
- Then "Position Type/Expected Hours of Work": description.
- Then "Travel": description.
- Then "Additional Comments": relocation assistance, work visa sponsorship.
- Then "Annualized Salary Range": $86,150 - $106,650.
- Then "Benefits": description.
- Then link to Benefits Guide.
- Then EEO policy again (should remove).
We need to output sections: About the role (maybe combine intro and project description), Responsibilities (Essential Functions), Requirements (Required Education And Experience), Qualifications (Preferred Education And Experience maybe?), Skills (maybe from required: programming languages, math stats, agentic workflows), Benefits, Pay, Schedule (Position Type/Expected Hours of Work). Also maybe Work Environment? Not in list of allowed headings but we could include if we think it's substantive; but instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "use
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no invention, no summarizing away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove EEO statements etc. Must keep essential functions, responsibilities, requirements, qualifications, benefits, pay, schedule if present.
Let's parse the posting.
Content:
- Intro paragraph about Allen Institute mission etc. That's "About the role"? Actually it's about the institute and the Neural Dynamics accelerator. Could be considered "About the role" or maybe "About the Institute". The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections are present.
We have:
- Description of goal: "The goal of the Neural Dynamics accelerator is to understand how the brain generates flexible behavior..." That's about the role/project.
- Then: "We are seeking an exceptional scientist to join the Neuromodulation, specifically to create a comprehensively map of the structural organization of neuromodulatory systems in the mouse brain."
- Then details about neuromodulators, project brings together transcriptomic, morphological, connectivity datasets.
- Then: "The scientist will work closely with experimentalists and develop and apply advanced statistical, computational, ML and AI methods to analyze multimodal data including single cell transcriptomics, single neuron reconstructions, input and output connectivity, and in vitro and in vivo physiology."
- Then: "A central biological question is how neuronal properties measured across these modalities align to define functionally relevant cell types."
- Then: "This role offers substantial scope to think deeply about this question and develop conceptual and quantitative frameworks to address it."
- Then: "The scientist will lead the project’s multimodal integration and analysis efforts in close collaboration with experimental and computational teams across the Allen Institute."
- Then: "They will be expected to produce foundational knowledge and openly shared datasets on the structural organization of neuromodulation."
- Then: "For an example of this approach to integrating multimodal neuronal data, see Su et al. Nature 2026."
- Then: "At the Allen Institute, we believe that science is for everyone – and should be open to everyone. We are dedicated to combating biases and reducing barriers to STEM careers more broadly. We also believe that science is better when it includes different perspectives and voices. We strive to make the Allen Institute a place where everyone feels like they belong and are empowered to do their best work in a supportive environment. We are an equal-opportunity employer and strongly encourage people from all backgrounds to apply for our open positions." This is EEO boilerplate; we should remove.
- Then "Essential Functions" list: bullet points.
- Then "Required Education And Experience": list.
- Then "Preferred Education And Experience": list.
- Then "Physical Demands": description.
- Then "Work Environment": description.
- Then "Position Type/Expected Hours of Work": description.
- Then "Travel": description.
- Then "Additional Comments": relocation assistance, work visa sponsorship.
- Then "Annualized Salary Range": $86,150 - $106,650.
- Then "Benefits": description.
- Then link to Benefits Guide.
- Then EEO policy again (should remove).
We need to output sections: About the role (maybe combine intro and project description), Responsibilities (Essential Functions), Requirements (Required Education And Experience), Qualifications (Preferred Education And Experience maybe?), Skills (maybe from required: programming languages, math stats, agentic workflows), Benefits, Pay, Schedule (Position Type/Expected Hours of Work). Also maybe Work Environment? Not in list of allowed headings but we could include if we think it's substantive; but instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. We should stick to those.
Thus we need to map content:
- About the role: description of institute, goal, project, what scientist will do (overview). Could be a paragraph.
- Responsibilities: Essential Functions list (lead project, develop frameworks, conduct analyses, develop methods, collaborate, communicate, help draft reports). Use - .
- Requirements: Required Education And Experience (PhD in fields, proficiency in programming languages, strong grounding in math/stat, deep familiarity with agentic workflows). Use
- .
- Qualifications: Preferred Education And Experience (0-5 years postdoc, interest in neural circuits, experience with cellular/systems/computational neuroscience, ability to work independently/collaboratively, strong communication/organizational skills, strong publication record). Use
- .
- Skills: maybe combine programming languages, math/stat, agentic workflows, communication etc. But we already have those in Requirements and Qualifications. Could create a Skills section summarizing technical skills: proficiency in Python/R, statistical methods, agentic workflows, etc. However we must not invent or summarize away detail; we can list them as items. But we already have them in Requirements; maybe we can still have Skills section with those specifics. However we must preserve ALL substantive information; we can duplicate? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is okay as long as we don't lose info. But better to avoid duplication? Not prohibited. However we might choose to not have Skills section if its content is covered elsewhere. But they said "Prefer a few substantive sections over many thin ones." So maybe we combine skills into Requirements or Qualifications. But we need to include a Skills section only if posting has real specific content for it. The posting does mention "High proficiency in one or more high-level programming languages (e.g. Python, and R)", "Strong grounding in mathematical and statistical methods", "Deep familiarity with agentic workflows for data analysis". Those are skills. Could be placed under Skills. But they also appear under Required Education And Experience. We could move them to Skills and keep Requirements focused on education/experience. However the Required Education And Experience includes those items; we could keep them there and not create Skills. But we need to decide.
Given the instruction to prefer few substantive sections, maybe we have About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. That's 6 sections. Skills could be omitted as its content is covered in Requirements. That seems fine.
Now Benefits: we have description of medical, dental, vision, basic life insurance, 401k plan, paid time off, link to Benefits Guide. That's substantive.
Pay: Annualized Salary Range $86,150 - $106,650. That's specific.
Schedule: Position Type/Expected Hours of Work: "This role is currently working onsite and is expected to work onsite for the majority of the working hours. We are a Washington State employer, and the primary work location for Allen Institute employees is 615 Dexter Ave N.; any remote work must be performed in Washington State." That's schedule/location. Also Travel: occasional national and international conferences. Could be part of Schedule or separate. But we only have Schedule heading allowed; we can include travel info under Schedule.
Additional Comments: relocation assistance, work visa sponsorship. Could be part of Benefits or maybe a separate section but not in allowed headings. Could be included under Benefits? Not exactly. Could be included under About the role? Might be considered extra info. But we should preserve all substantive information. Where to put relocation assistance and visa sponsorship? Could be under Benefits (as additional benefits) or under a separate section like "Additional Info". But not in allowed headings. Perhaps we can include them under Benefits as extra bullet points. Or we could create a section "Additional Information" but not in allowed headings; risk of not following instruction. 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 suggests those are examples. However to be safe, we could include them under Benefits as extra bullet points (relocation assistance, visa sponsorship). Or we could add a separate section "Additional Info" but risk being considered not following instruction. I'd rather include them under Benefits.
Now we need to strip boilerplate: EEO statements, equal-opportunity employer, policy, etc. Also remove "Note: Reasonable accommodations may be made..." etc. Also remove "This description reflects management’s assignment of essential functions; it does not proscribe or restrict the tasks that may be assigned." Also remove "Please note, this opportunity offers relocation assistance" and "Please note, this opportunity may offer work visa sponsorship" - we keep those as substantive (they are not boilerplate). Actually they are substantive; we keep them.
Also remove "Final salary depends on required education for the role, experience, and level of skills relevant to the role, along with work location, where applicable." That's part of Pay description; we can keep it as part of Pay.
Now we need to output only HTML fragment, no /, no markdown fences.
We'll produce something like:
About the role
... paragraphs ...
Responsibilities
- ...
...
Requirements
- ...
...
Qualifications
- ...
...
Benefits
- ...
...
Pay
...
Schedule
...
Make sure to preserve all substantive info.
Let's craft each section.
About the role: combine introductory paragraphs about Allen Institute mission, Neural Dynamics accelerator goal, project description, what scientist will do (lead multimodal integration, produce foundational knowledge, etc). Also mention the example Su et al. Nature 2026. Also mention the institute's commitment to open science, diversity, belonging? That's EEO-ish but also part of culture; maybe we keep as part of About the role? It's not boilerplate? It's about inclusive environment. Could be considered part of About the role. However the instruction says remove EEO/equal-opportunity/scam-warning boilerplate. The diversity statement might be considered EEO boilerplate. Safer to remove it. So we will exclude the paragraph about "At the Allen Institute, we believe that science is for everyone – and should be open to everyone..." etc. That's EEO. So we will not include that.
Thus About the role will include:
- The Allen Institute accelerates science for a healthier world through large-scale research designed to answer some of the most complex questions in biology. Our multi-disciplinary teams generate foundational knowledge, tools, and data to understand how our brain, cells, and immune system work. We share our work openly so others can build on it, move faster, and ask bigger questions. We drive discovery forward and create new possibilities for improving human health.
- The goal of the Neural Dynamics accelerator is to understand how the brain generates flexible behavior. We aim to uncover the algorithms—implemented by dynamics in brain-wide neural circuits—that allow animals to build internal models, process information, and choose actions. We are seeking an exceptional scientist to join the Neuromodulation, specifically to create a comprehensively map of the structural organization of neuromodulatory systems in the mouse brain. Neuromodulators such as norepinephrine, serotonin, dopamine, and acetylcholine are released by small populations of neurons yet exert widespread effects on neural dynamics and behavior. Recent
- .
- Requirements: Required Education And Experience (PhD in fields, proficiency in programming languages, strong grounding in math/stat, deep familiarity with agentic workflows). Use
- .
- Qualifications: Preferred Education And Experience (0-5 years postdoc, interest in neural circuits, experience with cellular/systems/computational neuroscience, ability to work independently/collaboratively, strong communication/organizational skills, strong publication record). Use
- .
- Skills: maybe combine programming languages, math/stat, agentic workflows, communication etc. But we already have those in Requirements and Qualifications. Could create a Skills section summarizing technical skills: proficiency in Python/R, statistical methods, agentic workflows, etc. However we must not invent or summarize away detail; we can list them as items. But we already have them in Requirements; maybe we can still have Skills section with those specifics. However we must preserve ALL substantive information; we can duplicate? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is okay as long as we don't lose info. But better to avoid duplication? Not prohibited. However we might choose to not have Skills section if its content is covered elsewhere. But they said "Prefer a few substantive sections over many thin ones." So maybe we combine skills into Requirements or Qualifications. But we need to include a Skills section only if posting has real specific content for it. The posting does mention "High proficiency in one or more high-level programming languages (e.g. Python, and R)", "Strong grounding in mathematical and statistical methods", "Deep familiarity with agentic workflows for data analysis". Those are skills. Could be placed under Skills. But they also appear under Required Education And Experience. We could move them to Skills and keep Requirements focused on education/experience. However the Required Education And Experience includes those items; we could keep them there and not create Skills. But we need to decide.
Given the instruction to prefer few substantive sections, maybe we have About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. That's 6 sections. Skills could be omitted as its content is covered in Requirements. That seems fine.
Now Benefits: we have description of medical, dental, vision, basic life insurance, 401k plan, paid time off, link to Benefits Guide. That's substantive.
Pay: Annualized Salary Range $86,150 - $106,650. That's specific.
Schedule: Position Type/Expected Hours of Work: "This role is currently working onsite and is expected to work onsite for the majority of the working hours. We are a Washington State employer, and the primary work location for Allen Institute employees is 615 Dexter Ave N.; any remote work must be performed in Washington State." That's schedule/location. Also Travel: occasional national and international conferences. Could be part of Schedule or separate. But we only have Schedule heading allowed; we can include travel info under Schedule.
Additional Comments: relocation assistance, work visa sponsorship. Could be part of Benefits or maybe a separate section but not in allowed headings. Could be included under Benefits? Not exactly. Could be included under About the role? Might be considered extra info. But we should preserve all substantive information. Where to put relocation assistance and visa sponsorship? Could be under Benefits (as additional benefits) or under a separate section like "Additional Info". But not in allowed headings. Perhaps we can include them under Benefits as extra bullet points. Or we could create a section "Additional Information" but not in allowed headings; risk of not following instruction. 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 suggests those are examples. However to be safe, we could include them under Benefits as extra bullet points (relocation assistance, visa sponsorship). Or we could add a separate section "Additional Info" but risk being considered not following instruction. I'd rather include them under Benefits. Now we need to strip boilerplate: EEO statements, equal-opportunity employer, policy, etc. Also remove "Note: Reasonable accommodations may be made..." etc. Also remove "This description reflects management’s assignment of essential functions; it does not proscribe or restrict the tasks that may be assigned." Also remove "Please note, this opportunity offers relocation assistance" and "Please note, this opportunity may offer work visa sponsorship" - we keep those as substantive (they are not boilerplate). Actually they are substantive; we keep them. Also remove "Final salary depends on required education for the role, experience, and level of skills relevant to the role, along with work location, where applicable." That's part of Pay description; we can keep it as part of Pay. Now we need to output only HTML fragment, no /, no markdown fences. We'll produce something like:
About the role
... paragraphs ...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Benefits
- ... ...
Pay
...
Schedule
...
Make sure to preserve all substantive info. Let's craft each section. About the role: combine introductory paragraphs about Allen Institute mission, Neural Dynamics accelerator goal, project description, what scientist will do (lead multimodal integration, produce foundational knowledge, etc). Also mention the example Su et al. Nature 2026. Also mention the institute's commitment to open science, diversity, belonging? That's EEO-ish but also part of culture; maybe we keep as part of About the role? It's not boilerplate? It's about inclusive environment. Could be considered part of About the role. However the instruction says remove EEO/equal-opportunity/scam-warning boilerplate. The diversity statement might be considered EEO boilerplate. Safer to remove it. So we will exclude the paragraph about "At the Allen Institute, we believe that science is for everyone – and should be open to everyone..." etc. That's EEO. So we will not include that. Thus About the role will include: - The Allen Institute accelerates science for a healthier world through large-scale research designed to answer some of the most complex questions in biology. Our multi-disciplinary teams generate foundational knowledge, tools, and data to understand how our brain, cells, and immune system work. We share our work openly so others can build on it, move faster, and ask bigger questions. We drive discovery forward and create new possibilities for improving human health. - The goal of the Neural Dynamics accelerator is to understand how the brain generates flexible behavior. We aim to uncover the algorithms—implemented by dynamics in brain-wide neural circuits—that allow animals to build internal models, process information, and choose actions. We are seeking an exceptional scientist to join the Neuromodulation, specifically to create a comprehensively map of the structural organization of neuromodulatory systems in the mouse brain. Neuromodulators such as norepinephrine, serotonin, dopamine, and acetylcholine are released by small populations of neurons yet exert widespread effects on neural dynamics and behavior. Recent
- .
- Skills: maybe combine programming languages, math/stat, agentic workflows, communication etc. But we already have those in Requirements and Qualifications. Could create a Skills section summarizing technical skills: proficiency in Python/R, statistical methods, agentic workflows, etc. However we must not invent or summarize away detail; we can list them as items. But we already have them in Requirements; maybe we can still have Skills section with those specifics. However we must preserve ALL substantive information; we can duplicate? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is okay as long as we don't lose info. But better to avoid duplication? Not prohibited. However we might choose to not have Skills section if its content is covered elsewhere. But they said "Prefer a few substantive sections over many thin ones." So maybe we combine skills into Requirements or Qualifications. But we need to include a Skills section only if posting has real specific content for it. The posting does mention "High proficiency in one or more high-level programming languages (e.g. Python, and R)", "Strong grounding in mathematical and statistical methods", "Deep familiarity with agentic workflows for data analysis". Those are skills. Could be placed under Skills. But they also appear under Required Education And Experience. We could move them to Skills and keep Requirements focused on education/experience. However the Required Education And Experience includes those items; we could keep them there and not create Skills. But we need to decide.
Given the instruction to prefer few substantive sections, maybe we have About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. That's 6 sections. Skills could be omitted as its content is covered in Requirements. That seems fine.
Now Benefits: we have description of medical, dental, vision, basic life insurance, 401k plan, paid time off, link to Benefits Guide. That's substantive.
Pay: Annualized Salary Range $86,150 - $106,650. That's specific.
Schedule: Position Type/Expected Hours of Work: "This role is currently working onsite and is expected to work onsite for the majority of the working hours. We are a Washington State employer, and the primary work location for Allen Institute employees is 615 Dexter Ave N.; any remote work must be performed in Washington State." That's schedule/location. Also Travel: occasional national and international conferences. Could be part of Schedule or separate. But we only have Schedule heading allowed; we can include travel info under Schedule.
Additional Comments: relocation assistance, work visa sponsorship. Could be part of Benefits or maybe a separate section but not in allowed headings. Could be included under Benefits? Not exactly. Could be included under About the role? Might be considered extra info. But we should preserve all substantive information. Where to put relocation assistance and visa sponsorship? Could be under Benefits (as additional benefits) or under a separate section like "Additional Info". But not in allowed headings. Perhaps we can include them under Benefits as extra bullet points. Or we could create a section "Additional Information" but not in allowed headings; risk of not following instruction. The instruction says use
- .
- Qualifications: Preferred Education And Experience (0-5 years postdoc, interest in neural circuits, experience with cellular/systems/computational neuroscience, ability to work independently/collaboratively, strong communication/organizational skills, strong publication record). Use