Senior Software Developer (Salesforce)

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (or Qualifications), Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to extract content. Given posting: - Company description: "Our Company: ISN was established in 2001 and is a global leader in contractor and supplier management. We work closely with a variety of household-name clients in the US, Canada, Europe, Australia, Latin America, and the Middle East to connect them with safe and reliable contractors and suppliers and incorporate a level of due diligence in the contractor management process." That could be "About the role"? Actually "About the role" is usually description of role. But we have "The Position: As a member of ISN's Enterprise CRM team, the Senior Software Developer will build and maintain solutions within Salesforce, perform code reviews, and support business requests by participating in end-user meetings." That's about the role. We also have "Who should apply?" list of qualifications/experience. We have Responsibilities list. We have Benefits list. We have Onsite Requirements (schedule/location) - includes schedule: "In-person attendance is required at minimum 2 days onsite per week and required for certain meetings and tasks (generally Wednesday and Thursday for collaboration with stakeholders and customers, trainings, team collaboration day, ISN events, team events, performance reviews, etc.) The first month will involve extensive onboarding, job training, and shadowing with the business team. Employees should anticipate spending additional time onsite during this period to support training and knowledge transfer activities." Thus we have schedule info: minimum 2 days onsite per week, specific days. We have location: "Onsite Requirements: 3232 McKinney Ave #1500, Dallas, TX 75204 Employees must be within a commutable distance to the Dallas, TX office. Relocation is required for candidates not already local to the DFW area." We have Pay: Not mentioned. So we should NOT include Pay section. We have Benefits: Yes, list. We have Skills: Preferred Skills list. We have Qualifications: "Who should apply?" includes required qualifications and certifications. We have Responsibilities: list. We have About the role: maybe combine company description and position description. We must not repeat job title as heading. The page already shows it, so we don't add heading for Senior Software Developer. We must not put Job ID/requisition numbers as headings (none present). We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. At end there is EEO statement and drug screen etc. Those are boilerplate; we should remove them. Also note: "ISN Benefits*" heading with asterisk; we will treat as Benefits section. We need to use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. We need to decide which headings to use. The instructions list possible headings; we should use those that match content. We have: - About the role: could include company description and position description. - Responsibilities: list. - Requirements: maybe combine "Who should apply?" (required qualifications) and maybe also certifications? Could be Requirements. - Qualifications: maybe separate? But we have both Requirements and Qualifications as possible headings. We need to avoid duplication; we can choose one. The posting includes "Who should apply?" which includes required experience, certifications, preferred skills. Could treat as Requirements (mandatory) and Skills (preferred). The instructions say we can have both Requirements and Qualifications sections; but we should not create thin sections. Better to combine required qualifications into Requirements, and preferred skills into Skills. Thus: - Requirements: list of mandatory qualifications: 6+ years Salesforce development experience, experience with MuleSoft, Apex, Lightning Web Components, Flows, SOQL/SOSL, web services dev using REST, JSON, XML, strong understanding of Salesforce product suite (Sales Cloud, Service Cloud, Revenue Cloud (CPQ & Billing), Experience Cloud), experience managing a large Salesforce org (900+ seats), comfortable working beyond written acceptance criteria, experience with code review, interest in frequent business end-user interaction and collaboration, Bachelor's degree in Computer Science or related field and/or equivalent work experience, Certifications: Salesforce Certified Administrator, Salesforce Certified Platform App Builder, Salesforce Certified Platform Developer. We should keep as list. - Skills (Preferred Skills): Experience with Agentforce, Salesforce Certified Platform Administrator II, Salesforce Certified MuleSoft Developer. - Responsibilities: list as given. - Benefits: list as given. - Schedule: include onsite requirements: minimum 2 days onsite per week (generally Wednesday and Thursday), first month extensive onboarding etc. Also location? Location maybe not schedule but could be included in Schedule or maybe separate? There's no heading for Location; we could include location in About the role or maybe in a short p under Schedule? But schedule heading is for schedule info; location could be placed in About the role or maybe we can add a short p under Schedule about location? The instructions: Use headings only for those sections; we can include other info in prose under those headings. So we can put location in About the role or maybe under Schedule as a note. Better to put location in About the role (company location). But About the role is about role, not location. However we can include location in a short p under Schedule? The schedule heading is for schedule; location is not schedule but we could still include it as a p under Schedule if we want to avoid extra heading. But we have no other heading for location; we could put it in About the role as a brief note: "Position is based at ISN's office: 3232 McKinney Ave #1500, Dallas, TX 75204." That seems okay. We must not include boilerplate: EEO, drug screen, background check, equal opportunity, etc. Remove. Also remove duplicated lines: none. Now construct HTML. Structure:

  About the role

  ISN was established in 2001 and is a global leader in contractor and supplier management. We work closely with a variety of household-name clients in the US, Canada, Europe, Australia, Latin America, and the Middle East to connect them with safe and reliable contractors and suppliers and incorporate a level of due diligence in the contractor management process. As a member of ISN's Enterprise CRM team, the Senior Software Developer will build and maintain solutions within Salesforce, perform code reviews, and support business requests by participating in end-user meetings. Position is based at ISN's office: 3232 McKinney Ave #1500, Dallas, TX 75204.

  Responsibilities

  • Develop and design Salesforce solutions using both programmatic and declarative tools
  • Build and maintain integrations using REST/SOAP APIs, middleware, and platform events
  • Interact regularly with business end-users to discuss and recommend enhancements. This requires a strong understanding of how end-users work within our Salesforce instance in order to translate functional requirements into Salesforce technical requirement and recommend solutions.
  • Complete Salesforce Admin functions, including user management, data management, and reports/dashboards
  • Perform code reviews; strong attention to detail and QA knowledge required
  • Identify gaps, edge cases, or downstream cross-cloud impacts not explicitly stated in requirements
  • Collaborate with Salesforce architects, developers, business analysts, ISN software engineers, and business end-users to improve functionality and processes
  • Shadow business end-users to gain a deep understanding of the business use of Salesforce, business needs, and the impact on users' day-to-day roles
  • Effectively leverage approved AI-powered tools and automation to enhance productivity across daily work activities and applicable elements of the Software Development Life Cycle — requirements, design, development, testing, deployment, and/or operations

  Requirements

  • 6+ years of Salesforce development experience
  • Experience with MuleSoft, Apex, Lightning Web Components, Flows, and SOQL/SOSL
  • Web services development experience using REST, JSON, and XML
  • Strong understanding of the Salesforce product suite including Sales Cloud, Service Cloud, Revenue Cloud (CPQ & Billing), and Experience Cloud
  • Experience managing a large Salesforce org (900+ seats)
  • Comfortable working beyond written acceptance criteria — asking clarifying questions and identifying downstream or cross-cloud impacts not explicitly stated in requirements
  • Experience with code review
  • Interest in frequent business end-user interaction and collaboration
  • Bachelor's degree in Computer Science or a related field from an accredited university, and/or equivalent work experience
  • Certifications: Salesforce Certified Administrator, Salesforce Certified Platform App Builder, Salesforce Certified Platform Developer

  Skills

  • Experience with Agentforce
  • Salesforce Certified Platform Administrator II
  • Salesforce Certified MuleSoft Developer

  Benefits

  • 100% company-paid monthly insurance premiums for employees and dependents - Medical, Dental, Vision, and Life Insurance
  • 4% retirement matching
  • Paid time off: 0-1 year – 15 day (pro-rated first year); 1-5 years – 20 days; 5-10 years – 25 days; 10+ years – 30 days
  • Holidays – 13 paid holidays
  • Monthly cell phone reimbursement
  • Complimentary parking space or monthly reimbursement for DART public transportation
  • Team-building activities and events, including quarterly kick-off meetings and community volunteer day
  • Matching charitable gift program
  • Professional development & training opportunities
  • Wellness Program: Focuses on community, financial, mental, nutrition, physical and social health
  • Business casual, jeans allowed

  Schedule

  • In-person attendance required minimum 2 days onsite per week (generally Wednesday and Thursday for collaboration with stakeholders and customers, trainings, team collaboration day, ISN events, team events, performance reviews, etc.)
  • First month involves extensive onboarding, job training, and shadowing with the business team; additional onsite time anticipated during this period to support training and knowledge transfer activities
  We must ensure no extra headings like Pay. Also ensure we didn't include any boilerplate like EEO, drug screen, etc. Check that we preserved all substantive information: company description, position description, location, responsibilities, requirements, preferred skills, benefits, schedule. Yes. We omitted the note about "ISN does not provide work visa sponsorship..." That's substantive? It's a requirement about work authorization. Should we include? It's a requirement: "Applicants for employment must possess work authorization/right to work without the need for sponsorship by the employer now or in the future." That is a requirement. Should we include under Requirements. Also note about relocation required for candidates not already local to DFW area. That's also a requirement. Also note about onsite requirements: we already captured schedule but also mention relocation required. Should we include that under Requirements or Schedule? Probably under Requirements as a eligibility criterion. Let's add. Also note: "Employees must be within a commutable distance to the Dallas, TX office." That's also a requirement. Thus add to Requirements list: - Must possess work authorization/right to work without need for sponsorship (