Manager, Salesforce Engineering
GreatAmerica · Des Moines, IA · 3 wk ago
Full-time
We need to output HTML fragment with headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info.
We need to parse the posting.
Let's extract sections:
- About the role: description of company and role overview. The posting starts with company description and then "We Are Looking to Add a Key Member to our Product Delivery Team!" then repeats company description. Then "As Manager, Salesforce Engineering, you will lead a high-performing team...". So we can put that in About the role.
- Responsibilities: list of duties under headings: Leadership & Strategy, Technical Delivery & Innovation, Architecture & Development, Integration & Data Collaboration, Collaboration & Agile Execution. Those are responsibilities.
- Requirements: maybe experience section: "Experience To be successful in this role you will need: 5+ years of technical leadership and people management.7–8 years of hands-on Salesforce development and administration experience." plus list of proven expertise items.
- Qualifications: Education and certifications: "Education Bachelor’s degree in Information Systems or related field.Salesforce Certified Admin, Advanced Admin, Platform Developer I & II required.Additional certifications (e.g., Revenue Cloud Consultant, Integration Architecture Designer) are a plus."
- Skills: "Skills & Abilities" list.
- Benefits: "Financial Benefits Sharing rewards..." includes list: Competitive Compensation, Monthly Bonuses for Eligible Employees, 401(k) and Company Match, Annual Profit Sharing, Paid Time Off, then Health, Wellbeing, And Family Planning Benefits list, Education And Career Planning Benefits list, Perks list.
- Pay: Not explicitly stated; only "Competitive Compensation" but no numbers. The rule: do NOT create Pay section unless posting actually states them. It says "Competitive Compensation" but no specific figure. That's vague; maybe we should not create Pay section because it's not specific. The rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. "Competitive Compensation" is vague but still states something; but it's not a specific number. Might be considered placeholder? Safer to omit Pay section.
- Schedule: Not mentioned; maybe hybrid work arrangements mentioned under Perks. That's schedule? It says "Hybrid work arrangements". That could be schedule info. But rule: only create Schedule section if posting actually states them. It does mention hybrid work arrangements under Perks. Could treat as Schedule? However they said prefer few substantive sections over many thin ones. Could include Schedule as part of Benefits or Perks. But we have a Benefits section already; we could include hybrid work arrangements there. However they said include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. Hybrid work arrangements is specific enough. So we could create a Schedule section with that content. But we also have Perks which includes hybrid work arrangements. Might be redundant. Better to put hybrid work arrangements under Benefits or Perks. Since we already have Benefits section, we can add hybrid work arrangements there.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits.
We need to use
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info.
We need to parse the posting.
Let's extract sections:
- About the role: description of company and role overview. The posting starts with company description and then "We Are Looking to Add a Key Member to our Product Delivery Team!" then repeats company description. Then "As Manager, Salesforce Engineering, you will lead a high-performing team...". So we can put that in About the role.
- Responsibilities: list of duties under headings: Leadership & Strategy, Technical Delivery & Innovation, Architecture & Development, Integration & Data Collaboration, Collaboration & Agile Execution. Those are responsibilities.
- Requirements: maybe experience section: "Experience To be successful in this role you will need: 5+ years of technical leadership and people management.7–8 years of hands-on Salesforce development and administration experience." plus list of proven expertise items.
- Qualifications: Education and certifications: "Education Bachelor’s degree in Information Systems or related field.Salesforce Certified Admin, Advanced Admin, Platform Developer I & II required.Additional certifications (e.g., Revenue Cloud Consultant, Integration Architecture Designer) are a plus."
- Skills: "Skills & Abilities" list.
- Benefits: "Financial Benefits Sharing rewards..." includes list: Competitive Compensation, Monthly Bonuses for Eligible Employees, 401(k) and Company Match, Annual Profit Sharing, Paid Time Off, then Health, Wellbeing, And Family Planning Benefits list, Education And Career Planning Benefits list, Perks list.
- Pay: Not explicitly stated; only "Competitive Compensation" but no numbers. The rule: do NOT create Pay section unless posting actually states them. It says "Competitive Compensation" but no specific figure. That's vague; maybe we should not create Pay section because it's not specific. The rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. "Competitive Compensation" is vague but still states something; but it's not a specific number. Might be considered placeholder? Safer to omit Pay section.
- Schedule: Not mentioned; maybe hybrid work arrangements mentioned under Perks. That's schedule? It says "Hybrid work arrangements". That could be schedule info. But rule: only create Schedule section if posting actually states them. It does mention hybrid work arrangements under Perks. Could treat as Schedule? However they said prefer few substantive sections over many thin ones. Could include Schedule as part of Benefits or Perks. But we have a Benefits section already; we could include hybrid work arrangements there. However they said include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. Hybrid work arrangements is specific enough. So we could create a Schedule section with that content. But we also have Perks which includes hybrid work arrangements. Might be redundant. Better to put hybrid work arrangements under Benefits or Perks. Since we already have Benefits section, we can add hybrid work arrangements there.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits.
We need to use for each section heading. Use - for any list of duties/requirements/benefits, and
for prose.
We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from each section.
Let's extract content precisely.
About the role: combine company description and role overview.
Company description: "GreatAmerica is a highly successful entrepreneurial company providing equipment financing to businesses across the United States. Our exemplary customer service, our principle-centered business philosophy and our team-based operating approach are key to our success and growth. We have also recently become a bank! We Are Looking to Add a Key Member to our Product Delivery Team! GreatAmerica is a highly successful entrepreneurial company providing equipment financing to businesses across the United States. Our exemplary customer service, principle-centered business philosophy, and team-based operating approach are crucial to our success and growth. GreatAmerica is structured in cross-functional product teams that allow individuals to make informed decisions that benefit the company and our customers. There is no doubt that we are building the greatest company of its kind, offering the finest products and services available anywhere. When you are part of the GreatAmerica team, you are part of the future, part of an opportunity to grow professionally and to reach your potential while enjoying your work."
Then role overview: "As Manager, Salesforce Engineering, you will lead a high-performing team of developers and admins to deliver secure, scalable, and innovative solutions across the Salesforce ecosystem. You’ll combine deep technical expertise with strategic leadership to drive platform excellence, team growth, and business impact."
We should not repeat the job title as a heading, but we can include it in prose.
We need to avoid duplication: The company description appears twice; we should preserve all substantive information but not duplicate lines? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't explicitly say to deduplicate, but we should avoid duplicated lines as per earlier: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove duplicated lines. So we need to deduplicate the repeated company description. We'll keep one copy.
Thus About the role prose: combine unique sentences.
Let's craft About the role paragraph(s). Could be multiple
tags.
Now Responsibilities: we have headings with bullet-like sentences.
We need to turn each responsibility into list items under
. The headings like "Leadership & Strategy" etc are subheadings but we are not to create extra headings; we just need list items. Could we keep subheadings as part of list item text? Probably yes: each responsibility bullet can start with the bold heading. We'll preserve the text.
List items:
- Lead, mentor, and grow a team of Salesforce engineers and admins, fostering a culture of innovation, collaboration, and continuous learning.
- Conduct regular 1:1s, performance reviews, and career development planning.
- Advocate for the team’s priorities within the broader engineering and product organization.
- Recruit and retain top Salesforce talent.
- Promote a DevOps mindset and continuous delivery culture.
- Create inclusive, high-trust environments that empower individuals and teams.
- Own end-to-end delivery of Salesforce initiatives, ensuring quality, timeliness, and stakeholder satisfaction.
- Establish and enforce development standards, code quality, and deployment processes.
- Stay current with Salesforce platform capabilities, releases, and ecosystem trends.
- Drive innovation through evaluation and adoption of new Salesforce features, tools, and integrations.
- Ensure compliance with security, data privacy, and regulatory requirements.
- Participate in Salesforce Governance COE and Architecture Review Boards to uphold platform integrity and best practices.
- Design and implement scalable solutions across Sales, Service, Experience, Revenue, and Financial Clouds using Apex, LWC, Aura, and declarative tools.
- Develop and support Lightning Web Components, Aura components, Visualforce pages, and dynamic forms.
- Implement secure programming practices to avoid platform vulnerabilities.
- Lead development efforts using CI/CD tools (e.g., Copado), source control (Git), and test-driven development.
- Optimize existing features and refactor code to improve performance and maintainability.
- Implement robust logging, monitoring, and alerting for deployed solutions.
- Troubleshoot and resolve application and data issues, ensuring platform health.
- Design and support inbound/outbound integrations using Salesforce APIs (REST/SOAP) and middleware tools like MuleSoft.
- Provide OpenAPI Specifications (OAS) for external teams integrating with Salesforce.
- Collaborate with non-Salesforce teams on data modeling, access, and integration concerns.
- Extend support for functional and non-functional testing teams to ensure quality delivery.
- Partner closely with Product Owners and cross-functional teams to understand business needs and translate them into technical solutions.
- Participate in agile ceremonies, including sprint planning, demos, grooming, and standups.
- Contribute to design discussions, code reviews, and process improvements.
- Support cross-team dependencies and contribute to Agile Release Train planning (SAFe framework experience is a plus).
Now Requirements: The "Experience" section.
We need to capture: "5+ years of technical leadership and people management.7–8 years of hands-on Salesforce development and administration experience." Note missing space after period; we should keep as is? Probably we should keep exactly but we can add a space for readability? The instruction: preserve ALL substantive information; do not invent or summarize away detail. Changing punctuation might be considered altering detail. Safer to keep as given: "5+ years of technical leadership and people management.7–8 years of hands-on Salesforce development and administration experience." We'll keep that sentence.
Then list of proven expertise items (each line). We'll make list items.
Proven expertise list:
- Apex, LWC, Aura, SOQL/SOSL, Flows (screen, record-triggered, auto-launch)
- Apex triggers, batch classes, scheduled classes
- Salesforce security models (Profiles, Permission Sets, Roles, Sharing Rules)
- Data modeling, formulas, validation rules
- Secure programming practices and performance optimization
- Developer Console, CLI, Debug Logs, Query Optimizer
- Salesforce APIs, integration patterns, and event architecture
- CI/CD environments using tools like Copado
- Git workflows, pull request reviews, merge conflict resolution
- Agile/Scrum methodologies; SAFe experience preferred
- Middleware tools like MuleSoft and cross-platform integrations
Now Qualifications: Education and certifications.
Education: "Bachelor’s degree in Information Systems or related field.Salesforce Certified Admin, Advanced Admin, Platform Developer I & II required.Additional certifications (e.g., Revenue Cloud Consultant, Integration Architecture Designer) are a plus."
We need to keep as is, maybe add spaces after periods? The original missing spaces. We'll preserve exactly.
We could split into two sentences: but we must preserve. We'll keep as one string.
Now Skills: "Skills & Abilities" list.
We need to capture each bullet.
List:
- Candidates must possess the exceptional interpersonal skills to communicate effectively with internal & external resources, clients, and third parties
- Strong negotiation and collaboration skills and ability to develop and manage stakeholder expectations
- Exceptional communication skills (both verbal and written)
- Work both independently and in a team-oriented, collaborative environment
- Create inclusive team environments that foster trust and a sense of empowerment
- Effectively prioritize and execute tasks in a high-pressure environment and excels at communicating shifts in prioritization
- Adapt to shifting business priorities, demands, and timelines through analytical and problem-solving capabilities
- Must be able to multi-task and have a combination of organizational and analytical skills
- Strong push to always gain a combination of business and technical knowledge of the product in their area
- Must be systems-oriented, enjoy working with new tools and be a self-motivated learner
- Entrepreneurial attitude, with the ability to thrive in a fast-paced work environment
- Demonstrated self-starter who is goal-oriented, a critical thinker, and a creative problem solver
- Strong sense of urgency and follow-through in addressing issues and meeting timelines
Now Benefits: We need to capture all benefits listed.
Financial Benefits Sharing rewards is an integral part of our culture. We believe in the value of hard work and reward our employees beyond the paycheck. Our total rewards package is based on eligibility and includes: Competitive CompensationMonthly Bonuses for Eligible Employees401(k) and Company MatchAnnual Profit SharingPaid Time Off
Note missing spaces; we should preserve as given? Might be awkward but we must preserve. However we can add spaces for readability? The instruction says preserve ALL substantive information; does adding spaces count as altering? It
- for any list of duties/requirements/benefits, and
for prose. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from each section. Let's extract content precisely. About the role: combine company description and role overview. Company description: "GreatAmerica is a highly successful entrepreneurial company providing equipment financing to businesses across the United States. Our exemplary customer service, our principle-centered business philosophy and our team-based operating approach are key to our success and growth. We have also recently become a bank! We Are Looking to Add a Key Member to our Product Delivery Team! GreatAmerica is a highly successful entrepreneurial company providing equipment financing to businesses across the United States. Our exemplary customer service, principle-centered business philosophy, and team-based operating approach are crucial to our success and growth. GreatAmerica is structured in cross-functional product teams that allow individuals to make informed decisions that benefit the company and our customers. There is no doubt that we are building the greatest company of its kind, offering the finest products and services available anywhere. When you are part of the GreatAmerica team, you are part of the future, part of an opportunity to grow professionally and to reach your potential while enjoying your work." Then role overview: "As Manager, Salesforce Engineering, you will lead a high-performing team of developers and admins to deliver secure, scalable, and innovative solutions across the Salesforce ecosystem. You’ll combine deep technical expertise with strategic leadership to drive platform excellence, team growth, and business impact." We should not repeat the job title as a heading, but we can include it in prose. We need to avoid duplication: The company description appears twice; we should preserve all substantive information but not duplicate lines? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't explicitly say to deduplicate, but we should avoid duplicated lines as per earlier: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove duplicated lines. So we need to deduplicate the repeated company description. We'll keep one copy. Thus About the role prose: combine unique sentences. Let's craft About the role paragraph(s). Could be multiple
tags. Now Responsibilities: we have headings with bullet-like sentences. We need to turn each responsibility into list items under
- . The headings like "Leadership & Strategy" etc are subheadings but we are not to create extra headings; we just need list items. Could we keep subheadings as part of list item text? Probably yes: each responsibility bullet can start with the bold heading. We'll preserve the text.
List items:
- Lead, mentor, and grow a team of Salesforce engineers and admins, fostering a culture of innovation, collaboration, and continuous learning.
- Conduct regular 1:1s, performance reviews, and career development planning.
- Advocate for the team’s priorities within the broader engineering and product organization.
- Recruit and retain top Salesforce talent.
- Promote a DevOps mindset and continuous delivery culture.
- Create inclusive, high-trust environments that empower individuals and teams.
- Own end-to-end delivery of Salesforce initiatives, ensuring quality, timeliness, and stakeholder satisfaction.
- Establish and enforce development standards, code quality, and deployment processes.
- Stay current with Salesforce platform capabilities, releases, and ecosystem trends.
- Drive innovation through evaluation and adoption of new Salesforce features, tools, and integrations.
- Ensure compliance with security, data privacy, and regulatory requirements.
- Participate in Salesforce Governance COE and Architecture Review Boards to uphold platform integrity and best practices.
- Design and implement scalable solutions across Sales, Service, Experience, Revenue, and Financial Clouds using Apex, LWC, Aura, and declarative tools.
- Develop and support Lightning Web Components, Aura components, Visualforce pages, and dynamic forms.
- Implement secure programming practices to avoid platform vulnerabilities.
- Lead development efforts using CI/CD tools (e.g., Copado), source control (Git), and test-driven development.
- Optimize existing features and refactor code to improve performance and maintainability.
- Implement robust logging, monitoring, and alerting for deployed solutions.
- Troubleshoot and resolve application and data issues, ensuring platform health.
- Design and support inbound/outbound integrations using Salesforce APIs (REST/SOAP) and middleware tools like MuleSoft.
- Provide OpenAPI Specifications (OAS) for external teams integrating with Salesforce.
- Collaborate with non-Salesforce teams on data modeling, access, and integration concerns.
- Extend support for functional and non-functional testing teams to ensure quality delivery.
- Partner closely with Product Owners and cross-functional teams to understand business needs and translate them into technical solutions.
- Participate in agile ceremonies, including sprint planning, demos, grooming, and standups.
- Contribute to design discussions, code reviews, and process improvements.
- Support cross-team dependencies and contribute to Agile Release Train planning (SAFe framework experience is a plus).
Now Requirements: The "Experience" section.
We need to capture: "5+ years of technical leadership and people management.7–8 years of hands-on Salesforce development and administration experience." Note missing space after period; we should keep as is? Probably we should keep exactly but we can add a space for readability? The instruction: preserve ALL substantive information; do not invent or summarize away detail. Changing punctuation might be considered altering detail. Safer to keep as given: "5+ years of technical leadership and people management.7–8 years of hands-on Salesforce development and administration experience." We'll keep that sentence.
Then list of proven expertise items (each line). We'll make list items.
Proven expertise list:
- Apex, LWC, Aura, SOQL/SOSL, Flows (screen, record-triggered, auto-launch)
- Apex triggers, batch classes, scheduled classes
- Salesforce security models (Profiles, Permission Sets, Roles, Sharing Rules)
- Data modeling, formulas, validation rules
- Secure programming practices and performance optimization
- Developer Console, CLI, Debug Logs, Query Optimizer
- Salesforce APIs, integration patterns, and event architecture
- CI/CD environments using tools like Copado
- Git workflows, pull request reviews, merge conflict resolution
- Agile/Scrum methodologies; SAFe experience preferred
- Middleware tools like MuleSoft and cross-platform integrations
Now Qualifications: Education and certifications.
Education: "Bachelor’s degree in Information Systems or related field.Salesforce Certified Admin, Advanced Admin, Platform Developer I & II required.Additional certifications (e.g., Revenue Cloud Consultant, Integration Architecture Designer) are a plus."
We need to keep as is, maybe add spaces after periods? The original missing spaces. We'll preserve exactly.
We could split into two sentences: but we must preserve. We'll keep as one string.
Now Skills: "Skills & Abilities" list.
We need to capture each bullet.
List:
- Candidates must possess the exceptional interpersonal skills to communicate effectively with internal & external resources, clients, and third parties
- Strong negotiation and collaboration skills and ability to develop and manage stakeholder expectations
- Exceptional communication skills (both verbal and written)
- Work both independently and in a team-oriented, collaborative environment
- Create inclusive team environments that foster trust and a sense of empowerment
- Effectively prioritize and execute tasks in a high-pressure environment and excels at communicating shifts in prioritization
- Adapt to shifting business priorities, demands, and timelines through analytical and problem-solving capabilities
- Must be able to multi-task and have a combination of organizational and analytical skills
- Strong push to always gain a combination of business and technical knowledge of the product in their area
- Must be systems-oriented, enjoy working with new tools and be a self-motivated learner
- Entrepreneurial attitude, with the ability to thrive in a fast-paced work environment
- Demonstrated self-starter who is goal-oriented, a critical thinker, and a creative problem solver
- Strong sense of urgency and follow-through in addressing issues and meeting timelines
Now Benefits: We need to capture all benefits listed.
Financial Benefits Sharing rewards is an integral part of our culture. We believe in the value of hard work and reward our employees beyond the paycheck. Our total rewards package is based on eligibility and includes: Competitive CompensationMonthly Bonuses for Eligible Employees401(k) and Company MatchAnnual Profit SharingPaid Time Off
Note missing spaces; we should preserve as given? Might be awkward but we must preserve. However we can add spaces for readability? The instruction says preserve ALL substantive information; does adding spaces count as altering? It