Principal Engineer, Salesforce

We need to output HTML fragment with sections: About the role? Actually the job description includes many paragraphs. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We need to preserve all substantive info, remove boilerplate: company description? The "Company Description About AbbVie" is likely boilerplate but maybe we keep? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company description might be considered boilerplate? It's not EEO but it's generic description. Might be okay to keep? The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." The company description is substantive? It describes AbbVie mission. Might be considered part of job posting but not required sections. However we only output sections with headings; we could include a

for company description before sections? The instruction: Output ONLY the HTML fragment — no /, no markdown code fences. It didn't forbid extra paragraphs outside sections. But they said use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. So we can have prose paragraphs outside headings? Probably they expect sections with headings and content under them. Could also have a leading

  for company description before any heading? Not sure. Safer to include a section "About the role" with the job description prose (the paragraphs after Job Description). The "Company Description About AbbVie" could be placed under "About the role" or maybe separate "About the company". But they didn't list About the company as a heading option. So we could incorporate it into About the role. We need to extract responsibilities list: many bullet-like sentences but not formatted as list. We need to turn them into

  • . The responsibilities paragraph is a long sentence with many duties separated by periods. We should split into list items each duty. Similarly qualifications: list of requirements. We must not invent or summarize away detail. Must preserve all substantive info. So we need to capture each duty as separate list item, preserving the text. Let's parse responsibilities section: "Own thesystemarchitecture and engineering standardswithinOnePRMplatform,and ensure alignment withSalesforce Platformarchitecture principles,Solutions architecture standards,Salesforce best practices, security requirements, validated systems expectations, and SLC governance.Serve as the principalarchitecture & engineeringleader forOnePRM, shaping solution direction,technical architecture & design,data modeling,integration strategy,engineering decisions,and platform evolution to support business growth and long-term sustainability.Drive theOnePRMtechnical strategy and multi-year roadmapfor systems, including modernization, migration, consolidation, and future-state platform design in support of enterprise business priorities.Evaluate emerging Salesforce capabilities, AI-enabled solutions, and engineering tools; lead proofs of concept; and translate successful pilots into scalable, production-ready capabilities that improve business value and operating efficiency.Lead multiple engineering PODs and blended teams across architecture, development, QA automation, DevOps, and vendor partners, ensuring accountability todeliverycommitments, quality standards, and engineering outcomes.Define and govern scalable data models,scalable workflow automation,secure integration patterns, and resilient enterprise interfaces across Salesforce and connected platforms to support reliable business operations and future growth.Partner with program, product, and business leaders to execute complex release plans, manage dependencies, mitigate technical risks, and ensure seamless coordination across concurrent workstreams.Drive CI/CD/CT modernization and shift-left quality practices, including automation,codeanalysis, testing rigor, and compliance controls to improve release velocity and reduce production defects.Establish and govern design review, code review, release readiness, and pre-deployment approval processes to ensure consistent execution, technical quality, and compliance across internal and external delivery teams.Govern technical debt, refactoring, and remediation as strategic investments that strengthen maintainability, reduce risk, and improve long-term platform scalability.Maintain strong standards for data quality, documentation, privacy, security, and compliancein accordance withAbbVie policies, validated system requirements, and enterprise governance expectations.Coach and developapplicationarchitects, tech leads, and senior engineers; strengthen technical depth across the team; and build succession capability for critical architecture and engineering roles.Partner with senior business leaders, product owners, architects, and external partners to translate strategic needs into sustainable solutions and prioritize investments that maximize enterprise value.Oversee team capacity, vendor performance, and budgetutilizationtooptimizedelivery efficiency,maintainaccountability, and ensure responsible stewardship of engineering investments." We need to split at each period that ends a sentence. However some sentences have abbreviations like "CI/CD/CT". That's okay. We'll produce list items each sentence. Similarly Qualifications: It's a paragraph with multiple sentences. Qualifications text: "Required: Bachelors degree or equivalent education with 8 years of experience, Masters degree or equivalent education with 7 years of experience, or PhD with 3 years of experience in application strategy, requirements, architecture, design, engineering, and related technology disciplinesExperience inplanning,architecture, design, development, integration, and operations of CRM solutions on the Salesforce platform, using service cloud, experience cloud, health cloud / life sciences cloud; pharmaceutical or life sciences industry experience preferred.Deep hands-on experience with Salesforce CRM technical capabilities, includingworkflow automation, responsive UI,data architecture, relational data modeling,data migration, data quality management,API engineering, integration design, and platform configuration.In-depth knowledge of the systems development life cycle, enterprise application development practices, and technology alternatives for complex business systems.Demonstrated experience leading large enterprise projects with responsibility for business requirements analysis, solution architecture, technical design, and end-to-end solution delivery.Demonstrated ability to lead technically complex initiatives, influence stakeholders, and provide guidance to engineering teams, architects, and vendor partners.Strong understanding of enterprise architecture principles, Salesforce Well-Architected concepts, and the design of scalable, sustainable, and supportable enterprise solutions.Hands-on experience with Salesforce development and configuration tools, including Apex, Triggers, Lightning Web Components (LWC), Flows, and integration features.Strong background in integration architecture and engineering, including REST and SOAP APIs, middleware-based integrations, direct system-to-system interfaces, and enterprise integration patterns.Demonstrated ability to apply object-oriented design principles and design patterns to enterprise solutions.Experience with DevOps, CI/CD/CT practices, and Salesforce ecosystem delivery tooling to support automated, repeatable, and high-quality releases.Experience with Salesforce Data 360andAgentforcepreferred. Experience with Agentic software engineering usingAgentforceVibes is preferred.Excellent verbal and written communication skills, with the ability to present complex technical concepts clearly to senior BTS leaders, business stakeholders, and cross-functional partners. Preferred Salesforce Administrator, Platform App Builder, Platform DeveloperI, andApplication Architect and/or System Architect certification, or active pursuit of those architect-level credentials.Additional Salesforce Consultant certifications, such as Sales Cloud, Service Cloud, or other relevant cloud certifications.Salesforce certifications in Data Architecture and Management and Integration Architecture." We need to split into list items each sentence. Note there are some missing spaces due to OCR: e.g., "disciplinesExperience". We'll keep as is but maybe add a space? We must not invent detail; we should preserve exactly as given? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should not add spaces that weren't there. However the missing spaces are likely OCR errors; but we must not "invent". Changing text could be considered inventing? It's ambiguous. Safer to keep the exact text as given, even if it runs together. But readability suffers. However we must not add info. I'd keep as is. Similarly Benefits: The posting mentions: "We offer a comprehensive package of benefits including paid time off (vacation, holidays, sick),medical/dental/visioninsurance and 401(k) to eligibleemployees.This job is eligible toparticipatein our long-term incentiveprograms." Also earlier: "Note: No amount of payis considered to bewages or compensation until such amount is earned, vested, anddeterminable.The amount and availability of any bonus,commission,incentive, benefits, or any other form ofcompensation and benefitsthat are allocable to a particular employeeremainsin the Company's sole andabsolutediscretion unless anduntil paid andmay bemodifiedat the Companys sole and absolute discretion, consistent withapplicable law." That's more about compensation. Pay: The posting includes a compensation range description: "Applicable only to applicants applying to a position in any location with pay disclosure requirements under state orlocal law: The compensation range described below is the range of possible base pay compensation that the Companybelieves ingood faith it will pay for this role at the timeof thisposting based on the job grade for this position.Individualcompensation paid within this range will depend on many factors including geographic location,andwemayultimatelypaymore or less than the posted range. This range may bemodifiedin thefuture." However they didn't actually give numbers. So we cannot create Pay section because no specific numbers. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits: they do state benefits (paid time off, medical/dental/vision insurance, 401(k), long-term incentive programs). So we can include Benefits section. Schedule: not mentioned. So omit Schedule. Skills: Not explicitly a separate section; but we could include Skills if there is a list of skills. The qualifications include many skills; but we could treat Qualifications as covering requirements. The instruction: Use headings for Skills if there is real specific content. The posting does not have a separate "Skills" heading; but we could still create a Skills section if we extract skills from qualifications. However that might be considered inventing a section not present. Better to follow the given headings only when posting has real specific content for it. Since there is no explicit Skills section, we should not create one. We'll have Qualifications (which includes requirements). Could also have Requirements (maybe same as Qualifications). The posting has "Qualifications Required:" and then list. So we can use Qualifications heading. We also need About the role: we can put the job description paragraphs (the long description) as prose under About the role. Could also split into

    paragraphs. We must not repeat the job title as a heading. We must not include Job ID/requisition numbers. We must remove boilerplate: EEO etc. At end there is equal opportunity employer text; we should remove. Also remove "Additional Information" about pay disclosure? That's part of Pay but we don't have numbers, but we could still include that as prose under Benefits? Actually it's about pay disclosure; but since we aren't making Pay section, we could maybe include that as a

    under About the role? But it's about compensation; maybe better to omit because it's boilerplate? It's not exactly boilerplate; it's a standard disclosure. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is a legal disclosure about pay; might be considered legal boilerplate. Safer to remove. Thus we will output:

    About the role

    AbbVie US Commercial Business Technology Solutions (BTS) is seeking a Principal Engineer, Salesforce to join the Patient Services & Consumer Marketing Technology Services and Architecture team. This role provides strategic and technical leadership for the planning, architecture, design, integration, implementation, and operations of Patient Services solutions on AbbVie's OnePRM (Patient Relationship Management) platform. This position is accountable for advancing the modernization of Patient Services capabilities that help patients start therapy faster, remain adherent to treatment, and receive more personalized, data- and AI-enabled experiences. The role owns the long-term technology roadmap for solutions supporting more than 2,200 end users and 2