Technical Account Manager
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. 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. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to parse the posting.
Content:
"A Little About Us EDB provides a data and AI platform that enables organizations to harness the full power of Postgres for transactional, analytical, and AI workloads across any cloud, anywhere. EDB empowers enterprises to control risk, manage costs and scale efficiently for a data and AI led world. Serving more than 1,500 customers globally and as the leading contributor to the vibrant and fast-growing PostgreSQL community, EDB supports major government organizations, financial services, media and information technology companies. EDB’s data-driven solutions enable customers to modernize legacy systems and break data silos while leveraging enterprise-grade open source technologies. EDB delivers the confidence of up to 99.999% high availability with mission critical capabilities built in such as security, compliance controls, and observability. For more information, visit www.enterprisedb.com EDB is hiring a Technical Account Manager (TAM) for US. The TAM is responsible for building and maintaining post-sales relationships with EDB’s largest and most complex customers. These customers are typically large accounts adopting Postgres and AI solutions. The TAM serves as a trusted technical advisor to drive successful outcomes and to ensure that the customers become a positive reference and continue their journey on Postgres technology. The TAM is also the customer's primary point of contact into all technical areas of EDB. As such, the TAM’s technical abilities are critical in identifying solutions, architecture, troubleshooting issues, and answering technical questions as they arise. What You Will Do… Establish a close working relationship with the customer’s senior technical leadership team and become their trusted advisor.Help EDB customers maximize the value of their Postgres investmentAssist EDB customers to develop and deploy Postgres strategies Provide technical leadership for the customer's major Postgres initiatives (This may include solutions consulting, architecture guidance, and project management)Maintain current functional and technical knowledge of the entire EDB product lineProvide clear and constructive product feedback to EDB’s product management teams based on customer requirementsHelp to document best practices in developing and deploying EDB solutionsFunction as a front-line technical resource for "best practice" and informal customer questionsTravel up to 25% of the time as required What Will Give You An Edge… At least five (5) years of hands-on experience with Postgres, Oracle, DB2 or MS SQL Server; professional certifications in any of the relational databases are desirableAdvanced technical skills, specifically in data management platforms, operating systems, cloud technologies, and technical architectureKnowledgeable about data analytics and AI/ML conceptsExperience with KubernetesExcellent analytical skills regarding technical and project management issuesGood understanding of strategic sales processWell-developed organizational skills with an ability to manage competing client demandsExcellent communications and interpersonal skills, including ability to interact and communicate with CxO level personnelBachelors/Masters degree in Information Technology / Computer science or equivalent technical training or industry experience preferred EDB is committed to supporting our employees' overall well being by offering a range of benefits and resources to promote a healthy work-life balance and wellness. We provide access to CuraLinc to aid employees in health and wellness tips and practices, as well as Wellness Fridays extending to December 2026! Check out our career site for more information on perks and benefits and reach out to our Talent Acquisition team for region specific benefits. We know it takes a unique mix of people and skills to help us in our mission to supercharge Postgres, and we understand that not everyone will check every box. We’d love to hear from you and we want you to apply! EDB is proud to be an equal opportunity workplace. We celebrate diversity and are committed to creating an inclusive environment for all employees. EDB was built on a commitment to trust and respect each other and to embrace an array of people and ideas. These values remain at the center of our culture and are key to our company’s integrity. EDB does not seek or accept unsolicited resumes or CVs from recruitment agencies. EDB and its affiliates are not responsible for, and will not pay, any fees, commissions, or any other similar payment related to unsolicited resumes or CVs except as required in a written signed agreement between EDB and the recruitment agency or party requesting payment of a fee."
We need to remove boilerplate: EEO, equal opportunity, unsolicited resumes, etc. Also remove "Check out our career site for more information on perks and benefits and reach out to our Talent Acquisition team for region specific benefits." That's maybe benefits info but it's generic; we have specific benefits: access to CuraLinc, Wellness Fridays extending to December 2026. Those are specific benefits. So we can include a Benefits section with those items.
We also have "Travel up to 25% of the time as required" - that's schedule/travel info. Could be Schedule section? The instruction says include Schedule section only if posting actually states them. It does state travel up to 25% of the time as required. That's schedule/travel. So we can include a Schedule section with that bullet.
Pay: Not mentioned. So no Pay section.
We need sections: About the role? Could be "About the role" or "Responsibilities". The posting includes "What You Will Do…" which is responsibilities. Also "What Will Give You An Edge…" which is qualifications/skills/requirements. Also "A Little About Us" is company overview, could be "About the company" but not required. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose appropriate.
We need to preserve all substantive information. So we need to include company overview? It's substantive but not required heading; we could put it in a
before sections. The instruction: "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 include a short paragraph about the company as intro.
We need to output only HTML fragment.
Let's structure:
EDB provides a data and AI platform that enables organizations to harness the full power of Postgres for transactional, analytical, and AI workloads across any cloud, anywhere. EDB empowers enterprises to control risk, manage costs and scale efficiently for a data and AI led world. Serving more than 1,500 customers globally and as the leading contributor to the vibrant and fast-growing PostgreSQL community, EDB supports major government organizations, financial services, media and information technology companies. EDB’s data-driven solutions enable customers to modernize legacy systems and break data silos while leveraging enterprise-grade open source technologies. EDB delivers the confidence of up to 99.999% high availability with mission critical capabilities built in such as security, compliance controls, and observability. For more information, visit www.enterprisedb.com
Then sections:
About the role
maybe we can put a short paragraph describing the role: "EDB is hiring a Technical Account Manager (TAM) for US. The TAM is responsible for building and maintaining post-sales relationships with EDB’s largest and most complex customers. These customers are typically large accounts adopting Postgres and AI solutions. The TAM serves as a trusted technical advisor to drive successful outcomes and to ensure that the customers become a positive reference and continue their journey on Postgres technology. The TAM is also the customer's primary point of contact into all technical areas of EDB. As such, the TAM’s technical abilities are critical in identifying solutions, architecture, troubleshooting issues, and answering technical questions as they arise."
That's substantive.
Then Responsibilities: from "What You Will Do…" list.
We need to convert to - . The responsibilities are sentences separated by periods? Let's extract:
- Establish a close working relationship with the customer’s senior technical leadership team and become their trusted advisor.
- Help EDB customers maximize the value of their Postgres investment
- Assist EDB customers to develop and deploy Postgres strategies
- Provide technical leadership for the customer's major Postgres initiatives (This may include solutions consulting, architecture guidance, and project management)
- Maintain current functional and technical knowledge of the entire EDB product line
- Provide clear and constructive product feedback to EDB’s product management teams based on customer requirements
- Help to document best practices in developing and deploying EDB solutions
- Function as a front-line technical resource for "best practice" and informal customer questions
- Travel up to 25% of the time as required
Note: Travel up to 25% could be schedule but we can keep in responsibilities or schedule. Since we have a Schedule section, we could move travel there. But responsibilities list includes travel; we could keep it there or move. The instruction: prefer few substantive sections over many thin ones. We could keep travel in responsibilities and not have separate Schedule section. However we have specific schedule info; we could make a Schedule section with that bullet. But then responsibilities would lose that bullet. Might be okay to have both sections. But we need to avoid thin sections. Schedule section with just one bullet might be thin. Better to keep travel in responsibilities and not create Schedule section. The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state travel up to 25% of the time as required, which is schedule-related. But we could still include Schedule section if we want, but it's okay to not include if we think it's thin. However the instruction says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid having a section with one real item. So we could include Schedule with that bullet. But we also have Benefits section with two items (CuraLinc, Wellness Fridays). That's substantive enough.
Thus we will have sections: About the role, Responsibilities, Requirements (or Qualifications/Skills), Benefits, Schedule.
But we need to avoid duplication. The "What Will Give You An Edge…" includes experience, skills, education. That's qualifications/skills. We can split into Requirements and Skills maybe. But we can combine into one section "Requirements" or "Qualifications". The instruction lists both Requirements and Qualifications as possible headings. We can choose one. Let's use "Requirements" for the experience/skills/education.
We need to list items as
- . Let's extract:
- At least five (5) years of hands-on experience with Postgres, Oracle, DB2 or MS SQL Server; professional certifications in any of the relational databases are desirable
- Advanced technical skills, specifically in data management platforms, operating systems, cloud technologies, and technical architecture
- Knowledgeable about data analytics and AI/ML concepts
- Experience with Kubernetes
- Excellent analytical skills regarding technical and project management issues
- Good understanding of strategic sales process
- Well-developed organizational skills
for prose. 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. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting. Content: "A Little About Us EDB provides a data and AI platform that enables organizations to harness the full power of Postgres for transactional, analytical, and AI workloads across any cloud, anywhere. EDB empowers enterprises to control risk, manage costs and scale efficiently for a data and AI led world. Serving more than 1,500 customers globally and as the leading contributor to the vibrant and fast-growing PostgreSQL community, EDB supports major government organizations, financial services, media and information technology companies. EDB’s data-driven solutions enable customers to modernize legacy systems and break data silos while leveraging enterprise-grade open source technologies. EDB delivers the confidence of up to 99.999% high availability with mission critical capabilities built in such as security, compliance controls, and observability. For more information, visit www.enterprisedb.com EDB is hiring a Technical Account Manager (TAM) for US. The TAM is responsible for building and maintaining post-sales relationships with EDB’s largest and most complex customers. These customers are typically large accounts adopting Postgres and AI solutions. The TAM serves as a trusted technical advisor to drive successful outcomes and to ensure that the customers become a positive reference and continue their journey on Postgres technology. The TAM is also the customer's primary point of contact into all technical areas of EDB. As such, the TAM’s technical abilities are critical in identifying solutions, architecture, troubleshooting issues, and answering technical questions as they arise. What You Will Do… Establish a close working relationship with the customer’s senior technical leadership team and become their trusted advisor.Help EDB customers maximize the value of their Postgres investmentAssist EDB customers to develop and deploy Postgres strategies Provide technical leadership for the customer's major Postgres initiatives (This may include solutions consulting, architecture guidance, and project management)Maintain current functional and technical knowledge of the entire EDB product lineProvide clear and constructive product feedback to EDB’s product management teams based on customer requirementsHelp to document best practices in developing and deploying EDB solutionsFunction as a front-line technical resource for "best practice" and informal customer questionsTravel up to 25% of the time as required What Will Give You An Edge… At least five (5) years of hands-on experience with Postgres, Oracle, DB2 or MS SQL Server; professional certifications in any of the relational databases are desirableAdvanced technical skills, specifically in data management platforms, operating systems, cloud technologies, and technical architectureKnowledgeable about data analytics and AI/ML conceptsExperience with KubernetesExcellent analytical skills regarding technical and project management issuesGood understanding of strategic sales processWell-developed organizational skills with an ability to manage competing client demandsExcellent communications and interpersonal skills, including ability to interact and communicate with CxO level personnelBachelors/Masters degree in Information Technology / Computer science or equivalent technical training or industry experience preferred EDB is committed to supporting our employees' overall well being by offering a range of benefits and resources to promote a healthy work-life balance and wellness. We provide access to CuraLinc to aid employees in health and wellness tips and practices, as well as Wellness Fridays extending to December 2026! Check out our career site for more information on perks and benefits and reach out to our Talent Acquisition team for region specific benefits. We know it takes a unique mix of people and skills to help us in our mission to supercharge Postgres, and we understand that not everyone will check every box. We’d love to hear from you and we want you to apply! EDB is proud to be an equal opportunity workplace. We celebrate diversity and are committed to creating an inclusive environment for all employees. EDB was built on a commitment to trust and respect each other and to embrace an array of people and ideas. These values remain at the center of our culture and are key to our company’s integrity. EDB does not seek or accept unsolicited resumes or CVs from recruitment agencies. EDB and its affiliates are not responsible for, and will not pay, any fees, commissions, or any other similar payment related to unsolicited resumes or CVs except as required in a written signed agreement between EDB and the recruitment agency or party requesting payment of a fee." We need to remove boilerplate: EEO, equal opportunity, unsolicited resumes, etc. Also remove "Check out our career site for more information on perks and benefits and reach out to our Talent Acquisition team for region specific benefits." That's maybe benefits info but it's generic; we have specific benefits: access to CuraLinc, Wellness Fridays extending to December 2026. Those are specific benefits. So we can include a Benefits section with those items. We also have "Travel up to 25% of the time as required" - that's schedule/travel info. Could be Schedule section? The instruction says include Schedule section only if posting actually states them. It does state travel up to 25% of the time as required. That's schedule/travel. So we can include a Schedule section with that bullet. Pay: Not mentioned. So no Pay section. We need sections: About the role? Could be "About the role" or "Responsibilities". The posting includes "What You Will Do…" which is responsibilities. Also "What Will Give You An Edge…" which is qualifications/skills/requirements. Also "A Little About Us" is company overview, could be "About the company" but not required. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose appropriate. We need to preserve all substantive information. So we need to include company overview? It's substantive but not required heading; we could put it in a
before sections. The instruction: "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 include a short paragraph about the company as intro. We need to output only HTML fragment. Let's structure:
EDB provides a data and AI platform that enables organizations to harness the full power of Postgres for transactional, analytical, and AI workloads across any cloud, anywhere. EDB empowers enterprises to control risk, manage costs and scale efficiently for a data and AI led world. Serving more than 1,500 customers globally and as the leading contributor to the vibrant and fast-growing PostgreSQL community, EDB supports major government organizations, financial services, media and information technology companies. EDB’s data-driven solutions enable customers to modernize legacy systems and break data silos while leveraging enterprise-grade open source technologies. EDB delivers the confidence of up to 99.999% high availability with mission critical capabilities built in such as security, compliance controls, and observability. For more information, visit www.enterprisedb.com
Then sections:About the role
maybe we can put a short paragraph describing the role: "EDB is hiring a Technical Account Manager (TAM) for US. The TAM is responsible for building and maintaining post-sales relationships with EDB’s largest and most complex customers. These customers are typically large accounts adopting Postgres and AI solutions. The TAM serves as a trusted technical advisor to drive successful outcomes and to ensure that the customers become a positive reference and continue their journey on Postgres technology. The TAM is also the customer's primary point of contact into all technical areas of EDB. As such, the TAM’s technical abilities are critical in identifying solutions, architecture, troubleshooting issues, and answering technical questions as they arise." That's substantive. Then Responsibilities: from "What You Will Do…" list. We need to convert to- . The responsibilities are sentences separated by periods? Let's extract:
- Establish a close working relationship with the customer’s senior technical leadership team and become their trusted advisor.
- Help EDB customers maximize the value of their Postgres investment
- Assist EDB customers to develop and deploy Postgres strategies
- Provide technical leadership for the customer's major Postgres initiatives (This may include solutions consulting, architecture guidance, and project management)
- Maintain current functional and technical knowledge of the entire EDB product line
- Provide clear and constructive product feedback to EDB’s product management teams based on customer requirements
- Help to document best practices in developing and deploying EDB solutions
- Function as a front-line technical resource for "best practice" and informal customer questions
- Travel up to 25% of the time as required
Note: Travel up to 25% could be schedule but we can keep in responsibilities or schedule. Since we have a Schedule section, we could move travel there. But responsibilities list includes travel; we could keep it there or move. The instruction: prefer few substantive sections over many thin ones. We could keep travel in responsibilities and not have separate Schedule section. However we have specific schedule info; we could make a Schedule section with that bullet. But then responsibilities would lose that bullet. Might be okay to have both sections. But we need to avoid thin sections. Schedule section with just one bullet might be thin. Better to keep travel in responsibilities and not create Schedule section. The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state travel up to 25% of the time as required, which is schedule-related. But we could still include Schedule section if we want, but it's okay to not include if we think it's thin. However the instruction says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid having a section with one real item. So we could include Schedule with that bullet. But we also have Benefits section with two items (CuraLinc, Wellness Fridays). That's substantive enough.
Thus we will have sections: About the role, Responsibilities, Requirements (or Qualifications/Skills), Benefits, Schedule.
But we need to avoid duplication. The "What Will Give You An Edge…" includes experience, skills, education. That's qualifications/skills. We can split into Requirements and Skills maybe. But we can combine into one section "Requirements" or "Qualifications". The instruction lists both Requirements and Qualifications as possible headings. We can choose one. Let's use "Requirements" for the experience/skills/education.
We need to list items as
- . Let's extract: - At least five (5) years of hands-on experience with Postgres, Oracle, DB2 or MS SQL Server; professional certifications in any of the relational databases are desirable - Advanced technical skills, specifically in data management platforms, operating systems, cloud technologies, and technical architecture - Knowledgeable about data analytics and AI/ML concepts - Experience with Kubernetes - Excellent analytical skills regarding technical and project management issues - Good understanding of strategic sales process - Well-developed organizational skills