Contracts & Compliance Senior Manager
BDO USA · Houston, TX · 1 mo ago
HybridAccountingFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real content. The posting includes job duties (responsibilities), education/qualifications, knowledge/skills/abilities, maybe about us (but that's boilerplate? It's about the company; we should remove EEO/legal boilerplate but "About us" might be considered not required? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About us" is not exactly EEO but could be considered company description; not sure if we should keep. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The "About us" is substantive about company but maybe not required for job posting? Usually we keep it as a section maybe "About the company". However the allowed headings list includes only specific ones: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list About the company. So we should not create a heading not in list. So we should incorporate "About us" maybe into Responsibilities? No. Better to omit it because not in allowed headings and not required. The instruction: Use
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real content. The posting includes job duties (responsibilities), education/qualifications, knowledge/skills/abilities, maybe about us (but that's boilerplate? It's about the company; we should remove EEO/legal boilerplate but "About us" might be considered not required? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About us" is not exactly EEO but could be considered company description; not sure if we should keep. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The "About us" is substantive about company but maybe not required for job posting? Usually we keep it as a section maybe "About the company". However the allowed headings list includes only specific ones: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list About the company. So we should not create a heading not in list. So we should incorporate "About us" maybe into Responsibilities? No. Better to omit it because not in allowed headings and not required. The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, but likely we should stick to those. We'll include sections that have content: Responsibilities (job duties), Requirements (education, experience, licenses), Qualifications (maybe same as Requirements?), Skills (knowledge, skills & abilities). Benefits: there is mention of ESOP and Total Rewards benefits in About us section. That is benefits info. So we can include Benefits section with that content. Pay and Schedule: not mentioned, so omit.
We must not repeat job title as heading. No Job ID.
We need to preserve all substantive information: job duties list, education/qualifications, knowledge/skills/abilities, benefits (ESOP, Total Rewards). Also maybe "About us" not needed.
We need to format duties as - . For responsibilities we have many paragraphs; we can break into logical groups: Contract Vehicles, Teaming Agreements, Proposal Support, Project Compliance, Compliance Maintenance, Additional Responsibilities, Supervisory Responsibilities. Each as
- . Could also combine but better to keep.
For Requirements: Education: Bachelor’s degree required, Advanced degree preferred. Experience: 7+ years relevant contracts, grants and compliance experience; 3+ years direct administration of GSA MAS or GWAC/IDIQ; Demonstrated experience owning SAM.gov entity registration; 3+ years supporting federal, state and local gov proposals; Experience applying knowledge of FAR, DFARS etc; Working knowledge of FAR Part 8.4 and 16.5; Experience managing federal registrations across multiple affiliated legal entities preferred; Prior experience within professional services firm preferred. License/Certifications: NCMA CFCM or CPCM preferred. Software: Proficiency in Microsoft Office Suite (Excel, PowerPoint, Word) and Copilot required; Working proficiency with federal contracting systems (SAM.gov, FAS SRP, eSRS, FSRS, GSA eOffer/eMod, CPARS) required; Prior experience utilizing online documentation/proposal software preferred; Knowledge of CRM or database systems preferred. Language: N/A (we should not include N/A). Other Knowledge, Skills & Abilities: list.
We need to separate Requirements vs Qualifications vs Skills. The posting has "Education: Qualifications, Knowledge, Skills and Abilities:" then sections Education, Experience, License/Certifications, Software, Language, Other Knowledge, Skills & Abilities. So we could map: Requirements = Education + Experience + License/Certifications + Software + Language? Qualifications maybe same as Requirements? Skills = Other Knowledge, Skills & Abilities. To avoid duplication, we could make one Requirements section covering education, experience, licenses, software. And Skills section for other KSAs. Qualifications maybe not needed. But we need to follow instruction: include a section ONLY when posting has real specific content for it. We have content for Responsibilities, Requirements (education/experience/licenses/software), Skills (other KSAs), Benefits (ESOP, Total Rewards). We'll not include Qualifications if it duplicates.
We must not include placeholder text like "N/A". So omit Language section.
Now craft HTML.
Structure:
Responsibilities
- Contract Vehicles: ...
...
We need to preserve all details; we can split long sentences but keep meaning.
Let's extract each bullet from the "Job Duties:" section after the initial paragraph.
The text after "Job Duties:" includes a paragraph then "Job Duties:" again then list headings: Contract Vehicles, Teaming Agreements, Proposal Support, Project Compliance, Compliance Maintenance, Additional Responsibilities, Supervisory Responsibilities.
We'll create li for each heading with its content.
We need to ensure we don't lose any details.
Let's copy content:
Contract Vehicles:
- Evaluates and recommends contract and grant vehicles, including both competitive and non-competitive opportunities, based on growth strategy, risk and compliance implications
- Prepares, and coordinates required contractual and grant documentation and organizational information to support contract and grant vehicle submissions
- Monitors business compliance with established ongoing reporting, renewal, and administrative requirements of active contract and grant vehicles
Teaming Agreements:
- Coordinates preparation, routing, and execution of non-disclosure agreements (NDAs), teaming agreements, and subcontracts with prospective and existing partners in coordination with Legal
- Provides business input to capture and proposal teams on strategic teaming approaches and terms
- Supports implementation of contractual requirements through monitoring, identifying whether agreements align with contract and grant requirements and internal policies
Proposal Support:
- Reviews RFPs, RFIs, and RFQs to identify business compliance requirements and potential contractual or grant issues, and coordinates with OGC for legal review
- Coordinates and supports development of business responses to contractual sections of proposals, including representations and certifications, terms and conditions, and exception summaries
- Analyzes key clauses, including FAR, DFARS, and GSA terms, and provide compliance assessments to internal stakeholders
- Serves as liaison between internal teams and government contracting officers during the proposal phase
- Partners with OGC and leadership teams to provide business input on terms and support the development of thoughtful and strategic responses to terms and conditions
Project Compliance:
- Serves as the primary point of contact for government customers (and strategic advisor on more complex matters) on all contract-related matters throughout the contract lifecycle
- May lead contract kick-off meetings and ensure the operational team understands compliance obligations
- Coordinates operational administration of contract modifications, performance monitoring, reporting requirements, and final closeout
- Ensures deliverables and established contractual obligations are tracked and met in a timely, compliant manner
Compliance Maintenance:
- Develops and maintains internal policies and procedures to support business compliance with established FAR, DFARS, GSA requirements, and other applicable federal, state and local laws
- Conducts regular internal audits and compliance reviews to identify and coordinate remediation of gaps in business processes or procedures
- Serves as a business facing resource for established federal, state and local compliance requirements, providing training and guidance to internal teams in coordination with OGC, as needed
- Monitors regulatory updates for potential operational impact, coordinates with OGC, and supports updates to internal practices to maintain business compliance with established requirements
Additional Responsibilities:
- Builds strong working relationships across OGC, compliance, finance, P&C, capture, and delivery teams to support business operations and compliance
- Develops and reports on key contracts and compliance metrics for senior leadership, identifying trends, risks, and improvement opportunities
- Performs additional specialized duties such as GSA contract oversight, SAM.gov registration management, and FOCI program oversight, depending on team and company needs
- Leads process improvement initiatives to enhance efficiency, reduce risk, and support scalability
- Participates in strategy development for new market entry, contract and grant expansion, and partnership models from a compliance perspective
- Supports pre- and post-award contract and grant strategy and risk mitigation planning
- Represents the Contracts and Compliance function in internal and external meetings, audits, and reviews
- Supports due diligence efforts for potential acquisitions or partner evaluations
- Performs other duties as assigned to support corporate goals and the growth of the Contracts & Compliance function
Supervisory Responsibilities:
- Provides day-to-day direction, coaching, and oversight to staff involved in contracts, grants, compliance, proposal support, or related operational activities
- May supervise, mentor, or serve as career advisor to team members, depending on business need
Now Requirements section: Education, Experience, License/Certifications, Software.
We'll combine into - each.
Education:
- Bachelor’s degree, required
- Advanced degree, preferred
Experience:
- Seven (7) years or more of relevant contracts, grants and compliance experience with Federal, state and local governments, required
- Three (3) years or more of direct administration of a GSA Multiple Award Schedule contract or a federal GWAC/IDIQ vehicle (e.g., OASIS+, Alliant, SEWP), including modifications, sales reporting, and option or renewal actions, required
- Demonstrated experience owning a SAM.gov entity registration, including annual renewal and completion of FAR 52.204-8 annual representations and certifications, required
- Three (3) years or more supporting federal, state and local government proposals, required
- Experience applying knowledge of Federal Acquisitions Regulations, Defense Acquisitions Regulations and other applicable contracting rules, requirements and procedures, required
- Working knowledge of FAR Part 8.4 (Federal Supply Schedules) and FAR Part 16.5 (task and delivery order contracts), required
- Experience managing federal registrations and certifications across multiple affiliated legal entities with distinct UEIs, CAGE codes, and reporting obligations, preferred
- Prior experience working within a professional services firm, preferred
License/Certifications:
- NCMA Certified Federal Contracts Manager (CFCM) or Certified Professional Contracts Manager (CPCM), preferred
Software:
- Proficiency in the use of Microsoft Office Suites, specifically Excel, PowerPoint and Word, and Copilot, required
- Working proficiency with federal contracting systems, including SAM.gov, the FAS Sales Reporting Portal (SRP), eSRS and FSRS, GSA eOffer and eMod, and CPARS, required
- Prior experience utilizing online documentation / proposal software, preferred
- Knowledge of CRM systems or database systems, preferred
Language: N/A (omit)
Skills section: Other Knowledge, Skills & Abilities list.
Let's extract:
- Solid understanding of Federal Government proposal processes and requirements as well as procurement processes and policies
- Solid understanding of state and local contract and grant proposal processes and requirements as well as procurement processes and policies
- Demonstrated ability to independently interpret GSA MAS and OASIS+ contract terms, identify scope and pricing compliance issues, and correspond directly with a Contracting Officer or Contract Specialist
- Excellent verbal and written communication skills as well as interpersonal skills
- Ability to interact effectively with people at all organizational levels of the firm
- Ability to work independently within a team environment and with a customer service focus
- Superior organizational skills required with ability to multi-task in a fast-paced, deadline-driven environment
- Detail oriented with in-depth knowledge and application of English grammar and ability to proofread all written materials including proposals, pitches, presentations, etc.
- Demonstrated ability to thoughtfully and positively influence, lead, and manage change
Now Benefits section: from About us: ESOP, Total Rewards benefits.
We need to capture: "We are proud to be an ESOP company, offering participants a stake in the firm’s success through beneficial ownership and a unique opportunity to enhance their financial well-being. As a qualified retirement plan, the ESOP is a meaningful addition to our comprehensive compensation and Total Rewards
- . For responsibilities we have many paragraphs; we can break into logical groups: Contract Vehicles, Teaming Agreements, Proposal Support, Project Compliance, Compliance Maintenance, Additional Responsibilities, Supervisory Responsibilities. Each as
- . Could also combine but better to keep.
For Requirements: Education: Bachelor’s degree required, Advanced degree preferred. Experience: 7+ years relevant contracts, grants and compliance experience; 3+ years direct administration of GSA MAS or GWAC/IDIQ; Demonstrated experience owning SAM.gov entity registration; 3+ years supporting federal, state and local gov proposals; Experience applying knowledge of FAR, DFARS etc; Working knowledge of FAR Part 8.4 and 16.5; Experience managing federal registrations across multiple affiliated legal entities preferred; Prior experience within professional services firm preferred. License/Certifications: NCMA CFCM or CPCM preferred. Software: Proficiency in Microsoft Office Suite (Excel, PowerPoint, Word) and Copilot required; Working proficiency with federal contracting systems (SAM.gov, FAS SRP, eSRS, FSRS, GSA eOffer/eMod, CPARS) required; Prior experience utilizing online documentation/proposal software preferred; Knowledge of CRM or database systems preferred. Language: N/A (we should not include N/A). Other Knowledge, Skills & Abilities: list.
We need to separate Requirements vs Qualifications vs Skills. The posting has "Education: Qualifications, Knowledge, Skills and Abilities:" then sections Education, Experience, License/Certifications, Software, Language, Other Knowledge, Skills & Abilities. So we could map: Requirements = Education + Experience + License/Certifications + Software + Language? Qualifications maybe same as Requirements? Skills = Other Knowledge, Skills & Abilities. To avoid duplication, we could make one Requirements section covering education, experience, licenses, software. And Skills section for other KSAs. Qualifications maybe not needed. But we need to follow instruction: include a section ONLY when posting has real specific content for it. We have content for Responsibilities, Requirements (education/experience/licenses/software), Skills (other KSAs), Benefits (ESOP, Total Rewards). We'll not include Qualifications if it duplicates.
We must not include placeholder text like "N/A". So omit Language section.
Now craft HTML.
Structure:
Responsibilities
- Contract Vehicles: ... ...
- each. Education: - Bachelor’s degree, required - Advanced degree, preferred Experience: - Seven (7) years or more of relevant contracts, grants and compliance experience with Federal, state and local governments, required - Three (3) years or more of direct administration of a GSA Multiple Award Schedule contract or a federal GWAC/IDIQ vehicle (e.g., OASIS+, Alliant, SEWP), including modifications, sales reporting, and option or renewal actions, required - Demonstrated experience owning a SAM.gov entity registration, including annual renewal and completion of FAR 52.204-8 annual representations and certifications, required - Three (3) years or more supporting federal, state and local government proposals, required - Experience applying knowledge of Federal Acquisitions Regulations, Defense Acquisitions Regulations and other applicable contracting rules, requirements and procedures, required - Working knowledge of FAR Part 8.4 (Federal Supply Schedules) and FAR Part 16.5 (task and delivery order contracts), required - Experience managing federal registrations and certifications across multiple affiliated legal entities with distinct UEIs, CAGE codes, and reporting obligations, preferred - Prior experience working within a professional services firm, preferred License/Certifications: - NCMA Certified Federal Contracts Manager (CFCM) or Certified Professional Contracts Manager (CPCM), preferred Software: - Proficiency in the use of Microsoft Office Suites, specifically Excel, PowerPoint and Word, and Copilot, required - Working proficiency with federal contracting systems, including SAM.gov, the FAS Sales Reporting Portal (SRP), eSRS and FSRS, GSA eOffer and eMod, and CPARS, required - Prior experience utilizing online documentation / proposal software, preferred - Knowledge of CRM systems or database systems, preferred Language: N/A (omit) Skills section: Other Knowledge, Skills & Abilities list. Let's extract: - Solid understanding of Federal Government proposal processes and requirements as well as procurement processes and policies - Solid understanding of state and local contract and grant proposal processes and requirements as well as procurement processes and policies - Demonstrated ability to independently interpret GSA MAS and OASIS+ contract terms, identify scope and pricing compliance issues, and correspond directly with a Contracting Officer or Contract Specialist - Excellent verbal and written communication skills as well as interpersonal skills - Ability to interact effectively with people at all organizational levels of the firm - Ability to work independently within a team environment and with a customer service focus - Superior organizational skills required with ability to multi-task in a fast-paced, deadline-driven environment - Detail oriented with in-depth knowledge and application of English grammar and ability to proofread all written materials including proposals, pitches, presentations, etc. - Demonstrated ability to thoughtfully and positively influence, lead, and manage change Now Benefits section: from About us: ESOP, Total Rewards benefits. We need to capture: "We are proud to be an ESOP company, offering participants a stake in the firm’s success through beneficial ownership and a unique opportunity to enhance their financial well-being. As a qualified retirement plan, the ESOP is a meaningful addition to our comprehensive compensation and Total Rewards
- . Could also combine but better to keep.
For Requirements: Education: Bachelor’s degree required, Advanced degree preferred. Experience: 7+ years relevant contracts, grants and compliance experience; 3+ years direct administration of GSA MAS or GWAC/IDIQ; Demonstrated experience owning SAM.gov entity registration; 3+ years supporting federal, state and local gov proposals; Experience applying knowledge of FAR, DFARS etc; Working knowledge of FAR Part 8.4 and 16.5; Experience managing federal registrations across multiple affiliated legal entities preferred; Prior experience within professional services firm preferred. License/Certifications: NCMA CFCM or CPCM preferred. Software: Proficiency in Microsoft Office Suite (Excel, PowerPoint, Word) and Copilot required; Working proficiency with federal contracting systems (SAM.gov, FAS SRP, eSRS, FSRS, GSA eOffer/eMod, CPARS) required; Prior experience utilizing online documentation/proposal software preferred; Knowledge of CRM or database systems preferred. Language: N/A (we should not include N/A). Other Knowledge, Skills & Abilities: list.
We need to separate Requirements vs Qualifications vs Skills. The posting has "Education: Qualifications, Knowledge, Skills and Abilities:" then sections Education, Experience, License/Certifications, Software, Language, Other Knowledge, Skills & Abilities. So we could map: Requirements = Education + Experience + License/Certifications + Software + Language? Qualifications maybe same as Requirements? Skills = Other Knowledge, Skills & Abilities. To avoid duplication, we could make one Requirements section covering education, experience, licenses, software. And Skills section for other KSAs. Qualifications maybe not needed. But we need to follow instruction: include a section ONLY when posting has real specific content for it. We have content for Responsibilities, Requirements (education/experience/licenses/software), Skills (other KSAs), Benefits (ESOP, Total Rewards). We'll not include Qualifications if it duplicates.
We must not include placeholder text like "N/A". So omit Language section.
Now craft HTML.
Structure: