AI Operator Lead 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 not repeat job title as heading. We need to include only sections with real specific content. We must preserve all substantive info, no boilerplate, no EEO, no navigation, no application instructions, no duplicated lines. Must not include Pay/Schedule/Benefits unless posting actually states them. The posting includes salary range: "The anticipated annual salary range for this position is between $165,000 - 253,000." Also mentions performance-based bonus, employee share purchase program, equity programs, medical/dental/vision insurance, paid time off, sick leave, tuition reimbursement, 401(k) contributions and employer match, flexible spending accounts, life insurance, disability coverage, commuter subsidy. So Benefits section exists. Pay section exists (salary range). Schedule? Not mentioned. Travel Requirements: "Boston-area candidates preferred Remote U.S. candidates will be considered Limited travel may be required for team collaboration, workshops, and business meetings." That's not schedule but travel. Not required to include schedule unless present. So we can omit Schedule. We need sections: About the role (maybe "About The Team" and "Position Summary" combined). Responsibilities (Key Responsibilities). Qualifications (Required and Preferred). Skills? Could be implied but we have qualifications. Could create Skills section for technical skills? But we must not create thin sections. Better to have Qualifications covering required and preferred. Could also have "What Success Looks Like" maybe as a separate section? Not in list of allowed headings but we could treat as "About the role" or "Responsibilities"? 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. We can map content: About the role: include introductory paragraphs about PTC, team, position summary. Responsibilities: Key Responsibilities bullet list. Qualifications: Required and Preferred bullet list. Benefits: list of benefits. Pay: salary range and bonus etc. Possibly also "Travel Requirements" could be under About the role or separate but not in allowed headings; maybe we can incorporate into About the role as a note. We must not include boilerplate like EEO, immigration sponsorship, privacy policy, etc. Also remove duplicated lines (like repeated EEO statements). Also remove application instructions like "What To Send Us" etc. That's application instructions; we must remove them. Also remove "What Success Looks Like" maybe considered part of responsibilities? It's not application instruction; it's description of success. Could be included under About the role or Responsibilities? Might be okay to include as a separate section "What Success Looks Like" but not in allowed headings. Safer to incorporate into About the role or Responsibilities. However the instruction says "Prefer a few substantive sections over many thin ones." So we can have About the role, Responsibilities, Qualifications, Benefits, Pay. That's five sections. We need to preserve all substantive information: we must keep details like AI Infrastructure team within Growth Marketing, mandate, etc. Also keep details about responsibilities bullet points. Keep qualifications bullet points. Keep benefits details. Keep pay range and bonus, ESPP, equity programs, insurance, 401k, etc. Also keep travel requirements? Might be considered part of About the role. We'll include a short paragraph under About the role about location/travel. We must not include repeated lines like "Applications will be accepted on an on-going basis." etc. Also not include "PTC is an Equal Opportunity Employer" etc. We must output only HTML fragment, no markdown fences. Let's craft. Structure:

About the role

... paragraphs ...

Responsibilities

• ... each bullet ...

Qualifications

• ... required ...
• ... preferred ...

Maybe separate Required and Preferred as subheadings? But we cannot add extra headings beyond h3? Could use inside li? Probably okay. Better: have two

with headings inside? But we must not create extra headings. Could just list all qualifications with indication. But we need to preserve required vs preferred. Could do:

Qualifications

Required:

...

Preferred:

...
That's fine.

Benefits

...

Pay

... salary range, bonus, ESPP, equity programs...

