Commercial Contracts Manager
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
2. Use - for lists,
for prose
3. Do NOT repeat job title as heading
4. Do NOT put Job ID/requisition numbers as headings
5. Preserve ALL substantive information
6. Remove boilerplate (cookie/navigation/legal/EEO/scam-warning)
7. Include section ONLY when posting has real specific content
8. Never emit heading followed by filler/placeholder text
9. Never create Pay/Schedule/Benefits sections unless posting actually states them
10. Output ONLY HTML fragment - no /, no markdown code fences
Let me analyze the content:
The posting has:
- About Nooks (company description)
- About The Role (role description)
- Key Responsibilities (with sub-sections: Commercial Negotiation, Playbook and Enablement, Deal Support and Reporting)
- The Skillset (requirements/qualifications)
- Compensation & Benefits (yearly bonus, equity, health, 401k, flexible time away)
- Eligibility & Clearance (work authorization, security clearance)
- Location-Specific Addendums (work independently, build playbook, travel)
- What Success Looks Like In This Role
- Cross-Functional Expectations
- Salary Range: $123,000 - $136,000 USD
I need to organize this into appropriate sections. The rules say use
for section headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule".
I should map:
- "About The Role" -> "About the role" (h3)
- "Key Responsibilities" -> "Responsibilities" (h3) with sub-lists
- "The Skillset" -> "Requirements" or "Qualifications" (h3) - this is a list of requirements
- "Compensation & Benefits" -> "Benefits" (h3) and "Pay" (h3) since salary range is given
- "Eligibility & Clearance" -> could be part of Requirements or separate
- "Location-Specific Addendums" -> maybe part of About the role or separate
- "What Success Looks Like In This Role" -> could be part of About the role or separate
- "Cross-Functional Expectations" -> could be part of About the role
The rules say: "Prefer a few substantive sections over many thin ones." So I should consolidate.
Also: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text"
The posting has specific content for:
- About the role (the "About The Role" section)
- Responsibilities (the "Key Responsibilities" with three sub-sections)
- Requirements/Qualifications (The Skillset)
- Benefits (Compensation & Benefits lists specific benefits)
- Pay (Salary Range is specific: $123,000 - $136,000 USD)
- Eligibility & Clearance (specific requirements)
- Location-Specific Addendums (specific info)
- What Success Looks Like (specific)
- Cross-Functional Expectations (specific)
But I should consolidate. Let me think about structure:
1. About the role (h3) - combine "About The Role" and maybe "Location-Specific Addendums" and "What Success Looks Like" and "Cross-Functional Expectations" as they describe the role context.
2. Responsibilities (h3) - the Key Responsibilities with three sub-areas. I'll use nested lists or separate lists under subheadings? The rules say use - for any list of duties. I could use
for sub-sections? But the rules only mention for section headings. It says "use 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 those. I think I should use for main sections only. For sub-sections within Responsibilities, I could use or just include in list items. But the content has three distinct areas: Commercial Negotiation, Playbook and Enablement, Deal Support and Reporting. I could make them separate lists under Responsibilities with bold labels.
3. Requirements (h3) - The Skillset list.
4. Benefits (h3) - Compensation & Benefits list.
5. Pay (h3) - Salary Range.
6. Eligibility & Clearance (h3) - maybe combine with Requirements? But it's separate section in posting. Could be "Qualifications" or "Eligibility". The rules mention "Qualifications" as example heading. I'll use "Qualifications" for The Skillset and "Eligibility" for Eligibility & Clearance? But "Qualifications" and "Requirements" are similar. The rules list both "Requirements" and "Qualifications" as examples. I'll use "Requirements" for The Skillset and "Eligibility" for Eligibility & Clearance.
But the rules say "Prefer a few substantive sections over many thin ones." So maybe combine Eligibility into Requirements.
Also "Location-Specific Addendums" is specific: "You work independently your agreements cover across every location and lifecycle phase. No commercial contract playbook exists today, so you build the standard first and then hold every deal to it. Expect occasional travel for company events and select customer negotiations." This is about the role nature.
"What Success Looks Like In This Role" is specific success metrics.
"Cross-Functional Expectations" is about partnerships.
I think I'll create these sections:
- About the role (combining About The Role, Location-Specific Addendums, What Success Looks Like, Cross-Functional Expectations)
- Responsibilities (with three sub-areas as labeled lists)
- Requirements (The Skillset)
- Eligibility & Clearance (separate, as it's about work authorization and clearance)
- Benefits (Compensation & Benefits)
- Pay (Salary Range)
But the rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states both Benefits and Pay (salary range). So include both.
Now, for Responsibilities: I'll use Responsibilities
then for each sub-area, maybe a Commercial Negotiation
followed by - ... or just include the sub-area as part of list items? The content has bullet points under each. I'll do:
Responsibilities
Commercial Negotiation
- ...
Playbook and Enablement
- ...
Deal Support and Reporting
- ...
That seems clean.
For Requirements: The Skillset has bullet points. I'll use - .
For Eligibility & Clearance: two bullet points.
For Benefits: bullet points.
For Pay: just the salary range as paragraph.
Now, "About Nooks" is company description. Should I include? The rules say "Preserve ALL substantive information". It's about the company, not the role. But it's part of the posting. The rules don't say to exclude company description. However, the example headings don't include "About the company". The user said "reformat a job posting into clean, well-structured semantic HTML." I think I should include it as a section, maybe "About the company" but the rules only list specific headings. The rules say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It says "e.g." so not exhaustive. But also "include a section ONLY when the posting has real, specific content for it". The posting has "About Nooks" with specific content. I'll include it as "About the company" with . But the rules say "Do NOT repeat the job title as a heading (the page already shows it)". That's about job title. Company description is fine.
However, the user might expect only the role-related sections. But the instruction: "Preserve ALL substantive information". So I'll include About Nooks.
Let me structure:
About the company
Nooks is pioneering Classified-Infrastructure-as-a-Service (CIaaS) — designing, building, and operating Sensitive Compartmented Information Facilities (SCIFs) and other secured, classified environments for the defense and national security community. We work with the agencies, contractors, and mission-driven organizations that keep the nation safe, delivering the physical infrastructure that makes classified work possible. We're growing fast, operating across multiple markets, and building a company that takes both the mission and the business seriously.
About the role
You own the contract cycle for Nooks' commercial contracts: reviewing, redlining, and negotiating agreements with third parties from first draft through signature, including amendment and revisions as needed. Nooks needs these agreements to reach signature faster, without conceding terms under deadline pressure. You deliver both by drafting the contracts playbook with outside counsel and working every deal against it. You report to the VP of Growth, take legal direction from outside counsel, and work as a full-time individual contributor. At Nooks, we move fast. While you'll have clear ownership over your core responsibilities, startup life means priorities can shift. We're looking for a proactive problem-solver who is comfortable with ambiguity and ready to lean in wherever the team needs them most to drive us forward.
Location-Specific Addendums: You work independently your agreements cover across every location and lifecycle phase. No commercial contract playbook exists today, so you build the standard first and then hold every deal to it. Expect occasional travel for company events and select customer negotiations.
What Success Looks Like In This Role: An approved commercial contract playbook governs every customer negotiation, and the Growth team resolves routine terms without routing them to you. Commercial agreements reach signature on a predictable cycle time that you track and report, and deals no longer stall in contract review. Deviations from approved positions are rare, documented, and escalated before signature rather than discovered after. Every executed commercial agreement, amendment, and renewal sits in a complete record with key dates tracked. Leadership relies on you to tell them, before a deal closes, exactly which terms Nooks is accepting and why.
Cross-Functional Expectations: You partner daily with the Growth team and negotiate directly with customer legal and procurement teams. You execute on outside counsel's legal direction and bring material terms to the VP of Growth for decision. Pricing, government contracts, regulatory flow-down clauses, and security classification requirements sit with other owners; you route them rather than resolve them.
Responsibilities
Commercial Negotiation
- Review, redline, and negotiate commercial customer agreements, including service agreements, Non-Disclosure Agreements (NDAs), and teaming agreements, against approved playbook positions.
- Decide non-material terms within guidelines and escalate material terms, such as price and duration, to the VP of Growth with a recommendation.
- Draft and negotiate amendments, extensions, and renewals of executed commercial agreements, keeping each change consistent with current playbook positions.
Playbook and Enablement
- Draft the commercial contract playbook, setting
for prose 3. Do NOT repeat job title as heading 4. Do NOT put Job ID/requisition numbers as headings 5. Preserve ALL substantive information 6. Remove boilerplate (cookie/navigation/legal/EEO/scam-warning) 7. Include section ONLY when posting has real specific content 8. Never emit heading followed by filler/placeholder text 9. Never create Pay/Schedule/Benefits sections unless posting actually states them 10. Output ONLY HTML fragment - no /, no markdown code fences Let me analyze the content: The posting has: - About Nooks (company description) - About The Role (role description) - Key Responsibilities (with sub-sections: Commercial Negotiation, Playbook and Enablement, Deal Support and Reporting) - The Skillset (requirements/qualifications) - Compensation & Benefits (yearly bonus, equity, health, 401k, flexible time away) - Eligibility & Clearance (work authorization, security clearance) - Location-Specific Addendums (work independently, build playbook, travel) - What Success Looks Like In This Role - Cross-Functional Expectations - Salary Range: $123,000 - $136,000 USD I need to organize this into appropriate sections. The rules say use
for section headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule".
I should map:
- "About The Role" -> "About the role" (h3)
- "Key Responsibilities" -> "Responsibilities" (h3) with sub-lists
- "The Skillset" -> "Requirements" or "Qualifications" (h3) - this is a list of requirements
- "Compensation & Benefits" -> "Benefits" (h3) and "Pay" (h3) since salary range is given
- "Eligibility & Clearance" -> could be part of Requirements or separate
- "Location-Specific Addendums" -> maybe part of About the role or separate
- "What Success Looks Like In This Role" -> could be part of About the role or separate
- "Cross-Functional Expectations" -> could be part of About the role
The rules say: "Prefer a few substantive sections over many thin ones." So I should consolidate.
Also: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text"
The posting has specific content for:
- About the role (the "About The Role" section)
- Responsibilities (the "Key Responsibilities" with three sub-sections)
- Requirements/Qualifications (The Skillset)
- Benefits (Compensation & Benefits lists specific benefits)
- Pay (Salary Range is specific: $123,000 - $136,000 USD)
- Eligibility & Clearance (specific requirements)
- Location-Specific Addendums (specific info)
- What Success Looks Like (specific)
- Cross-Functional Expectations (specific)
But I should consolidate. Let me think about structure:
1. About the role (h3) - combine "About The Role" and maybe "Location-Specific Addendums" and "What Success Looks Like" and "Cross-Functional Expectations" as they describe the role context.
2. Responsibilities (h3) - the Key Responsibilities with three sub-areas. I'll use nested lists or separate lists under subheadings? The rules say use - for any list of duties. I could use
for sub-sections? But the rules only mention for section headings. It says "use 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 those. I think I should use for main sections only. For sub-sections within Responsibilities, I could use or just include in list items. But the content has three distinct areas: Commercial Negotiation, Playbook and Enablement, Deal Support and Reporting. I could make them separate lists under Responsibilities with bold labels.
3. Requirements (h3) - The Skillset list.
4. Benefits (h3) - Compensation & Benefits list.
5. Pay (h3) - Salary Range.
6. Eligibility & Clearance (h3) - maybe combine with Requirements? But it's separate section in posting. Could be "Qualifications" or "Eligibility". The rules mention "Qualifications" as example heading. I'll use "Qualifications" for The Skillset and "Eligibility" for Eligibility & Clearance? But "Qualifications" and "Requirements" are similar. The rules list both "Requirements" and "Qualifications" as examples. I'll use "Requirements" for The Skillset and "Eligibility" for Eligibility & Clearance.
But the rules say "Prefer a few substantive sections over many thin ones." So maybe combine Eligibility into Requirements.
Also "Location-Specific Addendums" is specific: "You work independently your agreements cover across every location and lifecycle phase. No commercial contract playbook exists today, so you build the standard first and then hold every deal to it. Expect occasional travel for company events and select customer negotiations." This is about the role nature.
"What Success Looks Like In This Role" is specific success metrics.
"Cross-Functional Expectations" is about partnerships.
I think I'll create these sections:
- About the role (combining About The Role, Location-Specific Addendums, What Success Looks Like, Cross-Functional Expectations)
- Responsibilities (with three sub-areas as labeled lists)
- Requirements (The Skillset)
- Eligibility & Clearance (separate, as it's about work authorization and clearance)
- Benefits (Compensation & Benefits)
- Pay (Salary Range)
But the rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states both Benefits and Pay (salary range). So include both.
Now, for Responsibilities: I'll use Responsibilities
then for each sub-area, maybe a Commercial Negotiation
followed by - ... or just include the sub-area as part of list items? The content has bullet points under each. I'll do:
Responsibilities
Commercial Negotiation
- ...
Playbook and Enablement
- ...
Deal Support and Reporting
- ...
That seems clean.
For Requirements: The Skillset has bullet points. I'll use - .
For Eligibility & Clearance: two bullet points.
For Benefits: bullet points.
For Pay: just the salary range as paragraph.
Now, "About Nooks" is company description. Should I include? The rules say "Preserve ALL substantive information". It's about the company, not the role. But it's part of the posting. The rules don't say to exclude company description. However, the example headings don't include "About the company". The user said "reformat a job posting into clean, well-structured semantic HTML." I think I should include it as a section, maybe "About the company" but the rules only list specific headings. The rules say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It says "e.g." so not exhaustive. But also "include a section ONLY when the posting has real, specific content for it". The posting has "About Nooks" with specific content. I'll include it as "About the company" with . But the rules say "Do NOT repeat the job title as a heading (the page already shows it)". That's about job title. Company description is fine.
However, the user might expect only the role-related sections. But the instruction: "Preserve ALL substantive information". So I'll include About Nooks.
Let me structure:
About the company
Nooks is pioneering Classified-Infrastructure-as-a-Service (CIaaS) — designing, building, and operating Sensitive Compartmented Information Facilities (SCIFs) and other secured, classified environments for the defense and national security community. We work with the agencies, contractors, and mission-driven organizations that keep the nation safe, delivering the physical infrastructure that makes classified work possible. We're growing fast, operating across multiple markets, and building a company that takes both the mission and the business seriously.
About the role
You own the contract cycle for Nooks' commercial contracts: reviewing, redlining, and negotiating agreements with third parties from first draft through signature, including amendment and revisions as needed. Nooks needs these agreements to reach signature faster, without conceding terms under deadline pressure. You deliver both by drafting the contracts playbook with outside counsel and working every deal against it. You report to the VP of Growth, take legal direction from outside counsel, and work as a full-time individual contributor. At Nooks, we move fast. While you'll have clear ownership over your core responsibilities, startup life means priorities can shift. We're looking for a proactive problem-solver who is comfortable with ambiguity and ready to lean in wherever the team needs them most to drive us forward.
Location-Specific Addendums: You work independently your agreements cover across every location and lifecycle phase. No commercial contract playbook exists today, so you build the standard first and then hold every deal to it. Expect occasional travel for company events and select customer negotiations.
What Success Looks Like In This Role: An approved commercial contract playbook governs every customer negotiation, and the Growth team resolves routine terms without routing them to you. Commercial agreements reach signature on a predictable cycle time that you track and report, and deals no longer stall in contract review. Deviations from approved positions are rare, documented, and escalated before signature rather than discovered after. Every executed commercial agreement, amendment, and renewal sits in a complete record with key dates tracked. Leadership relies on you to tell them, before a deal closes, exactly which terms Nooks is accepting and why.
Cross-Functional Expectations: You partner daily with the Growth team and negotiate directly with customer legal and procurement teams. You execute on outside counsel's legal direction and bring material terms to the VP of Growth for decision. Pricing, government contracts, regulatory flow-down clauses, and security classification requirements sit with other owners; you route them rather than resolve them.
Responsibilities
Commercial Negotiation
- Review, redline, and negotiate commercial customer agreements, including service agreements, Non-Disclosure Agreements (NDAs), and teaming agreements, against approved playbook positions.
- Decide non-material terms within guidelines and escalate material terms, such as price and duration, to the VP of Growth with a recommendation.
- Draft and negotiate amendments, extensions, and renewals of executed commercial agreements, keeping each change consistent with current playbook positions.
Playbook and Enablement
- Draft the commercial contract playbook, setting
for sub-sections? But the rules only mention for section headings. It says "use 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 those. I think I should use for main sections only. For sub-sections within Responsibilities, I could use or just include in list items. But the content has three distinct areas: Commercial Negotiation, Playbook and Enablement, Deal Support and Reporting. I could make them separate lists under Responsibilities with bold labels.
3. Requirements (h3) - The Skillset list.
4. Benefits (h3) - Compensation & Benefits list.
5. Pay (h3) - Salary Range.
6. Eligibility & Clearance (h3) - maybe combine with Requirements? But it's separate section in posting. Could be "Qualifications" or "Eligibility". The rules mention "Qualifications" as example heading. I'll use "Qualifications" for The Skillset and "Eligibility" for Eligibility & Clearance? But "Qualifications" and "Requirements" are similar. The rules list both "Requirements" and "Qualifications" as examples. I'll use "Requirements" for The Skillset and "Eligibility" for Eligibility & Clearance.
But the rules say "Prefer a few substantive sections over many thin ones." So maybe combine Eligibility into Requirements.
Also "Location-Specific Addendums" is specific: "You work independently your agreements cover across every location and lifecycle phase. No commercial contract playbook exists today, so you build the standard first and then hold every deal to it. Expect occasional travel for company events and select customer negotiations." This is about the role nature.
"What Success Looks Like In This Role" is specific success metrics.
"Cross-Functional Expectations" is about partnerships.
I think I'll create these sections:
- About the role (combining About The Role, Location-Specific Addendums, What Success Looks Like, Cross-Functional Expectations)
- Responsibilities (with three sub-areas as labeled lists)
- Requirements (The Skillset)
- Eligibility & Clearance (separate, as it's about work authorization and clearance)
- Benefits (Compensation & Benefits)
- Pay (Salary Range)
But the rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states both Benefits and Pay (salary range). So include both.
Now, for Responsibilities: I'll use Responsibilities
then for each sub-area, maybe a Commercial Negotiation
followed by - ... or just include the sub-area as part of list items? The content has bullet points under each. I'll do:
Responsibilities
Commercial Negotiation
- ...
Playbook and Enablement
- ...
Deal Support and Reporting
- ...
That seems clean.
For Requirements: The Skillset has bullet points. I'll use - .
For Eligibility & Clearance: two bullet points.
For Benefits: bullet points.
For Pay: just the salary range as paragraph.
Now, "About Nooks" is company description. Should I include? The rules say "Preserve ALL substantive information". It's about the company, not the role. But it's part of the posting. The rules don't say to exclude company description. However, the example headings don't include "About the company". The user said "reformat a job posting into clean, well-structured semantic HTML." I think I should include it as a section, maybe "About the company" but the rules only list specific headings. The rules say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It says "e.g." so not exhaustive. But also "include a section ONLY when the posting has real, specific content for it". The posting has "About Nooks" with specific content. I'll include it as "About the company" with . But the rules say "Do NOT repeat the job title as a heading (the page already shows it)". That's about job title. Company description is fine.
However, the user might expect only the role-related sections. But the instruction: "Preserve ALL substantive information". So I'll include About Nooks.
Let me structure:
About the company
Nooks is pioneering Classified-Infrastructure-as-a-Service (CIaaS) — designing, building, and operating Sensitive Compartmented Information Facilities (SCIFs) and other secured, classified environments for the defense and national security community. We work with the agencies, contractors, and mission-driven organizations that keep the nation safe, delivering the physical infrastructure that makes classified work possible. We're growing fast, operating across multiple markets, and building a company that takes both the mission and the business seriously.
About the role
You own the contract cycle for Nooks' commercial contracts: reviewing, redlining, and negotiating agreements with third parties from first draft through signature, including amendment and revisions as needed. Nooks needs these agreements to reach signature faster, without conceding terms under deadline pressure. You deliver both by drafting the contracts playbook with outside counsel and working every deal against it. You report to the VP of Growth, take legal direction from outside counsel, and work as a full-time individual contributor. At Nooks, we move fast. While you'll have clear ownership over your core responsibilities, startup life means priorities can shift. We're looking for a proactive problem-solver who is comfortable with ambiguity and ready to lean in wherever the team needs them most to drive us forward.
Location-Specific Addendums: You work independently your agreements cover across every location and lifecycle phase. No commercial contract playbook exists today, so you build the standard first and then hold every deal to it. Expect occasional travel for company events and select customer negotiations.
What Success Looks Like In This Role: An approved commercial contract playbook governs every customer negotiation, and the Growth team resolves routine terms without routing them to you. Commercial agreements reach signature on a predictable cycle time that you track and report, and deals no longer stall in contract review. Deviations from approved positions are rare, documented, and escalated before signature rather than discovered after. Every executed commercial agreement, amendment, and renewal sits in a complete record with key dates tracked. Leadership relies on you to tell them, before a deal closes, exactly which terms Nooks is accepting and why.
Cross-Functional Expectations: You partner daily with the Growth team and negotiate directly with customer legal and procurement teams. You execute on outside counsel's legal direction and bring material terms to the VP of Growth for decision. Pricing, government contracts, regulatory flow-down clauses, and security classification requirements sit with other owners; you route them rather than resolve them.
Responsibilities
Commercial Negotiation
- Review, redline, and negotiate commercial customer agreements, including service agreements, Non-Disclosure Agreements (NDAs), and teaming agreements, against approved playbook positions.
- Decide non-material terms within guidelines and escalate material terms, such as price and duration, to the VP of Growth with a recommendation.
- Draft and negotiate amendments, extensions, and renewals of executed commercial agreements, keeping each change consistent with current playbook positions.
Playbook and Enablement
- Draft the commercial contract playbook, setting
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 those. I think I should use for main sections only. For sub-sections within Responsibilities, I could use or just include in list items. But the content has three distinct areas: Commercial Negotiation, Playbook and Enablement, Deal Support and Reporting. I could make them separate lists under Responsibilities with bold labels.
3. Requirements (h3) - The Skillset list.
4. Benefits (h3) - Compensation & Benefits list.
5. Pay (h3) - Salary Range.
6. Eligibility & Clearance (h3) - maybe combine with Requirements? But it's separate section in posting. Could be "Qualifications" or "Eligibility". The rules mention "Qualifications" as example heading. I'll use "Qualifications" for The Skillset and "Eligibility" for Eligibility & Clearance? But "Qualifications" and "Requirements" are similar. The rules list both "Requirements" and "Qualifications" as examples. I'll use "Requirements" for The Skillset and "Eligibility" for Eligibility & Clearance.
But the rules say "Prefer a few substantive sections over many thin ones." So maybe combine Eligibility into Requirements.
Also "Location-Specific Addendums" is specific: "You work independently your agreements cover across every location and lifecycle phase. No commercial contract playbook exists today, so you build the standard first and then hold every deal to it. Expect occasional travel for company events and select customer negotiations." This is about the role nature.
"What Success Looks Like In This Role" is specific success metrics.
"Cross-Functional Expectations" is about partnerships.
I think I'll create these sections:
- About the role (combining About The Role, Location-Specific Addendums, What Success Looks Like, Cross-Functional Expectations)
- Responsibilities (with three sub-areas as labeled lists)
- Requirements (The Skillset)
- Eligibility & Clearance (separate, as it's about work authorization and clearance)
- Benefits (Compensation & Benefits)
- Pay (Salary Range)
But the rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states both Benefits and Pay (salary range). So include both.
Now, for Responsibilities: I'll use Responsibilities
then for each sub-area, maybe a Commercial Negotiation
followed by - ... or just include the sub-area as part of list items? The content has bullet points under each. I'll do:
Responsibilities
Commercial Negotiation
- ...
Playbook and Enablement
- ...
Deal Support and Reporting
- ...
That seems clean.
For Requirements: The Skillset has bullet points. I'll use - .
For Eligibility & Clearance: two bullet points.
For Benefits: bullet points.
For Pay: just the salary range as paragraph.
Now, "About Nooks" is company description. Should I include? The rules say "Preserve ALL substantive information". It's about the company, not the role. But it's part of the posting. The rules don't say to exclude company description. However, the example headings don't include "About the company". The user said "reformat a job posting into clean, well-structured semantic HTML." I think I should include it as a section, maybe "About the company" but the rules only list specific headings. The rules say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It says "e.g." so not exhaustive. But also "include a section ONLY when the posting has real, specific content for it". The posting has "About Nooks" with specific content. I'll include it as "About the company" with . But the rules say "Do NOT repeat the job title as a heading (the page already shows it)". That's about job title. Company description is fine.
However, the user might expect only the role-related sections. But the instruction: "Preserve ALL substantive information". So I'll include About Nooks.
Let me structure:
About the company
Nooks is pioneering Classified-Infrastructure-as-a-Service (CIaaS) — designing, building, and operating Sensitive Compartmented Information Facilities (SCIFs) and other secured, classified environments for the defense and national security community. We work with the agencies, contractors, and mission-driven organizations that keep the nation safe, delivering the physical infrastructure that makes classified work possible. We're growing fast, operating across multiple markets, and building a company that takes both the mission and the business seriously.
About the role
You own the contract cycle for Nooks' commercial contracts: reviewing, redlining, and negotiating agreements with third parties from first draft through signature, including amendment and revisions as needed. Nooks needs these agreements to reach signature faster, without conceding terms under deadline pressure. You deliver both by drafting the contracts playbook with outside counsel and working every deal against it. You report to the VP of Growth, take legal direction from outside counsel, and work as a full-time individual contributor. At Nooks, we move fast. While you'll have clear ownership over your core responsibilities, startup life means priorities can shift. We're looking for a proactive problem-solver who is comfortable with ambiguity and ready to lean in wherever the team needs them most to drive us forward.
Location-Specific Addendums: You work independently your agreements cover across every location and lifecycle phase. No commercial contract playbook exists today, so you build the standard first and then hold every deal to it. Expect occasional travel for company events and select customer negotiations.
What Success Looks Like In This Role: An approved commercial contract playbook governs every customer negotiation, and the Growth team resolves routine terms without routing them to you. Commercial agreements reach signature on a predictable cycle time that you track and report, and deals no longer stall in contract review. Deviations from approved positions are rare, documented, and escalated before signature rather than discovered after. Every executed commercial agreement, amendment, and renewal sits in a complete record with key dates tracked. Leadership relies on you to tell them, before a deal closes, exactly which terms Nooks is accepting and why.
Cross-Functional Expectations: You partner daily with the Growth team and negotiate directly with customer legal and procurement teams. You execute on outside counsel's legal direction and bring material terms to the VP of Growth for decision. Pricing, government contracts, regulatory flow-down clauses, and security classification requirements sit with other owners; you route them rather than resolve them.
Responsibilities
Commercial Negotiation
- Review, redline, and negotiate commercial customer agreements, including service agreements, Non-Disclosure Agreements (NDAs), and teaming agreements, against approved playbook positions.
- Decide non-material terms within guidelines and escalate material terms, such as price and duration, to the VP of Growth with a recommendation.
- Draft and negotiate amendments, extensions, and renewals of executed commercial agreements, keeping each change consistent with current playbook positions.
Playbook and Enablement
- Draft the commercial contract playbook, setting
for main sections only. For sub-sections within Responsibilities, I could use or just include in list items. But the content has three distinct areas: Commercial Negotiation, Playbook and Enablement, Deal Support and Reporting. I could make them separate lists under Responsibilities with bold labels.
3. Requirements (h3) - The Skillset list.
4. Benefits (h3) - Compensation & Benefits list.
5. Pay (h3) - Salary Range.
6. Eligibility & Clearance (h3) - maybe combine with Requirements? But it's separate section in posting. Could be "Qualifications" or "Eligibility". The rules mention "Qualifications" as example heading. I'll use "Qualifications" for The Skillset and "Eligibility" for Eligibility & Clearance? But "Qualifications" and "Requirements" are similar. The rules list both "Requirements" and "Qualifications" as examples. I'll use "Requirements" for The Skillset and "Eligibility" for Eligibility & Clearance.
But the rules say "Prefer a few substantive sections over many thin ones." So maybe combine Eligibility into Requirements.
Also "Location-Specific Addendums" is specific: "You work independently your agreements cover across every location and lifecycle phase. No commercial contract playbook exists today, so you build the standard first and then hold every deal to it. Expect occasional travel for company events and select customer negotiations." This is about the role nature.
"What Success Looks Like In This Role" is specific success metrics.
"Cross-Functional Expectations" is about partnerships.
I think I'll create these sections:
- About the role (combining About The Role, Location-Specific Addendums, What Success Looks Like, Cross-Functional Expectations)
- Responsibilities (with three sub-areas as labeled lists)
- Requirements (The Skillset)
- Eligibility & Clearance (separate, as it's about work authorization and clearance)
- Benefits (Compensation & Benefits)
- Pay (Salary Range)
But the rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states both Benefits and Pay (salary range). So include both.
Now, for Responsibilities: I'll use Responsibilities
then for each sub-area, maybe a Commercial Negotiation
followed by - ... or just include the sub-area as part of list items? The content has bullet points under each. I'll do:
Responsibilities
Commercial Negotiation
- ...
Playbook and Enablement
- ...
Deal Support and Reporting
- ...
That seems clean.
For Requirements: The Skillset has bullet points. I'll use - .
For Eligibility & Clearance: two bullet points.
For Benefits: bullet points.
For Pay: just the salary range as paragraph.
Now, "About Nooks" is company description. Should I include? The rules say "Preserve ALL substantive information". It's about the company, not the role. But it's part of the posting. The rules don't say to exclude company description. However, the example headings don't include "About the company". The user said "reformat a job posting into clean, well-structured semantic HTML." I think I should include it as a section, maybe "About the company" but the rules only list specific headings. The rules say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It says "e.g." so not exhaustive. But also "include a section ONLY when the posting has real, specific content for it". The posting has "About Nooks" with specific content. I'll include it as "About the company" with . But the rules say "Do NOT repeat the job title as a heading (the page already shows it)". That's about job title. Company description is fine.
However, the user might expect only the role-related sections. But the instruction: "Preserve ALL substantive information". So I'll include About Nooks.
Let me structure:
About the company
Nooks is pioneering Classified-Infrastructure-as-a-Service (CIaaS) — designing, building, and operating Sensitive Compartmented Information Facilities (SCIFs) and other secured, classified environments for the defense and national security community. We work with the agencies, contractors, and mission-driven organizations that keep the nation safe, delivering the physical infrastructure that makes classified work possible. We're growing fast, operating across multiple markets, and building a company that takes both the mission and the business seriously.
About the role
You own the contract cycle for Nooks' commercial contracts: reviewing, redlining, and negotiating agreements with third parties from first draft through signature, including amendment and revisions as needed. Nooks needs these agreements to reach signature faster, without conceding terms under deadline pressure. You deliver both by drafting the contracts playbook with outside counsel and working every deal against it. You report to the VP of Growth, take legal direction from outside counsel, and work as a full-time individual contributor. At Nooks, we move fast. While you'll have clear ownership over your core responsibilities, startup life means priorities can shift. We're looking for a proactive problem-solver who is comfortable with ambiguity and ready to lean in wherever the team needs them most to drive us forward.
Location-Specific Addendums: You work independently your agreements cover across every location and lifecycle phase. No commercial contract playbook exists today, so you build the standard first and then hold every deal to it. Expect occasional travel for company events and select customer negotiations.
What Success Looks Like In This Role: An approved commercial contract playbook governs every customer negotiation, and the Growth team resolves routine terms without routing them to you. Commercial agreements reach signature on a predictable cycle time that you track and report, and deals no longer stall in contract review. Deviations from approved positions are rare, documented, and escalated before signature rather than discovered after. Every executed commercial agreement, amendment, and renewal sits in a complete record with key dates tracked. Leadership relies on you to tell them, before a deal closes, exactly which terms Nooks is accepting and why.
Cross-Functional Expectations: You partner daily with the Growth team and negotiate directly with customer legal and procurement teams. You execute on outside counsel's legal direction and bring material terms to the VP of Growth for decision. Pricing, government contracts, regulatory flow-down clauses, and security classification requirements sit with other owners; you route them rather than resolve them.
Responsibilities
Commercial Negotiation
- Review, redline, and negotiate commercial customer agreements, including service agreements, Non-Disclosure Agreements (NDAs), and teaming agreements, against approved playbook positions.
- Decide non-material terms within guidelines and escalate material terms, such as price and duration, to the VP of Growth with a recommendation.
- Draft and negotiate amendments, extensions, and renewals of executed commercial agreements, keeping each change consistent with current playbook positions.
Playbook and Enablement
- Draft the commercial contract playbook, setting
Responsibilities
Commercial Negotiation
- ...
Playbook and Enablement
- ...
Deal Support and Reporting
- ...
- .
For Eligibility & Clearance: two bullet points.
For Benefits: bullet points.
For Pay: just the salary range as paragraph.
Now, "About Nooks" is company description. Should I include? The rules say "Preserve ALL substantive information". It's about the company, not the role. But it's part of the posting. The rules don't say to exclude company description. However, the example headings don't include "About the company". The user said "reformat a job posting into clean, well-structured semantic HTML." I think I should include it as a section, maybe "About the company" but the rules only list specific headings. The rules say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It says "e.g." so not exhaustive. But also "include a section ONLY when the posting has real, specific content for it". The posting has "About Nooks" with specific content. I'll include it as "About the company" with
. But the rules say "Do NOT repeat the job title as a heading (the page already shows it)". That's about job title. Company description is fine. However, the user might expect only the role-related sections. But the instruction: "Preserve ALL substantive information". So I'll include About Nooks. Let me structure:
About the company
Nooks is pioneering Classified-Infrastructure-as-a-Service (CIaaS) — designing, building, and operating Sensitive Compartmented Information Facilities (SCIFs) and other secured, classified environments for the defense and national security community. We work with the agencies, contractors, and mission-driven organizations that keep the nation safe, delivering the physical infrastructure that makes classified work possible. We're growing fast, operating across multiple markets, and building a company that takes both the mission and the business seriously.
About the role
You own the contract cycle for Nooks' commercial contracts: reviewing, redlining, and negotiating agreements with third parties from first draft through signature, including amendment and revisions as needed. Nooks needs these agreements to reach signature faster, without conceding terms under deadline pressure. You deliver both by drafting the contracts playbook with outside counsel and working every deal against it. You report to the VP of Growth, take legal direction from outside counsel, and work as a full-time individual contributor. At Nooks, we move fast. While you'll have clear ownership over your core responsibilities, startup life means priorities can shift. We're looking for a proactive problem-solver who is comfortable with ambiguity and ready to lean in wherever the team needs them most to drive us forward.
Location-Specific Addendums: You work independently your agreements cover across every location and lifecycle phase. No commercial contract playbook exists today, so you build the standard first and then hold every deal to it. Expect occasional travel for company events and select customer negotiations.
What Success Looks Like In This Role: An approved commercial contract playbook governs every customer negotiation, and the Growth team resolves routine terms without routing them to you. Commercial agreements reach signature on a predictable cycle time that you track and report, and deals no longer stall in contract review. Deviations from approved positions are rare, documented, and escalated before signature rather than discovered after. Every executed commercial agreement, amendment, and renewal sits in a complete record with key dates tracked. Leadership relies on you to tell them, before a deal closes, exactly which terms Nooks is accepting and why.
Cross-Functional Expectations: You partner daily with the Growth team and negotiate directly with customer legal and procurement teams. You execute on outside counsel's legal direction and bring material terms to the VP of Growth for decision. Pricing, government contracts, regulatory flow-down clauses, and security classification requirements sit with other owners; you route them rather than resolve them.
Responsibilities
Commercial Negotiation
- Review, redline, and negotiate commercial customer agreements, including service agreements, Non-Disclosure Agreements (NDAs), and teaming agreements, against approved playbook positions.
- Decide non-material terms within guidelines and escalate material terms, such as price and duration, to the VP of Growth with a recommendation.
- Draft and negotiate amendments, extensions, and renewals of executed commercial agreements, keeping each change consistent with current playbook positions.
Playbook and Enablement
- Draft the commercial contract playbook, setting