Salesforce Integration Architect

We need to output only HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate like EEO, application instructions, etc. Must preserve all substantive info. We need to parse the posting. Content: Company description: Bright Vision Technologies is a technology consulting and software development company delivering cloud, AI, data, and enterprise solutions across the United States. This is a fantastic opportunity to join an established and well-respected organization offering tremendous career growth potential. Location: 100% Remote (U.S.) Position Type: Full-time, Direct W2 Salary Range: $100,000–$180,000 Annually Experience Required: 12+ years Sponsorship: U.S. Citizens, Green Card Holders, EAD Holders, and H-1B transfer candidates are encouraged to apply. We are unable to sponsor new H-1B visa petitions for this position. Job Summary: We are seeking a Salesforce Integration Architect to design and govern integrations between Salesforce and the broader enterprise application landscape. The role focuses on integration architecture, middleware selection, API strategy, and event-driven patterns that connect Salesforce reliably with ERP, data, marketing, and operational systems. The ideal candidate has architected Salesforce integration solutions at meaningful scale and brings deep familiarity with both Salesforce-native and enterprise middleware approaches. In this role you will work closely with cross-functional partners — product, design, engineering, operations, and business stakeholders — to translate ambiguous requirements into well-engineered solutions, and will be expected to raise the bar through code review, design review, and mentorship of more junior engineers. The successful candidate brings strong engineering discipline, a clear communication style, and a track record of shipping meaningful work that holds up well in production. Key Responsibilities: list many bullet points. Required Qualifications: list bullet points. Preferred Qualifications: list bullet points. How To Apply: instructions (should be removed as application instructions). Also EEO statement removed. We need sections: About the role (maybe company description + location + position type?), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Pay: Salary Range given. So we can include Pay section. Schedule: Not explicitly given; maybe full-time implies schedule but not specific. We should not create Schedule unless posting actually states them. It does not state schedule details like hours, shift. So we should omit Schedule. Benefits: Not mentioned. No benefits details. So omit Benefits. Skills: Could be derived from qualifications? But we need to see if there is a specific Skills section in posting. Not explicitly. Could combine qualifications and skills? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include only those with real content. We have About the role (company overview, location, position type). Responsibilities (Key Responsibilities). Requirements (Experience Required? maybe also Sponsorship?). Qualifications (Required Qualifications). Skills (maybe Preferred Qualifications? Or we could treat Preferred Qualifications as Skills). But we need to decide. The posting includes "Required Qualifications" and "Preferred Qualifications". Those could map to Qualifications and Skills? Usually Skills separate. But we can treat Required Qualifications as Qualifications, Preferred Qualifications as Skills. Or we could combine both under Qualifications and omit Skills. However we need to follow instruction: include a section ONLY when posting has real, specific content for it. So we need to decide if there is content for Skills. The posting does not have a separate "Skills" heading, but we could infer that the qualifications include skills. However we should not invent sections. Better to not create a Skills section unless there is explicit skills list. There is no explicit Skills heading. So we omit Skills. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Pay. Check if we need Requirements separate from Qualifications. The posting has "Experience Required: 12+ years" and Sponsorship info. That could be Requirements. Also maybe "Job Summary" could be part of About the role. We'll put About the role: company description, location, position type, job summary? Actually job summary is more about role. Could be part of About the role. But we also have Responsibilities separate. So About the role could include company overview, location, position type, and maybe a brief summary. We'll include company description, location, position type, and job summary (the paragraph after Job Summary). That seems appropriate. Responsibilities: list the bullet points under Key Responsibilities. Requirements: include Experience Required: 12+ years, Sponsorship info (U.S. Citizens etc). Also maybe "Position Type: Full-time, Direct W2" could be part of About the role. We'll keep it there. Qualifications: Required Qualifications bullet list. Pay: Salary Range. We must not include application instructions, EEO, etc. Now format: Use

