Technical Account Manager
for headings. Use - for lists. Use
for prose. Remove boilerplate like EEO, etc. Also remove navigation, cookie, legal, duplicated lines, application instructions. We need to preserve all substantive information.
Let's parse the posting.
First paragraph: "About Harmony Harmony gives every employee an always-on expert for every service request, inside the tools they already use. Deployed inside Slack and Microsoft Teams, its agents draw on a context graph connecting each employee's identity, devices, applications, and history, resolving requests across IT, HR, finance, procurement, and legal automatically, before a ticket ever opens. With 100+ prebuilt agents that deploy in days, not months, and a 70% no-touch resolution rate, Harmony removes the manual work from enterprise service without removing the humans who should own the hard problems. Built for IT and HR teams that are done waiting for their service platform to catch up with the rest of the business."
That's about the company. Not a section heading we need? The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we likely don't need an "About Harmony" heading. The content about the company could be placed maybe in a
before sections? The instruction says output only HTML fragment, no extra headings. It didn't forbid other content. We can include a
about the company before sections. But we must not repeat job title. There's no explicit job title given in the snippet; maybe it's implied "Technical Account Manager". We should not repeat it as heading.
Next: "About The Role Harmony is building an enterprise service management platform that runs itself. We need a Technical Account Manager who owns the full post-sale technical relationship with our customers, from making sure the product works to making sure they're getting real value from it. This role blends technical support with strategic account management. You'll troubleshoot issues, drive adoption, monitor customer health, and be the person our customers trust to keep things running and growing. When a customer needs help, you're the first call. When a customer is at risk, you're the one who catches it early. There's a lot of room to grow here, and we'll make sure you have the support and ownership to do it from day one."
That's about the role. So we can have
About the role
then a with that prose.
Next: "What You’ll Do Own the ongoing relationship with a portfolio of customers, serving as their primary technical point of contactDrive product adoption and usage, ensuring customers are getting full value from the platform and discovering capabilities they haven't explored yetMonitor customer health proactively: track engagement patterns, flag risks early, and intervene before small issues become big problemsTroubleshoot technical issues across the platform, including configuration problems, integration errors, and unexpected behaviorReproduce, document, and escalate bugs to Engineering with clear steps and contextHelp build the internal infrastructure that supports the customer experience: implementing and configuring the tools, systems, and processes the team relies on as we scaleBuild dashboards, reports, and internal tooling to track customer health, support trends, and account metrics, making the data accessible and actionable for the teamContribute to and maintain internal documentation, runbooks, and knowledge base articlesCollaborate with Solution Engineering during onboarding and implementation to provide continuity into the post-sale relationshipSurface customer feedback and usage patterns to Product and Engineering to inform the roadmap"
These are duties/responsibilities. So we can have
Responsibilities
then a - for each bullet. Need to split by the sentences. Let's list them:
- Own the ongoing relationship with a portfolio of customers, serving as their primary technical point of contact
- Drive product adoption and usage, ensuring customers are getting full value from the platform and discovering capabilities they haven't explored yet
- Monitor customer health proactively: track engagement patterns, flag risks early, and intervene before small issues become big problems
- Troubleshoot technical issues across the platform, including configuration problems, integration errors, and unexpected behavior
- Reproduce, document, and escalate bugs to Engineering with clear steps and context
- Help build the internal infrastructure that supports the customer experience: implementing and configuring the tools, systems, and processes the team relies on as we scale
- Build dashboards, reports, and internal tooling to track customer health, support trends, and account metrics, making the data accessible and actionable for the team
- Contribute to and maintain internal documentation, runbooks, and knowledge base articles
- Collaborate with Solution Engineering during onboarding and implementation to provide continuity into the post-sale relationship
- Surface customer feedback and usage patterns to Product and Engineering to inform the roadmap
Now "Required Qualifications What We’re Looking For 2+ years of experience in technical account management, customer success, solutions consulting, support engineering or a related customer-facing technical roleStrong technical foundation: comfortable working with APIs, integrations, cloud infrastructure, and debugging issues across complex systemsAbility to manage a portfolio of accounts and prioritize across competing needs without dropping the ballClear communication skills, both in writing and in person. You need to be someone a VP of IT trusts as much as a support technician doesProactive mindset. You catch problems before customers report them, and you think about adoption and health without being askedExperience using AI tools (Claude, ChatGPT, Copilot) as a natural part of how you work"
These are qualifications/requirements. Could split into Requirements and Qualifications? The instruction says we can have sections Requirements, Qualifications, Skills. We need to decide what goes where. Usually "Required Qualifications" is qualifications. Could treat as Qualifications. Also "Preferred Qualifications" later.
We have "Preferred Qualifications Familiarity with ITSM concepts and enterprise IT environmentsExperience with tools like ServiceNow, Jira Service Management, Freshservice, Okta, or similarExposure to scripting or programming (Python, JavaScript, Bash, SQL)Previous experience at a B2B SaaS company"
Then "What We Offer Competitive salary and benefits packageComprehensive health, dental, and vision benefits401(k) with company matchA collaborative, fast-moving team in Downtown Manhattan"
That's benefits. Also maybe Pay? Not explicit salary number. So we should not create Pay section unless posting actually states them. It says "Competitive salary and benefits package" but no specific salary. According to instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. It says "Competitive salary and benefits package" is a statement but not a specific number. Is that considered filler? It's vague but it's stating that there is a competitive salary and benefits package. The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits package, but not specifics. However we have a Benefits section maybe we can include because they list specific benefits: health, dental, vision, 401(k) with match, collaborative team location. That's substantive. So we can create Benefits section with those details. Pay section: they only say "Competitive salary and benefits package" without number; that's vague; better to omit Pay section. Schedule: not mentioned, omit.
Now we need to decide sections: About the role, Responsibilities, Requirements (maybe required qualifications), Qualifications (maybe preferred qualifications?), Skills (maybe technical skills?), Benefits.
We could combine required and preferred into Qualifications and maybe Skills separate. But we need to avoid thin sections. Let's think.
We have Required Qualifications list: 2+ years experience, strong technical foundation (APIs, integrations, cloud infra, debugging), ability to manage portfolio, clear communication, proactive mindset, experience using AI tools.
Preferred Qualifications: familiarity with ITSM concepts, experience with tools like ServiceNow etc, exposure to scripting/programming, previous experience at B2B SaaS.
Skills could be derived from those: technical foundation, communication, etc. But we could just have Requirements (required) and Qualifications (preferred). Or we could have Requirements (required) and Skills (technical skills). Let's see instruction: they gave example headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can use all if we have content.
We need to avoid filler. Let's assign:
- Requirements: the required qualifications (2+ years experience, technical foundation, manage portfolio, communication, proactive, AI tools experience). Could be list.
- Qualifications: the preferred qualifications (ITSM familiarity, tools experience, scripting exposure, B2B SaaS experience). Could be list.
- Skills: maybe we could extract specific skills like APIs, integrations, cloud infrastructure, debugging, ServiceNow, Jira, Freshservice, Okta, Python, JavaScript, Bash, SQL, etc. But that may be redundant. Better to omit Skills if it would be thin. However we have technical foundation etc already in Requirements. Could still have Skills as a list of specific technical skills: APIs, integrations, cloud infrastructure, debugging, ServiceNow, Jira Service Management, Freshservice, Okta, Python, JavaScript, Bash, SQL. That seems substantive. But we need to ensure we are not inventing; we can pull from the text. The text mentions: "comfortable working with APIs, integrations, cloud infrastructure, and debugging issues across complex systems" (that's technical foundation). Also "Experience with tools like ServiceNow, Jira Service Management, Freshservice, Okta, or similar". Also "Exposure to scripting or programming (Python, JavaScript, Bash, SQL)". So we can list those as skills.
Thus we can have Skills section with those items.
Now Benefits: we have "Competitive salary and benefits packageComprehensive health, dental, and vision benefits401(k) with company matchA collaborative, fast-moving team in Downtown Manhattan". We should split into list items: Competitive salary and benefits package (though vague), Comprehensive health, dental, and vision benefits, 401(k) with company match, A collaborative, fast-moving team in Downtown Manhattan. The first item is vague but still stated. Could keep it. However instruction says avoid filler like "competitive salary" maybe considered filler? It's not a specific number but it's a statement. It's not "commensurate with experience" etc. It's okay maybe. But we could combine into a paragraph. Safer to include as a
maybe. But we need to use
- for any list of duties/requirements/benefits. Benefits is a list, so we should use
- . The first item "Competitive salary and benefits package" is vague but it's still a benefit statement. I'd include it.
Now we need to ensure we don't include boilerplate like EEO etc. Remove that.
Now produce HTML fragment.
Structure:
About Harmony ...
maybe.
Then About the role
...
Then Responsibilities
- ...
...
Then Requirements
- ...
...
Then Qualifications
- ...
...
Then Skills
- ...
...
Then Benefits
- ...
...
We must not include Pay or Schedule.
Check for any duplicated lines: ensure we didn't repeat.
Now craft the prose.
About Harmony paragraph: combine the first paragraph.
About the role paragraph: combine the "About The Role" paragraph
for prose. Remove boilerplate like EEO, etc. Also remove navigation, cookie, legal, duplicated lines, application instructions. We need to preserve all substantive information. Let's parse the posting. First paragraph: "About Harmony Harmony gives every employee an always-on expert for every service request, inside the tools they already use. Deployed inside Slack and Microsoft Teams, its agents draw on a context graph connecting each employee's identity, devices, applications, and history, resolving requests across IT, HR, finance, procurement, and legal automatically, before a ticket ever opens. With 100+ prebuilt agents that deploy in days, not months, and a 70% no-touch resolution rate, Harmony removes the manual work from enterprise service without removing the humans who should own the hard problems. Built for IT and HR teams that are done waiting for their service platform to catch up with the rest of the business." That's about the company. Not a section heading we need? The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we likely don't need an "About Harmony" heading. The content about the company could be placed maybe in a
before sections? The instruction says output only HTML fragment, no extra headings. It didn't forbid other content. We can include a
about the company before sections. But we must not repeat job title. There's no explicit job title given in the snippet; maybe it's implied "Technical Account Manager". We should not repeat it as heading. Next: "About The Role Harmony is building an enterprise service management platform that runs itself. We need a Technical Account Manager who owns the full post-sale technical relationship with our customers, from making sure the product works to making sure they're getting real value from it. This role blends technical support with strategic account management. You'll troubleshoot issues, drive adoption, monitor customer health, and be the person our customers trust to keep things running and growing. When a customer needs help, you're the first call. When a customer is at risk, you're the one who catches it early. There's a lot of room to grow here, and we'll make sure you have the support and ownership to do it from day one." That's about the role. So we can have
About the role
then awith that prose. Next: "What You’ll Do Own the ongoing relationship with a portfolio of customers, serving as their primary technical point of contactDrive product adoption and usage, ensuring customers are getting full value from the platform and discovering capabilities they haven't explored yetMonitor customer health proactively: track engagement patterns, flag risks early, and intervene before small issues become big problemsTroubleshoot technical issues across the platform, including configuration problems, integration errors, and unexpected behaviorReproduce, document, and escalate bugs to Engineering with clear steps and contextHelp build the internal infrastructure that supports the customer experience: implementing and configuring the tools, systems, and processes the team relies on as we scaleBuild dashboards, reports, and internal tooling to track customer health, support trends, and account metrics, making the data accessible and actionable for the teamContribute to and maintain internal documentation, runbooks, and knowledge base articlesCollaborate with Solution Engineering during onboarding and implementation to provide continuity into the post-sale relationshipSurface customer feedback and usage patterns to Product and Engineering to inform the roadmap" These are duties/responsibilities. So we can have
Responsibilities
then a- for each bullet. Need to split by the sentences. Let's list them:
- Own the ongoing relationship with a portfolio of customers, serving as their primary technical point of contact
- Drive product adoption and usage, ensuring customers are getting full value from the platform and discovering capabilities they haven't explored yet
- Monitor customer health proactively: track engagement patterns, flag risks early, and intervene before small issues become big problems
- Troubleshoot technical issues across the platform, including configuration problems, integration errors, and unexpected behavior
- Reproduce, document, and escalate bugs to Engineering with clear steps and context
- Help build the internal infrastructure that supports the customer experience: implementing and configuring the tools, systems, and processes the team relies on as we scale
- Build dashboards, reports, and internal tooling to track customer health, support trends, and account metrics, making the data accessible and actionable for the team
- Contribute to and maintain internal documentation, runbooks, and knowledge base articles
- Collaborate with Solution Engineering during onboarding and implementation to provide continuity into the post-sale relationship
- Surface customer feedback and usage patterns to Product and Engineering to inform the roadmap
Now "Required Qualifications What We’re Looking For 2+ years of experience in technical account management, customer success, solutions consulting, support engineering or a related customer-facing technical roleStrong technical foundation: comfortable working with APIs, integrations, cloud infrastructure, and debugging issues across complex systemsAbility to manage a portfolio of accounts and prioritize across competing needs without dropping the ballClear communication skills, both in writing and in person. You need to be someone a VP of IT trusts as much as a support technician doesProactive mindset. You catch problems before customers report them, and you think about adoption and health without being askedExperience using AI tools (Claude, ChatGPT, Copilot) as a natural part of how you work"
These are qualifications/requirements. Could split into Requirements and Qualifications? The instruction says we can have sections Requirements, Qualifications, Skills. We need to decide what goes where. Usually "Required Qualifications" is qualifications. Could treat as Qualifications. Also "Preferred Qualifications" later.
We have "Preferred Qualifications Familiarity with ITSM concepts and enterprise IT environmentsExperience with tools like ServiceNow, Jira Service Management, Freshservice, Okta, or similarExposure to scripting or programming (Python, JavaScript, Bash, SQL)Previous experience at a B2B SaaS company"
Then "What We Offer Competitive salary and benefits packageComprehensive health, dental, and vision benefits401(k) with company matchA collaborative, fast-moving team in Downtown Manhattan"
That's benefits. Also maybe Pay? Not explicit salary number. So we should not create Pay section unless posting actually states them. It says "Competitive salary and benefits package" but no specific salary. According to instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. It says "Competitive salary and benefits package" is a statement but not a specific number. Is that considered filler? It's vague but it's stating that there is a competitive salary and benefits package. The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits package, but not specifics. However we have a Benefits section maybe we can include because they list specific benefits: health, dental, vision, 401(k) with match, collaborative team location. That's substantive. So we can create Benefits section with those details. Pay section: they only say "Competitive salary and benefits package" without number; that's vague; better to omit Pay section. Schedule: not mentioned, omit.
Now we need to decide sections: About the role, Responsibilities, Requirements (maybe required qualifications), Qualifications (maybe preferred qualifications?), Skills (maybe technical skills?), Benefits.
We could combine required and preferred into Qualifications and maybe Skills separate. But we need to avoid thin sections. Let's think.
We have Required Qualifications list: 2+ years experience, strong technical foundation (APIs, integrations, cloud infra, debugging), ability to manage portfolio, clear communication, proactive mindset, experience using AI tools.
Preferred Qualifications: familiarity with ITSM concepts, experience with tools like ServiceNow etc, exposure to scripting/programming, previous experience at B2B SaaS.
Skills could be derived from those: technical foundation, communication, etc. But we could just have Requirements (required) and Qualifications (preferred). Or we could have Requirements (required) and Skills (technical skills). Let's see instruction: they gave example headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can use all if we have content.
We need to avoid filler. Let's assign:
- Requirements: the required qualifications (2+ years experience, technical foundation, manage portfolio, communication, proactive, AI tools experience). Could be list.
- Qualifications: the preferred qualifications (ITSM familiarity, tools experience, scripting exposure, B2B SaaS experience). Could be list.
- Skills: maybe we could extract specific skills like APIs, integrations, cloud infrastructure, debugging, ServiceNow, Jira, Freshservice, Okta, Python, JavaScript, Bash, SQL, etc. But that may be redundant. Better to omit Skills if it would be thin. However we have technical foundation etc already in Requirements. Could still have Skills as a list of specific technical skills: APIs, integrations, cloud infrastructure, debugging, ServiceNow, Jira Service Management, Freshservice, Okta, Python, JavaScript, Bash, SQL. That seems substantive. But we need to ensure we are not inventing; we can pull from the text. The text mentions: "comfortable working with APIs, integrations, cloud infrastructure, and debugging issues across complex systems" (that's technical foundation). Also "Experience with tools like ServiceNow, Jira Service Management, Freshservice, Okta, or similar". Also "Exposure to scripting or programming (Python, JavaScript, Bash, SQL)". So we can list those as skills.
Thus we can have Skills section with those items.
Now Benefits: we have "Competitive salary and benefits packageComprehensive health, dental, and vision benefits401(k) with company matchA collaborative, fast-moving team in Downtown Manhattan". We should split into list items: Competitive salary and benefits package (though vague), Comprehensive health, dental, and vision benefits, 401(k) with company match, A collaborative, fast-moving team in Downtown Manhattan. The first item is vague but still stated. Could keep it. However instruction says avoid filler like "competitive salary" maybe considered filler? It's not a specific number but it's a statement. It's not "commensurate with experience" etc. It's okay maybe. But we could combine into a paragraph. Safer to include as a
maybe. But we need to use
- for any list of duties/requirements/benefits. Benefits is a list, so we should use
- . The first item "Competitive salary and benefits package" is vague but it's still a benefit statement. I'd include it.
Now we need to ensure we don't include boilerplate like EEO etc. Remove that.
Now produce HTML fragment.
Structure:
About Harmony ...
maybe. ThenAbout the role
...
ThenResponsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Skills
- ... ...
Benefits
- ... ...
- . The first item "Competitive salary and benefits package" is vague but it's still a benefit statement. I'd include it.
Now we need to ensure we don't include boilerplate like EEO etc. Remove that.
Now produce HTML fragment.
Structure:
- for any list of duties/requirements/benefits. Benefits is a list, so we should use