Business Systems Architect
CEIA USA · Hudson, OH · 3 wk ago
Engineering$250/hrFull-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 only include sections where posting has real specific content. No filler like "commensurate with experience". We must preserve all substantive info, remove boilerplate (EEO, navigation, etc). No job title heading. No Job ID. No application instructions.
We need to parse the posting.
Brief Description: includes company description and role description. Could be "About the role" or maybe "About the role" heading. The description includes: "Headquartered in Hudson, OH, CEIA USA is a world leading manufacturer..." then "The Business Systems Architect will work to develop, optimize, and integrate our CRM environment..." That's role description. So we can put that under
. Ensure we preserve all details.
Let's list benefits:
- Paid Training opportunities to enhance your Career, and Educational Assistance
- A Rich Paid Time Off Plan—20-day (4-week) annual accrual starting at DOH that progressively increases with tenure.
- Select Paid Holidays, including the FULL period between Christmas and New Years - paid as Holiday Time.
- Premium health benefits, and wellness resources to keep you and your family supported.
- Medical Plan options that include a $250/$5
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections where posting has real specific content. No filler like "commensurate with experience". We must preserve all substantive info, remove boilerplate (EEO, navigation, etc). No job title heading. No Job ID. No application instructions.
We need to parse the posting.
Brief Description: includes company description and role description. Could be "About the role" or maybe "About the role" heading. The description includes: "Headquartered in Hudson, OH, CEIA USA is a world leading manufacturer..." then "The Business Systems Architect will work to develop, optimize, and integrate our CRM environment..." That's role description. So we can put that under About the role
with paragraphs.
Then "Requirements" section: includes bullet list of responsibilities? Actually the "Requirements" heading appears in the posting: "Requirements" then a list of bullet points (starting with "Own, develop, and continuously improve..."). Those are duties/responsibilities. Could be considered Responsibilities. But the posting also has "Education, Experience, And Knowledge" which is qualifications. Then "Other Duties" etc. Also "Working Conditions", "Supervisory Responsibility", "Travel is not required", etc. Also "Benefits" section: "Summary At CEIA USA, we believe that taking care of our people..." includes benefits details. So we need Benefits section.
Pay and Schedule: Not mentioned explicitly. No pay info. Schedule: Not mentioned (maybe standard office hours). Not given. So we should not include Pay or Schedule sections.
Skills: Could be derived from requirements but we might not need separate Skills if we have Requirements and Qualifications. The instruction: prefer few substantive sections over many thin ones. We could combine Requirements and Qualifications into one? But they ask to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content.
We have:
- About the role: company description + role overview.
- Responsibilities: the list of duties under "Requirements" heading (own, develop, continuously improve...). Those are responsibilities.
- Qualifications: Education, Experience, And Knowledge section.
- Skills: maybe we could extract from qualifications (programming languages, Deluge, REST APIs, etc.) but that overlaps with qualifications. Could combine Qualifications and Skills, but better to have Qualifications section and maybe Skills not needed if content overlaps. However we could still include Skills if we have specific skill list: "Advanced Zoho CRM experience beyond basic administration and configuration is preferred. Hands-on programming experience in at least one modern language outside Deluge, such as JavaScript, Python, Java, C#, PHP, or similar. Strong proficiency in Deluge scripting, including custom functions, complex business logic, workflows, and subform/related-record manipulation is preferred. Demonstrated experience with REST APIs, webhooks, system integrations, and data synchronization. Strong understanding of data structures, data modeling, integration architecture, and data integrity. Ability to analyze complex business problems and translate them into effective technical solutions. Strong understanding of software architecture, security, scalability, testing, and maintainability. Demonstrated initiative and ownership, with the ability to overcome obstacles and drive projects to completion without minimal oversight. Excellent written and verbal communication skills, including the ability to work effectively with technical personnel, business users, managers, and executives."
That's a mix of qualifications and skills. Could treat as Qualifications. The Education, Experience, And Knowledge section includes: "5+ years of hands-on experience developing, implementing, or architecting CRM based business systems. Advanced Zoho CRM experience beyond basic administration and configuration is preferred. Hands-on programming experience in at least one modern language outside Deluge, such as JavaScript, Python, Java, C#, PHP, or similar. Strong proficiency in Deluge scripting, including custom functions, complex business logic, workflows, and subform/related-record manipulation is preferred. Demonstrated experience with REST APIs, webhooks, system integrations, and data synchronization. Strong understanding of data structures, data modeling, integration architecture, and data integrity. Ability to analyze complex business problems and translate them into effective technical solutions. Strong understanding of software architecture, security, scalability, testing, and maintainability. Demonstrated initiative and ownership, with the ability to overcome obstacles and drive projects to completion without minimal oversight. Excellent written and verbal communication skills, including the ability to work effectively with technical personnel, business users, managers, and executives."
Thus Qualifications covers that.
Responsibilities: the list under "Requirements" heading (own, develop, continuously improve...). Let's extract those bullet points:
- Own, develop, and continuously improve the company's technology infrastructure, with an emphasis on current CRM software (Zoho) and advanced customization.
- Analyze business processes and proactively identify opportunities to improve efficiency, automation, data quality, and system usability.
- Design and develop complex workflows, custom modules, functions, and automations using Deluge, including sophisticated subform and related-record logic.
- Design, develop, and maintain REST API integrations, webhooks, and automated data flows between the CRM and other business systems.
- Integrate existing/future CRM platforms (Zoho) with legacy and third-party platforms, including systems such as Microsoft Dynamics GP (Great Plains).
- Build or support middleware, external services, or other software solutions when native capabilities are insufficient.
- Ensure solutions are scalable, secure, reliable, maintainable, and consistent with sound data architecture and governance practices.
- Lead projects from requirements and solution design through development, testing, implementation, documentation, and ongoing optimization.
- Troubleshoot complex system, integration, and data issues and proactively address technical debt and recurring problems.
- Partner with business stakeholders to understand requirements and provide practical technical recommendations.
- Communicate continuously with stakeholders regarding project status, risks, decisions, and outcomes.
- Present technical recommendations to department leaders and executive management and confidently defend sound technical decisions when necessary.
That's responsibilities.
Other Duties: note about job description not comprehensive, duties may change. That's boilerplate? It's generic but maybe we should keep? The instruction: remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Other Duties" is not exactly boilerplate but it's a generic statement. Might be considered boilerplate? It's typical but could be kept as part of responsibilities? However it's not substantive detail about the role. I'd consider it boilerplate and remove.
Working Conditions: includes description of office environment, physical demands, travel not required. That's substantive? Could be included under a section maybe "Working Conditions". But the allowed headings list does not include Working Conditions. So we cannot create a heading not in list. We could fold into About the role or Responsibilities? Probably we can omit because not in allowed headings. The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples but we should stick to those? It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should not create other headings like Working Conditions. So we need to incorporate that info elsewhere if relevant. Travel not required could be mentioned in About the role or Responsibilities? Probably we can omit as not critical. But we must preserve ALL substantive information. Travel not required is substantive. However if we cannot create a heading for it, we could add a paragraph under About the role or Responsibilities. The instruction: "Prefer a few substantive sections over many thin ones." So we could add a short paragraph under About the role mentioning work environment. That would preserve info.
Supervisory Responsibility: "This job has no supervisory responsibility." Could be included similarly.
EEO boilerplate: remove.
Benefits: we have a benefits paragraph under "Summary". Let's extract:
"At CEIA USA, we believe that taking care of our people is the key to building a thriving, high-performing team. That’s why we offer a comprehensive and market-leading benefits package, designed to support your well-being both inside and outside of work.
Paid Training opportunities to enhance your Career, and Educational Assistance
A Rich Paid Time Off Plan—20-day (4-week) annual accrual starting at DOH that progressively increases with tenure.
Select Paid Holidays, including the FULL period between Christmas and New Years - paid as Holiday Time.
Premium health benefits, and wellness resources to keep you and your family supported.
Medical Plan options that include a $250/$500 PPO Deductible that is lucratively subsidized by the Company.
Company Paid life insurance, short term disability, and long term disability.
401(k) with % match that is only capped by IRS maximums, and profit sharing; subject to eligibility requirements.
Annual Bonus Potential after 1 full year of employment.
Check out our products at: https://www.ceia-usa.com/"
We should preserve all that. The final sentence about checking out products maybe not a benefit but still part of summary. Could keep.
Thus Benefits section.
Pay: Not mentioned. So omit.
Schedule: Not mentioned. Omit.
Skills: Could be omitted if we have Qualifications covering skills. But we might still include Skills if we want to separate. However we have Qualifications already covering experience and knowledge. Skills could be derived from that list but would be duplicate. Better to omit Skills to avoid thin section.
Thus sections: About the role, Responsibilities, Qualifications, Benefits.
We need to ensure we don't repeat job title as heading. Not include.
Now produce HTML fragment:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should not create other headings like Working Conditions. So we need to incorporate that info elsewhere if relevant. Travel not required could be mentioned in About the role or Responsibilities? Probably we can omit as not critical. But we must preserve ALL substantive information. Travel not required is substantive. However if we cannot create a heading for it, we could add a paragraph under About the role or Responsibilities. The instruction: "Prefer a few substantive sections over many thin ones." So we could add a short paragraph under About the role mentioning work environment. That would preserve info.
Supervisory Responsibility: "This job has no supervisory responsibility." Could be included similarly.
EEO boilerplate: remove.
Benefits: we have a benefits paragraph under "Summary". Let's extract:
"At CEIA USA, we believe that taking care of our people is the key to building a thriving, high-performing team. That’s why we offer a comprehensive and market-leading benefits package, designed to support your well-being both inside and outside of work.
Paid Training opportunities to enhance your Career, and Educational Assistance
A Rich Paid Time Off Plan—20-day (4-week) annual accrual starting at DOH that progressively increases with tenure.
Select Paid Holidays, including the FULL period between Christmas and New Years - paid as Holiday Time.
Premium health benefits, and wellness resources to keep you and your family supported.
Medical Plan options that include a $250/$500 PPO Deductible that is lucratively subsidized by the Company.
Company Paid life insurance, short term disability, and long term disability.
401(k) with % match that is only capped by IRS maximums, and profit sharing; subject to eligibility requirements.
Annual Bonus Potential after 1 full year of employment.
Check out our products at: https://www.ceia-usa.com/"
We should preserve all that. The final sentence about checking out products maybe not a benefit but still part of summary. Could keep.
Thus Benefits section.
Pay: Not mentioned. So omit.
Schedule: Not mentioned. Omit.
Skills: Could be omitted if we have Qualifications covering skills. But we might still include Skills if we want to separate. However we have Qualifications already covering experience and knowledge. Skills could be derived from that list but would be duplicate. Better to omit Skills to avoid thin section.
Thus sections: About the role, Responsibilities, Qualifications, Benefits.
We need to ensure we don't repeat job title as heading. Not include.
Now produce HTML fragment:
About the role
... (company description + role overview + maybe work environment)
We need to combine company description and role overview. Let's craft: Headquartered in Hudson, OH, CEIA USA is a world leading manufacturer of security screening equipment, specializing in the design, engineering and production of a complete range of devices including: Walk-Through, Hand-Held, Table-Top and Ground Search Metal Detectors, Bottled Liquid Scanners, Non-Metallic Cargo Inspection and Loss Prevention Systems. CEIA USA provides nationwide sales, service and customer support to public (federal, state and local governments) and private sector customers in North America. Dynamic solutions are the foundation of CEIA USA's commitment to customer satisfaction. The Business Systems Architect will work to develop, optimize, and integrate our CRM environment as a critical component of our broader business systems. This role will work to proactively solve problems and identify business bottlenecks, challenges, and/or inefficient processes, and collaborate directly with employees, department leaders, and executive management in translating complex business needs into scalable, secure, and practical technology solutions. Optionally add: This role operates in a professional office environment with standard office equipment; occasional standing, walking, sitting, lifting up to 20 pounds; travel not required; no supervisory responsibility. We can incorporate that. Now Responsibilities:Responsibilities
- ... each bullet
Qualifications
- ... each bullet
Benefits
- ... each benefit bullet