for each section heading. Use

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

  for prose. We need to preserve all substantive information. Ensure we don't lose any details. Let's extract details. About the role prose: - Bright Vision Technologies is a technology consulting and software development company delivering cloud, AI, data, and enterprise solutions across the United States. - This is a fantastic opportunity to join an established and well-respected organization offering tremendous career growth potential. - Location: 100% Remote (U.S.) - Position Type: Full-time, Direct W2 - Job Summary: We are seeking a Salesforce Integration Architect to design and govern integrations between Salesforce and the broader enterprise application landscape. The role focuses on integration architecture, middleware selection, API strategy, and event-driven patterns that connect Salesforce reliably with ERP, data, marketing, and operational systems. The ideal candidate has architected Salesforce integration solutions at meaningful scale and brings deep familiarity with both Salesforce-native and enterprise middleware approaches. In this role you will work closely with cross-functional partners — product, design, engineering, operations, and business stakeholders — to translate ambiguous requirements into well-engineered solutions, and will be expected to raise the bar through code review, design review, and mentorship of more junior engineers. The successful candidate brings strong engineering discipline, a clear communication style, and a track record of shipping meaningful work that holds up well in production. We could combine into paragraphs. Responsibilities list (from Key Responsibilities): - Define the end-to-end integration architecture for Salesforce ecosystems spanning Sales, Service, Marketing, and Industry Clouds - Select and apply appropriate integration patterns including request-reply, fire-and-forget, batch, and event-driven approaches - Design integrations using Salesforce-native capabilities (Platform Events, Change Data Capture, Connect, Composite APIs) alongside enterprise middleware such as MuleSoft, Boomi, or Informatica - Lead integration design reviews and approve technical designs across Salesforce programs - Define API strategy, contract management, and versioning standards for Salesforce-related integrations - Architect data synchronization patterns for high-volume integrations with ERP, billing, and operational systems - Design identity and access patterns for Salesforce integrations including OAuth flows and connected app management - Establish error handling, retry, and dead-letter strategies that ensure reliable integration operations - Drive performance, scalability, and governor-limit management for integration-heavy Salesforce implementations, designing patterns that stay safely within platform limits even as transaction volumes grow over time - Collaborate with security teams to ensure integrations meet enterprise security requirements - Mentor and coach junior and mid-level engineers through code review, design review, pair programming, and structured knowledge sharing, helping the broader team grow in technical maturity and confidence over time - Produce high-quality architecture artifacts — context diagrams, sequence diagrams, decision records, and reference designs — that capture key technical decisions clearly enough to be understood months or years later - Collaborate closely with vendors to evaluate and onboard integration platforms, gathering requirements, aligning on technical approach, and ensuring that delivered solutions meet both functional needs and broader engineering and operational standards - Stay current with Salesforce integration capabilities and broader iPaaS evolution Requirements list: - Experience Required: 12+ years - Sponsorship: U.S. Citizens, Green Card Holders, EAD Holders, and H-1B transfer candidates are encouraged to apply. We are unable to sponsor new H-1B visa petitions for this position. Maybe also "Position Type: Full-time, Direct W2" but we already used in About the role. Qualifications list (Required Qualifications): - Bachelor’s or Master’s degree in Computer Science or a related field - 12 or more years of Salesforce experience, with significant time on complex integrations - Deep understanding of Salesforce APIs, Platform Events, and Change Data Capture - Hands-on experience with at least one major iPaaS such as MuleSoft, Boomi, or Informatica - Strong understanding of integration patterns and enterprise application architecture - Experience designing data synchronization strategies with ERP and operational systems - Strong understanding of identity, OAuth, and integration security - Excellent communication and stakeholder management skills - Salesforce Certified Integration Architect credential - Track record of leading large Salesforce integration programs Preferred Qualifications (we could treat as Skills? but we decided not to include Skills. However we might include them under Qualifications as additional? But they are preferred, not required. Could we add a separate section "Preferred Qualifications"? Not in allowed headings. Could we put them under Qualifications as a sublist? Might be okay to include them under Qualifications as additional bullet points, but we should differentiate? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It does not forbid having extra content under Qualifications beyond required. So we can include both required and preferred under Qualifications, maybe with a note "Preferred". But we must not invent headings. So we can just add them as part of Qualifications list. Thus Qualifications will include both required and preferred bullet points. Pay section: Salary Range: $100,000–$180,000 Annually. Now ensure we don't include any boilerplate: Remove "How To Apply", EEO statement, "Powered by JazzHR", etc. Now produce HTML fragment:

  About the role

  Bright Vision Technologies is a technology consulting and software development company delivering cloud, AI, data, and enterprise solutions across the United States. This is a fantastic opportunity to join an established and well-respected organization offering tremendous career growth potential. Location: 100% Remote (U.S.). Position Type: Full-time, Direct W2. We are seeking a Salesforce Integration Architect to design and govern integrations between Salesforce and the broader enterprise application landscape. The role focuses on integration architecture, middleware selection, API strategy, and event-driven patterns that connect Salesforce reliably with ERP, data, marketing, and operational systems. The ideal candidate has architected Salesforce integration solutions at meaningful scale and brings deep familiarity with both Salesforce-native and enterprise middleware approaches. In this role you will work closely with cross-functional partners — product, design, engineering, operations, and business stakeholders — to translate ambiguous requirements into well-engineered solutions, and will be expected to raise the bar through code review, design review, and mentorship of more junior engineers. The successful candidate brings strong engineering discipline, a clear communication style, and a track record of shipping meaningful work that holds up well in production.

  Responsibilities

  • Define the end-to-end integration architecture for Salesforce ecosystems spanning Sales, Service, Marketing, and Industry Clouds
  • Select and apply appropriate integration patterns including request-reply, fire-and-forget, batch, and event-driven approaches
  • Design integrations using Salesforce-native capabilities (Platform Events, Change Data Capture, Connect, Composite APIs) alongside enterprise middleware such as MuleSoft, Boomi, or Informatica