Jobs · Washington

Sr Partner Executive - Financial Services

Workday · Seattle, WA · 2 wk ago
Hybrid$122k–$183k/yrFull-time
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. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO etc. Also remove application instructions. Must not include filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. Let's parse the posting. Content: - Intro paragraph about Workday culture etc. That's generic but maybe part of "About the role"? Actually it's about company. Might be considered "About the role"? But we need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have sections in posting: "About The Team", "About The Role", "Sales", "Collaboration", "Operational Results", "About You", "Basic Qualifications", "Other Qualifications", "Workday Pay Transparency Statement", "Our Approach to Flexible Work", plus EEO etc. We need to map to required headings. We need to extract substantive content for each heading. Let's list content: About The Team: description of Global Partners Organization. About The Role: description of Partner Sales Executive responsibilities. Then there are sub-sections: Sales, Collaboration, Operational Results. Those could be considered Responsibilities. About You: Basic Qualifications and Other Qualifications. Pay: Workday Pay Transparency Statement includes base salary ranges. Benefits: Not explicitly listed; there is mention of "total compensation package", "Workday Bonus Plan", "role-specific commission/bonus", "annual refresh stock grants", "comprehensive benefits". But no specific benefits like health, 401k etc. The instruction: do NOT create Benefits section unless posting actually states them. It mentions "total compensation package" and "comprehensive benefits" but not specifics. Likely we should not create Benefits section because no specific benefits listed. However "Workday Bonus Plan or a role-specific commission/bonus, as well as annual refresh stock grants" could be considered benefits? It's compensation. Might be considered part of Pay? But Pay section is for salary ranges. Benefits could be bonus, stock. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state bonus plan and stock grants, which are part of compensation. Could be considered Benefits? But they are compensation elements. However we have a Pay section for base salary. Benefits could be separate. The posting mentions "total compensation package" and eligibility for bonus plan, commission/bonus, stock grants. That's substantive. So we could include a Benefits section with those details. Schedule: "Our Approach to Flexible Work" describes flexible work expectation: at least half time in office/field each quarter. That's schedule info. So we can include Schedule section. Now we need to avoid boilerplate: remove EEO, legal, accommodation, referral, privacy, scam warning etc. Also remove duplicated lines. Now structure: We will output:

About the Team

