Principal Software Engineer - Salesforce
GreatAmerica · Des Moines, IA · 3 wk ago
Full-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes description about role, responsibilities, requirements, qualifications, skills, benefits. No explicit Pay or Schedule details. So we should not include Pay or Schedule sections. Also we should not repeat job title as heading. Use for each section heading. Use
for each section heading. 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 etc.
We need to parse the posting and extract sections.
Let's identify content:
- Intro about GreatAmerica: "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 Technology Group!" This is about the company; could be "About the role"? Actually "About the role" maybe includes description of role. But we could treat this as "About the role" or maybe "About the company". The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections to include based on content.
We have:
- Role description: "The Principal Software Engineer is the highest-level individual contributor within Software Engineering and is responsible for defining, influencing and collaborating enterprise level solution designs, engineering strategy, software engineering governance standards, and long-term technology direction across multiple platforms, systems, and engineering domains. This role serves as a recognized technical authority who influences enterprise technology decisions, establishes reusable engineering standards and patterns, and drives software engineering across the organization. Principal Software Engineers operate with significant autonomy and are accountable for balancing reliability, scalability, security, regulatory requirements, cost optimization, and business outcomes across systems. Working closely with engineering leadership, architects, business leaders, risk and compliance partners, and external vendors, this role ensures software solutions align with organizational strategy and engineering standards are enforced while enabling sustainable, scalable, and resilient technology solutions."
That's responsibilities.
- Then "As a Principal Software Engineer, You Will" with sub-bullets: Technology Leadership & Enterprise Influence, Architecture, APIs & Integration Strategy, Engineering Excellence, Security & Reliability, Delivery, Innovation & AI-Native Engineering. Those are responsibilities/duties.
- Then "To Be Successful In This Role You Will Need" list of qualifications: Bachelor’s degree required in Information Systems or equivalent. 12+ years of software engineering experience, working in Sales Cloud, Service Cloud and Experience Cloud or related areas. Expert level experience leading technical design reviews and establish standards across teams. Expert level experience providing technical directions for complex Salesforce initiatives. Experience with identification of platform limitations and develops scalable patterns, least privileged architecture and deep understanding of Salesforce security framework. Advanced knowledge of developing and supporting Lightning web Components and the Aura framework. In depth knowledge of HTML and CSS. In depth knowledge of JavaScript. Advanced level of knowledge of APEX Language, SOQL, SOSL. Advanced level of knowledge of APEX triggers, batch classes and scheduled classes. Advanced level of knowledge of data modeling. Advanced level of knowledge of flows including screen and record triggers auto launch flows. Advanced level of knowledge of secure programming within the Salesforce Platform to avoid any security pitfalls. Advanced level of knowledge of Developer Console, Query Optimizer, Data loader, CLI and Debug Logs. Advanced level of knowledge and implementation experience on Integration patterns and salesforce APIs. Advanced level of knowledge of REST/SOAP API concepts and experience utilizing rest-based services from external parties and implementing rest-based services in Salesforce. Advanced knowledge of working with Git and source control management processes like pull request reviews, branch management and merge conflict resolution. Intermediate level of knowledge of working with Salesforce in a CI/CD environment using a tool like Gearset. In-depth experience of working in a Scrum and Agile Software Development Methodology is required. Experience with the SAFe, agile framework is a plus. Advanced level of experience in troubleshooting and isolating root causes in Salesforce applications. Ability to read, use and produce system design artifacts such as flowcharts and wireframes. Demonstrated experience defining/enforcing solution design standards, engineering strategy, or governance across multiple platforms, products, or technology domains. Experience in at least one other technology ecosystem that is outside of Salesforce. Proven ability to influence enterprise technology decisions and drive cross-functional alignment without direct authority.
That's qualifications/requirements.
- Then "Skills & Abilities" list: Expert knowledge of software engineering principles, solution design patterns, and distributed systems. Strong understanding of cloud technologies, automation practices, infrastructure, integrations, and modern engineering approaches. Advanced systems thinking and ability to connect technical decisions to organizational outcomes. Deep understanding of platform reliability, observability, security, governance, and operational excellence. Experience designing and governing technology standards used by multiple teams. Strong solution decision-making skills with the ability to evaluate tradeoffs across cost, risk, performance, and scalability. Ability to anticipate future technology needs and develop long-term platform strategies. Strong negotiation and collaboration skills and ability to develop and manage stakeholder expectations. 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. Ability to lead through expertise, mentorship, and organizational influence. Strong push to always gain a combination of business and technical knowledge of financial industry. 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. Strong sense of urgency and follow-through in addressing issues and meeting timelines. Experience operating within regulated, complex, or enterprise-scale environments preferred.
That's skills.
- Then "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 Compensation Monthly Bonuses for Eligible Employees 401(k) and Company Match Annual Profit Sharing Paid Time Off Health, Wellbeing, And Family Planning Benefits Paid Vacation Paid Sick Days Paid Holidays Gym Reimbursement Health Insurance Dental Insurance Vision Insurance Short-Term and Long-Term Disability Company Paid Life Insurance Flexible Spending Accounts (FSA) Health Savings Accounts (HSA) Employee Assistance Program Parental Leave Education And Career Planning Benefits Tuition Assistance Networking Opportunities Leadership Development Opportunities Perks Paid Parking Service Awards Hybrid work arrangements Business casual environment A strong organizational culture focused on our greatest asset: you!"
That's benefits.
No explicit Pay or Schedule details. So we omit those sections.
We need to include sections only when posting has real specific content. So we can have:
- About the role (maybe include intro about company and role overview). Could be "About the role" containing the paragraph about GreatAmerica and the role overview.
- Responsibilities: include the "As a Principal Software Engineer, You Will" bullet points (maybe also the earlier paragraph about responsibilities). We'll combine.
- Requirements: maybe the "To Be Successful In This Role You Will Need" list.
- Qualifications: maybe overlapping with requirements; but we could treat "Requirements" as the bullet list of qualifications, and "Qualifications" maybe the degree and years? However the instruction says we can have sections like Requirements, Qualifications, Skills. We need to avoid duplication. We could map:
- About the role: company intro + role purpose paragraph.
- Responsibilities: the "As a Principal Software Engineer, You Will" sections.
- Requirements: the "To Be Successful In This Role You Will Need" list (including degree, years, experience, etc.)
- Qualifications: maybe the "Experience in at least one other technology ecosystem..." etc? But that's already in requirements. Could split but better to keep one section for qualifications/requirements. However we need to follow instruction: use headings as examples; we can include only those that have content. We could include Requirements and Qualifications separately if we can split content meaningfully.
Let's see if we can separate:
Requirements: maybe the hard requirements: Bachelor’s degree required in Information Systems or equivalent. 12+ years of software engineering experience, working in Sales Cloud, Service Cloud and Experience Cloud or related areas. Expert level experience leading technical design reviews and establish standards across teams. Expert level experience providing technical directions for complex Salesforce initiatives. Experience with identification of platform limitations and develops scalable patterns, least privileged architecture and deep understanding of Salesforce security framework.
Qualifications: maybe the rest: Advanced knowledge of developing and supporting Lightning web Components and the Aura framework, In depth knowledge of HTML and CSS, In depth knowledge of JavaScript, Advanced level of knowledge of APEX Language, SOQL, SOSL, Advanced level of knowledge of APEX triggers, batch classes and scheduled classes, Advanced level of knowledge of data modeling, Advanced level of knowledge of flows including screen and record triggers auto launch flows, Advanced level of knowledge of secure programming within the Salesforce Platform to avoid any security pitfalls, Advanced level of knowledge of Developer Console, Query Optimizer, Data loader, CLI and Debug Logs, Advanced level of knowledge and implementation experience on Integration patterns and salesforce APIs, Advanced level of knowledge of REST/SOAP API concepts and experience utilizing rest-based services from external parties and implementing rest-based services in Salesforce, Advanced knowledge of working with Git and source control management processes like pull request reviews, branch management and merge conflict resolution, Intermediate level of knowledge of working with Salesforce in a CI/CD environment using a tool like Gearset, In-depth experience of working in a Scrum and Agile Software Development Methodology is required, Experience with the SAFe, agile framework is a plus, Advanced level of experience in troubleshooting and isolating root causes in Salesforce applications, Ability to read, use and produce system design artifacts such as flowcharts and wireframes, Demonstrated experience defining/enforcing solution design standards, engineering strategy, or governance across multiple platforms, products, or technology domains, Experience in at least one other technology ecosystem that is outside of Salesforce, Proven ability to influence enterprise technology decisions and drive cross-functional alignment without direct authority.
That seems plausible.
Skills: the "Skills & Abilities" list.
Benefits: the benefits list.
We'll not include Pay or Schedule.
Now we need to output HTML fragment with headings and appropriate - for lists,
for prose.
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep the exact phrasing? We should preserve the meaning but not necessarily exact wording? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep the details, but we can rephrase into list items? Probably we should keep the content as is, but we can format as list items. That's okay.
We need to avoid boilerplate like cookie/navigation/legal/EEO etc. The posting includes some at end: "If your experience aligns closely, please apply. We value diverse backgrounds and adding new perspectives. We encourage you to apply if you can make a strong impact in this role at www.greatamerica.com/careers. Please note, applicants must be authorized to work for any employer in the U.S. We are unable to sponsor or take over sponsorship of an employment visa." That's application instructions and EEO-ish; we should remove that.
Also remove duplicated lines.
Now craft HTML.
We'll start with
About the role
then containing the intro about GreatAmerica and the role overview paragraph.
Let's extract that paragraph: "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 Technology Group! The Principal Software Engineer is the highest-level individual contributor within Software Engineering and is responsible for defining, influencing and collaborating enterprise level solution designs, engineering strategy
for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate etc. We need to parse the posting and extract sections. Let's identify content: - Intro about GreatAmerica: "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 Technology Group!" This is about the company; could be "About the role"? Actually "About the role" maybe includes description of role. But we could treat this as "About the role" or maybe "About the company". The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections to include based on content.
We have:
- Role description: "The Principal Software Engineer is the highest-level individual contributor within Software Engineering and is responsible for defining, influencing and collaborating enterprise level solution designs, engineering strategy, software engineering governance standards, and long-term technology direction across multiple platforms, systems, and engineering domains. This role serves as a recognized technical authority who influences enterprise technology decisions, establishes reusable engineering standards and patterns, and drives software engineering across the organization. Principal Software Engineers operate with significant autonomy and are accountable for balancing reliability, scalability, security, regulatory requirements, cost optimization, and business outcomes across systems. Working closely with engineering leadership, architects, business leaders, risk and compliance partners, and external vendors, this role ensures software solutions align with organizational strategy and engineering standards are enforced while enabling sustainable, scalable, and resilient technology solutions."
That's responsibilities.
- Then "As a Principal Software Engineer, You Will" with sub-bullets: Technology Leadership & Enterprise Influence, Architecture, APIs & Integration Strategy, Engineering Excellence, Security & Reliability, Delivery, Innovation & AI-Native Engineering. Those are responsibilities/duties.
- Then "To Be Successful In This Role You Will Need" list of qualifications: Bachelor’s degree required in Information Systems or equivalent. 12+ years of software engineering experience, working in Sales Cloud, Service Cloud and Experience Cloud or related areas. Expert level experience leading technical design reviews and establish standards across teams. Expert level experience providing technical directions for complex Salesforce initiatives. Experience with identification of platform limitations and develops scalable patterns, least privileged architecture and deep understanding of Salesforce security framework. Advanced knowledge of developing and supporting Lightning web Components and the Aura framework. In depth knowledge of HTML and CSS. In depth knowledge of JavaScript. Advanced level of knowledge of APEX Language, SOQL, SOSL. Advanced level of knowledge of APEX triggers, batch classes and scheduled classes. Advanced level of knowledge of data modeling. Advanced level of knowledge of flows including screen and record triggers auto launch flows. Advanced level of knowledge of secure programming within the Salesforce Platform to avoid any security pitfalls. Advanced level of knowledge of Developer Console, Query Optimizer, Data loader, CLI and Debug Logs. Advanced level of knowledge and implementation experience on Integration patterns and salesforce APIs. Advanced level of knowledge of REST/SOAP API concepts and experience utilizing rest-based services from external parties and implementing rest-based services in Salesforce. Advanced knowledge of working with Git and source control management processes like pull request reviews, branch management and merge conflict resolution. Intermediate level of knowledge of working with Salesforce in a CI/CD environment using a tool like Gearset. In-depth experience of working in a Scrum and Agile Software Development Methodology is required. Experience with the SAFe, agile framework is a plus. Advanced level of experience in troubleshooting and isolating root causes in Salesforce applications. Ability to read, use and produce system design artifacts such as flowcharts and wireframes. Demonstrated experience defining/enforcing solution design standards, engineering strategy, or governance across multiple platforms, products, or technology domains. Experience in at least one other technology ecosystem that is outside of Salesforce. Proven ability to influence enterprise technology decisions and drive cross-functional alignment without direct authority.
That's qualifications/requirements.
- Then "Skills & Abilities" list: Expert knowledge of software engineering principles, solution design patterns, and distributed systems. Strong understanding of cloud technologies, automation practices, infrastructure, integrations, and modern engineering approaches. Advanced systems thinking and ability to connect technical decisions to organizational outcomes. Deep understanding of platform reliability, observability, security, governance, and operational excellence. Experience designing and governing technology standards used by multiple teams. Strong solution decision-making skills with the ability to evaluate tradeoffs across cost, risk, performance, and scalability. Ability to anticipate future technology needs and develop long-term platform strategies. Strong negotiation and collaboration skills and ability to develop and manage stakeholder expectations. 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. Ability to lead through expertise, mentorship, and organizational influence. Strong push to always gain a combination of business and technical knowledge of financial industry. 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. Strong sense of urgency and follow-through in addressing issues and meeting timelines. Experience operating within regulated, complex, or enterprise-scale environments preferred.
That's skills.
- Then "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 Compensation Monthly Bonuses for Eligible Employees 401(k) and Company Match Annual Profit Sharing Paid Time Off Health, Wellbeing, And Family Planning Benefits Paid Vacation Paid Sick Days Paid Holidays Gym Reimbursement Health Insurance Dental Insurance Vision Insurance Short-Term and Long-Term Disability Company Paid Life Insurance Flexible Spending Accounts (FSA) Health Savings Accounts (HSA) Employee Assistance Program Parental Leave Education And Career Planning Benefits Tuition Assistance Networking Opportunities Leadership Development Opportunities Perks Paid Parking Service Awards Hybrid work arrangements Business casual environment A strong organizational culture focused on our greatest asset: you!"
That's benefits.
No explicit Pay or Schedule details. So we omit those sections.
We need to include sections only when posting has real specific content. So we can have:
- About the role (maybe include intro about company and role overview). Could be "About the role" containing the paragraph about GreatAmerica and the role overview.
- Responsibilities: include the "As a Principal Software Engineer, You Will" bullet points (maybe also the earlier paragraph about responsibilities). We'll combine.
- Requirements: maybe the "To Be Successful In This Role You Will Need" list.
- Qualifications: maybe overlapping with requirements; but we could treat "Requirements" as the bullet list of qualifications, and "Qualifications" maybe the degree and years? However the instruction says we can have sections like Requirements, Qualifications, Skills. We need to avoid duplication. We could map:
- About the role: company intro + role purpose paragraph.
- Responsibilities: the "As a Principal Software Engineer, You Will" sections.
- Requirements: the "To Be Successful In This Role You Will Need" list (including degree, years, experience, etc.)
- Qualifications: maybe the "Experience in at least one other technology ecosystem..." etc? But that's already in requirements. Could split but better to keep one section for qualifications/requirements. However we need to follow instruction: use headings as examples; we can include only those that have content. We could include Requirements and Qualifications separately if we can split content meaningfully.
Let's see if we can separate:
Requirements: maybe the hard requirements: Bachelor’s degree required in Information Systems or equivalent. 12+ years of software engineering experience, working in Sales Cloud, Service Cloud and Experience Cloud or related areas. Expert level experience leading technical design reviews and establish standards across teams. Expert level experience providing technical directions for complex Salesforce initiatives. Experience with identification of platform limitations and develops scalable patterns, least privileged architecture and deep understanding of Salesforce security framework.
Qualifications: maybe the rest: Advanced knowledge of developing and supporting Lightning web Components and the Aura framework, In depth knowledge of HTML and CSS, In depth knowledge of JavaScript, Advanced level of knowledge of APEX Language, SOQL, SOSL, Advanced level of knowledge of APEX triggers, batch classes and scheduled classes, Advanced level of knowledge of data modeling, Advanced level of knowledge of flows including screen and record triggers auto launch flows, Advanced level of knowledge of secure programming within the Salesforce Platform to avoid any security pitfalls, Advanced level of knowledge of Developer Console, Query Optimizer, Data loader, CLI and Debug Logs, Advanced level of knowledge and implementation experience on Integration patterns and salesforce APIs, Advanced level of knowledge of REST/SOAP API concepts and experience utilizing rest-based services from external parties and implementing rest-based services in Salesforce, Advanced knowledge of working with Git and source control management processes like pull request reviews, branch management and merge conflict resolution, Intermediate level of knowledge of working with Salesforce in a CI/CD environment using a tool like Gearset, In-depth experience of working in a Scrum and Agile Software Development Methodology is required, Experience with the SAFe, agile framework is a plus, Advanced level of experience in troubleshooting and isolating root causes in Salesforce applications, Ability to read, use and produce system design artifacts such as flowcharts and wireframes, Demonstrated experience defining/enforcing solution design standards, engineering strategy, or governance across multiple platforms, products, or technology domains, Experience in at least one other technology ecosystem that is outside of Salesforce, Proven ability to influence enterprise technology decisions and drive cross-functional alignment without direct authority.
That seems plausible.
Skills: the "Skills & Abilities" list.
Benefits: the benefits list.
We'll not include Pay or Schedule.
Now we need to output HTML fragment with headings and appropriate - for lists,
for prose.
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep the exact phrasing? We should preserve the meaning but not necessarily exact wording? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep the details, but we can rephrase into list items? Probably we should keep the content as is, but we can format as list items. That's okay.
We need to avoid boilerplate like cookie/navigation/legal/EEO etc. The posting includes some at end: "If your experience aligns closely, please apply. We value diverse backgrounds and adding new perspectives. We encourage you to apply if you can make a strong impact in this role at www.greatamerica.com/careers. Please note, applicants must be authorized to work for any employer in the U.S. We are unable to sponsor or take over sponsorship of an employment visa." That's application instructions and EEO-ish; we should remove that.
Also remove duplicated lines.
Now craft HTML.
We'll start with
About the role
then containing the intro about GreatAmerica and the role overview paragraph.
Let's extract that paragraph: "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 Technology Group! The Principal Software Engineer is the highest-level individual contributor within Software Engineering and is responsible for defining, influencing and collaborating enterprise level solution designs, engineering strategy
- for lists,
for prose. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep the exact phrasing? We should preserve the meaning but not necessarily exact wording? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep the details, but we can rephrase into list items? Probably we should keep the content as is, but we can format as list items. That's okay. We need to avoid boilerplate like cookie/navigation/legal/EEO etc. The posting includes some at end: "If your experience aligns closely, please apply. We value diverse backgrounds and adding new perspectives. We encourage you to apply if you can make a strong impact in this role at www.greatamerica.com/careers. Please note, applicants must be authorized to work for any employer in the U.S. We are unable to sponsor or take over sponsorship of an employment visa." That's application instructions and EEO-ish; we should remove that. Also remove duplicated lines. Now craft HTML. We'll start with
About the role
thencontaining the intro about GreatAmerica and the role overview paragraph. Let's extract that paragraph: "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 Technology Group! The Principal Software Engineer is the highest-level individual contributor within Software Engineering and is responsible for defining, influencing and collaborating enterprise level solution designs, engineering strategy