Senior Software Engineer - Salesforce

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to extract content. First, identify about the role: The posting includes description of company and role. Could be "About the role" section: description of what the role entails. We can put a paragraph summarizing the role description: "As a Senior Software Engineer - Salesforce, you will design, develop, test, document and implement solutions..." etc. We need to preserve all substantive info, not invent. We need to avoid repeating job title as heading. Use

for each section heading. We need to use

• for any list of duties/requirements/benefits. We need to use

  for prose. We need to remove boilerplate: cookie/navigation/legal/EEO etc. Not present. We need to drop duplicated lines. We need to not include Pay/Schedule/Benefits unless posting actually states them. The posting includes "Financial Benefits" section with details: Competitive Compensation, Monthly Bonuses, 401(k) and Company Match, Annual Profit Sharing, Paid Time Off, health benefits, etc. Also "Perks" includes Paid Parking, Service Awards, Hybrid work arrangements, Business casual environment, strong culture. So we have Benefits section. Pay: Not explicitly stated a salary range; only "Competitive Compensation" but that's vague. The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. "Competitive Compensation" is not a specific number; but it's still stating compensation. However they said "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". "Competitive Compensation" is similar to placeholder? It's vague but not exactly those phrases. Might be considered filler. Safer to not include Pay section because no specific pay. We'll omit Pay. Schedule: Not mentioned. No schedule info. So omit Schedule. Now sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. We need to decide what goes where. Responsibilities: list of duties from the role description: design, develop, test, document, implement solutions; practice TDD; implement logging; work with CI/CD Copado; source control; refactor; troubleshoot; optimize; work on integrations; data discussions; suggest external teams about APIs; experience with Salesforce event architecture; implement security; work with middleware like MuleSoft; work with multiple teams on Agile train; extend support to testing teams; support other developers; ensure architectural integrity; live principles; participate in agile team; manage key relationships; extended hours may be required; perform additional duties; willing to travel; participate in research/prototyping; adhere to Salesforce Governance COE standards; continually gain knowledge; serve as solutions-oriented consultant; work with Solution Review and Architecture Review Boards; regular collaboration with Product Owner; understand broader business why; participate in design/arch discussions, grooming, demos, standups; contribute ideas on best practices; determine coding best practices; perform code reviews; enforce standards; train/coach/mentor. That's a lot. We'll put as

  • items. Requirements: maybe education and certifications: Bachelor's degree required in Information Systems or equivalent. Salesforce certified Admin, Advanced Admin, Salesforce Certified Platform Developer I and II are required. Experience: 5-8 years’ developer and admin experience working in Sales Cloud, Service Cloud and Experience Cloud; advanced knowledge of LWC and Aura; in-depth HTML/CSS; in-depth JavaScript; advanced Apex, SOQL, SOSL; advanced Apex triggers, batch, scheduled; intermediate VisualForce; advanced record sharing; advanced dynamic forms; advanced user security and access; intermediate formulas and validation rules; advanced data modeling; advanced flows; advanced secure programming; advanced knowledge of Developer Console, Query Optimizer, Data loader, CLI, Debug Logs; advanced integration patterns and Salesforce APIs; advanced REST/SOAP API concepts; advanced Git and source control; intermediate experience with CI/CD using Copado; in-depth experience in Scrum/Agile; experience with SAFe a plus; advanced troubleshooting; ability to read/use/produce system design artifacts; computer skills: expert MS Office, design & dev best practices preferred; advanced MS Office, VS Code. Qualifications: maybe overlapping with requirements. Could treat Requirements as experience/skills, Qualifications as education/certifications. But we need to avoid duplication. Let's decide: - About the role: brief paragraph describing role and company. - Responsibilities: list of duties. - Requirements: list of mandatory experience/technical skills (the long list). Could be split into Requirements and Skills? But we have Skills section also. Could put technical skills under Skills, and experience/years under Requirements. However the instruction: "Use
    • for any list of duties/requirements/benefits". So we can have multiple lists. We need to decide what goes to Requirements vs Skills vs Qualifications. Qualifications: education and certifications. Requirements: years of experience, experience with specific clouds, Agile/Scrum, etc. Skills: technical competencies like languages, tools, etc. But there is overlap. We'll try to separate. Let's extract: Education & Certifications (Qualifications): - Bachelor’s degree required in Information Systems or equivalent. - Salesforce certified Admin, Advanced Admin, Salesforce Certified Platform Developer I and II are required. Experience (Requirements): - 5-8 years’ developer and admin experience working in Sales Cloud, Service Cloud and Experience Cloud. - 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. - Extended hours may be required to meet deadlines. - Performs additional duties as required. - Willing and able to travel to conferences, training and other skill development opportunities. - Participates in research and prototyping of new features available in Salesforce. Skills (technical): - 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. - Intermediate level of knowledge of VisualForce pages and components. - Advanced level of knowledge of record sharing. - Advanced level of knowledge of dynamic forms. - Advanced level of knowledge of Salesforce user security and access including but not limited to Profiles, Permission Set Groups, Roles and Role Hierarchies, Sharing Rules, user management, permission sets and permission set groups. - Intermediate level of knowledge of formulas and validation rules. - 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 API’s. - 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 as CI/CD environment using a tool like Copado. - Computer Skills: Expert knowledge of MS Office products and Design & Development best practices preferred; Advanced knowledge of Microsoft Office, VS Code. Also some soft skills: interpersonal, communication, negotiation, collaboration, inclusive team environments, prioritize, adapt, multi-task, analytical, self-motivated learner, entrepreneurial attitude, self-starter, goal-oriented, critical thinker, creative problem solver, sense of urgency, follow-through. These could go under Skills as well (soft skills). But we already have many technical skills; we could add a separate bullet list for soft skills under Skills or maybe under Requirements? The instruction: "Use
      • for any list of duties/requirements/benefits". So we can have multiple lists within a section. We'll create sections:

        About the role

        ...

        Responsibilities

        • ...

        Requirements

        • ...

        Qualifications

        • ...

        Skills

        • ...

        Benefits

        • ...
        We must not repeat job title as heading. Good. Now we need to preserve all substantive information; do not invent or summarize away detail. So we need to include all points from the posting, but we can combine similar points but not lose detail. However we must be careful not to omit any substantive detail. That's a lot; we need to include everything. Let's extract all substantive sentences from the posting and map them. First, 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! ... 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." We can include that in About the role. Now role-specific: "As a Salesforce engineer you will be relied on to leverage your knowledge of Salesforce ecosystem, to design and implement ideal solutions by using out of box configuration , custom development on the platform that creates the greatest value for our customers. As a Senior Software Engineer - Salesforce, You Will Design, develop, test, document and implements solutions and reusable assets across various Salesforce Clouds including but not limited to sales, service and experience through declarative programming and Custom programming using Apex, LWC’s to meet the solution design, and be aligned with Salesforce best practices and architectural standardsEffectively practices test driven development creating and implementing effective unit tests and code coverage for all solutionsImplement sound logging and other diagnostic tools into each solution deployedWorking effectively with our CI/CD tool Copado to quickly and efficiently promote changes thru higher orgs including productionWorking on Source Control Management participating in Pull Request Reviews and resolving merge conflictsRefactoring and optimizing solutions to increase value and productivity of the teamTroubleshooting applications and data issues and implementing bug fixesOptimize and extend features in the existing Salesforce environmentsWork on inbound and outbound integrations in to and out from salesforce platform to other systems using various salesforce integration patternsShould be able to be part of salesforce data discussions and help Non salesforce teams with salesforce data model and data concernsUnderstand and suggest external teams about salesforce API’s and provide OAS as required for callouts into salesforceExperience with Salesforce event architecture and maintain the existing codebase of the ApplicationsImplement security and access provisioning using salesforce sharing and access mechanismsAbility to work and connect with middleware tools like MuleSoft from salesforceAbility to work and connect with multiple teams on Agile train to understand the cross-team dependenciesExtending support to functional and nonfunctional testing teams to deliver on the implemented productExtend support to other developers on the team for any issues and hurdles to maintain solid output from the teamEnsure architectural integrity and consistency across the applications in their product areaLives the GreatAmerica principles; Participate as an active member of an agile product team helping define effective stories, implement