maybe? But required headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It didn't list About the Team. However we could include About the role as heading; About the Team could be part of About the role? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., not exclusive. So we can add other headings if needed, but prefer few substantive sections. We could combine About the Team into About the role section. But we have separate About The Team paragraph. Could we put it under About the role? Might be okay. However we need to preserve all substantive info. If we omit About The Team heading, we lose that info unless we embed it elsewhere. We could embed it in About the role section as a paragraph. That would preserve info. Thus sections: - About the role (includes About The Team and About The Role description) - Responsibilities (includes Sales, Collaboration, Operational Results) - Requirements (maybe Basic Qualifications) - Qualifications (Other Qualifications) - Skills (maybe list of skills like proficiency in Google Sheets, Slides, Salesforce, communication, etc.) - Benefits (bonus plan, commission/bonus, stock grants) - Pay (base salary ranges) - Schedule (flexible work approach) We must not create sections with filler. Ensure each has real content. Now extract specifics. About The Team paragraph: "The Global Partners Organization is focused on developing partnerships that accelerate innovation and growth with Industry differentiation, expanded reach and customer success. This is an amazing opportunity to be part of the team that is driving a rapid and global change of paradigm, to embrace a modern ecosystem and implement a unified and global partner strategy with local flavor, with cross-functional engagement in programs, systems, processes and people." About The Role paragraph: "As part of the Partner Sales Team within GPO, the Partner Sales Executive will lead joint business development with our Partners focused on our Financial Services Industry, aligned to the Workday sales organization. The Partner Sales Executive is responsible for developing the Workday pipeline across all Partners within a designated segment and industry. In addition to working with our Partners, the Partner Executive will work across multiple internal functions, including (but not limited to) sales, services, marketing, pre-sales, value management, legal, and industry. This role requires strong partner sales experience, managing campaigns and sales plays, GTM and industry expertise, executive presence and strong communication and organizational skills." Now Responsibilities: we have sub-sections Sales, Collaboration, Operational Results. Sales bullet points (looks like a list but not formatted with bullets). Let's extract: "Sales Sales engagement and opportunity identification experience Experience cultivating mutually beneficial relationships with customers and partners Prospecting and identifying new opportunities Familiarity with technology partner ecosystems" Collaboration: "Collaboration Work across the Partners team including Channels, Software, Operations and Services Alliances to ensure alignment and execution. Collaborate closely with our Partner Managers (PMs) Model, live and champion the Workday values and VIBE (Value, Inclusion, Belonging and Equity)" Operational Results: "Operational Results Build target % and $ of ACV sourced/originated pipeline from partners Understand the Sales objectives across all go to market programs, and build a comprehensive and detailed plan for the business, mapping it to joint plans with partners. Operational execution from a partners perspective for forecasting, pipeline management, and deal execution across all phases of the sales process." We can format as
  • items. Now Requirements: Basic Qualifications: "5+ years professional experience in a technology (SaaS or cloud) company or WD Partner, collaborating with B2B Sales & Partners (SIs/ISVs/GSIs/Hyperscalers) 7+ years of professional experience in Business Development or Sales" We could combine as two items. Qualifications: Other Qualifications: "Deep Financial Services industry experience Proven results in working across matrixed organizations, with complex team-based sales environments, and able to influence sales organizations and partner GTM motions Cloud Technology, Data, Analytics, API, and platform experience and understanding Validated experience in delivering strong results in pipeline generation and bookings Outstanding verbal and written communication skills Proficiency in Google Sheets, Slides & Salesforce.com MBA a plus Moderate Travel: 15-25%" Note: Travel could be considered schedule? But it's about travel requirement. Might be part of Qualifications or maybe Schedule? The instruction: schedule section only if posting actually states them. Travel is not schedule of work days but travel percentage. Could be placed under Qualifications as a bullet. Skills: Could extract skills from qualifications: communication, Google Sheets, Slides, Salesforce, etc. But we already have qualifications covering skills. Might combine Skills with Qualifications? But we need separate Skills section if we have specific skill list. We could create Skills section listing: "Outstanding verbal and written communication skills", "Proficiency in Google Sheets, Slides & Salesforce.com", "Financial Services industry experience", "Cloud Technology, Data, Analytics, API, and platform experience". However that duplicates qualifications. Perhaps better to treat Qualifications as encompassing both experience and skills, and not create separate Skills section to avoid thin sections. The instruction: "Prefer a few substantive sections over many thin ones." So we could omit Skills section and put skill details under Qualifications. But the required headings list includes Skills as an example; but we can omit if not substantive. However we have skill specifics; we could put them under Qualifications. That would satisfy preserving info. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. Now Benefits: from Pay Transparency Statement: "As a part of the total compensation package, this role may be eligible for the Workday Bonus Plan or a role-specific commission/bonus, as well as annual refresh stock grants." Also maybe "comprehensive benefits" but not specific. We'll include those. Pay: base salary ranges: Primary Location: USA.IL.Chicago Primary Location Base Pay Range: $128,300 USD - $192,400 USD Additional US Location(s) Base Pay Range: $116,000 USD - $206,200 USD Additional Considerations: If performed in Colorado, the pay range for this job is $122,200 - $183,300 USD based on min and max pay range for that role if performed in CO. We need to preserve all that info. Schedule: "Our Approach to Flexible Work With Flex Work, we’re combining the best of both worlds: in-person time and remote. Our approach enables our teams to deepen connections, maintain a strong community, and do their best work. We know that flexibility can take shape in many ways, so rather than a number of required days in-office each week, we simply spend at least half (50%) of our time each quarter in the office or in the field with our customers, prospects, and partners (depending on role). This means you'll have the freedom to create a flexible schedule that caters to your business, team, and personal needs, while being intentional to make the most of time spent together. Those in our remote "home office" roles also have the opportunity to come together in our offices for important moments that matter." We'll include that as Schedule section. Now we must remove boilerplate: EEO, accommodation, referral, privacy, scam warning, legal etc. Also remove "The application deadline for this role is the same as the posting end date stated as below: 10/16/2026" maybe considered metadata but not required heading; could be dropped as minor metadata. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it. So we can drop the deadline line. Also remove "Workday Pay Transparency Statement" heading? We'll incorporate into Benefits and Pay sections. Now produce HTML. We'll need to wrap each section in

    and then content. For About the role: combine About The Team and About The Role paragraphs into

    elements. We'll output:

    About the role

    The Global Partners Organization is focused on developing partnerships that accelerate innovation and growth with Industry differentiation, expanded reach and customer success. This is an amazing opportunity to be part of the team that is driving a rapid and global change of paradigm, to embrace a modern ecosystem and implement a unified and global partner strategy with local flavor, with cross-functional engagement in programs, systems, processes and people.

    As part of the Partner Sales Team within GPO, the Partner Sales Executive will lead joint business development with our Partners focused on our Financial Services Industry, aligned to the Workday sales organization. The Partner Sales Executive is responsible for developing the Workday pipeline across all Partners within a designated segment and industry. In addition to working with our Partners, the Partner Executive will work across

Similar jobs