Technical Subject Matter Expert (SME) – (RFP, Proposal Development, Government Contracting)

Here's a thinking process: 1. **Analyze User Request:** - **Goal:** Reformat a job posting into clean, well-structured semantic HTML. - **Rules:** - Use `

` for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). - Use `

• ` for lists of duties/requirements/benefits. - Use `

  ` for prose. - Do NOT repeat the job title as a heading (already shown on page). - Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short `

  ` or drop it. - Preserve ALL substantive information; do NOT invent or summarize away detail. - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. - IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. - Prefer a few substantive sections over many thin ones. - Output ONLY the HTML fragment — no `/`, no markdown code fences. 2. **Analyze the Job Posting Text:** Let me carefully read and extract relevant sections, removing boilerplate. The posting text: Position Summary Technical SME is a senior-level technical and strategic advisor across the full business development lifecycle — from capture and solutioning through proposal submission — for large, complex, and/or high-value federal, state, and local government IT pursuits. This individual owns the technical solution strategy for major proposals, leads and mentors’ proposal and technical writers, and serves as a trusted technical expert for proposal development efforts. This role is distinguished from a standard SME by its scope (typically supporting the most strategically significant pursuits), its influence on win strategy and pricing-to-win, and its mentorship/leadership responsibility over other technical contributors. Incumbent will regularly travel for customer engagements, industry days, orals presentations, and capture strategy sessions. Must comply with, and help enforce, all company and customer data security, data handling, and AI usage policies, including those specific to government/classified environments. Key Responsibilities Serve as the senior-most technical expertise for high-value, strategically significant government IT pursuits, owning the end-to-end technical solution strategy from capture through submissionLead technical solutioning sessions and black hat/competitive assessments to shape differentiated, winning solutions ahead of RFP releaseAdvise Capture Managers and Business Development leadership on technical win strategy, teaming/partnering decisions, and make/buy assessments for proposed solutionsOwn and drive the technical volume(s) for major proposals, ensuring alignment with Sections L/M, PWS/SOW/SOO, and agency evaluation criteriaLead and mentor teams of technical writers and proposal contributors across multiple concurrent pursuits, ensuring consistency, quality, and compliance of technical contentServe as writer and senior reviewer for Pink/Red/Gold Team reviews, providing authoritative sign-off on technical accuracy and competitivenessPartner directly with pricing/cost leads to align technical solution decisions with Basis of Estimate (BOE), price-to-win strategy, and cost realismRepresent the organization in customer engagements, industry days, oral presentations, and executive-level discussions on technical solutionsOwn and evolve the organization's technical proposal content library, win themes, and reusable architectures across service lines and recompete pipelinesLead post-submission technical strategy: responses to Evaluation Notices (ENs), Clarification Requests, Discussions, and Best and Final Offer (BAFO) submissionsMaintain command of emerging technology trends, agency modernization priorities, and competitive intelligence to shape long-range capture and technical strategy Required Qualifications Bachelor’s degree in computer science, Information Technology, Engineering, or related field; Master's degree preferred12+ years of progressive technical experience in IT (cloud, cybersecurity, software/systems engineering, network, or data/AI), including 8+ years directly supporting government contract pursuits12+ years of progressive technical experience in IT (cloud, cybersecurity, software/systems engineering to include DevSecOps, network, or data/AI), including 8+ years directly supporting government contract pursuitsDemonstrated track record leading technical volumes on large-scale government proposals, with a history of contract winsDeep working knowledge of federal acquisition processes (FAR/DFARS), solicitation structures, and compliance-driven technical writing at a senior/authoritative levelProven leadership experience managing or mentoring technical SME teams across multiple concurrent proposal effortsExecutive-level written and verbal communication skills, with experience presenting to C-suite, customers, and evaluation boards Preferred Qualifications Established relationships and direct experience with target agencies (DoD, DHS, VA, civilian agencies) and their technical/compliance frameworksAdvanced understanding of data security, data integrity, and responsible AI governance — including how AI usage requirements differ by customer (particularly government customers) and the imperative to confirm rather than assume permitted useShipley or equivalent advanced proposal methodology certificationSenior technical certifications (e.g., AWS/Azure/GCP Professional/Architect level, CISSP, PMP, ITIL, TOGAF)Extensive experience with GWAC/IDIQ vehicles (GSA MAS, OASIS+, SEWP, Alliant) and large Task Order competitionsHistory of building or leading Centers of Excellence, technical practice areas, or solution architecture functions Key Competencies Recognized technical authority and executive presenceStrategic thinking across capture, solutioning, and pricingMastery of federal compliance and acquisition requirementsLeadership, mentorship, and team developmentSound governance over data security, data integrity, and AI tool usage — setting the standard for the organizationAbility to influence senior stakeholders and represent the organization externallyExceptional, evaluator-focused technical writing and review skills Salary: $150,000 - $160,000 Physical Demands: While performing the duties of this job, the employee is regularly required to sit. The employee frequently is required to walk; use hands to finger, handle or feel; reach with hands and arms; and talk or hear. The employee is occasionally required to stand. The employee may lift or move objects up to 5 pounds. Specific vision abilities required by this job include close vision, distance vision, color vision, and ability to adjust focus. MicroHealth will recruit, hire, train, and promote persons in all job titles, and ensure that all other personnel actions are administered without regard to race, color, religion, sex, sexual orientation, gender identity, genetic information, national origin, disability, or status as a protected veteran and ensure that all employment decisions are based only on valid job requirements. All qualified applicants will receive consideration for employment without regard to race, color, religion, sex, sexual orientation, gender identity, national origin, disability, or status as a protected veteran. If you need a reasonable accommodation due to a disability for any part of the employment process, please send an e-mail to hr@microhealthllc.com with your request and contact information. Powered by JazzHR 0cIoPe9hFe Now, I need to parse this into structured HTML sections as per rules. Let's identify the substantive sections and content: - The posting starts with "Position Summary" and a paragraph describing the role. This could be "About the role" or just a lead paragraph. The rules say use `

  ` for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It also says "Do NOT repeat the job title as a heading (the page already shows it)". I'll assume the job title isn't repeated here, but there's a "Position Summary" line. I'll likely use the first paragraph as an introductory `

  ` or maybe under "About the role". But the rules say include a section ONLY when the posting has real, specific content for it. "About the role" seems appropriate for the opening summary. - "Key Responsibilities" section: There's a big block of responsibilities without bullet points in the original, but I should format them as `

  • ` lists. I need to split the long text into logical bullet points. The rules say "Use
    • for any list of duties/requirements/benefits". I'll parse the responsibilities into separate li items. - "Required Qualifications": There are two identical bullet points about 12+ years experience. I'll keep them as separate li or combine noting the duplication? The rules say "Preserve ALL substantive information; do NOT invent or summarize away detail." So I should include both, but maybe note they're similar? I'll just list them as separate li items as they appear, but maybe combine since they're essentially the same. I'll read carefully: "12+ years of progressive technical experience in IT (cloud, cybersecurity, software/systems engineering, network, or data/AI), including 8+ years directly supporting government contract pursuits" appears twice, slightly varied second one includes "DevSecOps". I'll treat them as two bullet points under Qualifications, or maybe put under a "Qualifications" section as `
      • `. - "Preferred Qualifications": Another block of bullet points. - "Key Competencies": Another block. - "Salary: $150,000 - $160,000" - This is Pay. Rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "$150,000 - $160,000", so I can include a Pay section with that exact text. - "Physical Demands:" section with details. This could be part of Requirements or a separate section, but rules list specific headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Physical Demands might fit under Requirements or Skills, but I need to see. The rules say include a section ONLY when the posting has real, specific content for it. Physical Demands is specific content. I could fold it into a `

        ` under Requirements or have a separate section. But the allowed headings are listed. I think I can use `

        ` for "Requirements" and include physical demands there, or maybe create a "Requirements" section that includes both qualifications and physical demands. However, the rules say "Prefer a few substantive sections over many thin ones." I'll likely group relevant stuff. - At the end: "MicroHealth will recruit, hire, train, and promote persons in all job titles..." This is EEO/boilerplate. Rule: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So I remove this entire block. - "Powered by JazzHR 0cIoPe9hFe" - Also boilerplate, remove. - Application instructions like "If you need a reasonable accommodation..." - remove as application instructions. - The posting doesn't explicitly have "Benefits" or "Schedule" sections with content. Rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." There's no benefits or schedule text, so I should NOT create those sections. - The rules say section headings examples: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". I need to decide which to include. I'll include: About the role, Responsibilities, Qualifications (maybe split Required and Preferred), Key Competencies, and Pay. I'll avoid creating thin sections. Let me re-read the rules carefully: "use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This gives allowed heading names. "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and