VP, Senior Salesforce Engineer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (or Minimum Requirements), maybe Benefits, Pay, Schedule. Need to include only sections with real content. We have: - About the role: The initial paragraph describing role: "Jefferies is seeking a Salesforce Developer to design, build, and support highly customized Salesforce applications used across multiple lines of business, including Investment Banking, Global Markets, and Wealth Management. This role is ideal for a hands-on developer with strong experience across the Salesforce platform who enjoys solving complex problems, working on bespoke internal systems, and collaborating closely with product, business, and engineering partners. The ideal candidate has deep experience developing on Salesforce and a strong understanding of the broader Salesforce ecosystem, including Lightning (LWC/Aura), APIs and integrations, event-driven architectures, and modern front-end frameworks. Experience working in a fast-paced financial services environment is a strong plus." That's prose. - Responsibilities: list of bullet points. - Minimum Requirements: list of bullet points. - Nice to Have: list of bullet points. - Primary Location: maybe not needed as heading? Not in allowed headings list. Could be omitted. - Full Time Salary Range: $175,000 - $225,000. That's Pay. - About Us: description of company; could be considered "About the company" but not in allowed headings. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put About Us maybe under About the role? But we already have About the role. Could treat About Us as separate but not allowed heading; maybe we can omit or incorporate into About the role? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples, not exclusive? Probably we should stick to those headings. So we can have About the role (already), Responsibilities, Requirements (maybe combine Minimum Requirements and Nice to Have under Requirements?), Pay, Benefits, Schedule. We have Pay (salary range). Benefits: we have description of benefits in About Us paragraph: "In addition to salary, Jefferies Financial Group is proud to offer a comprehensive benefits package to eligible, full-time employees or part-time employees, who are scheduled to work at least 30 hours or more per week, including an annual discretionary incentive and retention bonus, competitive employee benefits, including: medical, dental & vision coverage; 401(k); life, accident, and disability insurance; and wellness programs. Jefferies also offers paid time off packages that include planned time off (e.g., vacation), unplanned time off (e.g., sick leave), and paid holidays, and for full-time employees, paid parental leave." That's benefits content. Schedule: we have "Full Time" and also "Ability to work in-office a minimum of 3-4 days per week." That's schedule info. So we can include Schedule section with that. We also have Primary Location but not needed. We need to avoid boilerplate like EEO etc. Remove those paragraphs. We must preserve all substantive information; not invent or summarize away detail. So we need to keep all bullet points exactly as given (maybe rephrase? Should preserve meaning but can keep same wording). Use

• for any list of duties/requirements/benefits. We need to ensure we don't create sections with filler like "commensurate with experience". Not present. We need to output only HTML fragment, no /, no markdown fences. Thus produce something like:

  About the role

  Jefferies is seeking a Salesforce Developer to design, build, and support highly customized Salesforce applications used across multiple lines of business, including Investment Banking, Global Markets, and Wealth Management. This role is ideal for a hands-on developer with strong experience across the Salesforce platform who enjoys solving complex problems, working on bespoke internal systems, and collaborating closely with product, business, and engineering partners. The ideal candidate has deep experience developing on Salesforce and a strong understanding of the broader Salesforce ecosystem, including Lightning (LWC/Aura), APIs and integrations, event-driven architectures, and modern front-end frameworks. Experience working in a fast-paced financial services environment is a strong plus.

  Responsibilities

  • Design, develop, and maintain custom Salesforce solutions across a heavily customized Salesforce org.
  • Build and support Apex, Lightning Web Components (LWC), JavaScript, and related front-end technologies.
  • Develop and maintain integrations using REST and SOAP APIs, including inbound and outbound data flows.
  • Work with CDC, Platform Events, and asynchronous processing to support event-driven architectures.
  • Integrate Salesforce with external systems via middleware, APIs, and real-time data exchanges.
  • Support and enhance authentication and access patterns, including SSO and identity integrations.
  • Troubleshoot and resolve complex issues across the Salesforce platform, including performance, security, and data integrity concerns.
  • Partner with business stakeholders and technical teams to translate requirements into scalable technical designs.
  • Participate in Agile ceremonies, contribute to sprint planning, and deliver high-quality solutions on tight timelines.
  • Ensure solutions follow Salesforce best practices, security guidelines, and performance standards.

  Requirements

  Minimum Requirements

  • 10+ years experience within the Salesforce ecosystem, with significant hands-on development experience in a complex, heavily customized Salesforce org.
  • Strong proficiency in:Apex
  • Lightning Web Components (LWC) and JavaScript
  • Salesforce data model and security architecture
  • Proven experience designing and implementing Salesforce integrations, including REST and SOAP APIs.
  • Solid understanding of Salesforce platform architecture, capabilities, and constraints.
  • Ability to read, debug, and optimize Apex and JavaScript code.
  • Experience working with event-driven patterns such as Platform Events and CDC.
  • Familiarity with SSO configuration and identity management concepts in Salesforce.
  • Experience with Git-based version control and CI/CD pipelines.
  • Comfortable working in a fast-paced, highly regulated environment with competing priorities.
  • Strong communication skills and experience collaborating with globally distributed teams.
  • Ability to work in-office a minimum of 3-4 days per week.
  • Experience working in Agile/Scrum development environments.
  Maybe also Nice to Have as part of Requirements or separate Qualifications? The allowed headings include Qualifications, Skills. Could put Nice to Have under Qualifications. But we need to avoid filler. We have Nice to Have list; we can include as Qualifications. Thus:

  Qualifications

  • Salesforce Platform App Builder certification.
  • Salesforce Developer or Architect certifications.
  • Experience developing Experience Cloud sites.
  • Familiarity with React or other modern front-end frameworks and how they integrate with Salesforce.
  • Understanding of relational databases and data design (SQL, SOQL, or similar).
  • Knowledge of least privilege access, separation of duties, and enterprise security principles.
  • Experience with JIRA and Confluence.
  • Background supporting Salesforce in financial services or investment banking environments.
  Pay:

  Pay

  Full Time Salary Range of $175,000 - $225,000.

  Benefits:

  Benefits

  In addition to salary, Jefferies Financial Group is proud to offer a comprehensive benefits package to eligible, full-time employees or part-time employees, who are scheduled to work at least 30 hours or more per week, including an annual discretionary incentive and retention bonus, competitive employee benefits, including: medical, dental & vision coverage; 401(k); life, accident, and disability insurance; and wellness programs. Jefferies also offers paid time off packages that include planned time off (e.g., vacation), unplanned time off (e.g., sick leave), and paid holidays, and for full-time employees, paid parental leave.

  Schedule: We have schedule info: Ability to work in-office a minimum of 3-4 days per week. Also Full Time. Could combine.

  Schedule

  Full-time position with expectation to work in-office a minimum of 3-4 days per week.

  We must not repeat job title as heading. Already not. We must not include Job ID etc. We must not include boilerplate like EEO etc. We removed. Check that we preserved all substantive information: The initial description, responsibilities, minimum requirements, nice to have, salary, benefits, schedule (in-office days). Also we kept "Full Time" in Pay and Schedule. We omitted "Primary Location" and "About Us" company description (the paragraph about Jefferies being a leading global firm). That is substantive? It's about the company; maybe we could include under About the role? But we already have About the role paragraph describing role. The company description could be considered extra but not required. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The company description is substantive; but maybe it's considered boilerplate? It's not navigation/legal/EEO; it's about the firm. Might be considered relevant. However the allowed headings do not include "About the company". Could we incorporate it into About the role? The About the role currently is about the role; we could add a sentence about Jefferies being a leading global firm. But that would be adding content not originally in the About the role paragraph; but we could merge the two paragraphs: first paragraph about role, second about company. That would preserve info. Let's do that: About the role section can contain both role description and company overview. That seems acceptable. Thus modify About the role paragraph to include both: "Jefferies is a leading global, full-service investment banking and capital markets firm that provides advisory, sales and trading, research, and wealth and asset management services. With more than 40 offices around the world, we offer insights and expertise to investors, companies, and governments. At Jefferies, we are committed to building a culture that provides opportunities for all employees regardless of our differences and supports a workforce that is reflective of the communities where we work and live. As a result, we are able to pool our collective insights and intelligence to provide fresh and innovative thinking for our clients. Jefferies is committed to creating and sustaining a workforce that welcomes individuals from all backgrounds to apply. Our employment decisions are made without regard to race, creed, color, national origin, ancestry, religion, pregnancy, age, medical condition, physical or mental disability, marital status, domestic partner status, sex, sexual orientation, gender, gender identity or expression, veteran or military status, genetic information, reproductive health decisions, or any other factor protected by applicable law. We are committed to hiring the most qualified applicants and complying with all federal, state, and local equal employment opportunity laws. As part of this commitment, Jefferies will extend reasonable accommodation to individuals with disabilities, as required by applicable law." But that's a lot of EEO boilerplate which we are supposed to remove. Indeed the instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we must remove the EEO paragraphs. So we should keep only the non-EEO part: "Jefferies is a leading global, full-service investment banking and capital markets firm that provides advisory, sales and trading, research, and wealth and asset management services. With more than 40 offices around the world, we offer