Subject Matter Expert III
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which headings to use based on content. We have "Who We Are" maybe as About the role? Could be "About the Company" but they said use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use "About the role" for the overview (Who We Are + role description). Then Responsibilities (list). Then maybe "Qualifications" for What You Need (education, certifications, clearance). Could also have "Skills" but not needed. Then Benefits. We must not repeat job title as heading. The job title is "Subject Matter Expert (SME) III". We'll not put that as heading. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate etc. We need to output only HTML fragment. Let's extract content: Who We Are: Lawelawe is a Native Hawaiian Owned Small Disadvantaged Business (NHO SDB) that specializes in providing a range of services to federal government clients, including program management, digital solutions, human capital and training. Lawelawe leverages our NHO status to secure federal contracts that not only drive business success but also support our overall mission to uplift economically disadvantaged Native Hawaiian families and preserve the Native Hawaiian heritage. You Are The Subject Matter Expert (SME) III will play a critical role in providing expertise in the development and execution of business and financial solutions, shaping the organization's strategic vision, and serving as a trusted advisor to senior leadership. Involves guiding the organization in adhering to government and industry best practices and standards, with a focus on business processes, service management, portfolio management, capital planning, and investment control. Responsibilities list: - Provide expert guidance in the development and execution of business and financial solutions that align with government and industry standards. - Serve as the organization's expert on topics related to business processes, service management, portfolio management, capital planning, and investment control. - Advise senior leadership on governance frameworks and decision-making models. - Offer insights and expertise on the business and financial aspects of the organization, helping shape its strategic vision, operational objectives, and tactical goals. - Assume technical/management leadership roles on major projects or assignments, setting goals and plans to meet project objectives. - Demonstrate deep domain knowledge and technical expertise, directing and controlling project activities, including financial management, staffing, and methods. - Interface with clients, negotiate project terms, and engage with senior management to ensure project success. - Provide expert technical guidance to senior leadership, supporting the realization of the organization's strategic vision and operational goals. - Perform the most complex independent tasks and decision-making, potentially supervising others in the process. - Possess expert knowledge of technical domain data requirements, system architecture, sensor/data sources, and industry standards. - Lead technical/management functions for the organization, potentially across multiple physical and virtual sites. - Manage and direct other SME/security staff, if necessary. - Develop and implement quality control methodologies to ensure compliance with quality assurance standards, guidelines, and procedures. Specific Duties and Tasks list: - Collaborate with the Chief Information Officer (CIO) and Division leads to develop project scope, deliverables, resources, work plans, budgets, and timelines for initiatives. - Work with Division and Branch leads to identify risks and opportunities across departments. - Analyze, evaluate, and mitigate risks, providing program reports to managers and stakeholders. - Develop and manage strategies, taking accountability for departmental goals and objectives. - Assist in departmental development by identifying risks and opportunities and coordinating with knowledge experts. The Team description: Lawelawe Defense Inc ("LDI") is an SBA Certified 8(a) Native Hawaiian Owned (NHO) SDB Lawelawe Defense offers an outstanding record of delivery on various projects encompassing: Program and Portfolio Management; Systems Engineering and Architecture; Network Engineering and Operations; Data Center Optimization and Operations; Desktop/Server and Application Virtualization. What You Need list: - Bachelor's degree or equivalent education. - Certificates such as PMI, PMP, or equivalent. - ITIL 4 Foundation certification. - Public Trust Clearance - Must be a US citizen Benefits list: - A competitive compensation package - Comprehensive health and wellness benefits, including medical, dental, and vision plans - Access to company-provided retirement savings options with matching contributions - Opportunities for professional growth and continued learning - Additional perks such as discounts on various services and products - Remote work environment Salary line: "Salary Dependent on Experience (DOE). Compensation will be based on qualifications, relevant experience, and internal equity." Since it's vague, we should not create Pay section. However we could possibly include it as a short paragraph under About the role? But rule: do not create Pay/Schedule/Benefits sections unless posting actually states them. It does state something about salary but it's placeholder. The rule says 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. The phrase "Salary Dependent on Experience (DOE)" is essentially placeholder. So we should not create a Pay section. We could maybe include that sentence in a paragraph under About the role or elsewhere? But the instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep that sentence somewhere. If we don't create a Pay section, we could embed it in a
within another section, maybe under About the role or under Benefits? But Benefits already separate. Could add a
after Benefits about compensation. However that might be considered creating a Pay section implicitly. Better to include a short paragraph under About the role or maybe a separate
not under a heading? The instruction says output only HTML fragment; we can have
elements not under headings. It didn't forbid that. So we can keep the salary sentence as a
after Benefits or before. But we must not create a Pay heading. So we can just include a
with that sentence. Similarly, we should not create Schedule heading. Now structure:
About the role
Who We Are ... You Are The Subject Matter Expert (SME) III will play a critical role ...
Then Responsibilities:Responsibilities
- ... each
without heading. Let's craft About the role paragraph: Combine Who We Are description, role overview, and The Team description. Who We Are: "Lawelawe is a Native Hawaiian Owned Small Disadvantaged Business (NHO SDB) that specializes in providing a range of services to federal government clients, including program management, digital solutions, human capital and training. Lawelawe leverages our NHO status to secure federal contracts that not only drive business success but also support our overall mission to uplift economically disadvantaged Native Hawaiian families and preserve the Native Hawaiian heritage." Role overview: "You Are The Subject Matter Expert (SME) III will play a critical role in providing expertise in the development and execution of business and financial solutions, shaping the organization's strategic vision, and serving as a trusted advisor to senior leadership. Involves guiding the organization in adhering to government and industry best practices and standards, with a focus on business processes, service management, portfolio management, capital planning, and investment control." The Team: "Lawelawe Defense Inc ("LDI") is an SBA Certified 8(a) Native Hawaiian Owned (NHO) SDB Lawelawe Defense offers an outstanding record of delivery on various projects encompassing: Program and Portfolio Management; Systems Engineering and Architecture; Network Engineering and Operations; Data Center Optimization and Operations; Desktop/Server and Application Virtualization." We can combine into a few sentences. Now Responsibilities: combine the two lists. We'll produce
- items for each bullet from both lists. Let's list all bullets: From Responsibilities: 1. Provide expert guidance in the development and execution of business and financial solutions that align with government and industry standards. 2. Serve as the organization's expert on topics related to business processes, service management, portfolio management, capital planning, and investment control. 3. Advise senior leadership on governance frameworks and decision-making models. 4. Offer insights and expertise on the business and financial aspects of the organization, helping shape its strategic vision, operational objectives, and tactical goals. 5. Assume technical/management leadership roles on major projects or assignments, setting goals and plans to meet project objectives. 6. Demonstrate deep domain knowledge and technical expertise, directing and controlling project activities, including financial management, staffing, and methods. 7. Interface with clients, negotiate project terms, and engage with senior management to ensure project success. 8. Provide expert technical guidance to senior leadership, supporting the realization of the organization's strategic vision and operational goals. 9. Perform the most complex independent tasks and decision-making, potentially supervising others in the process. 10. Possess expert knowledge of technical domain data requirements, system architecture, sensor/data sources, and industry standards. 11. Lead technical/management functions for the organization, potentially across multiple physical and virtual sites. 12. Manage and direct other SME/security staff, if necessary. 13. Develop and implement quality control