Salesforce Administrator
for each section heading. Use - for lists. Use
for prose. Remove boilerplate like EEO etc. Also remove "About TailorCare" and "About the Team"? 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." It doesn't say we must drop About TailorCare or About the Team, but we should include only sections with real content. The About the role section is present. The About TailorCare and About the Team could be considered prose but not under specified headings. Could we include them as
before the headings? The instruction: "Prefer a few substantive sections over many thin ones." It might be okay to include a brief intro paragraph about the company/team before the role. But they didn't give a heading for that; we could just put it as a
at start. However they said "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have other
content not under those headings. It's okay.
We need to preserve all substantive information. So we need to include the About TailorCare description, About the Team description, About the Role description (maybe short). Then Responsibilities list, Qualifications list, Benefits list, Pay range.
We must not include boilerplate like EEO etc. Also remove duplicated lines.
Let's extract content.
About TailorCare: paragraph(s). We'll keep as
.
About the Team: paragraph(s). Keep as
.
About the Role: "We are looking for a Salesforce Administrator to join the team. Our instance is built on Health Cloud with Sales and Service Cloud capabilities behind our outreach, engagement, and care coordination workflows. We do not integrate directly with clinical care systems, but the org holds PHI under HIPAA, so access design and data handling matter here. You will work inside our sprints as a hands-on contributor rather than a ticket queue, carrying new features across the last mile and owning quality assurance for Salesforce releases." That's the role description.
Key Responsibilities: list items separated by periods? Actually they are sentences separated by periods but no bullet. We need to convert to
- . Let's split:
- Provision and maintain users, roles, profiles, permission sets, and licenses, and configure objects, fields, page layouts, and record types as new features land.
- Contribute to declarative automation alongside engineers, who continue to own automation where appropriate.
- Keep data clean: imports and exports, deduplication rules, and field-level data governance.
- Manage sandboxes and support releases from build through deployment.
- Build reports, dashboards, and the guardrails that let business teams self-serve where it makes sense.
- Write test plans, run manual regression on Salesforce releases, coordinate UAT sign-off, and keep the test case library and configuration docs current.
- Join sprint planning and design discussions, raise Salesforce-side risk early, and execute administrative business requests triaged and sized against a defined share of your capacity each sprint.
- Partner with Security and Compliance on least-privilege access design, access reviews, and PHI handling under HIPAA.
Key Qualifications: list:
- 2-4 years administering a production Salesforce org.
- Strong command of the Salesforce sharing and security model, including org-wide defaults, role hierarchy, sharing rules, and field-level security.
- Depth in Salesforce configuration (objects, fields, page layouts, record types) and hands-on Flow experience, including debugging flows you did not build.
- Working knowledge of SOQL, Salesforce reporting, and Data Loader or a comparable bulk data tool.
- Experience supporting a release process across sandboxes, and writing and executing manual test plans with UAT coordination.
- Demonstrated strong ownership of work coupled with an ability to collaborate openly and transparently.
- Health Cloud experience, or experience administering an org holding PHI under HIPAA or comparable regulated data, is preferred.
- Exposure to test automation practices, or the ability to read Apex and debug logs well enough to route an issue to an engineer, is preferred.
- Salesforce Administrator certification (ADM 201) is preferred, not required, and experience in healthcare and/or startups is a big plus.
Pay Range: "$75,400—$92,400 USD". We'll put in
under Pay section.
Benefits: list from "What's In It For You" bullet points:
- Meaningful Work: We are dedicated to our mission and deeply value our patients and each other. Each day offers the opportunity to make a positive impact.
- Work Environment: We operate as a remote-first company with options for a hybrid work model in Nashville.
- Time Off: Our generous paid time off (PTO) and holiday plans ensure you have ample time to rest and recharge.
- Family First: We offer paid parental leave and support a healthy work-life balance, encouraging flexibility and autonomy. We love talking about our family and pets!
- Comprehensive Benefits: From Day 1, employees enjoy medical, dental, vision, life, and disability insurance, wellness resources and an employer HSA contribution.
- Fair Compensation: We are committed to equitable pay for all team members and support your future goals with a 401k plan that includes employer matching.
- Community: We foster an inclusive environment where you can rely on your teammates, share honest feedback, and feel comfortable being your authentic self at work each day.
We should keep these as list items.
We should not include the EEO statement.
Now produce HTML.
Structure:
About TailorCare: ...
About the Team: ...
About the Role: ...
About the role
maybe redundant? Actually we already have About the Role paragraph. But the instruction says use for section headings (e.g. About the role...). So we should have a heading "About the role". Then we can put the role description paragraph under it. However we already have About the Role paragraph earlier; we could combine. Better to follow spec: have heading About the role and then paragraph(s) describing role. We can omit the earlier "About the Role:" paragraph and just put under heading.
Similarly for Responsibilities, Qualifications, Benefits, Pay.
We also might include About TailorCare and About the Team as
before headings (no heading). That's fine.
Thus output:
About TailorCare: TailorCare is transforming the experience of specialty care. Our comprehensive care program takes a deeply personal, evidence-based approach to improving patient outcomes for joint, back, and muscle conditions. By combining a careful assessment of patients' symptoms, health histories, preferences, and goals with predictive data and the latest evidence-based guidelines, we help patients choose—and navigate—the most effective treatment pathway for them, every step of the way. TailorCare values the experiences and perspectives of individuals from all backgrounds. We are a highly collaborative, curious, and determined team passionate about scaling a high-growth start-up to improve the lives of those in pain. TailorCare is a remote-first company with a hybrid office in Nashville.
About the Team: We are Team 2: Care Team Enablement, building solutions that enable our care team to serve more patients without working harder. Our solutions are primarily built on the Salesforce platform through our Seamline product, with additional services and integrations as needed. Our users are internal with two core roles: Care Advocates, who run outreach and get patients engaged, and Care Navigators, who handle clinical intakes and care coordination. Everything we ship lands in someone's daily work, so we stay close to the people using it.
About the role
We are looking for a Salesforce Administrator to join the team. Our instance is built on Health Cloud with Sales and Service Cloud capabilities behind our outreach, engagement, and care coordination workflows. We do not integrate directly with clinical care systems, but the org holds PHI under HIPAA, so access design and data handling matter here. You will work inside our sprints as a hands-on contributor rather than a ticket queue, carrying new features across the last mile and owning quality assurance for Salesforce releases.
Responsibilities
- Provision and maintain users, roles, profiles, permission sets, and licenses, and configure objects, fields, page layouts, and record types as new features land.
- Contribute to declarative automation alongside engineers, who continue to own automation where appropriate.
- Keep data clean: imports and exports, deduplication rules, and field-level data governance.
- Manage sandboxes and support releases from build through deployment.
- Build reports, dashboards, and the guardrails that let business teams self-serve where it makes sense.
- Write test plans, run manual regression on Salesforce releases, coordinate UAT sign-off, and keep the test case library and configuration docs current.
- Join sprint planning and design discussions, raise Salesforce-side risk early, and execute administrative business requests triaged and sized against a defined share of your capacity each sprint.
- Partner with Security and Compliance on least-privilege access design, access reviews, and PHI handling under HIPAA.
Qualifications
- 2-4 years administering a production Salesforce org.
- Strong command of the Salesforce sharing and security model, including org-wide defaults, role hierarchy, sharing rules, and field-level security.
- Depth in Salesforce configuration (objects, fields, page layouts, record types) and hands-on Flow experience, including debugging flows you did not build.
- Working knowledge of SOQL, Salesforce reporting, and Data Loader or a comparable bulk data tool.
- Experience supporting a release process across sandboxes, and writing and executing manual test plans with UAT coordination.
- Demonstrated strong ownership of work coupled with an ability to collaborate openly and transparently.
- Health Cloud experience, or experience administering an org holding PHI under HIPAA or comparable regulated data, is preferred.
- Exposure to test automation practices, or the ability to read Apex and debug logs well enough to route an issue to an engineer, is preferred.
- Salesforce Administrator certification (ADM 201) is preferred, not required, and experience in healthcare and/or startups is a big plus.
Benefits
- Meaningful Work: We are dedicated to our mission and deeply value our patients and each other. Each day offers the opportunity to make a positive impact.
- Work Environment: We operate as a remote-first company with options for a hybrid work model in Nashville.
- Time Off: Our generous paid time off (PTO) and holiday plans ensure you have ample time to rest and recharge.
- Family First: We offer paid parental leave and support a healthy work-life balance, encouraging flexibility and autonomy. We love talking about our family and pets!
- Comprehensive Benefits: From Day 1, employees enjoy medical, dental, vision, life, and disability insurance, wellness resources and an employer HSA contribution.
for prose. Remove boilerplate like EEO etc. Also remove "About TailorCare" and "About the Team"? 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." It doesn't say we must drop About TailorCare or About the Team, but we should include only sections with real content. The About the role section is present. The About TailorCare and About the Team could be considered prose but not under specified headings. Could we include them as
before the headings? The instruction: "Prefer a few substantive sections over many thin ones." It might be okay to include a brief intro paragraph about the company/team before the role. But they didn't give a heading for that; we could just put it as a
at start. However they said "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have other
content not under those headings. It's okay. We need to preserve all substantive information. So we need to include the About TailorCare description, About the Team description, About the Role description (maybe short). Then Responsibilities list, Qualifications list, Benefits list, Pay range. We must not include boilerplate like EEO etc. Also remove duplicated lines. Let's extract content. About TailorCare: paragraph(s). We'll keep as
. About the Team: paragraph(s). Keep as
. About the Role: "We are looking for a Salesforce Administrator to join the team. Our instance is built on Health Cloud with Sales and Service Cloud capabilities behind our outreach, engagement, and care coordination workflows. We do not integrate directly with clinical care systems, but the org holds PHI under HIPAA, so access design and data handling matter here. You will work inside our sprints as a hands-on contributor rather than a ticket queue, carrying new features across the last mile and owning quality assurance for Salesforce releases." That's the role description. Key Responsibilities: list items separated by periods? Actually they are sentences separated by periods but no bullet. We need to convert to
- . Let's split:
- Provision and maintain users, roles, profiles, permission sets, and licenses, and configure objects, fields, page layouts, and record types as new features land.
- Contribute to declarative automation alongside engineers, who continue to own automation where appropriate.
- Keep data clean: imports and exports, deduplication rules, and field-level data governance.
- Manage sandboxes and support releases from build through deployment.
- Build reports, dashboards, and the guardrails that let business teams self-serve where it makes sense.
- Write test plans, run manual regression on Salesforce releases, coordinate UAT sign-off, and keep the test case library and configuration docs current.
- Join sprint planning and design discussions, raise Salesforce-side risk early, and execute administrative business requests triaged and sized against a defined share of your capacity each sprint.
- Partner with Security and Compliance on least-privilege access design, access reviews, and PHI handling under HIPAA.
Key Qualifications: list:
- 2-4 years administering a production Salesforce org.
- Strong command of the Salesforce sharing and security model, including org-wide defaults, role hierarchy, sharing rules, and field-level security.
- Depth in Salesforce configuration (objects, fields, page layouts, record types) and hands-on Flow experience, including debugging flows you did not build.
- Working knowledge of SOQL, Salesforce reporting, and Data Loader or a comparable bulk data tool.
- Experience supporting a release process across sandboxes, and writing and executing manual test plans with UAT coordination.
- Demonstrated strong ownership of work coupled with an ability to collaborate openly and transparently.
- Health Cloud experience, or experience administering an org holding PHI under HIPAA or comparable regulated data, is preferred.
- Exposure to test automation practices, or the ability to read Apex and debug logs well enough to route an issue to an engineer, is preferred.
- Salesforce Administrator certification (ADM 201) is preferred, not required, and experience in healthcare and/or startups is a big plus.
Pay Range: "$75,400—$92,400 USD". We'll put in
under Pay section. Benefits: list from "What's In It For You" bullet points: - Meaningful Work: We are dedicated to our mission and deeply value our patients and each other. Each day offers the opportunity to make a positive impact. - Work Environment: We operate as a remote-first company with options for a hybrid work model in Nashville. - Time Off: Our generous paid time off (PTO) and holiday plans ensure you have ample time to rest and recharge. - Family First: We offer paid parental leave and support a healthy work-life balance, encouraging flexibility and autonomy. We love talking about our family and pets! - Comprehensive Benefits: From Day 1, employees enjoy medical, dental, vision, life, and disability insurance, wellness resources and an employer HSA contribution. - Fair Compensation: We are committed to equitable pay for all team members and support your future goals with a 401k plan that includes employer matching. - Community: We foster an inclusive environment where you can rely on your teammates, share honest feedback, and feel comfortable being your authentic self at work each day. We should keep these as list items. We should not include the EEO statement. Now produce HTML. Structure:
About TailorCare: ...
About the Team: ...
About the Role: ...
About the role
maybe redundant? Actually we already have About the Role paragraph. But the instruction says usefor section headings (e.g. About the role...). So we should have a heading "About the role". Then we can put the role description paragraph under it. However we already have About the Role paragraph earlier; we could combine. Better to follow spec: have heading About the role and then paragraph(s) describing role. We can omit the earlier "About the Role:" paragraph and just put under heading. Similarly for Responsibilities, Qualifications, Benefits, Pay. We also might include About TailorCare and About the Team as
before headings (no heading). That's fine. Thus output:
About TailorCare: TailorCare is transforming the experience of specialty care. Our comprehensive care program takes a deeply personal, evidence-based approach to improving patient outcomes for joint, back, and muscle conditions. By combining a careful assessment of patients' symptoms, health histories, preferences, and goals with predictive data and the latest evidence-based guidelines, we help patients choose—and navigate—the most effective treatment pathway for them, every step of the way. TailorCare values the experiences and perspectives of individuals from all backgrounds. We are a highly collaborative, curious, and determined team passionate about scaling a high-growth start-up to improve the lives of those in pain. TailorCare is a remote-first company with a hybrid office in Nashville.
About the Team: We are Team 2: Care Team Enablement, building solutions that enable our care team to serve more patients without working harder. Our solutions are primarily built on the Salesforce platform through our Seamline product, with additional services and integrations as needed. Our users are internal with two core roles: Care Advocates, who run outreach and get patients engaged, and Care Navigators, who handle clinical intakes and care coordination. Everything we ship lands in someone's daily work, so we stay close to the people using it.
About the role
We are looking for a Salesforce Administrator to join the team. Our instance is built on Health Cloud with Sales and Service Cloud capabilities behind our outreach, engagement, and care coordination workflows. We do not integrate directly with clinical care systems, but the org holds PHI under HIPAA, so access design and data handling matter here. You will work inside our sprints as a hands-on contributor rather than a ticket queue, carrying new features across the last mile and owning quality assurance for Salesforce releases.
Responsibilities
- Provision and maintain users, roles, profiles, permission sets, and licenses, and configure objects, fields, page layouts, and record types as new features land.
- Contribute to declarative automation alongside engineers, who continue to own automation where appropriate.
- Keep data clean: imports and exports, deduplication rules, and field-level data governance.
- Manage sandboxes and support releases from build through deployment.
- Build reports, dashboards, and the guardrails that let business teams self-serve where it makes sense.
- Write test plans, run manual regression on Salesforce releases, coordinate UAT sign-off, and keep the test case library and configuration docs current.
- Join sprint planning and design discussions, raise Salesforce-side risk early, and execute administrative business requests triaged and sized against a defined share of your capacity each sprint.
- Partner with Security and Compliance on least-privilege access design, access reviews, and PHI handling under HIPAA.
Qualifications
- 2-4 years administering a production Salesforce org.
- Strong command of the Salesforce sharing and security model, including org-wide defaults, role hierarchy, sharing rules, and field-level security.
- Depth in Salesforce configuration (objects, fields, page layouts, record types) and hands-on Flow experience, including debugging flows you did not build.
- Working knowledge of SOQL, Salesforce reporting, and Data Loader or a comparable bulk data tool.
- Experience supporting a release process across sandboxes, and writing and executing manual test plans with UAT coordination.
- Demonstrated strong ownership of work coupled with an ability to collaborate openly and transparently.
- Health Cloud experience, or experience administering an org holding PHI under HIPAA or comparable regulated data, is preferred.
- Exposure to test automation practices, or the ability to read Apex and debug logs well enough to route an issue to an engineer, is preferred.
- Salesforce Administrator certification (ADM 201) is preferred, not required, and experience in healthcare and/or startups is a big plus.
Benefits
- Meaningful Work: We are dedicated to our mission and deeply value our patients and each other. Each day offers the opportunity to make a positive impact.
- Work Environment: We operate as a remote-first company with options for a hybrid work model in Nashville.
- Time Off: Our generous paid time off (PTO) and holiday plans ensure you have ample time to rest and recharge.
- Family First: We offer paid parental leave and support a healthy work-life balance, encouraging flexibility and autonomy. We love talking about our family and pets!
- Comprehensive Benefits: From Day 1, employees enjoy medical, dental, vision, life, and disability insurance, wellness resources and an employer HSA contribution.