Sr. Salesforce Software Engineer
Natera · Austin, TX · 2 wk ago
Engineering$125k–$156k/yrFull-time
We need to output HTML fragment with sections: About the role? The posting includes "The Opportunity" then "What You'll Do", "Required", "Preferred", "Knowledge, Skills & Abilities", "Why Join Natera", "Compensation & Benefits", "OUR OPPORTUNITY" (company description), "What We Offer", then EEO boilerplate etc. We must remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Keep substantive info.
We need headings: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We must not repeat job title as heading. We need to decide which sections to include based on content.
We have content: The Opportunity (intro) could be "About the role". Then "What You'll Do" -> Responsibilities. Then "Required" -> Requirements/Qualifications. Then "Preferred" maybe part of Qualifications or Skills. Then "Knowledge, Skills & Abilities" -> Skills. Then "Why Join Natera" maybe Benefits? Actually it's about impact, scale, growth. Could be part of "About the role" or separate but we need only sections with real content. Could combine into "Why Join Natera" as a section maybe "About the team" but not in list. The instruction says use those headings only; we can also use other headings? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We must not repeat job title as heading. We need to decide which sections to include based on content.
We have content: The Opportunity (intro) could be "About the role". Then "What You'll Do" -> Responsibilities. Then "Required" -> Requirements/Qualifications. Then "Preferred" maybe part of Qualifications or Skills. Then "Knowledge, Skills & Abilities" -> Skills. Then "Why Join Natera" maybe Benefits? Actually it's about impact, scale, growth. Could be part of "About the role" or separate but we need only sections with real content. Could combine into "Why Join Natera" as a section maybe "About the team" but not in list. The instruction says use those headings only; we can also use other headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings when appropriate. Probably we should stick to those headings. So we need to map content to those.
We have compensation and benefits: "Compensation & Benefits" section includes base salary, performance bonuses, equity, benefits list, pay range. So we can have Benefits
and maybe Pay
. The instruction: include a section ONLY when posting has real, specific content for it. So we can have both Pay and Benefits if content exists. Pay: they give pay range $125,000—$156,300 USD. Also mention base salary, performance bonuses, equity. So we can put Pay section with that. Benefits: list health insurance, 401(k) matching, flexible PTO, professional development budget, plus later "What We Offer" includes comprehensive medical, dental, vision, life and disability plans, free testing, fertility care benefits, pregnancy and baby bonding leave, commuter benefits, employee referral program. So Benefits section.
Schedule: they mention "Ability to work on-site in our Austin, TX offices three days per week". That's schedule info (on-site 3 days/week). So we can have Schedule section.
We also need About the role: intro paragraph.
Responsibilities: from "What You'll Do" bullet points.
Requirements/Qualifications: from "Required" and maybe "Preferred". Could combine into Requirements (mandatory) and Qualifications (preferred) but we have both headings. We could put Requirements for mandatory, Qualifications for preferred. Or we could just use Requirements and Qualifications as separate.
Skills: from "Knowledge, Skills & Abilities".
We must not include boilerplate like EEO, scam warning, etc.
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details like percentages (25%, 50%, 25%) etc. Keep them.
We must not repeat job title as heading. Not include Job ID.
We must output only HTML fragment, no /, no markdown fences.
Thus produce something like:
About the role
Benefits
and maybePay
. The instruction: include a section ONLY when posting has real, specific content for it. So we can have both Pay and Benefits if content exists. Pay: they give pay range $125,000—$156,300 USD. Also mention base salary, performance bonuses, equity. So we can put Pay section with that. Benefits: list health insurance, 401(k) matching, flexible PTO, professional development budget, plus later "What We Offer" includes comprehensive medical, dental, vision, life and disability plans, free testing, fertility care benefits, pregnancy and baby bonding leave, commuter benefits, employee referral program. So Benefits section. Schedule: they mention "Ability to work on-site in our Austin, TX offices three days per week". That's schedule info (on-site 3 days/week). So we can have Schedule section. We also need About the role: intro paragraph. Responsibilities: from "What You'll Do" bullet points. Requirements/Qualifications: from "Required" and maybe "Preferred". Could combine into Requirements (mandatory) and Qualifications (preferred) but we have both headings. We could put Requirements for mandatory, Qualifications for preferred. Or we could just use Requirements and Qualifications as separate. Skills: from "Knowledge, Skills & Abilities". We must not include boilerplate like EEO, scam warning, etc. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details like percentages (25%, 50%, 25%) etc. Keep them. We must not repeat job title as heading. Not include Job ID. We must output only HTML fragment, no /, no markdown fences. Thus produce something like:About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Skills
- ... ...
Schedule
Ability to work on-site in our Austin, TX offices three days per week.
Pay
Base salary range: $125,000—$156,300 USD, plus performance bonuses and equity.
Benefits
- ... ...
About the role
The Opportunity We are seeking an exceptional Senior Salesforce engineer to lead the design and evolution of our Sales Cloud and Service Cloud platforms. In this strategic role, you'll own the technical architecture, govern platform standards, and drive transformation initiatives that impact thousands of users across go-to-market and customer success functions. You'll be our technical authority on Salesforce best practices, scalability, and innovation.
But we might want to trim redundant "The Opportunity". Keep substance. Now Responsibilities:Responsibilities
- Platform Architecture & Governance (25%): Design end-to-end solutions integrating Sales and Service Cloud; establish metadata frameworks, custom objects, and data models for scalability; define platform standards, coding guidelines, and integration patterns; ensure compliance with Salesforce Governor Limits and platform constraints; lead org hygiene initiatives, technical debt reduction, and long-term roadmap evolution.
- Solution Design & Implementation (50%): Architect complex workflows, automation, omni-channel, and AI-driven capabilities (Einstein Analytics, Einstein Copilot); design secure integrations (MuleSoft, AWS, REST/OAuth) between Salesforce and enterprise systems; lead implementation of key initiatives (data cloud, person accounts, skill-based routing) from design through production.
- Mentorship & Technical Leadership (25%): Guide Salesforce developers and admins; conduct design reviews and architecture validation; partner with product, business systems, and engineering leadership on roadmap alignment.
Requirements
- Ability to work on-site in our Austin, TX offices three days per week.
- 10+ years of Salesforce architecture and implementation experience, with deep expertise in Sales and Service Cloud.
- Expert-level knowledge of Apex, Lightning Web Components (LWC), Flows, and SOQL optimization.
- Proven ability to design secure, scalable integrations (REST APIs, OAuth, SSO, MuleSoft).
- Experience architecting multi-org, multi-cloud solutions in enterprise environments.
- Strong knowledge of Salesforce Governor Limits, performance optimization, and data modeling.
Qualifications
- AWS, MuleSoft, or Heroku integration experience.
- Experience with Einstein Analytics, Einstein Copilot, or AI-driven Salesforce capabilities.
- Salesforce Certified Application Architect or System Architect (or both).
- Healthcare or regulated industry experience.
Skills
- Strategic Design: Ability to balance innovation with pragmatic delivery; make trade-offs between technical perfection and business velocity.
- Security Mindset: Deep understanding of data governance, OAuth, SAML, multi-tenancy, and compliance frameworks.
- Executive Communication: Translate technical architecture into compelling business value for C-suite and product stakeholders.
- Mentorship: Ability to elevate team capability through code review, design collaboration, and knowledge sharing.
Schedule
Ability to work