IT Systems Engineer

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We need to parse the posting. We have sections: About The Team, About The Role, How You'll Have An Impact, Requirements, Nice to have, Massachusetts Applicants (legal), Base Pay Range, Travel note, Get to Know Klaviyo, AI fluency, accommodations, etc. We need to map to allowed headings: About the role (we have About The Role), Responsibilities (maybe How You'll Have An Impact), Requirements (Requirements), Qualifications (maybe Nice to have?), Skills (maybe not separate), Benefits (maybe not explicit), Pay (Base Pay Range), Schedule (maybe not). Also we could have About the team? Not in allowed headings list; but we could treat as About the role? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not limited to those? Probably we should stick to those headings only. So we need to map content to those headings. We have About The Role content: we can put under

About the role

. Responsibilities: How You'll Have An Impact content. Requirements: Requirements section. Qualifications: Nice to have? Could treat as Qualifications. Skills: maybe we could extract skills from requirements? But we already have Requirements and Qualifications; maybe we can combine. However we should not create thin sections. If we don't have specific content for Skills, we should omit. Benefits: The posting mentions benefits in compensation package: "In addition to base salary, our total compensation package may include participation in the company’s annual cash bonus plan, variable compensation (OTE) for sales and customer success roles, equity, sign-on payments, and a comprehensive range of health, welfare, and wellbeing benefits based on eligibility." That's benefits info. So we can create Benefits section. Pay: Base Pay Range. Schedule: Not mentioned; maybe travel note? Not schedule. So omit Schedule. We also need to include minor metadata like Job ID etc? Not present. We must remove boilerplate: cookie/navigation/legal/EEO etc. Remove Massachusetts Applicants? That's legal but maybe we keep? It's a legal statement about Massachusetts law; could be considered boilerplate legal. Probably remove. Also remove equal opportunity, scam warning, etc. Also remove "Get to Know Klaviyo" maybe not needed? It's about company description; could be considered boilerplate? Might be considered substantive? It's generic marketing. Might be considered boilerplate; but we could keep as part of About the role? Not needed. Safer to omit. We need to preserve all substantive information; not invent or summarize away detail. So we need to keep details from sections we include. Let's extract content: About The Role: "As an IT Systems Engineer on the IT Systems team, you will help design, implement, and maintain the enterprise systems every Klaviyo depends on identity, endpoint management, and the SaaS platforms that run the company. You’ll contribute to projects that range from SSO/SCIM implementations to multi-tool integrations and automations, with a focus on scalability and efficiency. You’ll work closely with operations, engineering, and the IT Searchbar team to keep systems healthy and help work through technical escalations. Klaviyo is building an AI-first future, and IT is where a lot of that gets real. You will be expected to use AI in your day-to-day work to research, script, document, and troubleshoot faster, and to help bring AI-assisted workflows to the systems we run for the rest of the company. This is a hands-on, high-learning role for someone early in their systems career who wants to build depth quickly alongside senior engineers." We'll put that in

