Jobs · Sales

Account Manager

Athena Security Inc. · United States · 1 mo ago
RemoteRemoteSalesFull-time
We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. The posting includes: About Athena Security (company description) - could be "About the role"? Actually "About the role" is a heading we can use for role overview. The posting includes "Role Overview" which we can map to About the role. Then "Key Responsibilities" -> Responsibilities. Then "What We're Looking For" -> Requirements (or Qualifications). Also "Why Athena Security?" -> Benefits? It includes competitive base salary + performance-based compensation, remote flexibility, etc. That's benefits. No explicit Pay or Schedule specifics besides travel percentage (50-80% travel). That could be Schedule? Travel is not schedule but maybe we can put Schedule section with travel expectation. However rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state "Competitive base salary + performance-based compensation." That's pay info, but it's vague (no numbers). The rule says: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "Competitive base salary + performance-based compensation" is somewhat vague but still specific? It's not a number but it's a statement. Might be acceptable as Pay section? The rule says avoid filler like "commensurate with experience". This is similar but maybe okay. However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state competitive base salary + performance-based compensation, so we can include Pay. For Schedule, they state travel 50-80% travel, primarily local and regional. That's schedule info (travel). Could be Schedule. Benefits: they list remote flexibility, mission-driven team, etc. So we can include Benefits. We must not repeat job title as heading. No Job ID. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can reformat. We need to use

