Proposal Content Writer, State Curriculum Adoptions (K-12 Curriculum RFP Writer)
K12 Coalition · Eagan, MN · 1 mo ago
Public RelationsFull-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 if posting has real specific content.
We need to parse the job posting.
Key info:
- Brief Description About K12 Coalition (company description). Could be "About the role"? Actually "About the role" is typical heading for role description. We have "The Opportunity" describing role. Could treat as About the role.
- Responsibilities: "What You’ll Do" with bullet points (multiple). We'll need
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content.
We need to parse the job posting.
Key info:
- Brief Description About K12 Coalition (company description). Could be "About the role"? Actually "About the role" is typical heading for role description. We have "The Opportunity" describing role. Could treat as About the role.
- Responsibilities: "What You’ll Do" with bullet points (multiple). We'll need - .
- Requirements: list of requirements (education, experience, skills). Could be under Requirements heading.
- Qualifications: maybe same as Requirements? But we can combine? The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content.
We have:
- About the role: we have description of role, opportunity, what they do. Could be under About the role.
- Responsibilities: "What You’ll Do" list.
- Requirements: education, experience, etc.
- Qualifications: maybe overlapping; but we could treat Requirements as qualifications. However we need to avoid duplicate content. Could put Requirements heading with education/experience, and Qualifications heading with skills like writing, project management, etc. But we need to see if posting distinguishes.
Let's extract:
From posting:
**About the role / Opportunity**:
- "At K12 Coalition, a commitment to transforming educational outcomes for K-12 schools drives all that we do. As we expand our work in curriculum and instructional materials, we are seeking a Proposal Content Writer, State Curriculum Adoptions to support the development of high-quality, compelling, and compliant state adoption submissions. The Proposal Content Writer, State Curriculum Adoptions is part of K12 Coalition’s Sales team and will bring specialized experience developing RFP responses and proposal content for state-level curriculum and instructional materials adoptions. This role will partner closely with curriculum, product, sales, and other subject matter experts to translate complex requirements and program information into clear, persuasive content that demonstrates alignment with state standards, evaluation criteria, and instructional priorities. This is an excellent opportunity for an experienced proposal writer who understands the unique complexities of K-12 curriculum adoptions and thrives in a collaborative, deadline-driven environment. The Proposal Content Writer reports directly to the Director, Business Development."
That's good for About the role.
**Responsibilities** (What You’ll Do):
- State Adoption & Curriculum Proposal Development
- Lead the content development of high-quality RFP responses and submissions for state curriculum and instructional materials adoptions, in partnership with project management support.
- Translate complex state adoption requirements, rubrics, standards, and evaluation criteria into clear, compelling, and compliant proposal content.
- Develop a deep understanding of Lavinia Group’s RedThread Literacy and Math curriculum, including intervention materials, program design, instructional approach, key differentiators, and alignment to state requirements, to accurately and effectively represent our solutions in adoption submissions.
- Customize proposal content to demonstrate alignment between curriculum solutions and state-specific academic standards, instructional priorities, and adoption requirements.
- Thoroughly review RFPs and adoption materials to identify key requirements, evaluation criteria, deadlines, and potential compliance risks.
- Content Development & Collaboration
- Write, edit, and refine proposal content that clearly communicates program design, instructional approach, implementation, professional learning, and other components required for curriculum adoption.
- Collaborate with subject matter experts to translate technical, academic, and product information into accessible and persuasive proposal language.
- Maintain consistency in messaging, terminology, tone, and positioning across proposal materials and supporting documentation.
- Develop and maintain reusable content, templates, and resources to support future curriculum adoption and proposal efforts.
- Proposal Management & Quality
- Manage multiple workstreams and deadlines associated with complex state adoption submissions, ensuring deliverables are accurate, complete, and submitted on time.
- Conduct detailed reviews of proposal materials to ensure alignment with RFP requirements, scoring criteria, and submission guidelines.
- Coordinate feedback and revisions across stakeholders while maintaining version control and ensuring final content reflects agreed-upon messaging and procurement requirements.
- Support additional proposal, curriculum adoption, and business development initiatives as organizational needs evolve.
- Other Duties
- Support the team with additional tasks and responsibilities as needed to help meet evolving organizational goals and objectives.
We can flatten into a single list of duties, but better to keep subheadings? The instruction says use
for section headings, and - for any list of duties/requirements/benefits. It doesn't forbid having multiple
under same heading. We'll just put all duties under Responsibilities heading as a with each duty as - . Could combine sub-bullets but okay.
**Requirements**:
- Master’s degree in Education, Curriculum & Instruction, or a closely related education field required.
- 3+ years of experience in proposal development, RFP writing, or curriculum publishing, with at least 1 year of direct experience supporting state-level curriculum or instructional materials adoption submissions.
- Strong understanding of state curriculum adoption processes, including evaluation criteria, standards alignment, compliance requirements, and instructional materials review.
- Exceptional writing and editing skills, with the ability to translate complex curriculum and product information into clear, compelling proposal content.
- Ability to quickly develop deep knowledge of curriculum products, instructional approaches, and supporting evidence in order to translate complex program information into compelling proposal content.
- Experience interpreting detailed RFPs, rubrics, scoring criteria, and submission requirements and developing content aligned to those requirements.
- Strong project management and organizational skills with demonstrated success managing complex, deadline-driven submissions involving multiple stakeholders.
- Ability to collaborate effectively with curriculum experts, product teams, sales or partnerships teams, and other subject matter experts.
- Exceptional attention to detail, particularly when reviewing requirements, managing documentation, and ensuring proposal compliance.
- Experience with K-12 curriculum, instructional materials, education publishing, or education technology strongly preferred.
- Experience supporting multi-state curriculum adoption efforts or multiple subject areas is a plus.
**Qualifications**: Might be similar to Requirements; but we could treat Requirements as qualifications. However we need to decide if we need separate Qualifications heading. The posting doesn't have a separate "Qualifications" label; it's all under Requirements. So we could just have Requirements heading and not Qualifications. But we could also split: Requirements (education/experience) and Qualifications (skills). But risk of duplication. Safer to follow the posting: we have a "Requirements" block. We'll output that as Requirements heading.
**Skills**: Not explicitly listed separate; but we could extract skills like writing, editing, project management, collaboration, attention to detail, etc. However those are already in Requirements. Could create Skills heading but would duplicate. Better to not create Skills if no distinct section.
**Benefits**: The posting mentions benefits under "Why Work with Us": "We believe in supporting the whole employee by offering a comprehensive benefits package designed to meet diverse needs. Our full-time employee benefits include flexible time off, paid parental leave, comprehensive medical, dental, and vision insurance, and a 401(k) with company matching." That's specific benefits. So we should include Benefits heading with a
of those.
**Pay**: The posting mentions compensation philosophy: "As part of our commitment to maintaining fair and consistent compensation practices, new hires are typically brought into the organization at a salary between the band minimum and midpoint, based on their qualifications, location, internal alignment, and the budgeted amount for the role." That's not a specific number or range; it's vague. The instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It says "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". The compensation philosophy is vague but not a specific number; it's still filler? It says "typically brought into the organization at a salary between the band minimum and midpoint". That's not a specific number, but it's still somewhat vague. It might be considered filler. Safer to omit Pay section because no concrete pay info.
**Schedule**: Not mentioned; only location remote, full-time exempt salaried. No schedule details. So omit Schedule.
**About the role**: we have content.
We also have "Employment Type Full-Time Exempt Salaried Location: Remote, available from anywhere within the U.S." That's metadata; we could fold into a short under About the role or maybe separate? The instruction says do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include a short paragraph with employment type and location.
We also have "Brief Description About K12 Coalition" at start. That could be part of About the role or maybe a separate "About the company". But headings list does not include About the company; only About the role. We could incorporate that into About the role paragraph.
Thus final HTML:
About the role
[description + employment type + location]
Responsibilities
- ...
...
Requirements
- ...
...
Benefits
- ...
...
We must not include any other headings like Qualifications, Skills, Pay, Schedule.
We need to preserve all substantive information; not invent or summarize away detail. So we need to include all bullet points from Responsibilities, Requirements, Benefits exactly as given (or close). Must not omit any.
Let's extract exact bullet points.
From Responsibilities:
State Adoption & Curriculum Proposal Development
- Lead the content development of high-quality RFP responses and submissions for state curriculum and instructional materials adoptions, in partnership with project management support.
- Translate complex state adoption requirements, rubrics, standards, and evaluation criteria into clear, compelling, and compliant proposal content.
- Develop a deep understanding of Lavinia Group’s RedThread Literacy and Math curriculum, including intervention materials, program design, instructional approach, key differentiators, and alignment to state requirements, to accurately and effectively represent our solutions in adoption submissions.
- Customize proposal content to demonstrate alignment between curriculum solutions and state-specific academic standards, instructional priorities, and adoption requirements.
- Thoroughly review RFPs and adoption materials to identify key requirements, evaluation criteria, deadlines, and potential compliance risks.
Content Development & Collaboration
- Write, edit, and refine proposal content that clearly communicates program design, instructional approach, implementation, professional learning, and other components required for curriculum adoption.
- Collaborate with subject matter experts to translate technical, academic, and product information into accessible and persuasive proposal language.
- Maintain consistency in messaging, terminology, tone, and positioning across proposal materials and supporting documentation.
- Develop and maintain reusable content, templates, and resources to support future curriculum adoption and proposal efforts.
Proposal Management & Quality
- Manage multiple workstreams and deadlines associated with complex state adoption submissions, ensuring deliverables are accurate, complete, and submitted on time.
- Conduct detailed reviews of proposal materials to ensure alignment with RFP requirements, scoring criteria, and submission guidelines.
- Coordinate feedback and revisions across stakeholders while maintaining version control and ensuring final content reflects agreed-upon messaging and procurement requirements.
- Support additional proposal, curriculum adoption, and business development initiatives as organizational needs evolve.
Other Duties
- Support the team with additional tasks and responsibilities as needed to help meet evolving organizational goals and objectives.
We could keep each bullet as separate - . The headings like "State Adoption & Curriculum Proposal Development" are subheadings; but we are not allowed to use headings other than
for sections. We could either keep them as plain text inside
- or we could bold them? The instruction says output only HTML fragment; we can use inside
- . That's okay. We'll keep the subheading as plain text maybe ending with colon. We'll include them as part of the
- text.
Thus
for section headings, and - for any list of duties/requirements/benefits. It doesn't forbid having multiple
under same heading. We'll just put all duties under Responsibilities heading as a with each duty as - . Could combine sub-bullets but okay.
**Requirements**:
- Master’s degree in Education, Curriculum & Instruction, or a closely related education field required.
- 3+ years of experience in proposal development, RFP writing, or curriculum publishing, with at least 1 year of direct experience supporting state-level curriculum or instructional materials adoption submissions.
- Strong understanding of state curriculum adoption processes, including evaluation criteria, standards alignment, compliance requirements, and instructional materials review.
- Exceptional writing and editing skills, with the ability to translate complex curriculum and product information into clear, compelling proposal content.
- Ability to quickly develop deep knowledge of curriculum products, instructional approaches, and supporting evidence in order to translate complex program information into compelling proposal content.
- Experience interpreting detailed RFPs, rubrics, scoring criteria, and submission requirements and developing content aligned to those requirements.
- Strong project management and organizational skills with demonstrated success managing complex, deadline-driven submissions involving multiple stakeholders.
- Ability to collaborate effectively with curriculum experts, product teams, sales or partnerships teams, and other subject matter experts.
- Exceptional attention to detail, particularly when reviewing requirements, managing documentation, and ensuring proposal compliance.
- Experience with K-12 curriculum, instructional materials, education publishing, or education technology strongly preferred.
- Experience supporting multi-state curriculum adoption efforts or multiple subject areas is a plus.
**Qualifications**: Might be similar to Requirements; but we could treat Requirements as qualifications. However we need to decide if we need separate Qualifications heading. The posting doesn't have a separate "Qualifications" label; it's all under Requirements. So we could just have Requirements heading and not Qualifications. But we could also split: Requirements (education/experience) and Qualifications (skills). But risk of duplication. Safer to follow the posting: we have a "Requirements" block. We'll output that as Requirements heading.
**Skills**: Not explicitly listed separate; but we could extract skills like writing, editing, project management, collaboration, attention to detail, etc. However those are already in Requirements. Could create Skills heading but would duplicate. Better to not create Skills if no distinct section.
**Benefits**: The posting mentions benefits under "Why Work with Us": "We believe in supporting the whole employee by offering a comprehensive benefits package designed to meet diverse needs. Our full-time employee benefits include flexible time off, paid parental leave, comprehensive medical, dental, and vision insurance, and a 401(k) with company matching." That's specific benefits. So we should include Benefits heading with a
of those.
**Pay**: The posting mentions compensation philosophy: "As part of our commitment to maintaining fair and consistent compensation practices, new hires are typically brought into the organization at a salary between the band minimum and midpoint, based on their qualifications, location, internal alignment, and the budgeted amount for the role." That's not a specific number or range; it's vague. The instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It says "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". The compensation philosophy is vague but not a specific number; it's still filler? It says "typically brought into the organization at a salary between the band minimum and midpoint". That's not a specific number, but it's still somewhat vague. It might be considered filler. Safer to omit Pay section because no concrete pay info.
**Schedule**: Not mentioned; only location remote, full-time exempt salaried. No schedule details. So omit Schedule.
**About the role**: we have content.
We also have "Employment Type Full-Time Exempt Salaried Location: Remote, available from anywhere within the U.S." That's metadata; we could fold into a short under About the role or maybe separate? The instruction says do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include a short paragraph with employment type and location.
We also have "Brief Description About K12 Coalition" at start. That could be part of About the role or maybe a separate "About the company". But headings list does not include About the company; only About the role. We could incorporate that into About the role paragraph.
Thus final HTML:
About the role
[description + employment type + location]
Responsibilities
- ...
...
Requirements
- ...
...
Benefits
- ...
...
We must not include any other headings like Qualifications, Skills, Pay, Schedule.
We need to preserve all substantive information; not invent or summarize away detail. So we need to include all bullet points from Responsibilities, Requirements, Benefits exactly as given (or close). Must not omit any.
Let's extract exact bullet points.
From Responsibilities:
State Adoption & Curriculum Proposal Development
- Lead the content development of high-quality RFP responses and submissions for state curriculum and instructional materials adoptions, in partnership with project management support.
- Translate complex state adoption requirements, rubrics, standards, and evaluation criteria into clear, compelling, and compliant proposal content.
- Develop a deep understanding of Lavinia Group’s RedThread Literacy and Math curriculum, including intervention materials, program design, instructional approach, key differentiators, and alignment to state requirements, to accurately and effectively represent our solutions in adoption submissions.
- Customize proposal content to demonstrate alignment between curriculum solutions and state-specific academic standards, instructional priorities, and adoption requirements.
- Thoroughly review RFPs and adoption materials to identify key requirements, evaluation criteria, deadlines, and potential compliance risks.
Content Development & Collaboration
- Write, edit, and refine proposal content that clearly communicates program design, instructional approach, implementation, professional learning, and other components required for curriculum adoption.
- Collaborate with subject matter experts to translate technical, academic, and product information into accessible and persuasive proposal language.
- Maintain consistency in messaging, terminology, tone, and positioning across proposal materials and supporting documentation.
- Develop and maintain reusable content, templates, and resources to support future curriculum adoption and proposal efforts.
Proposal Management & Quality
- Manage multiple workstreams and deadlines associated with complex state adoption submissions, ensuring deliverables are accurate, complete, and submitted on time.
- Conduct detailed reviews of proposal materials to ensure alignment with RFP requirements, scoring criteria, and submission guidelines.
- Coordinate feedback and revisions across stakeholders while maintaining version control and ensuring final content reflects agreed-upon messaging and procurement requirements.
- Support additional proposal, curriculum adoption, and business development initiatives as organizational needs evolve.
Other Duties
- Support the team with additional tasks and responsibilities as needed to help meet evolving organizational goals and objectives.
We could keep each bullet as separate - . The headings like "State Adoption & Curriculum Proposal Development" are subheadings; but we are not allowed to use headings other than
for sections. We could either keep them as plain text inside
- or we could bold them? The instruction says output only HTML fragment; we can use inside
- . That's okay. We'll keep the subheading as plain text maybe ending with colon. We'll include them as part of the
- text.
Thus
- under same heading. We'll just put all duties under Responsibilities heading as a
- . Could combine sub-bullets but okay.
**Requirements**:
- Master’s degree in Education, Curriculum & Instruction, or a closely related education field required.
- 3+ years of experience in proposal development, RFP writing, or curriculum publishing, with at least 1 year of direct experience supporting state-level curriculum or instructional materials adoption submissions.
- Strong understanding of state curriculum adoption processes, including evaluation criteria, standards alignment, compliance requirements, and instructional materials review.
- Exceptional writing and editing skills, with the ability to translate complex curriculum and product information into clear, compelling proposal content.
- Ability to quickly develop deep knowledge of curriculum products, instructional approaches, and supporting evidence in order to translate complex program information into compelling proposal content.
- Experience interpreting detailed RFPs, rubrics, scoring criteria, and submission requirements and developing content aligned to those requirements.
- Strong project management and organizational skills with demonstrated success managing complex, deadline-driven submissions involving multiple stakeholders.
- Ability to collaborate effectively with curriculum experts, product teams, sales or partnerships teams, and other subject matter experts.
- Exceptional attention to detail, particularly when reviewing requirements, managing documentation, and ensuring proposal compliance.
- Experience with K-12 curriculum, instructional materials, education publishing, or education technology strongly preferred.
- Experience supporting multi-state curriculum adoption efforts or multiple subject areas is a plus.
**Qualifications**: Might be similar to Requirements; but we could treat Requirements as qualifications. However we need to decide if we need separate Qualifications heading. The posting doesn't have a separate "Qualifications" label; it's all under Requirements. So we could just have Requirements heading and not Qualifications. But we could also split: Requirements (education/experience) and Qualifications (skills). But risk of duplication. Safer to follow the posting: we have a "Requirements" block. We'll output that as Requirements heading.
**Skills**: Not explicitly listed separate; but we could extract skills like writing, editing, project management, collaboration, attention to detail, etc. However those are already in Requirements. Could create Skills heading but would duplicate. Better to not create Skills if no distinct section.
**Benefits**: The posting mentions benefits under "Why Work with Us": "We believe in supporting the whole employee by offering a comprehensive benefits package designed to meet diverse needs. Our full-time employee benefits include flexible time off, paid parental leave, comprehensive medical, dental, and vision insurance, and a 401(k) with company matching." That's specific benefits. So we should include Benefits heading with a
- of those.
**Pay**: The posting mentions compensation philosophy: "As part of our commitment to maintaining fair and consistent compensation practices, new hires are typically brought into the organization at a salary between the band minimum and midpoint, based on their qualifications, location, internal alignment, and the budgeted amount for the role." That's not a specific number or range; it's vague. The instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It says "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". The compensation philosophy is vague but not a specific number; it's still filler? It says "typically brought into the organization at a salary between the band minimum and midpoint". That's not a specific number, but it's still somewhat vague. It might be considered filler. Safer to omit Pay section because no concrete pay info.
**Schedule**: Not mentioned; only location remote, full-time exempt salaried. No schedule details. So omit Schedule.
**About the role**: we have content.
We also have "Employment Type Full-Time Exempt Salaried Location: Remote, available from anywhere within the U.S." That's metadata; we could fold into a short
- ... ...
- ... ...
- ... ...
- . The headings like "State Adoption & Curriculum Proposal Development" are subheadings; but we are not allowed to use headings other than
for sections. We could either keep them as plain text inside
- or we could bold them? The instruction says output only HTML fragment; we can use inside
- . That's okay. We'll keep the subheading as plain text maybe ending with colon. We'll include them as part of the
- text. Thus
under About the role or maybe separate? The instruction says do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include a short paragraph with employment type and location. We also have "Brief Description About K12 Coalition" at start. That could be part of About the role or maybe a separate "About the company". But headings list does not include About the company; only About the role. We could incorporate that into About the role paragraph. Thus final HTML:
About the role
[description + employment type + location]
Responsibilities
Requirements
Benefits
- with each duty as