. Responsibilities (How You'll Have An Impact): List of bullet points: "Own your projects and tickets end to end from problem statement to rollout to documentation and when you see something broken, fix it or get it to the right owner rather than route around it. Ship changes quickly to systems that thousands of Klaviyos rely on, while testing your work, getting a peer review, and having a rollback plan before you touch production. Speed matters, and so does not skipping steps. Treat Klaviyos as your customers partner with stakeholders to build and improve the tooling, integrations, and documentation that make their work easier today and scale for where the business is headed. Leave behind clean configurations, least-privilege access, and runbooks and knowledge base articles good enough that the next person never has to ask you. Be clear on what success looks like for each project, and use ticket data, system telemetry, and adoption metrics to show the impact of what you built. Ramp on new platforms quickly, use AI to accelerate both your learning and your output, and treat feedback from your team as a gift." We need to format as

• each bullet. The bullet sentences may be long; we can split each sentence as separate
• . Let's parse: - Own your projects and tickets end to end from problem statement to rollout to documentation and when you see something broken, fix it or get it to the right owner rather than route around it. - Ship changes quickly to systems that thousands of Klaviyos rely on, while testing your work, getting a peer review, and having a rollback plan before you touch production. Speed matters, and so does not skipping steps. - Treat Klaviyos as your customers partner with stakeholders to build and improve the tooling, integrations, and documentation that make their work easier today and scale for where the business is headed. - Leave behind clean configurations, least-privilege access, and runbooks and knowledge base articles good enough that the next person never has to ask you. - Be clear on what success looks like for each project, and use ticket data, system telemetry, and adoption metrics to show the impact of what you built. - Ramp on new platforms quickly, use AI to accelerate both your learning and your output, and treat feedback from your team as a gift. We'll keep as is. Requirements: List of requirements bullet points. Let's extract: - 2+ years of hands-on experience in IT support, systems administration, or systems engineering, or equivalent practical experience through an apprenticeship, internship, help desk role, home lab, or certification-backed project work. - Working familiarity with the admin side of core SaaS platforms such as Google Workspace, Jamf, Slack, Atlassian, and Zoom. - Experience with problem identification and the ability to collaborate with stakeholders to find solutions. - Foundational understanding of IT systems, including enterprise device management, secure identity, and endpoint security. - Experience or familiarity with deploying and managing macOS and iOS devices through an MDM (Jamf preferred), including configuration profiles and policies. Exposure to Windows management such as Intune and Autopilot is a plus. - Interest in learning how to automate workflows and repetitive tasks. - Some experience with or willingness to learn IdP configuration, management, and maintenance, including SSO (SAML/OIDC) and SCIM provisioning. Experience with Okta or Entra ID (Azure AD) is a plus. - Understanding of the importance of clean, concise controls and easily editable security functionality within tools, and a willingness to support access reviews and audit evidence requests for SOC 2 and SOX. - AI proficiency: you already use AI as part of how you work. You are comfortable using LLM assistants and agents such as ChatGPT, Claude, Gemini, or Glean to research, draft and debug scripts, write documentation, and cut down repetitive work, and you can explain where AI accelerated you and where you applied your own judgment to verify its output. You are curious about applying AI to IT problems. - Foundational scripting skills with an interest in further developing these skills. Experience with Bash, PowerShell, or Python is a plus. - Familiarity with the identity lifecycle onboarding, role changes, and offboarding and why timely, accurate access matters. - Comfort reading API documentation and working with REST and JSON to connect systems together, or a clear appetite to learn. - A disciplined approach to change: you test before you deploy, document what you changed, and communicate clearly with the people it affects. - Strong written communication and a habit of documenting your work. - Participation in an after-hours on-call rotation with the IT Systems team is required for site-specific or business-blocking issues. We'll put each as
• . Qualifications (Nice to have): List: - Familiarity with SSO and automation solutions such as Workato, Okta Workflows, n8n, or similar. - Basic understanding of enterprise-scale networking topics including routing, DNS, DHCP, VPN, and corporate Wi-Fi. - Experience in a fast-paced, high-growth IT environment is preferred. - Interest in developing skills to build applications and tools that utilize APIs. - Familiarity with AWS and GCP concepts such as VPC, EC2, Security Groups, ACLs, and IAM is a plus. - Experience building with AI beyond the chat window prompt and context engineering, connecting an LLM to systems via APIs or MCP, or standing up an AI-assisted workflow or agent that saved real time. - Experience administering an ITSM or ticketing platform such as Freshservice or Jira Service Management, including forms, workflows, and reporting. - Relevant certifications such as Jamf 100/200, Okta Certified Professional, CompTIA A+, Network+, or Security+, or AWS, Azure, or Google Cloud fundamentals. We'll put as
• . Benefits: From text: "In addition to base salary, our total compensation package may include participation in the company’s annual cash bonus plan, variable compensation (OTE) for sales and customer success roles, equity, sign-on payments, and a comprehensive range of health, welfare, and wellbeing benefits based on eligibility." We'll put as

  maybe bullet list? Could be

  • but it's a sentence. We'll use

    . Pay: Base Pay Range For US Locations: $96,000—$144,000 USD We'll put as

    . We should not include schedule. We also need to include About the team? Not allowed heading; maybe we could incorporate into About the role? But we have About the role heading already; we could add a short paragraph about team under About the role? But we already have About the role content; we could add a separate

    About the team

    but not in allowed list; better to omit. We must not repeat job title as heading. We must output only HTML fragment. Let's construct:

    About the role

    ...

    Responsibilities

    • Own your projects and tickets end to end from problem statement to rollout to documentation and when you see something broken, fix it or get it to the right owner rather than route around it.
    • Ship changes quickly to systems that thousands of Klaviyos rely on, while testing your work, getting a peer review, and having a rollback plan before you touch production. Speed matters, and so does not skipping steps.
    • Treat Klaviyos as your customers partner with stakeholders to build and improve the tooling, integrations, and documentation that make their work easier today and scale for where the business is headed.
    • Leave behind clean configurations, least-privilege access, and runbooks and knowledge base articles good enough that the next person never has to ask you.
    • Be clear on what success looks like for each project, and use ticket data, system telemetry, and adoption metrics to show the impact of what you built.
    • Ramp on new platforms quickly, use AI to accelerate both your learning and your output, and treat feedback from your team as a gift.

    Requirements

    • 2+ years of hands-on experience in IT support, systems administration