Sr. Salesforce Technical Architect II (6816)
for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose. Remove boilerplate, navigation, EEO, etc. Must preserve all substantive info. Include sections only if posting has real specific content.
Let's extract content:
Job description: As Sr. Salesforce Technical Architect II, you’ll serve as the subject matter expert (SME) for all Salesforce platform capabilities, architecture, and implementation decisions within a large-scale modernization and digital transformation program. This role will define how Salesforce is built, not just what is built—owning decisions across the full spectrum of platform capabilities, including declarative configuration vs. custom development, Apex vs. Flow, Lightning Web Components (LWC) vs. OmniStudio, and integration patterns. The ideal candidate brings deep, multi-domain Salesforce expertise and operates confidently as both a hands-on technical leader and strategic architect, guiding teams in building scalable, secure, and maintainable solutions within an AI-enabled engineering ecosystem. We know that you can’t have great technology services without amazing people. At MetroStar, we are obsessed with our people and have led a two-decade legacy of building the best and brightest teams. Because we know our future relies on our deep understanding and relentless focus on our people, we live by our mission: A passion for our people. Value for our customers. If you think you can see yourself delivering our mission and pursuing our goals with us, then check out the job description below!
Then "What you’ll do:" list bullet points.
Then "What you’ll need to succeed:" list bullet points.
Then "SALARY RANGE: $160,000 - $180,000" plus explanation.
Then "Additional Compensation: This role may also be eligible for bonuses and/or additional incentives based on individual and company performance."
Then "Benefits: All full-time employees are eligible to participate in our benefits programs:" list.
Then "Like we said, we are big fans of our people..." etc. That's fluff but still about benefits? Might be considered boilerplate but it's about benefits. We can include benefits details.
We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove "Application Deadline: Applications will be accepted on a rolling basis until the position is filled; candidates are encouraged to apply as early as possible for full consideration." That's application instruction, remove.
Also remove "Additional Compensation: This role may also be eligible for bonuses and/or additional incentives based on individual and company performance." That's part of compensation but not salary range; we can include under Pay? Might be considered part of Pay section. We can include in Pay section.
Also remove "Like we said, we are big fans of our people. That’s why we offer a generous benefits package, professional growth, and valuable time to recharge. Learn more about our company culture code and benefits. Plus, check out our accolades." That's fluff; maybe we can keep as part of Benefits? It's generic; but we already have benefits list. Might be considered boilerplate; we can drop.
Also remove "Commitment to Non-Discrimination ..." and "What we want you to know: In compliance with federal law, all persons hired will be required to verify identity and eligibility to work in the United States and to complete the required employment eligibility verification form upon hire. Not ready to apply now? Sign up to join our newsletter here." That's boilerplate; remove.
Now we need sections.
Potential sections:
- About the role: could be the introductory paragraph(s) describing role and mission. Use
.
- Responsibilities: the "What you’ll do:" bullet list.
- Requirements: maybe combine "What you’ll need to succeed:" as Requirements? Could also have Qualifications and Skills separate. The posting lists experience, technical expertise, etc. Could split: Requirements (experience), Qualifications (education, certifications), Skills (technical). But we need to avoid thin sections. Perhaps combine Requirements and Qualifications into one? But guidelines: Use headings only when posting has real specific content. We have content for each.
Let's parse:
"What you’ll need to succeed:" includes:
- 8–10 years of experience in software engineering and architecture, with 6+ years hands-on Salesforce expertise.
- Deep technical expertise in Apex, LWC, OmniStudio, and Flow, including performance optimization and advanced design patterns.
- Proven ability to make architectural decisions across OOTB, low-code, and custom development approaches.
- Strong experience designing and implementing enterprise integrations (REST, SOAP, events, middleware).
- Deep understanding of Salesforce data modeling, security architecture, and sharing models.
- Experience operating in Agile, DevSecOps, and continuous delivery environments, including AI-assisted development practices.
- Bachelor’s degree in Computer Science, Engineering, Information Systems, or related field (or equivalent experience).
- Active Secret clearance
- Salesforce architect-level certification (Application Architect, System Architect, or Platform Developer II).
We could split:
- Requirements: experience (8-10 years, 6+ Salesforce), maybe also Agile/DevSecOps experience.
- Qualifications: Bachelor’s degree, Active Secret clearance, Salesforce architect-level certification.
- Skills: technical expertise in Apex, LWC, OmniStudio, Flow, architectural decisions, integrations, data modeling, security, etc.
But we need to avoid duplication. Let's decide:
Section "Requirements": list of experience requirements (years, hands-on, Agile/DevSecOps, etc.)
Section "Qualifications": education, clearance, certifications.
Section "Skills": deep technical expertise list.
But the posting also includes "Proven ability to make architectural decisions across OOTB, low-code, and custom development approaches." That's skill.
"Strong experience designing and implementing enterprise integrations (REST, SOAP, events, middleware)." skill.
"Deep understanding of Salesforce data modeling, security architecture, and sharing models." skill.
Thus we can allocate.
Now Benefits: list: Health, dental, and vision insurance; 401(k) retirement plan with company match; Paid time off (PTO) and holidays; Parental Leave and dependent care; Flexible work arrangements; Professional development opportunities; Employee assistance and wellness programs.
Pay: Salary range $160,000 - $180,000; plus mention of additional compensation (performance-based bonuses, company-paid training and/or certifications, referral bonuses). Also "Additional Compensation: This role may also be eligible for bonuses and/or additional incentives based on individual and company performance." We'll combine.
Schedule: Not mentioned. So we should not include Schedule section.
Now About the role: The initial paragraphs describing role and mission. Could be two paragraphs: first paragraph about role, second about mission/people. We'll keep as
maybe combine.
Now Responsibilities: bullet list from "What you’ll do:".
Let's extract bullet points:
- Serve as the Salesforce architectural authority, owning platform design across configuration, customization, and integrations.
- Define OOTB vs. Flow vs. Apex vs. LWC vs. OmniStudio decisions, balancing scalability, speed, and maintainability.
- Establish and enforce architecture standards, design patterns, and best practices across the platform.
- Design end-to-end, multi-cloud Salesforce architectures including Service, Experience, Data Cloud, and AI capabilities.
- Act as a hands-on architect, contributing to complex builds (Apex, LWC, integrations, data models) when needed.
- Lead solution design sessions, code reviews, and technical deep dives to ensure quality and alignment.
- Architect scalable, high-performance applications using the optimal mix of declarative and custom approaches.
- Define enterprise integration and data architecture, including APIs, event-driven patterns, governance, and analytics readiness.
- Drive adoption of AI-enabled engineering, leveraging Einstein, Agentforce, and intelligent automation.
- Enforce security, governance, and DevSecOps practices while partnering with stakeholders to deliver robust, risk-aware solutions.
Now we need to output HTML fragment only, no markdown fences.
Let's craft.
We'll start with
About the role
then ...
.
Then Responsibilities
then - ...
.
Then Requirements
then - ...
for experience requirements.
Then Qualifications
then - ...
for degree, clearance, cert.
Then Skills
then - ...
for technical expertise.
Then Benefits
then - ...
.
Then Pay
then ...
for salary range and additional compensation.
We must not include Schedule.
Check for any duplicated lines: ensure we didn't repeat.
Now write content.
About the role paragraph: combine first two paragraphs maybe.
Original: "As Sr. Salesforce Technical Architect II, you’ll serve as the subject matter expert (SME) for all Salesforce platform capabilities, architecture, and implementation decisions within a large-scale modernization and digital transformation program.This role will define how Salesforce is built, not just what is built—owning decisions across the full spectrum of platform capabilities, including declarative configuration vs. custom development, Apex vs. Flow, Lightning Web Components (LWC) vs. OmniStudio, and integration patterns.The ideal candidate brings deep, multi-domain Salesforce expertise and operates confidently as both a hands-on technical leader and strategic architect, guiding teams in building scalable, secure, and maintainable solutions within an AI-enabled engineering ecosystem.We know that you can’t have great technology services without amazing people. At MetroStar, we are obsessed with our people and have led a two-decade legacy of building the best and brightest teams. Because we know our future relies on our deep understanding and relentless focus on our people, we live by our mission: A passion for our people. Value for our customers.If you think you can see yourself delivering our mission and pursuing our goals with us, then check out the job description below!"
We can trim the last sentence about checking out job description below (since we are already in description). Might be considered boilerplate? It's a call to action; maybe remove as it's not substantive. We'll keep the core description.
Thus About the role paragraph: "As Sr. Salesforce Technical Architect II, you’ll serve as the subject matter expert (SME) for all Salesforce platform capabilities, architecture, and implementation decisions within a large-scale modernization and digital transformation program. This role will define how Salesforce is built, not just what is built—owning decisions across the full spectrum of platform capabilities, including declarative configuration vs. custom development, Apex vs. Flow, Lightning Web Components (LWC) vs. OmniStudio, and integration patterns. The ideal candidate brings deep, multi-domain Salesforce expertise and operates confidently as both a hands-on technical leader and strategic architect, guiding teams in building scalable, secure, and maintainable solutions within an AI-enabled engineering ecosystem. We know that you can’t have great technology services without amazing people. At MetroStar, we are obsessed with our people and have led a two-decade legacy of building the best and brightest teams. Because we know our future relies on our deep understanding and relentless focus on our people, we live by our mission: A passion for our people. Value for our customers."
Now Responsibilities list as above.
Now Requirements: list experience items:
- 8–10 years of experience in software engineering and architecture, with 6+ years hands-on Salesforce expertise.
- Experience operating in Agile, DevSecOps, and continuous delivery environments, including AI-assisted development practices.
Maybe also "Proven ability to make architectural decisions across OOTB, low-code, and custom development approaches." but that's skill. We'll keep
for prose. Remove boilerplate, navigation, EEO, etc. Must preserve all substantive info. Include sections only if posting has real specific content. Let's extract content: Job description: As Sr. Salesforce Technical Architect II, you’ll serve as the subject matter expert (SME) for all Salesforce platform capabilities, architecture, and implementation decisions within a large-scale modernization and digital transformation program. This role will define how Salesforce is built, not just what is built—owning decisions across the full spectrum of platform capabilities, including declarative configuration vs. custom development, Apex vs. Flow, Lightning Web Components (LWC) vs. OmniStudio, and integration patterns. The ideal candidate brings deep, multi-domain Salesforce expertise and operates confidently as both a hands-on technical leader and strategic architect, guiding teams in building scalable, secure, and maintainable solutions within an AI-enabled engineering ecosystem. We know that you can’t have great technology services without amazing people. At MetroStar, we are obsessed with our people and have led a two-decade legacy of building the best and brightest teams. Because we know our future relies on our deep understanding and relentless focus on our people, we live by our mission: A passion for our people. Value for our customers. If you think you can see yourself delivering our mission and pursuing our goals with us, then check out the job description below! Then "What you’ll do:" list bullet points. Then "What you’ll need to succeed:" list bullet points. Then "SALARY RANGE: $160,000 - $180,000" plus explanation. Then "Additional Compensation: This role may also be eligible for bonuses and/or additional incentives based on individual and company performance." Then "Benefits: All full-time employees are eligible to participate in our benefits programs:" list. Then "Like we said, we are big fans of our people..." etc. That's fluff but still about benefits? Might be considered boilerplate but it's about benefits. We can include benefits details. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove "Application Deadline: Applications will be accepted on a rolling basis until the position is filled; candidates are encouraged to apply as early as possible for full consideration." That's application instruction, remove. Also remove "Additional Compensation: This role may also be eligible for bonuses and/or additional incentives based on individual and company performance." That's part of compensation but not salary range; we can include under Pay? Might be considered part of Pay section. We can include in Pay section. Also remove "Like we said, we are big fans of our people. That’s why we offer a generous benefits package, professional growth, and valuable time to recharge. Learn more about our company culture code and benefits. Plus, check out our accolades." That's fluff; maybe we can keep as part of Benefits? It's generic; but we already have benefits list. Might be considered boilerplate; we can drop. Also remove "Commitment to Non-Discrimination ..." and "What we want you to know: In compliance with federal law, all persons hired will be required to verify identity and eligibility to work in the United States and to complete the required employment eligibility verification form upon hire. Not ready to apply now? Sign up to join our newsletter here." That's boilerplate; remove. Now we need sections. Potential sections: - About the role: could be the introductory paragraph(s) describing role and mission. Use
. - Responsibilities: the "What you’ll do:" bullet list. - Requirements: maybe combine "What you’ll need to succeed:" as Requirements? Could also have Qualifications and Skills separate. The posting lists experience, technical expertise, etc. Could split: Requirements (experience), Qualifications (education, certifications), Skills (technical). But we need to avoid thin sections. Perhaps combine Requirements and Qualifications into one? But guidelines: Use headings only when posting has real specific content. We have content for each. Let's parse: "What you’ll need to succeed:" includes: - 8–10 years of experience in software engineering and architecture, with 6+ years hands-on Salesforce expertise. - Deep technical expertise in Apex, LWC, OmniStudio, and Flow, including performance optimization and advanced design patterns. - Proven ability to make architectural decisions across OOTB, low-code, and custom development approaches. - Strong experience designing and implementing enterprise integrations (REST, SOAP, events, middleware). - Deep understanding of Salesforce data modeling, security architecture, and sharing models. - Experience operating in Agile, DevSecOps, and continuous delivery environments, including AI-assisted development practices. - Bachelor’s degree in Computer Science, Engineering, Information Systems, or related field (or equivalent experience). - Active Secret clearance - Salesforce architect-level certification (Application Architect, System Architect, or Platform Developer II). We could split: - Requirements: experience (8-10 years, 6+ Salesforce), maybe also Agile/DevSecOps experience. - Qualifications: Bachelor’s degree, Active Secret clearance, Salesforce architect-level certification. - Skills: technical expertise in Apex, LWC, OmniStudio, Flow, architectural decisions, integrations, data modeling, security, etc. But we need to avoid duplication. Let's decide: Section "Requirements": list of experience requirements (years, hands-on, Agile/DevSecOps, etc.) Section "Qualifications": education, clearance, certifications. Section "Skills": deep technical expertise list. But the posting also includes "Proven ability to make architectural decisions across OOTB, low-code, and custom development approaches." That's skill. "Strong experience designing and implementing enterprise integrations (REST, SOAP, events, middleware)." skill. "Deep understanding of Salesforce data modeling, security architecture, and sharing models." skill. Thus we can allocate. Now Benefits: list: Health, dental, and vision insurance; 401(k) retirement plan with company match; Paid time off (PTO) and holidays; Parental Leave and dependent care; Flexible work arrangements; Professional development opportunities; Employee assistance and wellness programs. Pay: Salary range $160,000 - $180,000; plus mention of additional compensation (performance-based bonuses, company-paid training and/or certifications, referral bonuses). Also "Additional Compensation: This role may also be eligible for bonuses and/or additional incentives based on individual and company performance." We'll combine. Schedule: Not mentioned. So we should not include Schedule section. Now About the role: The initial paragraphs describing role and mission. Could be two paragraphs: first paragraph about role, second about mission/people. We'll keep as
maybe combine. Now Responsibilities: bullet list from "What you’ll do:". Let's extract bullet points: - Serve as the Salesforce architectural authority, owning platform design across configuration, customization, and integrations. - Define OOTB vs. Flow vs. Apex vs. LWC vs. OmniStudio decisions, balancing scalability, speed, and maintainability. - Establish and enforce architecture standards, design patterns, and best practices across the platform. - Design end-to-end, multi-cloud Salesforce architectures including Service, Experience, Data Cloud, and AI capabilities. - Act as a hands-on architect, contributing to complex builds (Apex, LWC, integrations, data models) when needed. - Lead solution design sessions, code reviews, and technical deep dives to ensure quality and alignment. - Architect scalable, high-performance applications using the optimal mix of declarative and custom approaches. - Define enterprise integration and data architecture, including APIs, event-driven patterns, governance, and analytics readiness. - Drive adoption of AI-enabled engineering, leveraging Einstein, Agentforce, and intelligent automation. - Enforce security, governance, and DevSecOps practices while partnering with stakeholders to deliver robust, risk-aware solutions. Now we need to output HTML fragment only, no markdown fences. Let's craft. We'll start with
About the role
then...
. ThenResponsibilities
then- ...
Requirements
then- ...
Qualifications
then- ...
Skills
then- ...
Benefits
then- ...
Pay
then...
for salary range and additional compensation. We must not include Schedule. Check for any duplicated lines: ensure we didn't repeat. Now write content. About the role paragraph: combine first two paragraphs maybe. Original: "As Sr. Salesforce Technical Architect II, you’ll serve as the subject matter expert (SME) for all Salesforce platform capabilities, architecture, and implementation decisions within a large-scale modernization and digital transformation program.This role will define how Salesforce is built, not just what is built—owning decisions across the full spectrum of platform capabilities, including declarative configuration vs. custom development, Apex vs. Flow, Lightning Web Components (LWC) vs. OmniStudio, and integration patterns.The ideal candidate brings deep, multi-domain Salesforce expertise and operates confidently as both a hands-on technical leader and strategic architect, guiding teams in building scalable, secure, and maintainable solutions within an AI-enabled engineering ecosystem.We know that you can’t have great technology services without amazing people. At MetroStar, we are obsessed with our people and have led a two-decade legacy of building the best and brightest teams. Because we know our future relies on our deep understanding and relentless focus on our people, we live by our mission: A passion for our people. Value for our customers.If you think you can see yourself delivering our mission and pursuing our goals with us, then check out the job description below!" We can trim the last sentence about checking out job description below (since we are already in description). Might be considered boilerplate? It's a call to action; maybe remove as it's not substantive. We'll keep the core description. Thus About the role paragraph: "As Sr. Salesforce Technical Architect II, you’ll serve as the subject matter expert (SME) for all Salesforce platform capabilities, architecture, and implementation decisions within a large-scale modernization and digital transformation program. This role will define how Salesforce is built, not just what is built—owning decisions across the full spectrum of platform capabilities, including declarative configuration vs. custom development, Apex vs. Flow, Lightning Web Components (LWC) vs. OmniStudio, and integration patterns. The ideal candidate brings deep, multi-domain Salesforce expertise and operates confidently as both a hands-on technical leader and strategic architect, guiding teams in building scalable, secure, and maintainable solutions within an AI-enabled engineering ecosystem. We know that you can’t have great technology services without amazing people. At MetroStar, we are obsessed with our people and have led a two-decade legacy of building the best and brightest teams. Because we know our future relies on our deep understanding and relentless focus on our people, we live by our mission: A passion for our people. Value for our customers." Now Responsibilities list as above. Now Requirements: list experience items: - 8–10 years of experience in software engineering and architecture, with 6+ years hands-on Salesforce expertise. - Experience operating in Agile, DevSecOps, and continuous delivery environments, including AI-assisted development practices. Maybe also "Proven ability to make architectural decisions across OOTB, low-code, and custom development approaches." but that's skill. We'll keep