Product Solution Architect – Quote to Cash (Salesforce CPQ & CLM)

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. We need to extract from posting. We need to avoid repeating job title as heading. No Job ID etc. We need to remove boilerplate: EEO, legal, etc. We need to preserve all substantive info. Let's parse posting. First paragraph: "Your work days are brighter here..." It's generic marketing fluff. Might be considered boilerplate? It's not specific to role. Might be considered generic company description. Should we keep? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The initial paragraph is not exactly boilerplate but it's generic marketing. It might be considered not substantive for the role. However it's part of the posting. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The generic fluff may be considered not substantive? Hard to judge. Usually they'd want to keep role-specific content. The initial paragraph is about company culture, could be considered relevant but not specific to role. Might be okay to keep as a

before sections? There's no rule against having a leading paragraph. The instruction says output ONLY the HTML fragment; we can include a leading

describing company? It might be okay. But we need sections: About The Team, About The Role, Job Duties, About You (Basic Qualifications, Other Qualifications), Pay Transparency Statement, Flexible Work (Schedule), maybe Benefits? Not mentioned benefits explicitly. There's mention of "Workday Bonus Plan or a role-specific commission/bonus, as well as annual refresh stock grants." That's compensation/benefits. Also "total compensation package". Could be considered Benefits? But we have Pay section for salary ranges. Benefits could include bonus, stock grants. However we need to only create Benefits section if posting actually states them. It does mention bonus plan, commission/bonus, stock grants. That's benefits. So we can include Benefits. Schedule: Flexible work description: "With Flex Work, we’re combining the best of both worlds: in-person time and remote... spend at least half (50%) of our time each quarter in the office or in the field..." That's schedule info. So we can include Schedule. Pay: salary ranges given. Now we need to structure. Sections headings:

About the role

(but we already have About The Team and About The Role). The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should follow those exact headings? It says e.g., but we can use those headings. Likely they expect those headings. We need to map content. We have: - About the role: could combine About The Team and About The Role? Actually About The Role section exists. We'll put content from "About The Role" paragraph. - Responsibilities: from "Job Duties:" list. - Requirements: maybe from "Basic Qualifications:"? But they also have "Other Qualifications:" which could be Qualifications or Skills. The instruction includes Requirements, Qualifications, Skills. We need to decide. We have Basic Qualifications (10+ years experience etc.) and Other Qualifications (ability to lead..., produce artifacts..., partner..., Salesforce RCA/Revenue Cloud Advanced preferred, Open to 50% reporting to Atlanta office). Also there is "About You" heading. We could treat Basic Qualifications as Requirements, Other Qualifications as Qualifications, and maybe Skills as separate? But we have no explicit skills list besides those qualifications. Could combine. Better to follow: Requirements = Basic Qualifications. Qualifications = Other Qualifications. Skills maybe not present; we could omit Skills section if no specific content. But we need to ensure we don't create empty sections. Thus sections:

About the role

(content from About The Team and About The Role? Actually About The Team is separate but could be part of About the role? Might be okay to include both under About the role.)

Responsibilities

(Job Duties list)

Requirements

(Basic Qualifications list)

Qualifications

(Other Qualifications list)

Benefits

(Bonus plan, commission/bonus, stock grants)

Pay

(salary ranges)

Schedule

(Flex Work description) We should not include Skills. Now we need to format lists: use

