CFO (Chief Financial Officer)
Kanbrick · Springfield, MO · 3 wk ago
On-siteOTHRFull-time
We need to output HTML fragment with sections: About the role? The posting includes description of company and role. We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We have content about role: description of responsibilities, what you'll own, etc. That can go under Responsibilities. Also maybe "About the role" could be the introductory paragraph about Keep Supply and the role. The posting includes "At Keep Supply, we're in the business..." That's company overview; could be About the role? Actually "About the role" heading is for description of role, not company. But we can put company overview under About the role? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include those headings if content exists.
We have responsibilities detailed: bullet list under "What You'll Own". Also "By the End of Your First Year" outcomes. Also "How You'll Lead" leadership principles. Could be part of Responsibilities or separate sections like "Leadership Expectations". But only allowed headings from list. We could put leadership principles under Responsibilities as part of responsibilities. Or we could create a separate section "Qualifications" for requirements. Requirements list: "What We're Looking For". Also "Relevant Backgrounds Could Include". Also "Why Keep Supply". That's more about why join. Could be Benefits? Actually Benefits section includes compensation & benefits: medical, dental, vision 100%, unlimited PTO. Also mention "Backed by Kanbrick: access to a peer network...". That's benefits.
Pay: not specified. So we should NOT include Pay section because no specific pay info. Schedule: not specified. So omit.
We need to preserve all substantive information, not invent. Remove boilerplate: EEO, equal opportunity, etc. Also remove navigation, cookie, legal, duplicated lines, application instructions. There's no explicit application instructions.
We need to output only HTML fragment, no /, no markdown fences.
Structure: maybe:
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include those headings if content exists.
We have responsibilities detailed: bullet list under "What You'll Own". Also "By the End of Your First Year" outcomes. Also "How You'll Lead" leadership principles. Could be part of Responsibilities or separate sections like "Leadership Expectations". But only allowed headings from list. We could put leadership principles under Responsibilities as part of responsibilities. Or we could create a separate section "Qualifications" for requirements. Requirements list: "What We're Looking For". Also "Relevant Backgrounds Could Include". Also "Why Keep Supply". That's more about why join. Could be Benefits? Actually Benefits section includes compensation & benefits: medical, dental, vision 100%, unlimited PTO. Also mention "Backed by Kanbrick: access to a peer network...". That's benefits.
Pay: not specified. So we should NOT include Pay section because no specific pay info. Schedule: not specified. So omit.
We need to preserve all substantive information, not invent. Remove boilerplate: EEO, equal opportunity, etc. Also remove navigation, cookie, legal, duplicated lines, application instructions. There's no explicit application instructions.
We need to output only HTML fragment, no /, no markdown fences.
Structure: maybe:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Benefits
- ... ...
About the role
company overview + role description? Could split: About the role could include company overview and the role summary. We'll put company overview and the "The Role" paragraph. Then