Salesforce Architect (Salesforce CPQ)
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: Who We Are (intro), What You Will Do (responsibilities), What You Will Bring (requirements/qualifications), Who You Are (maybe skills/attributes), Why Emburse? (benefits/culture). There's no explicit Pay or Schedule. So we should not include Pay or Schedule sections. Benefits: maybe "Why Emburse?" includes competitive pay, flexible work, inclusive environment, etc. That's benefits. Could also include "A Company with Momentum", etc. So we can create a Benefits section with those points.
We need to use for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: EEO, AI hiring process, etc. Also remove duplicated lines. Also remove navigation, cookie, legal, etc. The posting includes EEO paragraph and AI hiring process note; we should remove those.
We need to not repeat job title as heading. The job title is Salesforce Architect (Salesforce CPQ). Not to be used as heading.
We need to not put Job ID/requisition numbers as headings; none present.
We need to include sections only when posting has real specific content. So we can have sections: About the role (maybe from Who We Are and intro), Responsibilities (What You Will Do), Requirements (What You Will Bring), Skills (Who You Are maybe), Benefits (Why Emburse?). Could also combine Requirements and Qualifications; but we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose to include only those with content. Could include About the role, Responsibilities, Requirements, Skills, Benefits. Qualifications maybe same as Requirements; but we can either include Qualifications if we have content distinct. The posting has "What You Will Bring" which includes hands-on developer roots, transformation track record, cross-platform integration mastery, process simplification mindset, stakeholder fluency. That's qualifications/requirements. Could split into Requirements and Qualifications but better to avoid duplication. The instruction: Prefer a few substantive sections over many thin ones. So we can combine Requirements and Qualifications into one section maybe called Requirements (or Qualifications). But headings list includes both; we can choose to include only one if content fits. Let's include "Requirements" for the What You Will Bring. And maybe "Skills" for Who You Are (soft skills/personal attributes). Benefits from Why Emburse?.
About the role: from Who We Are and intro paragraph.
Let's extract content.
Original text:
Who We Are: At Emburse, you’ll not just imagine the future – you’ll build it. As a leader in expense intelligence, we are creating a future where technology drives business value and inspires extraordinary results. Our AI-powered platform helps organizations modernize financial operations, increase visibility, and optimize spend across the enterprise. We are looking for a Salesforce Architect (Salesforce CPQ) to serve as the master technical builder of our enterprise revenue engine. In a high-growth, private-equity-backed SaaS environment, simply "configuring" Salesforce isn't enough—we are actively transforming how our business scales. Reporting directly to the Director of Business Systems , you will own the end-to-end technical architecture across Salesforce CRM and CPQ while partnering closely with our teams responsible for Billing, ERP, and marketing applications. We are looking for an architect who built their career on deep developer roots . You aren't an "ivory tower" consultant; you are a pragmatic technical leader who can design complex Quote-to-Cash data flows, dive deep and guide dev teams on code standards, and challenge business stakeholders to simplify processes rather than digitizing messiness.
What You Will Do Architect the Revenue Engine: Lead the technical design and redesign of our Quote-to-Cash (Q2C) and Lead-to-Cash (L2C) architecture, focusing on Salesforce CPQ and CRM along with the integrated Q2C ecosystem. Drive Business Transformation: Work directly with business stakeholders to translate complex requirements into scalable enterprise architecture—challenging existing processes to drive simplification and automation in our Sales motions. Define System Boundaries: Architect clean, robust integrations between Salesforce, CPQ and integrated enterprise systems (BillingPlatform(™), NetSuite, Marketo, HubSpot, and more ). Provide Technical Leadership: Guide and mentor technical teams and developers by leveraging your significant developer background to perform code reviews, enforce Apex/LWC standards, and drive robust solutioning discussions. Triage & Optimize: Evaluate trade-offs between out-of-the-box functionality vs. custom development, eliminating technical debt while prioritizing business velocity.
What You Will Bring Hands-on Developer Roots: Proven background as a Salesforce CPQ Developer who has successfully transitioned into a Technical/Solution Architect role. Transformation Track Record: Demonstrated experience leading end-to-end Digital or Business Transformation projects specifically focused on Quote-to-Cash or Lead-to-Cash redesign and optimization. Cross-Platform Integration Mastery: Broad familiarity and integration design experience with enterprise systems like NetSuite, Marketo, HubSpot, BillingPlatform(™), Gong, and Snowflake. Process Simplification Mindset: A strong track record of rethinking and optimizing business processes rather than simply recreating legacy workflows in Salesforce. Stakeholder Fluency: Exceptional ability to communicate technical tradeoffs, system limits, and architectural decisions to non-technical business leaders.
Who You Are A Pragmatic Architect: You know how code should be written because you’ve written it. You use that best-practice knowledge to guide dev teams and build architectures that work fluidly in production. A Problem Solver: You love a challenge and figuring out how to solve them because optimizing Salesforce ecosystems has been the driving factor in your successful career. A Business Partner: You aren't a master of your domain. When a stakeholder asks for a shortcut that adds technical debt, you offer a better, more scalable alternative. An Efficiency Champion: You live to eliminate friction in sales cycles, streamline quote line calculations, and ensure data flows cleanly from lead generation to revenue recognition.
Why Emburse? Finance is changing—and at Emburse, we’re leading the way. Our AI-powered solutions help organizations eliminate inefficiencies, gain real-time visibility, and optimize spend—so they can focus on what’s next, not what’s slowing them down. A Company with Momentum – We serve 12M+ users across 120 countries, helping businesses modernize their finance operations. A Team That Innovates – Work alongside some of the brightest minds in finance, tech, and AI to solve real- world challenges. A Culture That Empowers – Competitive pay, flexible work, and an inclusive, collaborative environment that supports your success. A Career That Matters – Your work here drives efficiency, innovation, and smarter financial decision-making for businesses everywhere. Shape your future & find what’s next at Emburse.
Then EEO etc.
We need to remove EEO and AI hiring process note.
Now produce HTML.
Structure:
About the role
... (combined Who We Are intro)
Responsibilities
- ... each bullet from What You Will Do
Requirements
- ... each bullet from What You Will Bring
Skills
- ... each bullet from Who You Are
Benefits
- ... each bullet from Why Emburse? (Finance is changing..., A Company with Momentum..., A Team That Innovates..., A Culture That Empowers..., A Career That Matters..., Shape your future & find what’s next at Emburse.)
We need to ensure we don't include filler like "commensurate with experience". Not present.
We need to preserve all substantive information; we should not omit any details from the sections.
Let's extract each piece precisely.
About the role: combine the Who We Are paragraph and maybe the sentence about reporting to Director of Business Systems etc. Actually the Who We Are includes that. Let's copy the whole Who We Are block up to before "What You Will Do". That includes:
"At Emburse, you’ll not just imagine the future – you’ll build it. As a leader in expense intelligence, we are creating a future where technology drives business value and inspires extraordinary results. Our AI-powered platform helps organizations modernize financial operations, increase visibility, and optimize spend across the enterprise. We are looking for a Salesforce Architect (Salesforce CPQ) to serve as the master technical builder of our enterprise revenue engine. In a high-growth, private-equity-backed SaaS environment, simply "configuring" Salesforce isn't enough—we are actively transforming how our business scales. Reporting directly to the Director of Business Systems , you will own the end-to-end technical architecture across Salesforce CRM and CPQ while partnering closely with our teams responsible for Billing, ERP, and marketing applications. We are looking for an architect who built their career on deep developer roots . You aren't an "ivory tower" consultant; you are a pragmatic technical leader who can design complex Quote-to-Cash data flows, dive deep and guide dev teams on code standards, and challenge business stakeholders to simplify processes rather than digitizing messiness."
We should not repeat the job title as heading, but it's okay to include it in the paragraph.
Now Responsibilities: list each bullet:
- Lead the technical design and redesign of our Quote-to-Cash (Q2C) and Lead-to-Cash (L2C) architecture, focusing on Salesforce CPQ and CRM along with the integrated Q2C ecosystem.
- Work directly with business stakeholders to translate complex requirements into scalable enterprise architecture—challenging existing processes to drive simplification and automation in our Sales motions.
- Architect clean, robust integrations between Salesforce, CPQ and integrated enterprise systems (BillingPlatform(™), NetSuite, Marketo, HubSpot, and more ).
- Guide and mentor technical teams and developers by leveraging your significant developer background to perform code reviews, enforce Apex/LWC standards, and drive robust solutioning discussions.
- Evaluate trade-offs between out-of-the-box functionality vs. custom development, eliminating technical debt while prioritizing business velocity.
Note: The original had headings like "Architect the Revenue Engine:", "Drive Business Transformation:", etc. We'll convert to list items.
Now Requirements: list each bullet from What You Will Bring:
- Proven background as a Salesforce CPQ Developer who has successfully transitioned into a Technical/Solution Architect role.
- Demonstrated experience leading end-to-end Digital or Business Transformation projects specifically focused on Quote-to-Cash or Lead-to-Cash redesign and optimization.
- Broad familiarity and integration design experience with enterprise systems like NetSuite, Marketo, HubSpot, BillingPlatform(™), Gong, and Snowflake.
- A strong track record of rethinking and optimizing business processes rather than simply recreating legacy workflows in Salesforce.
- Exceptional ability to communicate technical tradeoffs, system limits, and architectural decisions to non-technical business leaders.
Now Skills: list each bullet from Who You Are:
- You know how code should be written because you’ve written it. You use that best-practice knowledge to guide dev teams and build architectures that work fluidly in production.
- You love a challenge and figuring out how to solve them because optimizing Salesforce ecosystems has been the driving factor in your successful career.
- You aren't a master of your domain. When a stakeholder asks for a shortcut that adds technical debt, you offer a better, more scalable alternative.
- You live to eliminate friction in sales cycles, streamline quote line calculations, and ensure data flows cleanly from lead generation to revenue recognition.
Now Benefits: list each bullet from Why Emburse?:
- Finance is changing—and at Emburse, we’re leading the way. Our AI-powered solutions
- for any list of duties/requirements/benefits. Use
for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: EEO, AI hiring process, etc. Also remove duplicated lines. Also remove navigation, cookie, legal, etc. The posting includes EEO paragraph and AI hiring process note; we should remove those. We need to not repeat job title as heading. The job title is Salesforce Architect (Salesforce CPQ). Not to be used as heading. We need to not put Job ID/requisition numbers as headings; none present. We need to include sections only when posting has real specific content. So we can have sections: About the role (maybe from Who We Are and intro), Responsibilities (What You Will Do), Requirements (What You Will Bring), Skills (Who You Are maybe), Benefits (Why Emburse?). Could also combine Requirements and Qualifications; but we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose to include only those with content. Could include About the role, Responsibilities, Requirements, Skills, Benefits. Qualifications maybe same as Requirements; but we can either include Qualifications if we have content distinct. The posting has "What You Will Bring" which includes hands-on developer roots, transformation track record, cross-platform integration mastery, process simplification mindset, stakeholder fluency. That's qualifications/requirements. Could split into Requirements and Qualifications but better to avoid duplication. The instruction: Prefer a few substantive sections over many thin ones. So we can combine Requirements and Qualifications into one section maybe called Requirements (or Qualifications). But headings list includes both; we can choose to include only one if content fits. Let's include "Requirements" for the What You Will Bring. And maybe "Skills" for Who You Are (soft skills/personal attributes). Benefits from Why Emburse?. About the role: from Who We Are and intro paragraph. Let's extract content. Original text: Who We Are: At Emburse, you’ll not just imagine the future – you’ll build it. As a leader in expense intelligence, we are creating a future where technology drives business value and inspires extraordinary results. Our AI-powered platform helps organizations modernize financial operations, increase visibility, and optimize spend across the enterprise. We are looking for a Salesforce Architect (Salesforce CPQ) to serve as the master technical builder of our enterprise revenue engine. In a high-growth, private-equity-backed SaaS environment, simply "configuring" Salesforce isn't enough—we are actively transforming how our business scales. Reporting directly to the Director of Business Systems , you will own the end-to-end technical architecture across Salesforce CRM and CPQ while partnering closely with our teams responsible for Billing, ERP, and marketing applications. We are looking for an architect who built their career on deep developer roots . You aren't an "ivory tower" consultant; you are a pragmatic technical leader who can design complex Quote-to-Cash data flows, dive deep and guide dev teams on code standards, and challenge business stakeholders to simplify processes rather than digitizing messiness. What You Will Do Architect the Revenue Engine: Lead the technical design and redesign of our Quote-to-Cash (Q2C) and Lead-to-Cash (L2C) architecture, focusing on Salesforce CPQ and CRM along with the integrated Q2C ecosystem. Drive Business Transformation: Work directly with business stakeholders to translate complex requirements into scalable enterprise architecture—challenging existing processes to drive simplification and automation in our Sales motions. Define System Boundaries: Architect clean, robust integrations between Salesforce, CPQ and integrated enterprise systems (BillingPlatform(™), NetSuite, Marketo, HubSpot, and more ). Provide Technical Leadership: Guide and mentor technical teams and developers by leveraging your significant developer background to perform code reviews, enforce Apex/LWC standards, and drive robust solutioning discussions. Triage & Optimize: Evaluate trade-offs between out-of-the-box functionality vs. custom development, eliminating technical debt while prioritizing business velocity. What You Will Bring Hands-on Developer Roots: Proven background as a Salesforce CPQ Developer who has successfully transitioned into a Technical/Solution Architect role. Transformation Track Record: Demonstrated experience leading end-to-end Digital or Business Transformation projects specifically focused on Quote-to-Cash or Lead-to-Cash redesign and optimization. Cross-Platform Integration Mastery: Broad familiarity and integration design experience with enterprise systems like NetSuite, Marketo, HubSpot, BillingPlatform(™), Gong, and Snowflake. Process Simplification Mindset: A strong track record of rethinking and optimizing business processes rather than simply recreating legacy workflows in Salesforce. Stakeholder Fluency: Exceptional ability to communicate technical tradeoffs, system limits, and architectural decisions to non-technical business leaders. Who You Are A Pragmatic Architect: You know how code should be written because you’ve written it. You use that best-practice knowledge to guide dev teams and build architectures that work fluidly in production. A Problem Solver: You love a challenge and figuring out how to solve them because optimizing Salesforce ecosystems has been the driving factor in your successful career. A Business Partner: You aren't a master of your domain. When a stakeholder asks for a shortcut that adds technical debt, you offer a better, more scalable alternative. An Efficiency Champion: You live to eliminate friction in sales cycles, streamline quote line calculations, and ensure data flows cleanly from lead generation to revenue recognition. Why Emburse? Finance is changing—and at Emburse, we’re leading the way. Our AI-powered solutions help organizations eliminate inefficiencies, gain real-time visibility, and optimize spend—so they can focus on what’s next, not what’s slowing them down. A Company with Momentum – We serve 12M+ users across 120 countries, helping businesses modernize their finance operations. A Team That Innovates – Work alongside some of the brightest minds in finance, tech, and AI to solve real- world challenges. A Culture That Empowers – Competitive pay, flexible work, and an inclusive, collaborative environment that supports your success. A Career That Matters – Your work here drives efficiency, innovation, and smarter financial decision-making for businesses everywhere. Shape your future & find what’s next at Emburse. Then EEO etc. We need to remove EEO and AI hiring process note. Now produce HTML. Structure:
About the role
... (combined Who We Are intro)
Responsibilities
- ... each bullet from What You Will Do
Requirements
- ... each bullet from What You Will Bring
Skills
- ... each bullet from Who You Are
Benefits
- ... each bullet from Why Emburse? (Finance is changing..., A Company with Momentum..., A Team That Innovates..., A Culture That Empowers..., A Career That Matters..., Shape your future & find what’s next at Emburse.)