• for any list of duties/requirements/benefits. For prose use

  . We need to preserve all substantive information, not invent or summarize away detail. So we need to keep the exact wording? Probably we can keep the substance but not necessarily verbatim? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the details, but we can rephrase? Safer to keep the original sentences. We'll extract each piece. About The Team paragraph: "The Business Technology Go-To-Market team works in close partnership with our business partners to help fuel growth and revenue goals for Workday, along with driving outstanding customer and employee experiences. The team is responsible for developing and supporting innovative architecture-led solutions aligning with business value across Marketing, Sales, Services, Partners, Customer Support & Legal business functions with Salesforce being the primary platform alongside other groundbreaking platforms like Agentforce Revenue Management, Conga, Evisort, SnapLogic, AWS, AdobeSign, Docusign, Copado, as PaaS, OKTA, and others. We are seeking a Principal Product Solution Architect, CPQ & CLM, to come join our team that cultivates relationships with built on collaboration and trust to support a rapidly growing business. This is a senior individual contributor role where the ideal candidate brings deep hands-on experience with Configure, Price, Quote and Contract Lifecycle Management platforms, strong enterprise architecture judgment, and the ability to translate complex business requirements into elegant, maintainable product and process solutions. responsible for shaping the architecture, solution strategy, and delivery approach for critical capabilities across the quote-to-contract lifecycle. Our team cultivates relationships with built on collaboration and trust to support a rapidly growing business. We strive to improve efficiency and operational effectiveness through technology, innovation and inspiration." Note there is a duplicate sentence about cultivates relationships. We'll keep but maybe deduplicate? Instruction: remove duplicated lines. So we should remove duplicate lines. The duplicate: "Our team cultivates relationships with built on collaboration and trust to support a rapidly growing business." appears twice. We'll keep one. Also there is a fragment "responsible for shaping the architecture..." starts with lowercase; it's a sentence fragment but we keep. Now About The Role paragraph: "The Product Solution Architect will provide strategic leadership for the end-to-end Quote-to-Cash business process, including Salesforce CPQ, CLM, and connected enterprise applications. This role will partner closely with Product, Engineering, Sales, Deal Desk, Legal, Finance, Operations, CX, Partners and implementation teams to design solutions that improve how business configure products, price and quote accurately, generate compliant contracts, manage approvals, and accelerate deal execution. It will be key to understand business priorities, identify process improvement opportunities, and evaluate solution options that optimize business outcomes." Now Job Duties list: after "Job Duties:" we have a series of sentences each starting with a capital letter and ending with period. They are: - Translate business strategy into scalable solutions. - Partner with the Director, CPQ & CLM, product leaders, and business stakeholders to convert strategic priorities into actionable architecture, capability roadmaps, process designs, and platform solutions. - Serve as the senior technical and functional advisor. Provide expert guidance on CPQ and CLM platform capabilities, configuration options, customization tradeoffs, integration approaches, data model decisions, automation opportunities, and long-term scalability. - Shape the responsible adoption of AI-enabled capabilities within the Quote-to-Cash process, such as pricing and deal guidance, workflow automation, and contract intelligence. Ensure AI solutions are practical, secure, governed appropriately, and grounded in reliable business and data processes. - By combining business process leadership with architectural oversight, enable the organization to scale CPQ, CLM, and AI capabilities. - Drive quote-to-contract process optimization. Identify opportunities to simplify workflows, reduce manual effort, improve approval efficiency, increase quote accuracy, accelerate contract cycle times, and improve the customer and internal user experience. - Lead cross-functional solution alignment. Facilitate design discussions with Sales, Deal Desk, Revenue Operations, Legal Operations, Finance, Product, Engineering, Security, Compliance, and Enterprise Architecture to align on requirements, dependencies, risks, and implementation options. - Establish architecture standards and governance. Create reusable design patterns, documentation standards, decision frameworks, and best practices that support long-term maintainability and product scalability. - Provide subject matter expertise. Serve as a trusted advisor on CPQ and CLM platform capabilities, configuration tradeoffs, system limitations, data dependencies, automation opportunities, and implementation risks. Note some sentences have two sentences combined with period. We'll keep as is. Now Basic Qualifications list: after "Basic Qualifications:" we have lines each starting with a number and a dot. - 10+ years of professional experience in product solution architecture, enterprise applications, business systems architecture, quote-to-cash transformation. - 10+ years of professional experience in CPQ and CLM. - 10+ years of experience in product configuration, pricing models, discounting, quoting, approval workflows, contract templates, clause libraries, negotiation, redlining, e-signature, amendments, renewals, obligations, and downstream quote-to-cash dependencies. - 10+ years of experience with CRM, CPQ, CLM, ERP,, document generation, workflow automation, reporting, and integration platforms. (note double comma after ERP,, but we keep) - 10+ years of knowledge with data models, APIs, event-driven and batch integrations, workflow engines, security models, reporting requirements, platform configuration, and system dependencies. Now Other Qualifications list: after "Other Qualifications:" we have: - Demonstrated ability to lead senior-level conversations, facilitate decision-making, resolve conflicting priorities, and influence outcomes without direct authority. - Ability to produce clear architecture artifacts, process flows, solution designs, decision records, capability maps, and executive-ready recommendations. - Experience partnering with product and engineering teams through discovery, design, build, testing, release readiness, and post-launch optimization. - Salesforce RCA/Revenue Cloud Advanced (formerly known as Revenue Lifecycle Management or RLM), Conga, Vlocity preferred. - Open to 50% reporting to our Atlanta (Buckhead) office 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 mention "total compensation package". We'll include that. Now Pay: we have salary ranges: Primary Location: USA.GA.Atlanta Primary Location Base Pay Range: $166,200 USD - $249,400 USD Additional US Location(s) Base Pay Range: $157,900 USD - $280,600 USD Also note "Workday pay ranges vary based on work location." We'll include that. Now Schedule: from Flex Work section: "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