Salesforce Administrator
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out the inclusion and diversity, EEO statement, Important Note about work authorization, "Ready to apply?" etc. Also remove "In today’s competitive job market..." paragraph about pay transparency? Actually that is part of pay transparency statement; we need to keep pay info but can we keep the sentence about transparency? It's not boilerplate? It's part of the posting but maybe considered fluff. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The pay transparency statement is not exactly those categories, but could be considered boilerplate? It's about transparency; but it's not EEO. Might be okay to keep? However they said "Prefer a few substantive sections over many thin ones." The pay transparency statement is not substantive detail about the job; it's more about company policy. Might be considered boilerplate? Not sure. Safer to keep the pay range but maybe drop the surrounding sentence. The instruction: "Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". The pay transparency sentence is filler? It says "In today’s competitive job market, transparency and trust are more important than ever. At Lightspeed, we believe in fostering an open and honest work environment, starting with our job postings. Pay transparency is a key component of this commitment, ensuring that potential candidates have a clear understanding of the compensation they can expect." That's generic; could be considered filler. So we could omit that paragraph and just keep the pay range under Pay section.
Also remove "Inclusion and Diversity at Lightspeed:" etc. Also remove "Equal Employment Opportunity Statement:" etc. Also remove "Important Note: Applicants must be authorized to work in the U.S." Also remove "Ready to apply? Take the next step..." etc.
Now we need to structure.
We have company overview paragraph: "Company Overview: Lightspeed is the leading provider..." That's substantive about company. Could be under About the role or maybe a separate section "About the company". But headings allowed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. There's no "About the company". Could put company overview under About the role (makes sense). Or we could treat as part of Responsibilities? Better to put under About the role.
Then we have description of role: "As a Salesforce Developer, you will be a key technical contributor..." That's also role description; could be part of About the role.
Thus About the role section will contain company overview + role description paragraphs.
Then Responsibilities: list of duties from "What You’ll Do". That's many bullet-like sentences. We'll convert each sentence into
- under
. Ensure we preserve all details.
Then Requirements: from "What You'll Bring". There's Required Qualifications and Preferred Qualifications. We could combine into Requirements section, maybe separate Required and Preferred? But headings limited; we could have Requirements and maybe Skills? But we can put all qualifications under Requirements. Use - for each bullet.
We need to preserve details like "Minimum 3 years of hands-on Salesforce development and administration experience in a fast- paced SaaS or technology company." etc.
We should not repeat job title as heading.
Pay section: include the pay range: "Remote: $90,000 USD - $115,000 USD". Could be a
.
We should not include Benefits or Schedule sections as not present.
Now ensure we don't include any filler like "commensurate with experience". Not present.
Now produce HTML fragment.
We need to wrap sections in appropriate tags: each section heading
then content.
For About the role: maybe two paragraphs: company overview and role description. Use
for each.
For Responsibilities:
- each duty.
For Requirements:
- each qualification (both required and preferred). Could separate into required and preferred but not needed.
Pay:
with the range.
Let's extract duties exactly as written.
From "What You’ll Do:" list:
- Design, develop, test, and deploy custom Apex classes, triggers, Lightning Web Components (LWC), and Aura components to meet evolving business needs.
- Build and maintain scalable automation using Flow Builder, Process Builder, and Workflow Rules, with a preference for declarative solutions where appropriate.
- Participate in Agile development cycles, contributing to sprint planning, code reviews, and release management.
- Implement and maintain deployment pipelines using Salesforce DX, GitHub, and CI/CD frameworks such as Copado or Gearset.
- Maintain a comprehensive test suite (minimum 80% Apex code coverage) and manage sandbox strategy for development, UAT, and staging environments.
- Oversee daily operations of the Salesforce org, including user setup, profiles, permission sets, role hierarchy, and field-level security.
- Maintain and enhance page layouts, custom objects, record types, validation rules, and sharing settings to support business function changes.
- Conduct regular performance audits, security reviews, and data quality checks; enforce data governance and deduplication standards.
- Stay current with Salesforce releases (3x per year), evaluate new features, and implement relevant updates with appropriate regression testing.
- Maintain clear, up-to-date documentation of all configurations, customizations, integrations, and architectural decisions.
- Own and extend Lightspeed’s Salesforce integration architecture, ensuring reliable data flow across connected systems including: NetSuite (ERP & financial data) Certinia (Professional Services Automation) NICE CXOne (Contact Center) DocuSign (Contract execution) Conga Composer (Document generation) Enablix (Sales enablement) Qualtrics (Customer feedback) FormAssembly (Data collection) Avonni (UI/UX components)
- Evaluate, install, and configure third-party AppExchange applications to extend Salesforce functionality in alignment with business priorities.
- Build and maintain REST/SOAP API integrations with internal and external platforms.
- Partner with Revenue Operations, Customer Success, Finance, and Product teams to gather requirements and deliver solutions that scale with the business.
- Provide technical guidance and mentorship on Salesforce best practices across teams.
- Support end-user training and adoption initiatives, creating documentation and enablement materials as needed.
Now Requirements: "What You'll Bring:" includes Required Qualifications and Preferred Qualifications.
Required Qualifications list:
- Minimum 3 years of hands-on Salesforce development and administration experience in a fast- paced SaaS or technology company.
- Experience with Salesforce CPQ or Revenue Cloud for subscription, quoting, and contract lifecycle management.
- Active Salesforce certifications: Salesforce Administrator and Salesforce Platform Developer I.
- Proficiency in Apex, SOQL, Visualforce, and Lightning Web Components (LWC), with strong understanding of governor limits and Salesforce architecture.
- Experience with Salesforce DX and source-driven development workflows (version control with Git, scratch orgs, unlocked packages).
- Demonstrated ability to design and build REST/SOAP API integrations between Salesforce and third-party platforms.
- Solid understanding of the Salesforce Security Model: profiles, permission sets, field-level security, sharing rules, and OWD.
- Strong data modeling skills, including custom object design, lookup/master-detail relationships, and schema planning.
- Experience with CI/CD tools for Salesforce deployments (e.g., Copado, Gearset, or GitHub Actions with SFDX).
- Excellent problem-solving, prioritization, and project management skills in a dynamic environment.
- Strong communication and collaboration skills; comfortable working cross-functionally with both technical and non-technical stakeholders.
Preferred Qualifications:
- Additional certifications: Salesforce Platform Developer II, JavaScript Developer I, or Data Architect.
- Familiarity with the dealer, automotive, powersports, marine, or equipment industries.
- Experience in a B2B SaaS company with recurring revenue models.
- Hands-on experience with one or more of our key integrated platforms: NetSuite, Certinia, NICE CXOne, DocuSign, Conga Composer.
- Bachelor’s degree in Computer Science, Information Systems, Business Administration, or equivalent practical experience.
Now company overview paragraph: "Company Overview: Lightspeed is the leading provider of cloud-based software for dealerships, serving the Powersport, Marine, RV, Trailer, and Golf Car industries adding hundreds of dealerships to the Lightspeed community each year. Lightspeed’s Dealer Management Solution (DMS) enables dealerships to optimize their end-to-end business operations, including Sales, Parts, Service, Rentals, Payments, Accounting, and Customer Relationship Management (CRM). When implemented into their daily operations, Lightspeed helps dealers increase their profitability by selling more units, service, and parts, all while creating a more streamlined experience for customers. Lightspeed is the most complete and integrated DMS in the industry with over 500 integrations with Original Equipment Manufacturers (OEMs), aftermarket parts and accessory distributors and dozens of other software tools that a dealership may use to run their business. Uniquely designed by dealers for dealers, and refined over the past 4 decades, Lightspeed empowers over 4,500+ dealers across North America with the tools and technology they need to manage their dealerships."
Then role description paragraph: "As a Salesforce Developer, you will be a key technical contributor responsible for designing, building, and maintaining custom solutions within our Salesforce org. You will partner with Revenue Operations, Customer Success, Finance, and Product teams to translate complex business requirements into scalable technical implementations — spanning custom Apex development, Flow automation, and integrations across our DMS ecosystem. Your work will directly shape our ability to deliver exceptional customer experiences, support subscription and contract lifecycle management, and drive operational excellence as Lightspeed continues its growth trajectory. This is both a developer and a systems-ownership role: you will not just build features but be accountable for the health, performance, and governance of our Salesforce environment."
Now we need to ensure we don't duplicate content. The role description appears also in the responsibilities list; but we keep both as they are distinct.
Now produce HTML.
We must not include any markdown fences.
Let's craft:
About the role
Company overview paragraph.
Role description paragraph.
Responsibilities
- ...
...
Requirements
- ...
...
Pay
Remote: $90,000 USD - $115,000 USD
Check for any leftover boilerplate: we removed inclusion/diversity, EEO, important note, ready to apply, etc.
Now ensure we didn't miss any substantive info: The "What You'll Do" includes also "Own and extend Lightspeed’s Salesforce integration architecture, ensuring reliable data flow across connected systems including: NetSuite (ERP & financial data) Certinia (Professional Services Automation) NICE CXOne (Contact Center) DocuSign (Contract execution) Conga Composer (Document generation) Enablix (Sales enablement) Qualtrics (Customer feedback) FormAssembly (Data collection) Avonni (UI/UX components)". That's a long sentence; we keep
for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out the inclusion and diversity, EEO statement, Important Note about work authorization, "Ready to apply?" etc. Also remove "In today’s competitive job market..." paragraph about pay transparency? Actually that is part of pay transparency statement; we need to keep pay info but can we keep the sentence about transparency? It's not boilerplate? It's part of the posting but maybe considered fluff. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The pay transparency statement is not exactly those categories, but could be considered boilerplate? It's about transparency; but it's not EEO. Might be okay to keep? However they said "Prefer a few substantive sections over many thin ones." The pay transparency statement is not substantive detail about the job; it's more about company policy. Might be considered boilerplate? Not sure. Safer to keep the pay range but maybe drop the surrounding sentence. The instruction: "Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". The pay transparency sentence is filler? It says "In today’s competitive job market, transparency and trust are more important than ever. At Lightspeed, we believe in fostering an open and honest work environment, starting with our job postings. Pay transparency is a key component of this commitment, ensuring that potential candidates have a clear understanding of the compensation they can expect." That's generic; could be considered filler. So we could omit that paragraph and just keep the pay range under Pay section. Also remove "Inclusion and Diversity at Lightspeed:" etc. Also remove "Equal Employment Opportunity Statement:" etc. Also remove "Important Note: Applicants must be authorized to work in the U.S." Also remove "Ready to apply? Take the next step..." etc. Now we need to structure. We have company overview paragraph: "Company Overview: Lightspeed is the leading provider..." That's substantive about company. Could be under About the role or maybe a separate section "About the company". But headings allowed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. There's no "About the company". Could put company overview under About the role (makes sense). Or we could treat as part of Responsibilities? Better to put under About the role. Then we have description of role: "As a Salesforce Developer, you will be a key technical contributor..." That's also role description; could be part of About the role. Thus About the role section will contain company overview + role description paragraphs. Then Responsibilities: list of duties from "What You’ll Do". That's many bullet-like sentences. We'll convert each sentence into
- . Ensure we preserve all details.
Then Requirements: from "What You'll Bring". There's Required Qualifications and Preferred Qualifications. We could combine into Requirements section, maybe separate Required and Preferred? But headings limited; we could have Requirements and maybe Skills? But we can put all qualifications under Requirements. Use
- for each bullet.
We need to preserve details like "Minimum 3 years of hands-on Salesforce development and administration experience in a fast- paced SaaS or technology company." etc.
We should not repeat job title as heading.
Pay section: include the pay range: "Remote: $90,000 USD - $115,000 USD". Could be a
. We should not include Benefits or Schedule sections as not present. Now ensure we don't include any filler like "commensurate with experience". Not present. Now produce HTML fragment. We need to wrap sections in appropriate tags: each section heading
then content. For About the role: maybe two paragraphs: company overview and role description. Use
for each. For Responsibilities:
- each duty.
For Requirements:
- each qualification (both required and preferred). Could separate into required and preferred but not needed.
Pay:
with the range. Let's extract duties exactly as written. From "What You’ll Do:" list: - Design, develop, test, and deploy custom Apex classes, triggers, Lightning Web Components (LWC), and Aura components to meet evolving business needs. - Build and maintain scalable automation using Flow Builder, Process Builder, and Workflow Rules, with a preference for declarative solutions where appropriate. - Participate in Agile development cycles, contributing to sprint planning, code reviews, and release management. - Implement and maintain deployment pipelines using Salesforce DX, GitHub, and CI/CD frameworks such as Copado or Gearset. - Maintain a comprehensive test suite (minimum 80% Apex code coverage) and manage sandbox strategy for development, UAT, and staging environments. - Oversee daily operations of the Salesforce org, including user setup, profiles, permission sets, role hierarchy, and field-level security. - Maintain and enhance page layouts, custom objects, record types, validation rules, and sharing settings to support business function changes. - Conduct regular performance audits, security reviews, and data quality checks; enforce data governance and deduplication standards. - Stay current with Salesforce releases (3x per year), evaluate new features, and implement relevant updates with appropriate regression testing. - Maintain clear, up-to-date documentation of all configurations, customizations, integrations, and architectural decisions. - Own and extend Lightspeed’s Salesforce integration architecture, ensuring reliable data flow across connected systems including: NetSuite (ERP & financial data) Certinia (Professional Services Automation) NICE CXOne (Contact Center) DocuSign (Contract execution) Conga Composer (Document generation) Enablix (Sales enablement) Qualtrics (Customer feedback) FormAssembly (Data collection) Avonni (UI/UX components) - Evaluate, install, and configure third-party AppExchange applications to extend Salesforce functionality in alignment with business priorities. - Build and maintain REST/SOAP API integrations with internal and external platforms. - Partner with Revenue Operations, Customer Success, Finance, and Product teams to gather requirements and deliver solutions that scale with the business. - Provide technical guidance and mentorship on Salesforce best practices across teams. - Support end-user training and adoption initiatives, creating documentation and enablement materials as needed. Now Requirements: "What You'll Bring:" includes Required Qualifications and Preferred Qualifications. Required Qualifications list: - Minimum 3 years of hands-on Salesforce development and administration experience in a fast- paced SaaS or technology company. - Experience with Salesforce CPQ or Revenue Cloud for subscription, quoting, and contract lifecycle management. - Active Salesforce certifications: Salesforce Administrator and Salesforce Platform Developer I. - Proficiency in Apex, SOQL, Visualforce, and Lightning Web Components (LWC), with strong understanding of governor limits and Salesforce architecture. - Experience with Salesforce DX and source-driven development workflows (version control with Git, scratch orgs, unlocked packages). - Demonstrated ability to design and build REST/SOAP API integrations between Salesforce and third-party platforms. - Solid understanding of the Salesforce Security Model: profiles, permission sets, field-level security, sharing rules, and OWD. - Strong data modeling skills, including custom object design, lookup/master-detail relationships, and schema planning. - Experience with CI/CD tools for Salesforce deployments (e.g., Copado, Gearset, or GitHub Actions with SFDX). - Excellent problem-solving, prioritization, and project management skills in a dynamic environment. - Strong communication and collaboration skills; comfortable working cross-functionally with both technical and non-technical stakeholders. Preferred Qualifications: - Additional certifications: Salesforce Platform Developer II, JavaScript Developer I, or Data Architect. - Familiarity with the dealer, automotive, powersports, marine, or equipment industries. - Experience in a B2B SaaS company with recurring revenue models. - Hands-on experience with one or more of our key integrated platforms: NetSuite, Certinia, NICE CXOne, DocuSign, Conga Composer. - Bachelor’s degree in Computer Science, Information Systems, Business Administration, or equivalent practical experience. Now company overview paragraph: "Company Overview: Lightspeed is the leading provider of cloud-based software for dealerships, serving the Powersport, Marine, RV, Trailer, and Golf Car industries adding hundreds of dealerships to the Lightspeed community each year. Lightspeed’s Dealer Management Solution (DMS) enables dealerships to optimize their end-to-end business operations, including Sales, Parts, Service, Rentals, Payments, Accounting, and Customer Relationship Management (CRM). When implemented into their daily operations, Lightspeed helps dealers increase their profitability by selling more units, service, and parts, all while creating a more streamlined experience for customers. Lightspeed is the most complete and integrated DMS in the industry with over 500 integrations with Original Equipment Manufacturers (OEMs), aftermarket parts and accessory distributors and dozens of other software tools that a dealership may use to run their business. Uniquely designed by dealers for dealers, and refined over the past 4 decades, Lightspeed empowers over 4,500+ dealers across North America with the tools and technology they need to manage their dealerships." Then role description paragraph: "As a Salesforce Developer, you will be a key technical contributor responsible for designing, building, and maintaining custom solutions within our Salesforce org. You will partner with Revenue Operations, Customer Success, Finance, and Product teams to translate complex business requirements into scalable technical implementations — spanning custom Apex development, Flow automation, and integrations across our DMS ecosystem. Your work will directly shape our ability to deliver exceptional customer experiences, support subscription and contract lifecycle management, and drive operational excellence as Lightspeed continues its growth trajectory. This is both a developer and a systems-ownership role: you will not just build features but be accountable for the health, performance, and governance of our Salesforce environment." Now we need to ensure we don't duplicate content. The role description appears also in the responsibilities list; but we keep both as they are distinct. Now produce HTML. We must not include any markdown fences. Let's craft:
About the role
Company overview paragraph.
Role description paragraph.
Responsibilities
- ... ...
Requirements
- ... ...
Pay
Remote: $90,000 USD - $115,000 USD
Check for any leftover boilerplate: we removed inclusion/diversity, EEO, important note, ready to apply, etc. Now ensure we didn't miss any substantive info: The "What You'll Do" includes also "Own and extend Lightspeed’s Salesforce integration architecture, ensuring reliable data flow across connected systems including: NetSuite (ERP & financial data) Certinia (Professional Services Automation) NICE CXOne (Contact Center) DocuSign (Contract execution) Conga Composer (Document generation) Enablix (Sales enablement) Qualtrics (Customer feedback) FormAssembly (Data collection) Avonni (UI/UX components)". That's a long sentence; we keep
- each qualification (both required and preferred). Could separate into required and preferred but not needed.
Pay:
- each duty.
For Requirements: