ECM Developer

We need to output HTML fragment with sections: About the role? The posting includes description. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate. Preserve all substantive info. We need to parse the posting. Key sections: - About the role: maybe a paragraph summarizing role: "Build and Support Enterprise Content Management Solutions ... CGI is seeking an ECM Developer to join our team in San Diego, CA, supporting a large enterprise client. In this role, you will help design, develop, administer, integrate, and support enterprise content management solutions that improve document processing, workflow automation, information governance, and secure content lifecycle management. This opportunity supports four primary technical areas: Documentum, Kofax, SharePoint Administration, and SFTP server management. Candidates are not expected to be experts in all four areas; however, strong hands-on proficiency in one or more areas, along with the ability to learn and support adjacent technologies, is important. Location: San Diego, CA Work Model: Hybrid, with three days per week onsite at the client site." We can include that as About the role. - Responsibilities: The "Your future duties and responsibilities" and bullet list under each area. We need to extract responsibilities as list items. Could group them under responsibilities heading with

• . Should we separate by area? Probably just list responsibilities. We have responsibilities under each area: Documentum Development, Architecture & Administration (list of duties), Kofax Development & Administration, SharePoint Administration, SFTP Server Administration. We can combine them. - Requirements: The "Required Qualifications" section includes bullet list of qualifications. Also Education: Bachelor's degree required. - Qualifications: maybe separate from Requirements? The posting has "Required Qualifications" and "Desired Qualifications". Could map Required Qualifications to Requirements, Desired Qualifications to Qualifications? But the instruction says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have skills: maybe list of technical skills: Documentum, Kofax, SharePoint, SFTP, APIs, scripting, web tech, databases, etc. Could put under Skills. Qualifications: maybe education and certifications? Could include Bachelor's degree, certifications desired. Pay: we have compensation range: two different ranges appear duplicated: first "$122,574.00 $136,200.00" then later "$79,600.00 $139,300.00". There's inconsistency. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to include both ranges? The posting includes two ranges due to duplicated sections. We should include both as they appear. But we must not create placeholder text. Both are specific numbers. So we can include both ranges in Pay section. Schedule: we have hybrid model: three days per week onsite. Also location San Diego. Could put schedule: Hybrid, three days per week onsite. Benefits: list of benefits: Competitive compensation including profit participation program, Comprehensive medical, dental, and vision benefits, Basic life and accidental death & dismemberment insurance, Matching contributions through 401(k) plan, and CGI share purchase plan, Flexibility and paid accrued vacation leave, ranging from 10 to 20 days per year, based on job level, years of relevant prior experience, and years of service, 10 paid holidays per year, At least 80 consecutive hours of paid sick/safe leave, Paid parental leave, ranging from 20 to 70 consecutive business days, Bereavement leave, ranging from 1 to 7 days per year, Paid jury duty leave, up to time summoned, Learning opportunities and tuition assistance, Wellness and Well being programs. Also later duplicate benefits list: Competitive compensation, Comprehensive insurance options, Matching contributions through the 401(k) plan and the share purchase plan, Paid time off for vacation, holidays, and sick time, Paid parental leave, Learning opportunities and tuition assistance, Wellness and Well being programs. We need to preserve all substantive info, not remove duplicates? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Duplicated lines should be removed. So we should deduplicate benefits. Keep unique items. We also need to include location maybe in About the role or Schedule? Could include location in About the role. We must not include headings with filler text. Ensure each heading has substantive content. Now produce HTML fragment:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Qualifications

  • ...
  ...

  Skills

  • ...
  ...

  Benefits

  • ...
  ...

  Pay

  $122,574.00 - $136,200.00; $79,600.00 - $139,300.00 (estimated compensation range)

  Schedule

  Hybrid work model with three days per week onsite at the client site in San Diego, CA.

  We need to ensure we don't repeat job title. Also we need to preserve all substantive info from responsibilities etc. Let's extract responsibilities: From Documentum Development, Architecture & Administration: - Design, develop, and maintain Documentum repositories, object models, security frameworks, and application integrations - Develop and customize applications, TBOs, workflows, automation components, and integrations using Documentum APIs and DQL - Administer user access, permissions, configurations, content lifecycles, and system performance - Troubleshoot repository and application issues and identify opportunities to improve performance, reliability, and maintainability - Ensure Documentum solutions align with enterprise security, governance, and operational standards From Kofax Development & Administration: - Design, configure, and maintain Kofax batch classes supporting document capture, classification, indexing, and data extraction - Develop and maintain validation scripts, business rules, and automation to improve processing accuracy and efficiency - Administer Kofax servers, services, queues, configurations, and system performance - Integrate Kofax with enterprise applications and content management platforms - Troubleshoot scanning, capture, workflow, and system issues and implement sustainable solutions From SharePoint Administration: - Configure, administer, and maintain SharePoint sites, document libraries, lists, permissions, and related functionality - Manage access controls and support secure content collaboration across the environment - Perform system maintenance, patching, monitoring, and upgrades as required - Troubleshoot user and system issues and optimize SharePoint configurations and features - Support system availability, reliability, and adherence to enterprise governance standards From SFTP Server Administration: - Install, configure, maintain, and support secure SFTP environments - Manage user accounts, roles, permissions, authentication methods, and secure access - Maintain configurations in accordance with FIPS 140-2 and applicable internal security standards - Identify and remediate vulnerabilities and support security and compliance requirements - Perform configuration backups and troubleshoot connectivity, authentication, and file-transfer issues - Help ensure reliable and secure transfer of sensitive enterprise information We'll list each as
