Manager, SEC Reporting & Technical Accounting
CECO Environmental Corporation · Addison, TX · 4 wk ago
AccountingFull-time
We need to output HTML fragment with headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines. Preserve all substantive info.
We need to parse the posting.
Let's extract sections:
- About the role: The paragraph after "We are seeking an experienced and detail-oriented Manager of SEC Reporting and Technical Accounting to join our finance team." That's description of role. Also earlier paragraphs about company mission etc. Might be considered "About the role"? Usually "About the role" includes description of role and maybe company overview. We'll include a concise paragraph summarizing role and maybe company context but must preserve all substantive info, not invent or summarize away detail. We cannot omit details; we must preserve all substantive information. However we can combine into paragraphs but must keep all info. We cannot drop any substantive detail. So we need to include all details from the posting that are not boilerplate.
We need to decide what is substantive vs boilerplate. Boilerplate includes cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also "Equal Opportunity Employer" etc. Also "Accessibility Assistance or Accommodation". Also "About Us" repeated? There's a section "About Us" and "About Ceco". Those might be considered boilerplate? They are about company but maybe considered substantive? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About Us" is not explicitly listed as boilerplate, but could be considered company overview. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep company overview if it's substantive. However we need to decide if it's considered "About the role" or separate. The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those headings. Company overview could go under About the role (maybe). But we must not create sections with filler text. So we need to ensure each heading has real specific content.
Let's extract content:
Company overview paragraphs:
"CECO Environmental is a global leader in providing sustainable solutions for industrial air, water, and energy transition. Since 1966, we’ve been addressing the world’s most pressing environmental challenges. Our mission is to protect people, the environment, and industrial equipment, making a tangible impact across industries like renewable energy, semiconductor manufacturing, power generation, and water treatment. As a purpose-driven company, we foster a culture of innovation, collaboration, and integrity, ensuring that every project we undertake creates lasting positive change. At CECO, you’ll be part of a growing, dynamic team committed to a cleaner, safer, and more sustainable future. As part of the CECO corporate team, you will play a key role in supporting the continued growth and success of our global family of brands. Whether working in finance, HR, IT, accounting, marketing, or another corporate function, your expertise will help drive efficiency and innovation across our organization. By joining CECO, you’ll be part of a company committed to protecting the environment and enhancing industrial operations, all while fostering a collaborative and purpose-driven work environment."
That's substantive.
Then the role description: "We are seeking an experienced and detail-oriented Manager of SEC Reporting and Technical Accounting to join our finance team. In this role, you will lead the company’s SEC reporting efforts and drive compliance with all applicable accounting standards. You will be responsible for preparing accurate and timely filings, managing technical accounting matters, and serving as a resource for accounting policy decisions. The ideal candidate will have strong analytical skills and a thorough understanding of both U.S. GAAP and SEC regulations."
That's also role description.
We could combine these into About the role section.
Next: Responsibilities: bullet list under "Your Responsibilities Will Be". Items:
- Prepare quarterly (Form 10-Q) and annual (Form 10-K) SEC filings, including financial statements, footnotes, and Management’s Discussion and Analysis (MD&A).
- Coordinate with external auditors and internal departments to ensure timely and accurate filing of all required SEC reports.
- Collaborate with FP&A and other internal stakeholders to provide insights on financial results and ensure consistency across internal and external reporting.
- Research, interpret, and document technical accounting issues, including new accounting SEC regulations, accounting standards, and pronouncements.
- Monitor and revise accounting policies and procedures as needed, and provide guidance throughout the organization on the application of such policies.
- Provide technical accounting guidance for complex transactions (e.g., acquisitions, equity transactions, revenue recognition, etc.).
- Ensure SOX compliance related to financial reporting and technical accounting.
- Foster a culture of continuous improvement and professional development within the team.
- Collaborate with cross-functional teams to support accounting initiatives and projects.
- Other job duties as assigned.
That's responsibilities.
Next: Required Qualifications: list:
- Bachelor’s degree in accounting, finance, or a related field required.
- CPA license required.
- 7+ years of experience in public accounting or a combination of public accounting and corporate accounting, with a focus on SEC reporting and technical accounting.
- In-depth knowledge of U.S. GAAP, SEC reporting requirements, and SOX compliance.
- Strong analytical, problem-solving, and organizational skills.
- Excellent written and verbal communication skills.
- Proficiency in financial software and reporting tools; experience with ERP systems (Microsoft Dynamics) and SEC reporting software (DFIN) is a plus.
- Ability to work under pressure, meet deadlines, and manage multiple projects simultaneously.
That's qualifications.
Next: Travel Requirements: "The ability to travel domestically and internationally when necessary (up to 30%). Valid driver license required."
That could be under Requirements? Or maybe a separate section but we only have headings list; Travel could be part of Requirements or maybe we could create a "Requirements" section that includes travel? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we have Requirements and Qualifications separate. Typically Requirements might include experience, education, etc. Qualifications might be similar. But we have both Required Qualifications and maybe Skills. We'll map:
- Requirements: maybe include travel requirements, driver license, ability to travel, etc. Also maybe include "Valid driver license required." Also maybe include "Ability to work under pressure..." but that's more skill.
Better: Use Requirements for mandatory items like education, experience, licensure, travel, driver license. Use Qualifications for preferred or additional qualifications? But the posting lumps them as "Required Qualifications". So we could treat that as Qualifications section. Then Requirements could be empty? But we must not create a heading with filler. So we should only include sections that have real specific content. If we don't have distinct content for Requirements separate from Qualifications, we could omit Requirements heading and put everything under Qualifications. However the instruction says we can use those headings; we don't have to use all. So we can omit Requirements if no distinct content.
Skills: we have "Strong analytical, problem-solving, and organizational skills." "Excellent written and verbal communication skills." "Proficiency in financial software and reporting tools; experience with ERP systems (Microsoft Dynamics) and SEC reporting software (DFIN) is a plus." "Ability to work under pressure, meet deadlines, and manage multiple projects simultaneously." Those could be Skills.
Benefits: "We Offer We provide a variety of medical insurance plans, with dental and vision coverage, Employee 401(k), tuition reimbursement, and much more." Also maybe mention culture etc. But we need to preserve all substantive info. So Benefits section should include that.
Pay: Not mentioned. So we should not create Pay section.
Schedule: Not mentioned. So no Schedule.
We also have "ADA Requirements" and "Work Environment" etc. That's likely boilerplate (legal/ADA). Should be removed. Also "Compliance with company attendance standards." etc. That's likely boilerplate. Remove.
Also "About Ceco" and "About Us" duplicates; we should keep only one company overview maybe. The posting includes "About Us CECO’s Commitment to Our People ..." and "About Ceco CECO Environmental is a leading environmentally focused...". Those are somewhat overlapping but both contain substantive info about company. We should preserve all substantive info, not summarizing away detail. So we need to include both paragraphs? But they may be considered duplicated lines? They are not exactly duplicates but similar. The instruction: remove duplicated lines. If they are similar but not identical, we might keep both? However to avoid redundancy, we could combine them into a single paragraph that preserves all info without omission. But we must not invent or summarize away detail; combining could be considered summarizing? It's rephrasing but we could keep both as separate paragraphs; that's fine. It's not duplicating identical lines. So we can keep both.
But we need to place them under About the role maybe. However About the role heading is for role description, not company overview. But we could include company overview under About the role as part of role context. That seems okay.
Alternatively we could create a separate heading like "About the company" but not allowed; only allowed headings list. So we must fit into those headings. So we will put company overview under About the role.
Now we need to output HTML fragment with
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines. Preserve all substantive info.
We need to parse the posting.
Let's extract sections:
- About the role: The paragraph after "We are seeking an experienced and detail-oriented Manager of SEC Reporting and Technical Accounting to join our finance team." That's description of role. Also earlier paragraphs about company mission etc. Might be considered "About the role"? Usually "About the role" includes description of role and maybe company overview. We'll include a concise paragraph summarizing role and maybe company context but must preserve all substantive info, not invent or summarize away detail. We cannot omit details; we must preserve all substantive information. However we can combine into paragraphs but must keep all info. We cannot drop any substantive detail. So we need to include all details from the posting that are not boilerplate.
We need to decide what is substantive vs boilerplate. Boilerplate includes cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also "Equal Opportunity Employer" etc. Also "Accessibility Assistance or Accommodation". Also "About Us" repeated? There's a section "About Us" and "About Ceco". Those might be considered boilerplate? They are about company but maybe considered substantive? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About Us" is not explicitly listed as boilerplate, but could be considered company overview. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep company overview if it's substantive. However we need to decide if it's considered "About the role" or separate. The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those headings. Company overview could go under About the role (maybe). But we must not create sections with filler text. So we need to ensure each heading has real specific content.
Let's extract content:
Company overview paragraphs:
"CECO Environmental is a global leader in providing sustainable solutions for industrial air, water, and energy transition. Since 1966, we’ve been addressing the world’s most pressing environmental challenges. Our mission is to protect people, the environment, and industrial equipment, making a tangible impact across industries like renewable energy, semiconductor manufacturing, power generation, and water treatment. As a purpose-driven company, we foster a culture of innovation, collaboration, and integrity, ensuring that every project we undertake creates lasting positive change. At CECO, you’ll be part of a growing, dynamic team committed to a cleaner, safer, and more sustainable future. As part of the CECO corporate team, you will play a key role in supporting the continued growth and success of our global family of brands. Whether working in finance, HR, IT, accounting, marketing, or another corporate function, your expertise will help drive efficiency and innovation across our organization. By joining CECO, you’ll be part of a company committed to protecting the environment and enhancing industrial operations, all while fostering a collaborative and purpose-driven work environment."
That's substantive.
Then the role description: "We are seeking an experienced and detail-oriented Manager of SEC Reporting and Technical Accounting to join our finance team. In this role, you will lead the company’s SEC reporting efforts and drive compliance with all applicable accounting standards. You will be responsible for preparing accurate and timely filings, managing technical accounting matters, and serving as a resource for accounting policy decisions. The ideal candidate will have strong analytical skills and a thorough understanding of both U.S. GAAP and SEC regulations."
That's also role description.
We could combine these into About the role section.
Next: Responsibilities: bullet list under "Your Responsibilities Will Be". Items:
- Prepare quarterly (Form 10-Q) and annual (Form 10-K) SEC filings, including financial statements, footnotes, and Management’s Discussion and Analysis (MD&A).
- Coordinate with external auditors and internal departments to ensure timely and accurate filing of all required SEC reports.
- Collaborate with FP&A and other internal stakeholders to provide insights on financial results and ensure consistency across internal and external reporting.
- Research, interpret, and document technical accounting issues, including new accounting SEC regulations, accounting standards, and pronouncements.
- Monitor and revise accounting policies and procedures as needed, and provide guidance throughout the organization on the application of such policies.
- Provide technical accounting guidance for complex transactions (e.g., acquisitions, equity transactions, revenue recognition, etc.).
- Ensure SOX compliance related to financial reporting and technical accounting.
- Foster a culture of continuous improvement and professional development within the team.
- Collaborate with cross-functional teams to support accounting initiatives and projects.
- Other job duties as assigned.
That's responsibilities.
Next: Required Qualifications: list:
- Bachelor’s degree in accounting, finance, or a related field required.
- CPA license required.
- 7+ years of experience in public accounting or a combination of public accounting and corporate accounting, with a focus on SEC reporting and technical accounting.
- In-depth knowledge of U.S. GAAP, SEC reporting requirements, and SOX compliance.
- Strong analytical, problem-solving, and organizational skills.
- Excellent written and verbal communication skills.
- Proficiency in financial software and reporting tools; experience with ERP systems (Microsoft Dynamics) and SEC reporting software (DFIN) is a plus.
- Ability to work under pressure, meet deadlines, and manage multiple projects simultaneously.
That's qualifications.
Next: Travel Requirements: "The ability to travel domestically and internationally when necessary (up to 30%). Valid driver license required."
That could be under Requirements? Or maybe a separate section but we only have headings list; Travel could be part of Requirements or maybe we could create a "Requirements" section that includes travel? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we have Requirements and Qualifications separate. Typically Requirements might include experience, education, etc. Qualifications might be similar. But we have both Required Qualifications and maybe Skills. We'll map:
- Requirements: maybe include travel requirements, driver license, ability to travel, etc. Also maybe include "Valid driver license required." Also maybe include "Ability to work under pressure..." but that's more skill.
Better: Use Requirements for mandatory items like education, experience, licensure, travel, driver license. Use Qualifications for preferred or additional qualifications? But the posting lumps them as "Required Qualifications". So we could treat that as Qualifications section. Then Requirements could be empty? But we must not create a heading with filler. So we should only include sections that have real specific content. If we don't have distinct content for Requirements separate from Qualifications, we could omit Requirements heading and put everything under Qualifications. However the instruction says we can use those headings; we don't have to use all. So we can omit Requirements if no distinct content.
Skills: we have "Strong analytical, problem-solving, and organizational skills." "Excellent written and verbal communication skills." "Proficiency in financial software and reporting tools; experience with ERP systems (Microsoft Dynamics) and SEC reporting software (DFIN) is a plus." "Ability to work under pressure, meet deadlines, and manage multiple projects simultaneously." Those could be Skills.
Benefits: "We Offer We provide a variety of medical insurance plans, with dental and vision coverage, Employee 401(k), tuition reimbursement, and much more." Also maybe mention culture etc. But we need to preserve all substantive info. So Benefits section should include that.
Pay: Not mentioned. So we should not create Pay section.
Schedule: Not mentioned. So no Schedule.
We also have "ADA Requirements" and "Work Environment" etc. That's likely boilerplate (legal/ADA). Should be removed. Also "Compliance with company attendance standards." etc. That's likely boilerplate. Remove.
Also "About Ceco" and "About Us" duplicates; we should keep only one company overview maybe. The posting includes "About Us CECO’s Commitment to Our People ..." and "About Ceco CECO Environmental is a leading environmentally focused...". Those are somewhat overlapping but both contain substantive info about company. We should preserve all substantive info, not summarizing away detail. So we need to include both paragraphs? But they may be considered duplicated lines? They are not exactly duplicates but similar. The instruction: remove duplicated lines. If they are similar but not identical, we might keep both? However to avoid redundancy, we could combine them into a single paragraph that preserves all info without omission. But we must not invent or summarize away detail; combining could be considered summarizing? It's rephrasing but we could keep both as separate paragraphs; that's fine. It's not duplicating identical lines. So we can keep both.
But we need to place them under About the role maybe. However About the role heading is for role description, not company overview. But we could include company overview under About the role as part of role context. That seems okay.
Alternatively we could create a separate heading like "About the company" but not allowed; only allowed headings list. So we must fit into those headings. So we will put company overview under About the role.
Now we need to output HTML fragment with headings and - for lists,
for prose.
We must not include or . Just the fragment.
Let's structure:
About the role
... company overview ...
... role description ...
Then Responsibilities:
Responsibilities
- ...
...
Then Qualifications:
Qualifications
- ...
...
Then Skills:
Skills
- ...
...
Then Benefits:
Benefits
We provide a variety of medical insurance plans, with dental and vision coverage, Employee 401(k), tuition reimbursement, and much more.
Potentially also mention "At CECO, we are committed to a culture where every employee is valued and respected..." but that's more culture; could be part of Benefits? Might be considered part of Benefits or maybe we could include under Benefits as prose. However it's not a benefit per se but company culture. The instruction: we should not create sections unless posting has real specific content. It does have that content; we could include it under Benefits as a paragraph, or maybe we could add a separate section like "Culture" but not allowed. So we can include it in Benefits paragraph.
Thus Benefits paragraph: "We provide a variety of medical insurance plans, with dental and vision coverage, Employee 401(k), tuition reimbursement, and much more. At CECO, we are committed to a culture where every employee is valued and respected for their unique experiences and perspectives. We believe a diverse and inclusive work environment contributes to the rich exchange of ideas and diversity of thoughts, that inspires innovation and brings the best solutions to our customers."
Now check for any other substantive content not captured:
- "As part of the CECO corporate team, you will play a key role in supporting the continued growth and success of our global family of brands." Already in company overview.
- "Whether working in finance, HR, IT, accounting, marketing, or another corporate function, your expertise will help drive efficiency and innovation across our organization." Already.
- "By joining CECO, you’ll be part of a company committed to protecting the environment and enhancing industrial operations, all while fostering a collaborative and purpose-driven work environment." Already.
- "At CECO, our people are at the center of everything we do..." That's from "About Ceco’s Commitment to Our People". That's also substantive. Should we include? It's under "About Us" heading
- for lists,
for prose. We must not include or . Just the fragment. Let's structure:
About the role
... company overview ...
... role description ...
Then Responsibilities:Responsibilities
- ... ...
Qualifications
- ... ...
Skills
- ... ...
Benefits
We provide a variety of medical insurance plans, with dental and vision coverage, Employee 401(k), tuition reimbursement, and much more.
Potentially also mention "At CECO, we are committed to a culture where every employee is valued and respected..." but that's more culture; could be part of Benefits? Might be considered part of Benefits or maybe we could include under Benefits as prose. However it's not a benefit per se but company culture. The instruction: we should not create sections unless posting has real specific content. It does have that content; we could include it under Benefits as a paragraph, or maybe we could add a separate section like "Culture" but not allowed. So we can include it in Benefits paragraph. Thus Benefits paragraph: "We provide a variety of medical insurance plans, with dental and vision coverage, Employee 401(k), tuition reimbursement, and much more. At CECO, we are committed to a culture where every employee is valued and respected for their unique experiences and perspectives. We believe a diverse and inclusive work environment contributes to the rich exchange of ideas and diversity of thoughts, that inspires innovation and brings the best solutions to our customers." Now check for any other substantive content not captured: - "As part of the CECO corporate team, you will play a key role in supporting the continued growth and success of our global family of brands." Already in company overview. - "Whether working in finance, HR, IT, accounting, marketing, or another corporate function, your expertise will help drive efficiency and innovation across our organization." Already. - "By joining CECO, you’ll be part of a company committed to protecting the environment and enhancing industrial operations, all while fostering a collaborative and purpose-driven work environment." Already. - "At CECO, our people are at the center of everything we do..." That's from "About Ceco’s Commitment to Our People". That's also substantive. Should we include? It's under "About Us" heading