Technical Account Manager

We need to output HTML fragment with sections: About the role (but we shouldn't repeat job title; we can use heading "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include headings for sections that have content. We need to parse the posting. Content: - About the Role: paragraph describing role, plus note about travel flexibility. - What You’ll Do: list of duties (lead software implementation, consult, troubleshoot, collaborate). Should be

• . - Who You Are: list of qualifications/requirements (Bachelor's degree, 2 years experience, advanced knowledge of Yardi domain, etc). Should be list. - Ideal to Have: list of nice-to-have (ability to configure networks, experience with HTML/Cloud Services, Real Estate runs on Yardi). Might be considered "Skills" or "Qualifications"? Could be separate "Preferred Qualifications". But we have limited headings: Skills, Requirements, Qualifications. Could put under "Qualifications" the required, and maybe "Preferred Qualifications" as a subsection? But we only output headings; we could combine required and preferred into one "Qualifications" list, but we need to preserve all info. Could separate into "Requirements" (mandatory) and "Preferred Qualifications" (maybe as "Skills"?). The instruction: Prefer a few substantive sections over many thin ones. So maybe combine into "Qualifications" covering both required and preferred, but we need to differentiate? Not required. Could just list all bullet points under "Qualifications". However we also have "Skills" heading for skill-based items like proficiency in Microsoft 365, etc. Could separate. Let's extract: About the Role paragraph: "Join our team as a Technical Account Manager, where you’ll serve as a trusted resource helping clients get the most out of their software. By developing and maintaining expert-level knowledge of our products, you’ll support users with thoughtful solutions, guide them through training, and help streamline their operations. From supporting system implementation to building strong client relationships, you'll play a key role in ensuring businesses run smoothly and efficiently. If you enjoy learning, sharing your knowledge, and making a real impact, this role could be a great fit for you! *** This position requires flexibility for travel during the second week of employment for training purposes. Training may be conducted locally or at an alternate location based on business needs. Candidates should be prepared and available to travel as required during this time." We need to preserve all substantive info, but remove *** markers. So combine into a paragraph. What You’ll Do bullets: - Lead software implementation, configuration, and deployment to ensure clients get the most out of Yardi products. - Consult with clients to understand their needs, advise on best practices, and deliver strategic, customized solutions. - Troubleshoot and resolve complex software issues, serving as a trusted technical resource for clients and internal teams. - Collaborate across teams to identify opportunities that drive success and continuous improvement for your assigned clients. Who You Are (requirements): - Bachelor’s Degree in Business, Finance, Math, or Computer/Engineering Sciences; or an equivalent combination of education and experience - Two (2) years of technical or client support experience - Advanced knowledge of Yardi domain or significant experience in relevant industry - Demonstrated ability to independently manage and resolve client issues and requests - Advanced technical and product knowledge of one or more Yardi software products - Knowledge of accounting practices - Understanding of the property management or relevant Yardi supported industry and industry best practices - Competence in one or more of the following areas: Microsoft operating and network system operation, relational databases, or SQL/Oracle language - Independent, sound decision making, critical thinking, and problem-solving skills - Proven time management and organization skills - Excellent written and oral communication skills - Client-centered commitment and focus - Excellent interpersonal skills - Ability to meet critical deadlines and prioritize multiple tasks in a fast-paced environment - Collegial, team-oriented disposition with the ability to establish cooperative working relationships with all levels of employees and clients - Proficiency in Microsoft 365 desktop applications Ideal to Have: - Ability to configure and manage networks and peripherals - Experience with HTML/Cloud Services - Real Estate runs on Yardi. (This seems like a tagline; maybe it's a bullet? It's a sentence but could be considered a bullet. We'll keep as bullet.) About Us paragraph: description of Yardi, benefits, etc. This could be "About the Company" but not in allowed headings. Could be omitted? The instruction: include a section ONLY when the posting has real, specific content for it. We have content about company, but not a standard heading. Could we put under "About the Role"? No. Could we create a section "About the Company"? Not in allowed list. Probably we should omit because not in allowed headings. However we must preserve ALL substantive information; but we cannot invent headings not allowed. The allowed headings list is examples; maybe we can use other headings if appropriate? The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive. But they say "Prefer a few substantive sections over many thin ones." So we could add an "About the Company" heading if needed. However they also say "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we can add other headings as needed. Thus we can have sections: About the Role, Responsibilities (What You’ll Do), Qualifications (Who You Are + Ideal to Have), Benefits (from About Us), maybe Pay (Annual Salary Range), Schedule? Not present. So we omit Schedule. We need to extract Benefits: from About Us: "We offer a dynamic work environment, comprehensive training programs, and abundant opportunities for career growth." Also "We prioritize your well-being with comprehensive benefits, including 100% paid employee medical premiums, company profit-sharing plan, and flexible work arrangements." Also philanthropic stuff maybe not benefits. We'll include those. Pay: Annual Salary Range: $75,000 – $78,800. Now we need to output HTML fragment only, no markdown fences. Let's craft:

  About the Role

  Join our team as a Technical Account Manager, where you’ll serve as a trusted resource helping clients get the most out of their software. By developing and maintaining expert-level knowledge of our products, you’ll support users with thoughtful solutions, guide them through training, and help streamline their operations. From supporting system implementation to building strong client relationships, you'll play a key role in ensuring businesses run smoothly and efficiently. If you enjoy learning, sharing your knowledge, and making a real impact, this role could be a great fit for you! This position requires flexibility for travel during the second week of employment for training purposes. Training may be conducted locally or at an alternate location based on business needs. Candidates should be prepared and available to travel as required during this time.

  Responsibilities

  • Lead software implementation, configuration, and deployment to ensure clients get the most out of Yardi products.
  • Consult with clients to understand their needs, advise on best practices, and deliver strategic, customized solutions.
  • Troubleshoot and resolve complex software issues, serving as a trusted technical resource for clients and internal teams.
  • Collaborate across teams to identify opportunities that drive success and continuous improvement for your assigned clients.

  Qualifications

  • Bachelor’s Degree in Business, Finance, Math, or Computer/Engineering Sciences; or an equivalent combination of education and experience
  • Two (2) years of technical or client support experience
  • Advanced knowledge of Yardi domain or significant experience in relevant industry
  • Demonstrated ability to independently manage and resolve client issues and requests
  • Advanced technical and product knowledge of one or more Yardi software products
  • Knowledge of accounting practices
  • Understanding of the property management or relevant Yardi supported industry and industry best practices
  • Competence in one or more of the following areas: Microsoft operating and network system operation, relational databases, or SQL/Oracle language
  • Independent, sound decision making, critical thinking, and problem-solving skills
  • Proven time management and organization skills
  • Excellent written and oral communication skills
  • Client-centered commitment and focus
  • Excellent interpersonal skills
  • Ability to meet critical deadlines and prioritize multiple tasks in a fast-paced environment
  • Collegial, team-oriented disposition with the ability to establish cooperative working relationships with all levels of employees and clients
  • Proficiency in Microsoft 365 desktop applications
  • Ability to configure and manage networks and peripherals (ideal to have)
  • Experience with HTML/Cloud Services (ideal to have)
  • Real Estate runs on Yardi (ideal to have)
  But mixing ideal to have inside qualifications may be confusing. Perhaps better to have separate "Preferred Qualifications" heading. But not in list. Could use "Skills" for ideal to have? However skills heading is for skill-based items. The ideal to have includes ability to configure networks, experience with HTML/Cloud Services, and a tagline. Could go under "Skills". Let's think. We have skill items: proficiency in Microsoft 365 desktop applications (already in qualifications). Also ability to configure and manage networks and peripherals, experience with HTML/Cloud Services. Those are skills. So we could move those to a "Skills" section. The tagline "Real Estate runs on Yardi" is not a skill; maybe we can drop as it's just a slogan. But we must preserve ALL substantive information; is that substantive? It's more of a tagline; maybe it's not essential. Could be considered fluff. Might be okay to drop? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. The tagline is not substantive detail about job; it's a marketing line. Could be considered boilerplate? Not exactly. But it's a short phrase; maybe we can keep as a bullet under "Ideal to Have" but we don't have that heading. Could we add a heading "Ideal to Have"? Not in examples but could be allowed as it's a section heading. The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but they gave examples. Safer to stick to those headings. So we need to fit the ideal to have items into existing headings: Skills, Qualifications, etc. Thus we can put ability to configure networks and experience with HTML/Cloud Services under Skills. The tagline maybe we can drop as not substantive. But to be safe, we could include it as a bullet under Skills as well, though it's not a skill. Might be odd. Alternatively, we could create a section "About the Company" for the About Us paragraph, and keep the tagline there. But we already have About Us paragraph; we could put that under "About the Company". That would preserve the tagline as part of that paragraph. Let's do that: Add

  About the Company

  with the About Us paragraph (including the tagline). That seems reasonable and not conflicting with examples (they didn't list About the Company but it's similar to About the Role). The instruction didn't forbid; they gave examples but not exclusive. So we can add. Thus sections: About the Role, Responsibilities, Qualifications, Skills, Benefits, Pay, About the