• . Now Requirements (Required Qualifications): - 4+ years of experience in enterprise content management development, administration, engineering, or a related technical discipline - Hands-on proficiency with one or more enterprise content management technologies, such as Documentum, Kofax, SharePoint, OpenText, FileNet, or Hyland OnBase - Experience supporting document management, document capture, indexing, workflow automation, or content lifecycle processes - Experience integrating content management platforms with enterprise applications - Working knowledge of REST and/or SOAP APIs - Experience with scripting or automation technologies such as PowerShell or Python - Understanding of web technologies including HTML, CSS, and JavaScript - Familiarity with relational databases such as SQL Server, Oracle, or similar technologies - Knowledge of records management, information governance, security, and compliance principles - Strong troubleshooting, analytical, and problem-solving skills - Ability to collaborate effectively with technical teams, business stakeholders, and client personnel - Ability to work onsite at the San Diego client location three days per week Education: Bachelor's degree required, preferably in Computer Science, Information Systems, Engineering, or a related field. We could put Education under Requirements or Qualifications. Since we have Qualifications heading separate, maybe put Education there. But we also have Desired Qualifications. Let's decide: Requirements: the mandatory items (4+ years, hands-on proficiency, experience supporting..., experience integrating..., working knowledge of APIs, experience with scripting, understanding of web tech, familiarity with relational databases, knowledge of records management, strong troubleshooting, ability to collaborate, ability to work onsite three days per week). Also maybe include Bachelor's degree required? Could be part of Requirements. Qualifications: Desired Qualifications: certifications, cloud ECM experience, migration strategies, familiarity with enterprise security standards, Agile/Scrum experience, experience supporting large-scale enterprise or government tech environments. Skills: maybe list technical skills: Documentum, Kofax, SharePoint, SFTP, APIs (REST/SOAP), PowerShell, Python, HTML/CSS/JS, SQL Server/Oracle, etc. But we already have many in Requirements. To avoid duplication, we could put Skills as a concise list of technical proficiencies: Documentum, Kofax, SharePoint, SFTP, REST/SOAP APIs, PowerShell, Python, HTML/CSS/JavaScript, SQL Server/Oracle, etc. But we must preserve all substantive info; we can't omit details. If we put skills separately, we need to ensure we don't lose any info from Requirements. We could keep Requirements as the list of mandatory qualifications (including experience, education, etc.) and Skills as a subset focusing on technical abilities. However that may duplicate some items. The instruction says remove duplicated lines. So we should avoid duplicating same content. So we need to decide where each piece goes without duplication. Better approach: Use Requirements for the mandatory qualifications (including experience, education, etc.). Use Qualifications for desired qualifications (certifications, cloud, migration, Agile, large-scale). Use Skills for technical skills list (maybe summarizing the hands-on proficiency with specific platforms, APIs, scripting, web tech, databases). But we must ensure we don't duplicate any sentence exactly. Let's list mandatory qualifications (from Required Qualifications) as bullet points, but we can combine some into a concise statement to avoid duplication with Skills. However we must preserve all substantive info; we can rephrase but not lose detail. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Summarizing away detail is not allowed. So we cannot condense details; we must keep each piece of information. So we need to keep each bullet as is. If we also list skills separately, we would duplicate some info (like hands-on proficiency with platforms). That would be duplicated lines, which we should remove. So we should not create a separate Skills section if it would duplicate content already in Requirements. Instead, we could omit Skills section if no unique content beyond what's already covered. But the instruction says to include a section only when posting has real, specific content for it. If we have no unique content for Skills beyond what's already in Requirements, we should not create a Skills heading. However the heading list includes Skills as optional; we can omit it if no unique content. Similarly, Qualifications (desired) have unique content not in Requirements: certifications, cloud ECM experience, migration strategies, familiarity with enterprise security