IT Support Engineer

We need to output HTML fragment with sections: About the role? The posting includes "Company Overview", "What you'll do", "Responsibility", "Job Designation", "What you bring" (Basic, Preferred), "Wage Transparency Pay", "Benefits", "Work Authorization Notice", "Life at Docusign", "Accommodation", "Applicant and Candidate Privacy Notice", "States Not Eligible for Employment", "Equal Opportunity Employer", "EEO Know Your Rights poster". We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove "Work Authorization Notice"? That's legal? It's about work authorization; maybe considered legal boilerplate? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Work Authorization Notice is legal; likely remove. Also "Accommodation" maybe also legal? It's about accommodation request; could be considered legal but maybe keep? It's about providing accommodations; might be considered EEO? Probably remove as boilerplate. "Applicant and Candidate Privacy Notice" also legal. "States Not Eligible for Employment" also legal. "Equal Opportunity Employer" definitely boilerplate. "EEO Know Your Rights poster" boilerplate. So we keep: Company Overview, What you'll do, Responsibility, Job Designation, What you bring (Basic, Preferred), Wage Transparency Pay, Benefits, Life at Docusign (maybe keep as culture). Also maybe "Work Authorization Notice" removed. We must not repeat job title as heading. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we need to map content to these headings. The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings if we have content. We need to decide which sections we have content for. We have: - About the role: could be Company Overview + What you'll do? Actually "About the role" could be a summary of role. We have "What you'll do" describing role. Could treat that as About the role. - Responsibilities: we have a "Responsibility" section with bullet points (actually paragraph with multiple responsibilities separated by line breaks). We'll convert to

