Business Analyst

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: Position, Location, Work Type, Experience, Visa Type, then description. There's no explicit Benefits, Pay, Schedule. So we should not include those sections. We need sections: About the role (maybe from description), Responsibilities (Roles & Responsibilities), Requirements (maybe Required Skills?), Qualifications (Education?), Skills (maybe Required Skills?). We need to decide mapping. We must preserve all substantive info, not invent. Use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. We need to remove boilerplate: cookie/navigation/legal/EEO etc. Not present. Remove duplicated lines, application instructions (email, contact, etc). Also remove "Candidates are required to attend Phone/video calls..." etc. Also remove "Please email your resume..." etc. Also remove "After carefully reviewing..." etc. We need to keep substantive info: Position: Business Analyst? Actually title says Business Analyst but description is Senior Documentum Specialist. We should not repeat job title as heading. The page already shows it, so we don't include heading for job title. We'll include location etc maybe in About the role paragraph. We need to include all specifics: Location: Reston, VA (Hybrid - 3days Office). Work Type: C2C. Experience: 15+ Years. Visa Type: H1B, GC and US Citizen. Then the description about PETADATA looking for Senior Documentum Specialist with 15+ years hands-on experience... etc. We need to structure. Possible sections: - About the role: include company, location, work type, experience, visa, brief overview. - Responsibilities: list from "Roles & Responsibilities" bullet points (though they are paragraphs). We'll convert each sentence into list items? The instruction: Use

  • for any list of duties/requirements/benefits. The responsibilities are given as paragraphs with colon headings. We can treat each major responsibility as list item. - Requirements: maybe from "Required Skills" list. - Qualifications: Education (Bachelor's degree...). Also maybe certifications? But those are preferred skills. - Skills: maybe combine required and preferred? But we should not duplicate. Could have Skills section for required skills (technical). Qualifications for education. We need to avoid thin sections. Let's see content: About the role: we have location, work type, experience, visa type, company name, role description. Responsibilities: many bullet-like paragraphs. Requirements: list of required skills (15+ years experience, strong understanding, etc). That's a list. Qualifications: Education: Bachelor's degree... Skills: maybe we could list technical skills like Java, DFC, SQL, etc. But those are already in required skills. Might be redundant. Better: Have sections: About the role, Responsibilities, Required Skills, Education (Qualifications). Preferred Skills could be omitted if not required? But we could include as Skills section if there is content. Preferred Skills includes certifications, cloud-based ECM, other ECM platforms, DevOps. That's substantive. So we could have a Skills section for required skills, and maybe a Preferred Skills subsection? But we only allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put required skills under Requirements, education under Qualifications, and maybe skills under Skills (like technical skills). But we already have required skills covering many technical skills. Could split: Requirements = experience and visa etc? Hmm. Let's think: The posting includes: - Position: Business Analyst (but actual role Senior Documentum Specialist) - Location: Reston, VA (Hybrid - 3days Office) - Work Type: C2C - Experience: 15+ Years - Visa Type: H1B, GC and US Citizen - PETADATA is looking for a Senior Documentum Specialist with 15+ years of hands-on experience... - Roles & Responsibilities (list) - Required Skills (list) - Preferred Skills (list) - Education (Bachelor's degree) - Additional notes about interviews etc (to remove) Thus we can map: About the role: include company, location, work type, experience, visa, brief overview. Responsibilities: the Roles & Responsibilities content. Requirements: the Required Skills list. Qualifications: Education (Bachelor's degree) maybe also mention certifications? But certifications are preferred. Skills: Preferred Skills list. We should not create sections with filler. All have content. Now we need to format. We'll output:

    About the role

    ...

    Then

    Responsibilities

    • ...
    ...
    Then

    Requirements

    • ...
    ...
    Then

    Qualifications

    ...

    Then

    Skills

    • ...
    ...
    We must not include Benefits, Pay, Schedule. Now we need to extract prose for About the role. Combine: PETADATA is looking for a Senior Documentum Specialist with 15+ years of hands-on experience in Enterprise Content Management (ECM) solutions. The ideal candidate will have a strong background in Documentum, OpenText, and related ECM technologies. This role requires deep expertise in Documentum platform customization, integration, migration, and maintenance, as well as the ability to lead and manage complex ECM projects from concept to implementation. As a Senior Consultant, you will be expected to provide thought leadership, define best practices, and play an active role in the strategic direction of ECM initiatives for our clients. Add location etc: Location: Reston, VA (Hybrid - 3days Office). Work Type: C2C. Experience: 15+ Years. Visa Type: H1B, GC and US Citizen. We can incorporate into paragraph. Now Responsibilities: we need to break down the "Roles & Responsibilities" section into list items. Original text: Roles & Responsibilities Documentum Design & Development: Lead the design, development, and troubleshooting of Documentum applications, ensuring high performance, scalability, and security. Design and implement customized solutions using Documentum Content Server, D2 Config, D2 Classic, D2 Smart View, Brava, CTS, xPlore, and DFC Client. Oversee platform upgrades and migrations, including data migration, version upgrades, and architecture reconfiguration. Architect and configure Documentum workflows, business rules, and lifecycle management solutions. Implement best practices for Documentum security, including user roles, permissions, and access controls. API Development & Integration Design and develop REST APIs for Documentum and other ECM platforms, utilizing the Spring Framework. Integrate Documentum with external systems and third-party applications via REST APIs. Troubleshoot and resolve issues related to API performance, security, and integration. Cloud Expertise & AWS Management Leverage AWS services such as EC2, ECS, RDS, ALB, SSM, SQS, SNS, Lambda, and AWS SDK for scalable and resilient ECM solutions. Manage and optimize AWS deployments, review configurations, security policies, and analyze logs to ensure the reliability of cloud-based ECM applications. Troubleshoot and resolve complex cloud infrastructure issues, including system outages, network failures, and performance bottlenecks. Agile Methodology & Project Delivery Lead and contribute to Agile development teams, ensuring adherence to Agile principles and practices. Participate in sprint planning, stand-ups, retrospectives, and code reviews to maintain high code quality and alignment with project objectives. Collaborate closely with product owners, business analysts, and other stakeholders to gather requirements and deliver on-time, high-quality ECM solutions. Client Engagement & Technical Consulting Serve as the primary technical consultant for clients, translating business needs into technical ECM solutions. Provide high-level support to resolve issues, optimize performance, and ensure long-term scalability of the ECM systems. Deliver technical presentations and documentation to both technical and non-technical stakeholders. We can make each bold heading as a list item, or break into multiple items. Probably each heading as a list item with the sentences combined. We'll create list items: - Lead the design, development, and troubleshooting of Documentum applications, ensuring high performance, scalability, and security; design and implement customized solutions using Documentum Content Server, D2 Config, D2 Classic, D2 Smart View, Brava, CTS, xPlore, and DFC Client; oversee platform upgrades and migrations, including data migration, version upgrades, and architecture reconfiguration; architect and configure Documentum workflows, business rules, and lifecycle management solutions; implement best practices for Documentum security, including user roles, permissions, and access controls. - Design and develop REST APIs for Documentum and other ECM platforms using the Spring Framework; integrate Documentum with external systems and third-party applications via REST APIs; troubleshoot and resolve issues related to API performance, security, and integration. - Leverage AWS services such as EC2, ECS, RDS, ALB, SSM, SQS, SNS, Lambda, and AWS SDK for scalable and resilient ECM solutions; manage and optimize AWS deployments, review configurations, security policies, and analyze logs to ensure reliability of cloud-based ECM applications; troubleshoot and resolve complex cloud infrastructure issues, including system outages, network failures, and performance bottlenecks. - Lead and contribute to Agile development teams, ensuring adherence to Agile principles and practices; participate in sprint planning, stand-ups, retrospectives, and code reviews to maintain high code quality and alignment with project objectives; collaborate closely with product owners, business analysts, and other stakeholders to gather requirements and deliver on-time, high-quality ECM solutions. - Serve as the primary technical consultant for clients, translating business needs into technical ECM solutions; provide high-level support to resolve issues, optimize performance, and ensure long-term scalability of the ECM systems; deliver technical presentations and documentation to both technical and non-technical stakeholders. Now Requirements: list from Required Skills. Original: Required Skills 15+ years of experience working with Documentum and related ECM products (Content Server, D2 Config, D2 Classic, D2 Smart View, Brava, CTS, xPlore, DFC Client). Strong understanding of Documentum architecture, object model, and security. Experience with Documentum platform upgrades and migrations, including version upgrades and data migrations. 2+ years of experience implementing REST APIs using the Spring Framework, preferably for Documentum or similar ECM platforms. 3+ years of experience working with AWS services, including EC2, ECS, RDS, ALB, SSM, SQS, SNS, Lambda, and AWS SDK. Skilled in troubleshooting AWS deployments, reviewing configurations, security policies, and analyzing logs. Experience with OpenText and integrating it with Documentum or other enterprise systems. Experience working in an Agile environment, with a deep understanding of Agile principles and practices (e.g., Scrum, Kanban). Proficient in Java, Documentum Foundation Classes (DFC), SQL, and other relevant programming languages. Solid understanding of enterprise security, including encryption, access controls, and compliance standards (e.g., GDPR, HIPAA). Ability to work independently as well as in a collaborative team environment. Excellent communication skills, both written and verbal, with the ability to engage with technical and non-technical stakeholders. We'll make each as list item. Qualifications: Education: Bachelor's degree in Computer Science, Information Technology, Engineering, or a related field. We'll put as paragraph. Skills: Preferred Skills list. Original: Preferred Skills Certifications in Documentum or AWS are a plus. Experience with cloud-based ECM solutions (e.g., Amazon S3, Azure Blob Storage). Familiarity with other ECM platforms like OpenText, Alfresco, or SharePoint. Knowledge of DevOps practices and CI/CD pipelines for ECM systems. We'll make list items. Now ensure we don't include boilerplate like "Candidates are required to attend Phone/video calls..." etc. Now produce HTML fragment. Check that we didn't