Specialist Solutions Architect, Data

We need to output HTML fragment with sections: About the role? Actually the posting includes "Who We Are", "About Stripe", "About The Team", "What You'll Do", "Responsibilities", "Who You Are", "Minimum Requirements", "Preferred Qualifications", "Hybrid work at Stripe", "Pay and benefits". We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we must only include sections when posting has real specific content. We need to map content to these headings. We have content: "Who We Are About Stripe" maybe not needed as heading? The instruction: Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. We need to produce sections like About the role (maybe summarizing "About The Team" and "What You'll Do"?). Responsibilities: we have a list. Requirements: Minimum Requirements. Qualifications: Preferred Qualifications? Skills maybe part of requirements? Benefits: we have Pay and benefits section includes salary range and additional benefits. Pay: we have salary range. Schedule: we have Hybrid work at Stripe describing remote/in-office expectations. So we can include Schedule section. We must not include sections with filler like "commensurate with experience". We have actual content. We need to use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format them. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At end there is "Please find our California applicant personal information notice here. The application window will remain open for 100 days after the Job Post is published..." That's application instructions/boilerplate; we should remove. Also "We look forward to hearing from you..." maybe not boilerplate? It's a closing statement; but might be considered generic. Safer to remove? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The closing statement is not exactly those, but could be considered generic. However we might keep it as part of "About the role"? Might be safer to keep substantive content only. The closing statement is not substantive about role; it's a call to action. Probably remove. Also "At Stripe, we're looking for people with passion, grit, and integrity..." that's also generic; could be removed. We need to keep: Who We Are About Stripe (description), About The Team, What You'll Do, Responsibilities, Who You Are (minimum requirements), Preferred Qualifications, Hybrid work at Stripe, Pay and benefits. We need to map to headings: - About the role: could combine "Who We Are About Stripe", "About The Team", "What You'll Do". Provide prose. - Responsibilities: list. - Requirements: Minimum Requirements (list). - Qualifications: Preferred Qualifications (list). Could also include Skills? But we have skills within requirements; maybe we can put skills under Requirements as part of list? But we need a Skills section only if posting has real specific content for it. The posting includes skills like communication, presentation, etc within Minimum Requirements. Could create a Skills section but we already have those in Requirements. To avoid duplication, maybe we put skills under Requirements. The instruction: Use sections only when posting has real specific content for it. We have content for Skills (communication, presentation, etc). Could create a Skills section separate from Requirements. But we already have Requirements (minimum). Might be better to have Requirements (minimum) and Qualifications (preferred) and Skills (communication etc). However the Minimum Requirements already list skills like "Exceptional communication, presentation, and interpersonal skills". That's a skill. So we could split: Requirements: experience and technical qualifications; Skills: soft skills. But we risk duplication. Safer to follow the headings given: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We'll allocate content accordingly. Let's extract: About the role: description of Stripe, team, what you'll do. Responsibilities: bullet list. Requirements: Minimum Requirements (experience, hands-on experience, understanding, BI/analytics, software engineering/API integration, communication, presentation, interpersonal, collaborative relationships, ambiguity). That's a mix; but we can treat as Requirements. Qualifications: Preferred Qualifications (list). Skills: maybe we can extract communication etc from Requirements and put here, but we already used them. Could instead put soft skills under Skills and keep Requirements more technical. Let's parse Minimum Requirements: - 7+ years of experience in a technical sales, pre-sales, or solutions architecture role, with a focus on data platforms, analytics, or financial reporting - 3+ years of hands-on experience with data warehousing and pipeline architecture (e.g., Snowflake, BigQuery, Redshift, Databricks) and ETL/ELT tooling - Strong understanding of how payments and revenue data maps to financial reporting and reconciliation workflows - Experience working with or implementing BI/analytics platforms (Looker, Tableau, Sigma, Metabase, or similar) - Strong knowledge of software engineering and API integration patterns, including how data pipelines are built and maintained - Exceptional communication, presentation, and interpersonal skills, comfortable explaining complex technical concepts to both technical and non-technical audiences - A proven ability to build strong collaborative working relationships with business partners - Ability to deal effectively with ambiguity and thrive in an unstructured, fast-moving environment We could split: Requirements (first 5 bullet points) and Skills (last 3 bullet points). That seems reasonable. Qualifications: Preferred Qualifications list. Benefits: Additional benefits (equity, company bonus or sales commissions/bonuses; 401(k) plan; medical, dental, and vision benefits; and wellness stipends.) Pay: annual US base salary range $239,900 - $359,900, plus note about OTE. Schedule: Hybrid work at Stripe description. Now we need to output HTML fragment with

  headings and appropriate

  or

  • . We must not include any extra markup like or . Just the fragment. Let's craft. First, About the role: combine Who We Are About Stripe, About The Team, What You'll Do. We need to preserve all substantive information: So we need to include the sentences about Stripe mission, team description, what you'll do. Let's write a paragraph summarizing but not losing detail. However instruction: do NOT invent or summarize away detail. So we must keep the details, not just summarize. We can keep them as separate paragraphs but still preserve detail. That's okay. We'll produce:

    About the role

    Stripe is a financial infrastructure platform for businesses. Millions of companies—from the world's largest enterprises to the most ambitious startups—use Stripe to accept payments, grow their revenue, and accelerate new business opportunities. Our mission is to increase the GDP of the internet, and we have a staggering amount of work ahead.

    Specialist Solutions Architects (SSA) are domain experts aligned to specific Stripe solutions and customer buying centers. We have in-depth knowledge of specific solution offerings and a deep understanding of customer challenges. We align with specialist product sellers on deals, advise the broader pre-sales team on complex opportunities, support pipeline development and revenue attainment, serve as an advisor on go-to-market sales plays, and provide critical insights to our product and engineering teams.

    You will collaborate closely with sales and pre-sales teams to drive pipeline and revenue targets, while also educating the product and engineering teams on market trends and strongly influencing the product roadmap. You will develop deep relationships with senior customer business leaders and grow Stripe's solution offerings with new and existing customers. As a subject matter expert, you will scale the broader organization by creating reusable assets and coaching others on complex, high-value opportunities.

    That preserves details. Now Responsibilities: list each bullet. We need to capture each responsibility line from posting. List: - Act as a subject matter expert on Stripe's Data products (data pipelines/export, revenue and reconciliation reporting, and analytics tooling) to accelerate opportunities - Demonstrate a deep understanding of how businesses warehouse and model payments and revenue data — data pipelines into Snowflake, BigQuery, Redshift, and Databricks; ETL/ELT patterns; and how that data feeds financial reporting, reconciliation, and BI - Conduct deep discovery of customers' existing data architecture, warehouse, and reporting stack to architect solutions that align Stripe's Data capabilities with their analytics and finance requirements - Advise customers on how to design for complexity: multi-entity and multi-currency reporting, custom data models, integration with existing BI tools (Looker, Tableau, Sigma, Metabase) and ERP/GL systems, and data freshness/latency requirements - Create and share best practices and reusable assets such as reference architectures to enhance the quality and efficiency of the broader sales and pre-sales organizations - Partner closely with the Data product sales team and actively drive opportunities for Stripe's largest customers, leading solution strategy and owning key customer relationships - Serve as a "Voice of the Customer" to drive product and feature request prioritization - Identify product, industry, implementation, and competitive trends, and provide actionable insights to product stakeholders and sales to influence Stripe's Data product roadmap - Act as an escalation point to drive complex technical issues to resolution with Stripe's engineering team - Represent the technical health of the business on quarterly sales forecast calls and highlight deal blockers with proposed solutions - Support marketing events including executive briefings, conferences, user groups, and trade shows We'll put each as
  • . Now Requirements: we will list first five bullet points from Minimum Requirements (technical/experience). We'll keep them as
  • . List: - 7+ years of experience in a technical sales, pre-sales, or solutions architecture role, with a focus on data platforms, analytics, or financial reporting - 3+ years of hands-on experience with data warehousing and pipeline architecture (e.g., Snowflake, BigQuery, Redshift, Databricks) and ETL/ELT tooling - Strong understanding of how payments and revenue data maps to financial reporting and reconciliation workflows - Experience working with or implementing BI/analytics platforms (Looker, Tableau, Sigma, Metabase, or similar) - Strong knowledge of software engineering and API integration patterns, including how data pipelines are built and maintained Now Skills: list the remaining three bullet points: - Exceptional communication, presentation, and interpersonal skills, comfortable explaining complex technical concepts to both technical and non-technical audiences - A proven ability to build strong collaborative working relationships with business partners - Ability to deal effectively with ambiguity and thrive in an unstructured, fast-moving environment Now Qualifications: Preferred Qualifications list: - Experience integrating Stripe or other RESTful APIs into data pipelines or web applications - Familiarity with complex reporting scenarios: multi-entity consolidation, revenue recognition data models, or usage-based billing data - Experience with SQL at an advanced level and comfort working directly in a customer's data warehouse during discovery - Experience as a subject matter expert in financial services, fintech, or a data/analytics vertical - Pre-sales experience with Enterprise customers Now Benefits: list additional benefits: - equity - company bonus or sales commissions/bonuses - 401(k) plan - medical, dental, and vision benefits - wellness stipends We'll put as
  • . Now Pay: we need to include salary range and note about OTE. We'll put as

    The annual US base salary range for this role is $239,900 - $359,900. For sales roles