Senior Project Manager

We need to output HTML fragment with sections: About the role? The posting includes description about company, mission, assignment sections. 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 need to parse content: The posting includes: - Intro about Caylent (company description) - could be "About the role"? Actually "About the role" is typical heading for role description. The posting includes "The Mission" then "Your Assignment" with bullet-like paragraphs. Could treat as Responsibilities. - There's "Your Qualifications" and Preferred Qualifications" etc. - There's "Technical Knowledge Requirements" with subpoints. - Benefits listed. - Pay: Base Salary Range given. - Schedule: Not explicitly given; there is travel up to 25% but not schedule. So we should not include Schedule section because no specific schedule info. - Skills: Could be derived from technical knowledge requirements; but we have a separate "Technical Knowledge Requirements" which could be considered Skills. However we need to decide sections: maybe we include Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. We must not repeat job title as heading. No Job ID. We must preserve all substantive information; do not invent or summarize away detail. So we need to include details as given, but we can format as lists. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting includes EEO statement at end, also note about visa sponsorship, AI tools, etc. Those are boilerplate; we should remove them. Also the "NOTE: We’re unable to provide visa sponsorship..." is likely boilerplate; remove. Also the equal opportunity employer statement; remove. Also the accommodation request line; remove. Also the final paragraphs about diversity etc. Remove. We need to keep substantive content: company description, mission, assignment (responsibilities), qualifications, preferred qualifications, technical knowledge requirements, benefits, pay. We need to format using

