Enterprise Account Executive

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. No job title heading. No Job ID etc. Remove boilerplate. Need to preserve all substantive info. We need to parse the posting. First paragraph: description of company. Could be part of About the role? Actually "About The Role" heading present. So we should have

About the role

then content after that heading. The preceding company description maybe part of "About the role"? Usually "About the role" includes description of role, not company. But we can include company description under About the role? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have those headings if content exists. We need to decide which sections have content. Let's extract: About the role: The text after "About The Role" heading: "You'll carry an enterprise quota selling Finario into a three-legged buying committee: ..." up to "Ability to operate on a hybrid basis out of our Stamford, CT office". That seems like role description. So we put that under About the role. Responsibilities: The bullet list under "What you'll actually do". That includes multiple sentences. Could be responsibilities. So we can have

Responsibilities

with

• items. Requirements: There's "Required Qualifications" heading. That could be Qualifications section. Also "Desired Skills & Experience" could be Skills. Also "What’s In It For You" includes benefits. So we need sections: Qualifications, Skills, Benefits. Possibly also Pay and Schedule if present. Pay: not mentioned explicitly. Schedule: mention hybrid basis out of Stamford, CT office; ability to be in Stamford 4 x a week; travel ~25%; maybe schedule info. Could be considered Schedule? The instruction: include Schedule section only if posting actually states them. It mentions hybrid basis, travel, office days. That's schedule-ish. Could put under Schedule. But we also have "Ability to operate on a hybrid basis out of our Stamford, CT office" and "Bachelor's degree; able to be in Stamford 4 x a week; willing to travel". That's schedule details. So we can create Schedule section. Pay: Not mentioned. So omit Pay. Benefits: "What’s In It For You" includes: "A category-defining product...", "Enterprise deal size without enterprise-company bureaucracy.", "Six-figure ARR deals...", "You're supported, not solo.", "Benefits: competitive total rewards package including Health, Dental, 401k PTO and more! The little things matter: Fully funded parking (or hop the train, we're right across the street), stunning modern office space". So we can extract benefits: competitive total rewards package including Health, Dental, 401k, PTO and more; fully funded parking; modern office space. Also maybe other intangible benefits but we keep as benefits. Now we need to ensure we don't repeat headings with filler. We'll produce sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Schedule. Check if we need Requirements separate from Qualifications? The posting has "Required Qualifications". That's qualifications. So we can map that to Qualifications section. No separate Requirements. Now we need to preserve all substantive info, not invent or summarize away detail. Must not omit details like specific numbers, etc. We'll need to include all details from each section. Let's extract each piece. About the role content: "You'll carry an enterprise quota selling Finario into a three-legged buying committee: Finance owns the budget (CFO, VP Finance, FP&A), Engineering and Operations own the projects (VP Engineering, VP Operations, Capital Projects leadership, plant and facilities heads), and IT owns the deployment. Most enterprise deals at Finario involve all three. The AE who can navigate that conversation — sometimes leading with Finance, sometimes with the operating side, sometimes with IT, depending on where the pain lives and wins. Average deal is six-figure ARR; cycles run 3-9 months. You'll report to the head of sales and be supported by a sales engineer on demos and technical questions and a customer-success team on accounts, with direct access to the product team when a deep question comes up." That's the paragraph. Also after that there is "What you'll actually do" which we treat as Responsibilities. Now Responsibilities list: - Run the full sales cycle including prospecting, discovery, demo (with your SE), business case, procurement and security, negotiation, close - Build and manage a full-cycle pipeline, blending self-sourced outbound with marketing-generated leads; outbound is part of the job, not a fallback - Lead a multi-stakeholder sale- you'll be in rooms with Finance one week and operating execs the next, and need to be credible in both - Own the customer relationship through renewal and expansion — Finario customers stay for years and grow - Run a disciplined deal process using a formal methodology (MEDDIC, Challenger, etc.) with forecasting and clean pipeline hygiene are part of the job, not an afterthought - Travel to customer sites as needed (~25%) - Ability to operate on a hybrid basis out of our Stamford, CT office Note: The last two items maybe also schedule but we can keep them under Responsibilities as they are part of what you'll actually do. However we also have Schedule section later; we might duplicate. Better to keep schedule-specific items under Schedule, and responsibilities focus on sales activities. The posting includes "Travel to customer sites as needed (~25%)" and "Ability to operate on a hybrid basis out of our Stamford, CT office" under What you'll actually do list. We could move those to Schedule section. But we need to preserve all info; we can keep them in Responsibilities but also maybe schedule. To avoid duplication, we could put them under Schedule and not repeat. However the instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If we move them, we still preserve. It's okay. Thus Responsibilities will be first five items (full sales cycle, pipeline, multi-stakeholder sale, customer relationship, disciplined deal process). Then Schedule will include travel and hybrid office. Now Qualifications (Required Qualifications): "3-7+ years carrying quota in enterprise SaaS, with personally closed six-figure ARR deals Software sales experience is a hard requirement, this isn't an entry point from a different industry Trained in a real sales methodology such as MEDDIC, Challenger, SPIN, Sandler, etc. Comfortable holding both a business conversation (ROI, NPV, payback, capital governance) and an operational one (how capital projects actually get scoped, approved, and executed) Bachelor's degree; able to be in Stamford 4 x a week; willing to travel" Note: The last two items about Stamford 4x a week and willing to travel are schedule-related; we might move them to Schedule. But they are under Required Qualifications. However we can still keep them under Qualifications but also schedule? Might duplicate. Better to keep schedule items under Schedule and not duplicate. But we need to preserve all info; we can keep them under Schedule and not under Qualifications. However the Required Qualifications section includes them; if we omit them from Qualifications we lose that info from that section but we still have it elsewhere. The instruction: preserve ALL substantive information; does not require preserving original grouping. So we can reallocate as long as we keep the info. So we can move schedule details to Schedule section. Thus Qualifications will be: - 3-7+ years carrying quota in enterprise SaaS, with personally closed six-figure ARR deals - Software sales experience is a hard requirement, this isn't an entry point from a different industry - Trained in a real sales methodology such as MEDDIC, Challenger, SPIN, Sandler, etc. - Comfortable holding both a business conversation (ROI, NPV, payback, capital governance) and an operational one (how capital projects actually get scoped, approved, and executed) - Bachelor's degree Now Skills (Desired Skills & Experience): "Experience selling across multiple buyer groups (Finance + technical/operational + IT) is strongly preferred over single-buyer backgrounds. Experience in adjacent categories including but not limited to capital/project portfolio management (Planview, Oracle Primavera), EPM and corporate planning (Anaplan, Oracle, OneStream, SAP), industrial and engineering software (AVEVA, Aspen, Bentley, Hexagon), asset performance, and other multi-stakeholder enterprise software" We'll list as bullet points. Benefits: From "What’s In It For You": we have several bullet-like sentences. Let's extract: - A category-defining product, not a legacy tool to defend. You're selling into a purpose-built Capex platform with an in-house AI engine (Finario Predict); a real differentiator in demos, not a roadmap promise. - Enterprise deal size without enterprise-company bureaucracy. - Six-figure ARR deals, but you're one of a handful of AEs, not one of fifty, direct visibility with the head of sales and product team. - You're supported, not solo. A dedicated SE on demos and technical questions, a CS team once the deal closes, and product access for the hard questions, so your time stays focused on selling. - Benefits: competitive total rewards package including Health, Dental, 401k PTO and more! - The little things matter: Fully funded parking (or hop the train, we're right across the street), stunning modern office space We can combine into benefits section. Now Schedule: - Travel to customer sites as needed (~25%) - Ability to operate on a hybrid basis out of our Stamford, CT office - Able to be in Stamford 4 x a week; willing to travel (from qualifications) We might combine travel and hybrid. We should avoid duplication: travel appears twice; we can keep one. Let's list schedule items: - Travel to customer sites as needed (~25%) - Hybrid work basis: expected to be in Stamford office 4 days per week; ability to operate on a hybrid basis out of Stamford, CT office - Willing to travel (already covered) We could simplify: "Hybrid schedule: expected in Stamford office 4 days per week; travel to customer sites ~25%". That captures. Now we need to output HTML fragment with headings

  and content

  or

  • . Use

    for prose paragraphs. For lists use

    • . We must not include or . Just the fragment. We'll produce sections in order: About the role, Responsibilities, Qualifications, Skills, Benefits, Schedule. Now craft content. About the role: multiple sentences; we can put in

      . Responsibilities: list items. Qualifications: list items. Skills: list items. Benefits: could be a mix of prose and list; we can use

      for each benefit or combine into

      . Since they are distinct points, better as
      • . Schedule: maybe

        or

        . We'll use

        describing hybrid schedule and travel. Now ensure we don't include any boilerplate like EEO etc. Not present. Now produce final HTML. Check for any repeated content: we moved schedule details from qualifications and responsibilities; we kept them only in Schedule. Let's write. About the role paragraph: "You'll carry an enterprise quota selling Finario into a three-legged buying committee: Finance owns the budget (CFO, VP Finance, FP&A), Engineering and Operations own the projects (VP Engineering, VP Operations, Capital Projects leadership, plant and facilities heads), and IT owns the deployment. Most enterprise deals at Finario involve all three. The AE who can navigate that conversation — sometimes leading with Finance, sometimes with the operating side, sometimes with IT, depending on where the pain lives and wins. Average deal