for section headings. Use
  • for any list of duties/requirements/benefits, and

    for prose. We need to remove boilerplate: "How to Apply:" etc. Also remove navigation, legal, EEO, etc. Not present. We need to output only HTML fragment. Let's extract sections: About the role (Role Overview): includes description: "We’re looking for a high-energy, detail-oriented Account Manager to join our Customer Success team and take ownership of post-sale relationships with our clients for following locations: (Connecticut, New England, Dallas, Houston, Austin). This role blends account management, customer service, technical support coordination, and client-facing leadership. You’ll be responsible for ensuring smooth onboarding, training, deployment, and long-term satisfaction for some of our most important customers. The ideal candidate is proactive, articulate, and relationship-driven, with a strong sense of ownership and follow-through. You’re someone who makes clients feel supported, heard, and prioritized—always ready to jump in, solve problems, and go the extra mile. You approach each account with a service-oriented mindset, taking initiative and showing clients they’re in capable, reliable hands. This is not a laid-back desk job—it requires hustle, presence, and the ability to lead conversations and solve issues before they become problems." We can put that as prose under

    About the role

    with

    . Responsibilities (Key Responsibilities): list items: - Own the end-to-end onboarding process, including product demos, technical deployment coordination, and client training. - Serve as the primary point of contact for existing client accounts—building trust, solving problems, and driving satisfaction. - Provide outstanding support and communication, ensuring every customer feels heard, informed, and valued. - Conduct regular check-ins (virtual and on-site) to proactively monitor account health and identify issues or opportunities. - Present confidently during demos, training sessions, and in high-stakes client conversations. - Collaborate with internal teams (Engineering, Product, Customer Support) to address client needs and ensure successful outcomes. - Coordinate basic technical support needs—knowing when to solve directly or escalate appropriately. - Travel to client sites regularly (50–80% travel, primarily local and regional) for onboarding, training, and relationship management. - Capture and relay client feedback to help improve Athena’s processes and product offerings. - Cultivate strong rapport that leads to retention, referrals, and long-term partnerships. We'll put each as

  • . Requirements (What We're Looking For): list items: - 5+ years of experience in account management, customer success, sales, or support roles—preferably in B2B tech, hardware/software, or security industries. - Exceptional communication skills—verbal, written, and presentation. You must be articulate, polished, and confident. - A natural relationship-builder who inspires trust, listens well, and takes initiative. - Proven ability to manage details, timelines, and client expectations with follow-through. - Strong customer service and basic tech troubleshooting instincts—able to identify, coordinate, or resolve issues quickly. - Comfortable presenting to stakeholders, leading conversations, and owning the room. - Must be go-getter, not passive—able to take charge, self-direct, and stay three steps ahead. - Valid driver’s license and willingness to travel frequently by car for client site visits. - Experience working with CRMs, support ticketing systems, or technical documentation a plus. We'll put as
  • . Qualifications: Not separate; maybe we can combine with Requirements? The spec says we can have Qualifications section if there is content. The posting doesn't have separate qualifications beyond what we listed. Could omit Qualifications. Skills: Could be extracted from requirements but we already have them. Might not need separate Skills section if we already covered. But we could create Skills section listing skills like communication, relationship-building, etc. However that would duplicate. Better to not create thin sections. We'll omit Skills. Benefits (Why Athena Security?): list items: - Join a company making a real-world impact by saving lives through innovation. - Work closely with top-tier clients across the country. - Competitive base salary + performance-based compensation. - Remote flexibility with travel that keeps the job dynamic and relationship-driven. - Be part of a tight-knit, mission-driven team that values ownership and excellence. We'll put as
  • . Pay: We already included competitive base salary + performance-based compensation in Benefits. But we could also create Pay section with that line. However we must not duplicate. The rule: prefer a few substantive sections over many thin ones. So we can incorporate pay into Benefits. But they said include Benefits section only if posting actually states them. It does. So we can have Benefits section that includes the pay line. That's fine. Schedule: Travel expectation could be in Responsibilities (travel item). Could also be separate Schedule section. But we already have travel in Responsibilities. To avoid thin section, we can keep travel in Responsibilities and not create Schedule. Thus sections: About the role, Responsibilities, Requirements, Benefits. We need to ensure we preserve all substantive information: Did we miss anything? The company description "About Athena Security" at start: we omitted that. Should we include that as part of About the role? The instruction: "About Athena Security" is company overview, not role. Could be included as part of About the role? Might be considered boilerplate? It's substantive about company. The spec says we should preserve all substantive information. So we should include company description somewhere. Could be a separate section like "About the Company" but not in allowed headings. Allowed headings are limited to those list. We could put it under About the role as prose before role overview. That would be okay: About the role heading then paragraph includes company description and role overview. That preserves info. Thus under About the role we can have two paragraphs: first about Athena Security, second about role overview. We must not repeat job title as heading; we are not. Now produce HTML:

    About the role

    Athena Security is an industry leader in AI-powered concealed weapons detection, visitor management, and integrated security platforms. Our mission is simple: to help save lives by building the most advanced entryway security ecosystem available. We combine cutting-edge hardware and AI with intuitive software solutions to help schools, hospitals, casinos, and enterprises create safer spaces.

    We’re looking for a high-energy, detail-oriented Account Manager to join our Customer Success team and take ownership of post-sale relationships with our clients for following locations: (Connecticut, New England, Dallas, Houston, Austin). This role blends account management, customer service, technical support coordination, and client-facing leadership. You’ll be responsible for ensuring smooth onboarding, training, deployment, and long-term satisfaction for some of our most important customers. The ideal candidate is proactive, articulate, and relationship-driven, with a strong sense of ownership and follow-through. You’re someone who makes clients feel supported, heard, and prioritized—always ready to jump in, solve problems, and go the extra mile. You approach each account with a service-oriented mindset, taking initiative and showing clients they’re in capable, reliable hands. This is not a laid-back desk job—it requires hustle, presence, and the ability to lead conversations and solve issues before they become problems.

    Responsibilities

    • Own the end-to-end onboarding process, including product demos, technical deployment coordination, and client training.
    • Serve as the primary point of contact for existing client accounts—building trust, solving problems, and driving satisfaction.
    • Provide outstanding support and communication, ensuring every customer feels heard, informed, and valued.
    • Conduct regular check-ins (virtual and on-site) to proactively monitor account health and identify issues or opportunities.
    • Present confidently during demos, training sessions, and in high-stakes client conversations.
    • Collaborate with internal teams (Engineering, Product, Customer Support) to address client needs and ensure successful outcomes.
    • Coordinate basic technical support needs—knowing when to solve directly or escalate appropriately.
    • Travel to client sites regularly (50–80% travel, primarily local and regional) for onboarding, training, and relationship management.
    • Capture and relay client feedback to help improve Athena’s processes and product offerings.
    • Cultivate strong rapport that leads to retention, referrals, and long-term partnerships.

    Requirements

    • 5+ years of experience in account management, customer success, sales, or support roles—preferably in B2B tech, hardware/software, or security industries.
    • Exceptional communication skills—verbal, written, and presentation. You must be articulate, polished, and confident.
    • A natural relationship-builder who inspires trust, listens well, and takes initiative.
    • Proven ability to manage details, timelines, and client expectations with follow-through.
    • Strong customer service and basic tech troubleshooting instincts—able to identify, coordinate, or resolve issues quickly.
    • Comfortable presenting to stakeholders, leading conversations, and owning the room.
    • Must be go-getter, not passive—able to take charge, self-direct, and stay three steps ahead.
    • Valid driver’s license and willingness to travel frequently by car for client site visits.
    • Experience working with CRMs, support ticketing systems, or technical documentation a plus.

    Benefits

    • Join a company making a real-world impact by saving lives through innovation.
    • Work closely with top-tier clients across the country.
    • Competitive base salary + performance-based compensation.
    • Remote flexibility

Similar jobs

Account Manager

AM BestOldwick, NJ· 4 mo ago
Business Developmentapply on careers-ambest.icims.com

Account Manager

IncodeUnited States· 3 mo ago
RemoteSalesapply on job-boards.greenhouse.io

Account Manager

SandvikMebane, NC· 3 mo ago
Customer Serviceapply on sandvik.wd3.myworkdayjobs.com

Account Manager

Rent-A-CenterDillon, SC· 3 mo ago
Customer Service$13.01/hrapply on olivia.paradox.ai

Account Manager

Alera Group, Inc.Walnut Creek, CA· 2 mo ago
Business Developmentapply on careers.aleragroup.com

ACCOUNT MANAGER

Fallon Creative GroupEl Segundo, CA· 2 mo ago
Business Development$50k/yrapply on careers-publicisgroupe.icims.com