headings and

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

  for prose. We need to decide what constitutes a list. Many paragraphs are sentences; we can keep as

  . For bullet-like items (like responsibilities list) we can convert to

  • . The posting includes many sentences starting with verbs; we can treat each as a list item. Let's extract sections: **About the role** maybe include company description and mission? Could be separate "About the role" heading with prose about Caylent and the mission. We'll include that. **Responsibilities**: from "Your Assignment" subsections: Project Management & Client Engagement, Technical Implementation, Solution Development, Continuous Improvement & Innovation. Each has multiple bullet-like sentences. We'll create a
    • for each bullet. **Requirements**: maybe "Your Qualifications" (mandatory) and "Preferred Qualifications". Could combine as Requirements? But we have separate headings: Requirements and Qualifications. The instruction says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have: - Qualifications: Bachelor's degree, 5+ years experience technical project management, 3+ years AWS, experience with contact center technologies, demonstrated experience managing complex technical implementations, excellent communication skills, strong client relationship management capabilities, project management certification, experience with Agile and Waterfall. - Preferred Qualifications: AWS certifications, experience implementing/working with Amazon Connect, deep knowledge of AWS services (list), experience with IVR, CTI, telephony, familiarity with AI/ML, experience with CRM platforms, knowledge of scripting languages and IaC tools, contact center operations experience. We could put mandatory under "Qualifications" and preferred under "Requirements"? Or vice versa. Usually Requirements are mandatory, Qualifications are preferred. But we can decide: Requirements = mandatory qualifications; Qualifications = preferred qualifications. However the headings list both; we need to include both if content exists. We also have "Technical Knowledge Requirements" which could be under Skills. Thus: - Requirements (mandatory): list of mandatory qualifications. - Qualifications (preferred): list of preferred qualifications. - Skills: technical knowledge requirements (Amazon Connect expertise, AWS services integration knowledge). Could be a list. - Benefits: list. - Pay: base salary range and additional compensation components. We must not include sections with filler like "commensurate with experience". The pay section includes base salary range and note "commensurate with experience and qualifications." That's not filler; it's part of the description. We can include that. We must not include Schedule section because no specific schedule info. Now we need to strip boilerplate: remove EEO, visa sponsorship note, AI tools note, diversity statement, accommodation request, equal opportunity employer, etc. Also remove duplicated lines? Not seeing duplicates. Now produce HTML fragment. Structure:

      About the role

      Caylent is an AI-first cloud services company ... (company description) ... The Mission We are seeking a talented Senior Project Manager ... (maybe include mission paragraph). We'll combine into prose. Better to keep mission as part of About the role. Let's craft About the role paragraph: Caylent is an AI-first cloud services company that helps organizations turn ambitious ideas into meaningful business impact. As an AWS Premier Tier Services Partner and a charter member of Anthropic’s Claude Partner Network, we combine deep expertise in AWS, artificial intelligence, and Anthropic’s Claude platform to help customers modernize their technology, build intelligent products, and move AI from experimentation into production. Our capabilities span generative and agentic AI, cloud migration and modernization, cloud-native application development, data and analytics, DevOps, managed services, security and compliance, and customer experience transformation. At Caylent, our people always come first. We are a fully remote global company with employees in Canada, the United States and Latin America. We celebrate the culture of each of our team members and foster a community of technological curiosity. Come talk to us to learn more about what it means to be a Caylien! The Mission: We are seeking a talented Senior Project Manager to join our growing Customer Engineering team. The right candidate is someone who can lead the planning, implementation, and development of cloud-based contact center solutions for our clients. You will be responsible for guiding cross-functional teams through the full lifecycle of Amazon Connect deployments, ensuring successful implementation and adoption. This role requires both technical depth in AWS services and strong project management capabilities to deliver exceptional customer experiences. That seems good. Now Responsibilities: we need to list bullet items from "Your Assignment". Let's extract each bullet: Project Management & Client Engagement: - Lead end-to-end project management for Amazon Connect implementations from initial discovery to successful client handoff - Develop comprehensive project plans with clear milestones, deliverables, and resource allocations aligned with Pronetx's delivery methodology - Build strong client relationships as the primary technical point of contact during implementation projects - Facilitate effective communication among stakeholders, Pronetx technical teams, and client stakeholders - Conduct regular status meetings and provide clear, concise updates to both Pronetx leadership and client teams - Manage project scope, schedule, and budget while maintaining Pronetx's high standards for quality - Identify, assess, and mitigate project risks and dependencies proactively Technical Implementation: - Oversee the technical implementation of Amazon Connect and integrated AWS services - Guide the design and configuration of contact flows, queues, and routing strategies based on client requirements - Coordinate the integration of Amazon Connect with client CRM systems, knowledge bases, and other enterprise applications - Lead implementations of AI/ML-powered features using Amazon Lex, Amazon Polly, and other AWS services - Ensure implementations follow AWS best practices for security, reliability, and operational excellence - Validate technical solutions against client requirements and performance expectations - Coordinate testing efforts across functional, performance, and user acceptance testing phases Solution Development: - Collaborate with Pronetx solutions architects to design custom CX solutions that leverage the full AWS ecosystem - Manage the development of custom components, extensions, and integrations for client-specific needs - Oversee the implementation of analytics and reporting solutions using Amazon Kinesis, Amazon S3, and Amazon QuickSight - Guide the development of CI/CD pipelines for Amazon Connect solutions deployment and updates - Ensure solutions are built with scalability, resilience, and future extensibility in mind - Coordinate knowledge transfer to client teams and Pronetx managed services teams Continuous Improvement & Innovation: - Develop reusable implementation assets, templates, and best practices to enhance Pronetx's delivery capabilities - Document lessons learned and contribute to the organization's implementation methodology - Stay current with Amazon Connect feature releases and AWS service enhancements - Identify opportunities to improve implementation efficiency and quality - Contribute to Pronetx's thought leadership in the Amazon Connect and CX space - Participate in client-facing presentations and demonstrations of Pronetx solutions - Mentor junior team members on Amazon Connect best practices and implementation approaches We'll put all these as

      • under Responsibilities. Now Requirements (mandatory qualifications): list: - Bachelor's degree in Computer Science, Information Technology, or related field - 5+ years of experience in technical project management - 3+ years of experience with AWS cloud technologies - Experience with contact center technologies and customer experience solutions - Demonstrated experience managing complex technical implementations - Excellent communication skills with the ability to explain complex technical concepts to diverse audiences - Strong client relationship management capabilities - Project management certification (PMP, PRINCE2, Scrum Master, or equivalent) - Experience with Agile and Waterfall project management methodologies Now Qualifications (preferred): list: - AWS Certified Solutions Architect Associate or Professional certification - Experience implementing or working with Amazon Connect - Deep knowledge of AWS services including Lambda, API Gateway, DynamoDB, S3, Kinesis, and CloudFormation - Experience with IVR systems, CTI integrations, and telephony technologies - Familiarity with AI/ML technologies such as natural language understanding and speech recognition - Experience with CRM platforms (Salesforce, Dynamics, ServiceNow, etc.) - Knowledge of scripting languages (Python, Node.js) and infrastructure as code tools - Contact center operations or customer service experience Now Skills: technical knowledge requirements (Amazon Connect Expertise and AWS Services Integration Knowledge). Could be two subheadings but we just need a list. List: Amazon Connect Expertise: - Contact Flow design and implementation - Queue configuration and routing strategies - IVR design and development - Agent workspace customization - Reporting and analytics capabilities - Task creation and management - Outbound campaigns - Contact Lens implementation and analysis AWS Services Integration Knowledge: - Amazon Lex for building conversational interfaces - Amazon Polly for text-to-speech capabilities - AWS Lambda for serverless compute functions - Amazon Kinesis for real-time data streaming - Amazon S3 for data storage - Amazon DynamoDB for NoSQL database requirements - Amazon QuickSight for analytics and visualization - AWS Identity and Access Management (IAM) for security - Amazon CloudWatch for monitoring and observability - AWS CloudFormation for infrastructure as code - Amazon API Gateway for API management - AWS Step Functions for workflow orchestration - Amazon EventBridge for event-driven architectures We can flatten into a single list or keep subheadings as

        then

        . The instruction: Use
        • for any list of duties/requirements/benefits, and

          for prose. So we can have a

          for heading like "Amazon Connect Expertise:" then a

          • . That's okay. Now Benefits: list: - Medical insurance for you and eligible dependents - 401k plan with company match up to 4% and immediate vesting - Competitive phantom equity - Company-issued laptop - Dental and vision insurance - Term disability and life insurance - Flexible Spending Account - Equipment and office stipend - Annual stipend for learning and development - Unlimited paid time off - 10 paid holidays Now Pay: we need