Commercial Account Executive - Data Foundation (MuleSoft + Informatica)
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide which sections have content.
From posting:
- Overview Of The Role: description of role, subsegments, two tracks, etc. That's about the role.
- Key Responsibilities: list of responsibilities.
- Required Qualifications: list.
- Things We Love (Preferred Experience): could be Qualifications? Actually "Things We Love (Preferred Experience)" is preferred qualifications. Could go under Qualifications or maybe Skills? The instruction: Use sections Requirements, Qualifications, Skills. We need to map.
- Core Competencies: could be Skills.
- Benefits: there is a paragraph about benefits later: "Salesforce offers a variety of benefits to help you live well including: time off programs, medical, dental, vision, mental health support, paid parental leave, life and disability insurance, 401(k), and an employee stock purchasing program." Also earlier "Unleash Your Potential" mentions benefits and resources. So we have benefits content.
- Pay: there is salary range info: "The typical base salary range for this position is $62,250 - $189,350 annually." Also location-specific ranges. So we have pay content.
- Schedule: there is "Location: Close proximity to office hub required; role is 3 days on-site per week". That's schedule info (hybrid). Also earlier "Some positions may be office-based, office-flexible, or remote depending on the team." So schedule content.
Thus we can include sections: About the role, Responsibilities, Requirements (maybe Required Qualifications), Qualifications (maybe Preferred Experience), Skills (Core Competencies), Benefits, Pay, Schedule.
We must not include sections with filler like "commensurate with experience". Not present.
We must not repeat job title.
We must not include boilerplate like EEO, accommodations, privacy statement, etc. Remove those.
We must preserve all substantive information. Must not invent or summarize away detail. Must keep details like subsegments, tracks, responsibilities list, qualifications list, preferred experience, core competencies, benefits list, pay ranges, schedule.
We need to format as HTML fragment: use for headings, - for lists,
for prose.
We need to ensure we don't include any markdown fences.
Let's extract content precisely.
First, About the role: from "Overview Of The Role" paragraph and subsegments description.
Paragraph: "Overview Of The Role AI agents are reshaping how companies automate decisions, orchestrate processes, and engage customers at scale. But AI is only as powerful as the data foundation behind it. As Commercial Account Executive within these teams, you will drive transformational outcomes for our customers using market-leading integration and data management technologies. Our Commercial Segment Is Made Up Of Two Subsegments - Mid-Market And General Business. These Segments Focus On Selling Into Different Company Sizes Mid-Market- 200-1000 EmployeesGeneral Business - 1000-5000 Employees This Single Posting Covers Two Distinct Selling Tracks Data Foundation Account Executive (Quarterback / Prime AE): You are the overall account owner and leader of the backend data strategy. Carrying a dual-product quota across MuleSoft and Informatica ACV, you own long-term account growth and orchestrate extended team resources—including Informatica overlay specialists—to deliver the complete data foundation story.Informatica Account Executive (Overlay / Specialist AE): You are the deep domain expert for Informatica’s Intelligent Data Management Cloud™ (IDMC). Partnering directly with Prime Account Executives, you uncover complex digital transformation opportunities, advise C-level executives, and drive maximum value from Informatica investments within larger account strategies."
We need to preserve that exactly? Probably we can keep as prose, maybe break into paragraphs but keep content.
We'll put that in a
under
About the role
.
Next Responsibilities: list under "Key Responsibilities". Items:
- Relationship Building: Establish executive presence and trusted-advisor relationships with C-suite decision-makers and key technical stakeholders.
- Strategy & Execution: Build and execute long-term, objective-aligned account plans that drive customer business outcomes.
- Resource Orchestration: Align cross-functional internal teams (SEs, Product Specialists, Cloud Sales, and Executives) to accelerate deal velocity.
- Value Messaging: Articulate the combined power of MuleSoft, Informatica, and the broader Salesforce ecosystem.
- Pipeline Generation: Drive net-new opportunity creation through target whitespace prospecting and warm lead expansion.
- Role Focus:Data Foundation AE: Dual-quota attainment, primary account ownership, and overarching platform strategy.
- Role Focus:Informatica AE: IDMC domain expertise, overlay execution, and driving targeted data expansion inside Prime accounts.
We need to keep each as list items.
We'll output - ... etc.
Next Required Qualifications: list:
- 5+ years of full-cycle B2B sales experience.
- Proven track record selling complex technical platforms, with market awareness in Integration, API Management, or Data Management.
- Business-value seller: Demonstrated ability to translate technical capabilities into executive-level business outcomes (revenue, risk mitigation, and competitive advantage).
- Matrix leadership: Exceptional ability to lead and strategize within a matrixed, extended overlay team structure.
- AI fluency: A natural curiosity about the evolving AI landscape, with the ability to credibly connect data and integration strategy to real-world AI outcomes.
- New business focus: Demonstrated expertise in new logo acquisition and greenfield territory development.
- Location: Close proximity to office hub required; role is 3 days on-site per week.
Note: location also appears in schedule but we can keep here as qualification? Might duplicate. But we need to preserve all substantive info; we can keep location in both sections? Might be duplication but we can't remove because it's substantive. However we might consider moving location to Schedule section to avoid duplication. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is okay if it's in original? It appears twice: once under Required Qualifications (Location: Close proximity to office hub required; role is 3 days on-site per week) and also earlier "Some positions may be office-based, office-flexible, or remote depending on the team." and later schedule. We could keep it in Schedule section and maybe not duplicate in Qualifications. But the Required Qualifications includes location as a qualification; it's substantive. If we omit it, we lose that detail. So we should keep it there. However we also need a Schedule section; we can include schedule info there (maybe just the hybrid schedule). We can keep location in Qualifications and also mention schedule in Schedule section (maybe just "3 days on-site per week").
We'll keep location in Qualifications.
Next Things We Love (Preferred Experience): list:
- Completion of formal sales methodology training (MEDDPICC, SPIN, Challenger Sales).
- Familiarity with complex IT selling involving multi-stakeholder approval matrixes across global organizations.
- Strong understanding of enterprise architecture concepts, digital transformation frameworks, and hybrid integration patterns.
- Background in technical solution architecture or management consulting in relevant sector.
- Data Foundation AE Preference: Strong understanding of API management, integration platforms, middleware, and data connectivity solutions.
- Informatica AE Preference: Prior experience with data management, MDM, or data quality platforms.
We can put these under Qualifications? Or maybe under Skills? The instruction includes Qualifications and Skills sections. We could treat "Things We Love (Preferred Experience)" as Qualifications (preferred). But we already have Required Qualifications. Could have two subsections? But we only allowed one Qualifications heading. Could combine required and preferred under Qualifications? Might be okay but we need to preserve distinction? Not required. Could put preferred under Skills? But core competencies are separate.
Better: Use Qualifications for required, Skills for core competencies and preferred experience? But the instruction gave examples: Skills could be like "Core Competencies". We'll put Core Competencies under Skills. Preferred experience could also go under Qualifications as "Preferred Qualifications". But we only have one Qualifications heading; we could include both required and preferred under that heading, maybe separate paragraphs. That would preserve all info.
Thus under Qualifications we can have two
paragraphs: one for Required Qualifications (list), another for Preferred Experience (list). Or we could keep separate headings but not allowed. We'll combine.
Next Core Competencies: list:
- Consultative sales approach grounded in customer success and integrity
- Collaborative team spirit with "company-first" mentality
- Ability to manage complex, multi-stakeholder sales cycles spanning multiple business units
We'll put under Skills.
Benefits: list from "Salesforce offers a variety of benefits to help you live well including: time off programs, medical, dental, vision, mental health support, paid parental leave, life and disability insurance, 401(k), and an employee stock purchasing program." Also earlier "Unleash Your Potential When you join Salesforce, you’ll be limitless in all areas of your life. Our benefits and resources support you to find balance and be your best, and our AI agents accelerate your impact so you can do your best." That's more generic. We'll keep the specific list.
Pay: salary range info: "The typical base salary range for this position is $62,250 - $189,350 annually. Your recruiter can share more about the specific salary range for the job location during the hiring process. There is a different range applicable to specific work locations. In California and New York, and select cities in the metropolitan areas of Boston, Chicago, Seattle, and Washington DC, the base pay range for this role in those locations is $68,150 - $208,300 per year. Your recruiter can share more about the specific salary range for the job location during the hiring process. The range represents base salary only, and does not include company bonus, incentive for sales roles, equity or benefits, as applicable."
We'll put that in
under Pay.
Schedule: we have "Location: Close proximity to office hub required; role is 3 days on-site per week." Also earlier "Some positions may be office-based, office-flexible, or remote depending on the team." We'll combine: maybe a paragraph: "Some positions may be office-based, office-flexible, or remote depending on the team. This role requires close proximity to an office hub and is scheduled for 3 days on-site per week."
We'll put under Schedule.
Now we must ensure we don't include boilerplate like "Accommodations", "Privacy Statement", "EEO", "Posting Statement", etc. Remove those.
Also remove "To get the best candidate experience, please consider applying for a maximum of 3 roles within 12 months to ensure you are not duplicating efforts." That's application instruction; remove.
Also remove "Job Category Sales" maybe metadata; remove.
Also remove "Applications for this position will be accepted on an ongoing basis." That's application instruction; remove.
Also remove "Note: By applying to this posting, recruiters and hiring managers who support multiple verticals across the organization — hiring for both SMB, Commercial and Enterprise Account Executives — will review your resume. Apply once and have it considered by multiple hiring teams." That's application instruction; remove.
Also remove "Some positions may be office-based, office-flexible
- for lists,
for prose. We need to ensure we don't include any markdown fences. Let's extract content precisely. First, About the role: from "Overview Of The Role" paragraph and subsegments description. Paragraph: "Overview Of The Role AI agents are reshaping how companies automate decisions, orchestrate processes, and engage customers at scale. But AI is only as powerful as the data foundation behind it. As Commercial Account Executive within these teams, you will drive transformational outcomes for our customers using market-leading integration and data management technologies. Our Commercial Segment Is Made Up Of Two Subsegments - Mid-Market And General Business. These Segments Focus On Selling Into Different Company Sizes Mid-Market- 200-1000 EmployeesGeneral Business - 1000-5000 Employees This Single Posting Covers Two Distinct Selling Tracks Data Foundation Account Executive (Quarterback / Prime AE): You are the overall account owner and leader of the backend data strategy. Carrying a dual-product quota across MuleSoft and Informatica ACV, you own long-term account growth and orchestrate extended team resources—including Informatica overlay specialists—to deliver the complete data foundation story.Informatica Account Executive (Overlay / Specialist AE): You are the deep domain expert for Informatica’s Intelligent Data Management Cloud™ (IDMC). Partnering directly with Prime Account Executives, you uncover complex digital transformation opportunities, advise C-level executives, and drive maximum value from Informatica investments within larger account strategies." We need to preserve that exactly? Probably we can keep as prose, maybe break into paragraphs but keep content. We'll put that in a
under
About the role
. Next Responsibilities: list under "Key Responsibilities". Items: - Relationship Building: Establish executive presence and trusted-advisor relationships with C-suite decision-makers and key technical stakeholders. - Strategy & Execution: Build and execute long-term, objective-aligned account plans that drive customer business outcomes. - Resource Orchestration: Align cross-functional internal teams (SEs, Product Specialists, Cloud Sales, and Executives) to accelerate deal velocity. - Value Messaging: Articulate the combined power of MuleSoft, Informatica, and the broader Salesforce ecosystem. - Pipeline Generation: Drive net-new opportunity creation through target whitespace prospecting and warm lead expansion. - Role Focus:Data Foundation AE: Dual-quota attainment, primary account ownership, and overarching platform strategy. - Role Focus:Informatica AE: IDMC domain expertise, overlay execution, and driving targeted data expansion inside Prime accounts. We need to keep each as list items. We'll output- ... etc.
Next Required Qualifications: list:
- 5+ years of full-cycle B2B sales experience.
- Proven track record selling complex technical platforms, with market awareness in Integration, API Management, or Data Management.
- Business-value seller: Demonstrated ability to translate technical capabilities into executive-level business outcomes (revenue, risk mitigation, and competitive advantage).
- Matrix leadership: Exceptional ability to lead and strategize within a matrixed, extended overlay team structure.
- AI fluency: A natural curiosity about the evolving AI landscape, with the ability to credibly connect data and integration strategy to real-world AI outcomes.
- New business focus: Demonstrated expertise in new logo acquisition and greenfield territory development.
- Location: Close proximity to office hub required; role is 3 days on-site per week.
Note: location also appears in schedule but we can keep here as qualification? Might duplicate. But we need to preserve all substantive info; we can keep location in both sections? Might be duplication but we can't remove because it's substantive. However we might consider moving location to Schedule section to avoid duplication. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is okay if it's in original? It appears twice: once under Required Qualifications (Location: Close proximity to office hub required; role is 3 days on-site per week) and also earlier "Some positions may be office-based, office-flexible, or remote depending on the team." and later schedule. We could keep it in Schedule section and maybe not duplicate in Qualifications. But the Required Qualifications includes location as a qualification; it's substantive. If we omit it, we lose that detail. So we should keep it there. However we also need a Schedule section; we can include schedule info there (maybe just the hybrid schedule). We can keep location in Qualifications and also mention schedule in Schedule section (maybe just "3 days on-site per week").
We'll keep location in Qualifications.
Next Things We Love (Preferred Experience): list:
- Completion of formal sales methodology training (MEDDPICC, SPIN, Challenger Sales).
- Familiarity with complex IT selling involving multi-stakeholder approval matrixes across global organizations.
- Strong understanding of enterprise architecture concepts, digital transformation frameworks, and hybrid integration patterns.
- Background in technical solution architecture or management consulting in relevant sector.
- Data Foundation AE Preference: Strong understanding of API management, integration platforms, middleware, and data connectivity solutions.
- Informatica AE Preference: Prior experience with data management, MDM, or data quality platforms.
We can put these under Qualifications? Or maybe under Skills? The instruction includes Qualifications and Skills sections. We could treat "Things We Love (Preferred Experience)" as Qualifications (preferred). But we already have Required Qualifications. Could have two subsections? But we only allowed one Qualifications heading. Could combine required and preferred under Qualifications? Might be okay but we need to preserve distinction? Not required. Could put preferred under Skills? But core competencies are separate.
Better: Use Qualifications for required, Skills for core competencies and preferred experience? But the instruction gave examples: Skills could be like "Core Competencies". We'll put Core Competencies under Skills. Preferred experience could also go under Qualifications as "Preferred Qualifications". But we only have one Qualifications heading; we could include both required and preferred under that heading, maybe separate paragraphs. That would preserve all info.
Thus under Qualifications we can have two
paragraphs: one for Required Qualifications (list), another for Preferred Experience (list). Or we could keep separate headings but not allowed. We'll combine. Next Core Competencies: list: - Consultative sales approach grounded in customer success and integrity - Collaborative team spirit with "company-first" mentality - Ability to manage complex, multi-stakeholder sales cycles spanning multiple business units We'll put under Skills. Benefits: list from "Salesforce offers a variety of benefits to help you live well including: time off programs, medical, dental, vision, mental health support, paid parental leave, life and disability insurance, 401(k), and an employee stock purchasing program." Also earlier "Unleash Your Potential When you join Salesforce, you’ll be limitless in all areas of your life. Our benefits and resources support you to find balance and be your best, and our AI agents accelerate your impact so you can do your best." That's more generic. We'll keep the specific list. Pay: salary range info: "The typical base salary range for this position is $62,250 - $189,350 annually. Your recruiter can share more about the specific salary range for the job location during the hiring process. There is a different range applicable to specific work locations. In California and New York, and select cities in the metropolitan areas of Boston, Chicago, Seattle, and Washington DC, the base pay range for this role in those locations is $68,150 - $208,300 per year. Your recruiter can share more about the specific salary range for the job location during the hiring process. The range represents base salary only, and does not include company bonus, incentive for sales roles, equity or benefits, as applicable." We'll put that in
under Pay. Schedule: we have "Location: Close proximity to office hub required; role is 3 days on-site per week." Also earlier "Some positions may be office-based, office-flexible, or remote depending on the team." We'll combine: maybe a paragraph: "Some positions may be office-based, office-flexible, or remote depending on the team. This role requires close proximity to an office hub and is scheduled for 3 days on-site per week." We'll put under Schedule. Now we must ensure we don't include boilerplate like "Accommodations", "Privacy Statement", "EEO", "Posting Statement", etc. Remove those. Also remove "To get the best candidate experience, please consider applying for a maximum of 3 roles within 12 months to ensure you are not duplicating efforts." That's application instruction; remove. Also remove "Job Category Sales" maybe metadata; remove. Also remove "Applications for this position will be accepted on an ongoing basis." That's application instruction; remove. Also remove "Note: By applying to this posting, recruiters and hiring managers who support multiple verticals across the organization — hiring for both SMB, Commercial and Enterprise Account Executives — will review your resume. Apply once and have it considered by multiple hiring teams." That's application instruction; remove. Also remove "Some positions may be office-based, office-flexible
- ... etc.
Next Required Qualifications: list:
- 5+ years of full-cycle B2B sales experience.
- Proven track record selling complex technical platforms, with market awareness in Integration, API Management, or Data Management.
- Business-value seller: Demonstrated ability to translate technical capabilities into executive-level business outcomes (revenue, risk mitigation, and competitive advantage).
- Matrix leadership: Exceptional ability to lead and strategize within a matrixed, extended overlay team structure.
- AI fluency: A natural curiosity about the evolving AI landscape, with the ability to credibly connect data and integration strategy to real-world AI outcomes.
- New business focus: Demonstrated expertise in new logo acquisition and greenfield territory development.
- Location: Close proximity to office hub required; role is 3 days on-site per week.
Note: location also appears in schedule but we can keep here as qualification? Might duplicate. But we need to preserve all substantive info; we can keep location in both sections? Might be duplication but we can't remove because it's substantive. However we might consider moving location to Schedule section to avoid duplication. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is okay if it's in original? It appears twice: once under Required Qualifications (Location: Close proximity to office hub required; role is 3 days on-site per week) and also earlier "Some positions may be office-based, office-flexible, or remote depending on the team." and later schedule. We could keep it in Schedule section and maybe not duplicate in Qualifications. But the Required Qualifications includes location as a qualification; it's substantive. If we omit it, we lose that detail. So we should keep it there. However we also need a Schedule section; we can include schedule info there (maybe just the hybrid schedule). We can keep location in Qualifications and also mention schedule in Schedule section (maybe just "3 days on-site per week").
We'll keep location in Qualifications.
Next Things We Love (Preferred Experience): list:
- Completion of formal sales methodology training (MEDDPICC, SPIN, Challenger Sales).
- Familiarity with complex IT selling involving multi-stakeholder approval matrixes across global organizations.
- Strong understanding of enterprise architecture concepts, digital transformation frameworks, and hybrid integration patterns.
- Background in technical solution architecture or management consulting in relevant sector.
- Data Foundation AE Preference: Strong understanding of API management, integration platforms, middleware, and data connectivity solutions.
- Informatica AE Preference: Prior experience with data management, MDM, or data quality platforms.
We can put these under Qualifications? Or maybe under Skills? The instruction includes Qualifications and Skills sections. We could treat "Things We Love (Preferred Experience)" as Qualifications (preferred). But we already have Required Qualifications. Could have two subsections? But we only allowed one Qualifications heading. Could combine required and preferred under Qualifications? Might be okay but we need to preserve distinction? Not required. Could put preferred under Skills? But core competencies are separate.
Better: Use Qualifications for required, Skills for core competencies and preferred experience? But the instruction gave examples: Skills could be like "Core Competencies". We'll put Core Competencies under Skills. Preferred experience could also go under Qualifications as "Preferred Qualifications". But we only have one Qualifications heading; we could include both required and preferred under that heading, maybe separate paragraphs. That would preserve all info.
Thus under Qualifications we can have two