Make sure not to include any boilerplate. Let's extract substantive content. From posting: Intro: "Our world is transforming, and PTC is leading the way. Our software brings the physical and digital worlds together, enabling companies to improve operations, create better products, and empower people in all aspects of their business. Our people make all the difference in our success. Today, we are a global team of nearly 7,000 and our main objective is to create opportunities for our team members to explore, learn, and grow – all while seeing their ideas come to life and celebrating the differences that make us who we are and the work we do possible." Then "AI Operations Lead (AI Engineer, Marketing OS)" is job title (skip). Then "About PTC" paragraph: "PTC (NASDAQ: PTC) is a global industrial software company that enables manufacturers to transform how they design, make, operate, and service products. Our solutions are used by some of the world's leading companies across aerospace, automotive, electronics, medical devices, and industrial manufacturing. As a leader in digital transformation, PTC is investing in next-generation technologies, including artificial intelligence, automation, and cloud-native platforms, to drive innovation internally and for our customers." Then "About The Team": "You'll join the AI Infrastructure team within Growth Marketing, working across industry and vertical marketing, demand generation, product marketing, customer marketing, brand and communications, and marketing operations. Our mandate is to rebuild how marketing work gets done — moving from documents and manual handoffs to data, AI agents, and automated workflows. As one of the first hires on this team, you will help define and scale AI-powered marketing operations across the organization." Then "Position Summary": "PTC is seeking an Agentic Operator to design, build, deploy, and scale the AI-powered systems that run GrowthOS. You will partner with marketers, business stakeholders, and technical teams to identify automation opportunities, build intelligent workflows, and enable teams to operate more efficiently through AI-enabled tools. You will work directly with end users — embedding with marketing teams to understand their workflows, translate business challenges into technical solutions, and build systems that automate repetitive work so marketers can focus on strategy, judgment, and customer engagement." Then "Key Responsibilities" list bullet points (we need to capture each). Let's extract: - Design and build AI-powered workflows and agent-based systems supporting marketing operations - Build reusable agent architectures — skills, tools, memory, orchestration, evaluation frameworks, and guardrails - Maintain prompt libraries, workflow templates, and automation frameworks - Evaluate emerging AI technologies and recommend adoption opportunities - Build and maintain workflow automation using orchestration platforms such as n8n, Zapier, Make or Claude Code - Design end-to-end processes connecting data, AI agents, and business systems - Develop automation frameworks that scale across marketing functions - Integrate AI-powered solutions with Salesforce, Eloqua, SiteCore, and internal data platforms - Build MCPs, APIs, connectors, and automation frameworks supporting data-driven decisions - Ensure data quality, reliability, security, and scalability - Establish monitoring, logging, evaluation, and reporting for AI-powered systems - Build validation frameworks and quality controls for reliable outputs - Build governance mechanisms supporting compliance, brand integrity, and auditability - Identify system failures, regressions, and improvement opportunities - Partner with marketing teams to understand business objectives and challenges - Train and coach users on AI-enabled workflows and tools - Drive adoption and long-term utilization of AI solutions - Document processes, playbooks, and best practices to support scalability That's many. Then "What To Send Us" (application instructions) - remove. Then "Qualifications Required" list: - Bachelor's degree in Computer Science, Software Engineering, Information Systems, or related field, or equivalent practical experience - 5+ years of software engineering experience - 2+ years hands-on experience building and deploying production AI or LLM-powered applications - Strong Python development experience - Experience with LLM APIs (Anthropic Claude, OpenAI GPT, Gemini, etc…) - Experience with workflow automation/orchestration platforms (n8n, Airflow, Temporal, Zapier, or comparable) - Experience integrating enterprise applications, including CRM, marketing automation, and business systems - Strong understanding of prompt design, evaluation methodologies, and production AI operations - Excellent communication and stakeholder management skills Then "Preferred Experience" list: - Experience designing and deploying multi-agent systems - Knowledge of agent orchestration frameworks, MCP, and tool-use architectures - Experience implementing retrieval-augmented generation (RAG) - Familiarity with MLOps, evaluation frameworks, and AI observability platforms - Experience building internal platforms or tools with measurable organizational adoption - Experience in marketing technology, marketing operations, or demand generation - Experience implementing AI governance, validation, and audit-trail frameworks Then "What Success Looks Like" paragraphs (two similar). We can incorporate maybe under About the role or Responsibilities? Might be okay to include as a short paragraph under About the role: "Success looks like: agents live and running for priority verticals, with speed and quality gains measurable against baseline; net-new campaign delivery time reduced from months to weeks; marketing teams successfully adopting and expanding AI-driven workflows on their own; repeatable frameworks established for AI automation, governance, and performance measurement." Also second paragraph similar but we can combine. Then "Why Join PTC" paragraph: "Opportunity to help shape AI transformation within a global technology company; Work directly on highly visible initiatives with executive sponsorship; Influence how marketing operations evolve through AI and automation; Partner with business and technical leaders across the organization; Build innovative solutions with real-world impact at enterprise scale." Then "Travel Requirements": "Boston-area candidates preferred Remote U.S. candidates will be considered Limited travel may be required for team collaboration, workshops, and business meetings." Then benefits and pay. Benefits paragraph: "Employees also have the opportunity to become a PTC shareholder through our employee share purchase program (ESPP), which allows for the purchase of discounted PTC stock. Certain roles may also be eligible for participation in our equity programs. Employees may be eligible for medical, dental and vision insurance, paid time off and sick leave, tuition reimbursement, 401(k) contributions and employer match, flexible spending accounts, life insurance, disability coverage and, if you are an office-assigned employee, a generous commuter subsidy." Pay paragraph: "PTC carefully considers a wide variety of factors when determining compensation. The anticipated annual salary range for this position is between $165,000 - 253,000. The salary range reflects a good-faith estimate of compensation at the time of posting. Actual compensation may vary based on a candidate's skills, qualifications, experience, and location. Additionally, candidates may be eligible for a performance-based bonus." We should keep that. Now we need to strip out any duplicated lines: there were duplicates of EEO etc which we removed. Now produce HTML. We'll need to ensure we don't include any markdown fences. Let's craft. We'll have:

About the role

Our world is transforming, and PTC is leading the way. Our software brings the physical and digital worlds together, enabling companies to improve operations, create better products, and empower people in all aspects of