• . - Requirements: we have "What you bring" Basic (required) and Preferred (preferred). Could split into Requirements (basic) and Qualifications/Skills (preferred). The instruction list includes Requirements, Qualifications, Skills. We can map Basic to Requirements, Preferred to Qualifications and Skills maybe combined. - Benefits: we have Benefits section. - Pay: we have Wage Transparency Pay. - Schedule: we have Job Designation (Hybrid) describing schedule: minimum 2 days per week in-office. That's schedule info. Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not emit empty sections. Ensure each has substantive content. We need to preserve all substantive information, not invent or summarize away detail. So we need to include all details from those sections. Let's extract content. Company Overview: "Docusign brings agreements to life. Over 1.5 million customers and more than a billion people in over 180 countries use Docusign solutions to accelerate the process of doing business and simplify people’s lives. With intelligent agreement management, Docusign unleashes business-critical data that is trapped inside of documents. Until now, these were disconnected from business systems of record, costing businesses time, money, and opportunity. Using Docusign’s Intelligent Agreement Management platform, companies can create, commit, and manage agreements with solutions created by the #1 company in e-signature and contract lifecycle management (CLM)." What you'll do: "We're looking for an IT Support Engineer to join our team, working out of our Seattle office and servicing our employees. The IT Support Engineer is dedicated to meeting the expectations and requirements of internal customers, delivering IT services, acting with customers in mind, establishing and maintaining effective relationships with customers and gaining their trust and respect. They will influence and assist in transitioning manual workflows and processes onto semi/fully automated self-service platforms for common IT end-user requests." That's the role description. Responsibility: list of duties: - Provide technical support to end users, with a focus on VIPs and Senior Executives, resolving hardware, software, and network issues in a timely manner, and managing associated ticket queues - Support Executive meetings in our executive meeting spaces, utilizing your expertise in AV support - Collaborate with cross-functional teams to identify and execute opportunities for automation and process improvement in IT services and workplace technology - Onboard new employees, including setup of systems and delivering training on workplace technology - Create documentation and training materials to support end users and internal IT teams, contributing to policies and procedures across the company, especially regarding workplace technology and office/real estate changes - Stay current with industry trends and best practices in IT automation, support, and workplace technology, recommending innovative solutions to enhance efficiency and productivity - Act as a lead in partnership with our Workplace Technology Team - Liaise between the IT and Network teams to support office upgrades, switch changes, and office buildouts, and office decommissioning activities We need to put each as
• . Job Designation: "Hybrid: Employee divides their time between in-office and remote work. Access to an office location is required. (Frequency: Minimum 2 days per week; may vary by team but will be weekly in-office expectation) Positions at Docusign are assigned a job designation of either In Office, Hybrid or Remote and are specific to the role/job. Preferred job designations are not guaranteed when changing positions within Docusign. Docusign reserves the right to change a position's job designation depending on business needs and as permitted by local law." We need schedule info: basically hybrid with min 2 days per week in-office. What you bring Basic: - Basic Bachelor's degree in Computer Science, Information Technology, or related field - Experience with Windows and Mac client systems administration - Experience delivering world class Executive support to Senior leadership - Experience with AV support and troubleshooting - Experience leading office relocations, commissioning and decommissioning of locations and work spaces Preferred: - Highly organized and excellent oral and written communication skills - Strong troubleshooting and problem-solving skills, resiliency in the face of continual change, and ability to handle high demands - Must be able to work a flexible schedule, including overtime and after-hours work - Excellent problem-solving skills and willingness and ability to rapidly learn new technologies and toolsets - Good operational understanding of Azure AD, Okta, ServiceNow, JIRA and Confluence - Strong team player but also able to work independently with minimal supervision - Ability to multi-task and scale quickly in a fast-paced environment - Vendor management experience interacting with and managing relationships with IT hardware and software vendors - Innovative skills and self-confidence needed - Interest in the way organizational processes work - Availability to travel on a periodic basis - ITIL certifications - Strong analytical skills for reporting and root-cause analysis We need to map Basic to Requirements, Preferred to Qualifications and Skills. Could split: Requirements = Basic; Qualifications = Preferred (maybe split into Qualifications and Skills). But we can also put all Preferred under Qualifications and Skills combined? The instruction list includes Qualifications and Skills as separate headings. We could put some under Qualifications (e.g., certifications, understanding of tools) and Skills (communication, troubleshooting). But to avoid over-splitting, we could put all Preferred under Qualifications and leave Skills empty? But we must not emit empty headings. So we need to decide a split that yields substantive content for each heading we use. We could use: - Requirements: Basic (bullet list) - Qualifications: Preferred items that are certifications/knowledge: "Good operational understanding of Azure AD, Okta, ServiceNow, JIRA and Confluence", "ITIL certifications", "Strong analytical skills for reporting and root-cause analysis" - Skills: Preferred items that are soft skills: "Highly organized and excellent oral and written communication skills", "Strong troubleshooting and problem-solving skills, resiliency in the face of continual change, and ability to handle high demands", "Must be able to work a flexible schedule, including overtime and after-hours work", "Excellent problem-solving skills and willingness and ability to rapidly learn new technologies and toolsets", "Strong team player but also able to work independently with minimal supervision", "Ability to multi-task and scale quickly in a fast-paced environment", "Vendor management experience interacting with and managing relationships with IT hardware and software vendors", "Innovative skills and self-confidence needed", "Interest in the way organizational processes work", "Availability to travel on a periodic basis" That seems reasonable. Now Benefits: list: - Paid Time Off: earned time off, as well as paid company holidays based on region - Paid Parental Leave: take up to six months off with your child after birth, adoption or foster care placement - Full Health Benefits Plans: options for 100% employer paid and minimum employee contribution health plans from day one of employment - Retirement Plans: select retirement and pension programs with potential for employer contributions - Learning and Development: options for coaching, online courses and education reimbursements - Compassionate Care Leave: paid time off following the loss of a loved one and other life-changing events We'll put as
  • . Pay: "Wage Transparency Pay for this position is based on a number of factors including geographic location and may vary depending on job-related knowledge, skills, and experience. Based on applicable legislation, the below details pay ranges in the following locations: Washington, : $34.90/hour - $48.38/hour This Role Is Also Eligible For The Following Bonus: Sales personnel are eligible for variable incentive pay dependent on their achievement of pre-established sales goals. Non-Sales roles are eligible for a company bonus plan, which is calculated as a percentage of eligible wages and dependent on company performance." We need to preserve that exactly. Note there is a weird "Washington, :" maybe a typo but we keep. Schedule: from Job Designation: "Hybrid: Employee divides their time between in-office and remote work. Access to an office location is required. (Frequency: Minimum 2 days per week; may vary by team but will be weekly in-office expectation)". We'll keep that. Now About the role: we could combine Company Overview and What you'll do? But About the role likely should be a summary of the role, not company overview. However we have no separate "About the role" besides What you'll do. Could treat Company Overview as About the company, not role. But we need a heading About the role; we can use What you'll do as About the role. That's fine. We must not repeat job title as heading. So we won't. Now output HTML fragment: sections each with

    heading then content. For About the role: we can put

    containing the What you'll do text. For Responsibilities:

    Responsibilities

    then
    • ... each duty. For Requirements:

      Requirements

      then
      • basic items. For Qualifications:

        Qualifications

        then
        • selected preferred items. For Skills:

          Skills

          then
          • remaining preferred items. For Benefits:

            Benefits

            then
            • . For Pay:

              Pay

              then

              (the wage text). For Schedule:

              Schedule

              then

              (the hybrid text). We must ensure we don't include any boilerplate like "Work Authorization Notice", etc. Now check for duplicated lines: none. Now produce HTML. Let's craft. About the role