Salesforce Developer I

We need to output HTML fragment with sections only if content present. The posting includes Vision, Mission, Department Purpose, Primary Purpose, Key Areas Of Focus (with subpoints), Business Systems and Application Support, Application Documentation, Job Competencies And Experience (with sub-sections: Education & Certifications, Experience, Organizational Competencies), Physical Requirements. We need to use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). However we must map content to appropriate headings. The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we should use those generic headings, but we can also use other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect we use those headings where appropriate. But we need to decide which sections correspond. We have content: Vision, Mission, Department Purpose, Primary Purpose, Key Areas Of Focus (Responsibilities), Business Systems and Application Support (maybe also responsibilities), Application Documentation (maybe responsibilities), Job Competencies And Experience (Qualifications/Skills), Organizational Competencies (Skills), Physical Requirements (maybe not needed unless specified). Benefits, Pay, Schedule not present, so we should not include those sections. We must not repeat the job title as a heading. The job title is "Salesforce Developer I". Not to be used as heading. We must not put Job ID/requisition numbers as headings; none present. We must remove boilerplate: Vision, Mission, Department Purpose maybe considered boilerplate? But they are substantive? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Vision/Mission/Department Purpose might be considered boilerplate but they are part of the posting's description. However they might be considered generic fluff. The instruction says "Prefer a few substantive sections over many thin ones." Vision/Mission/Department Purpose might be thin. But we need to preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep them if they are substantive. However they might be considered boilerplate but not explicitly listed as to remove. The list of boilerplate to remove: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Vision/Mission/Department Purpose not in that list, so we keep. Thus we will create sections: maybe "About the role" for Vision/Mission/Department Purpose/Primary Purpose? Or we could have separate headings: "About the role", "Responsibilities", "Qualifications", "Skills". Use

for each. We need to decide mapping: - About the role: could include Vision, Mission, Department Purpose, Primary Purpose. - Responsibilities: Key Areas Of Focus (Salesforce Development...), Business Systems and Application Support, Application Documentation. - Qualifications: Education & Certifications, Experience (years), Salesforce Certifications. - Skills: Organizational Competencies (list of competencies), maybe also technical skills (Apex, etc.) but those are under Experience. We must use

• for any list of duties/requirements/benefits. So for responsibilities we need to list each duty as
• . For qualifications we need list. We must use

  for prose. We must not create sections with filler like "commensurate with experience". Not present. We need to ensure we include all substantive information. Let's extract details. Vision: "Transform the university through the power of generosity." Mission: "Unite donor passions with university priorities to elevate the impact of Oklahoma State University." DEPARTMENT PURPOSE: "The Application Administration and Development team serves the OSU Foundation, donors, and university partners by providing effective and efficient software applications and processes which support strategic fundraising and advancement operations." PRIMARY PURPOSE: "The Salesforce Developer I will work alongside other database and data systems administrators and developers to support the maintenance, utilization, and enhancements of the OSU Foundation’s Salesforce environments including CRM Production and Sandbox organizations, Salesforce Experience Cloud, and Salesforce Marketing Cloud environments while also contributing to the administration, integration, development, and support of other technologies that support Foundation operations. The Salesforce Developer I will be responsible for consulting with the rest of the Information Services team members and internal business customers to assess, recommend, and implement best practice solutions." Key Areas Of Focus (70%): bullet list: - Develop, maintain, and support Apex classes and triggers with Salesforce cloud computing governing limits in mind. - Develop, maintain, and support an intuitive user interface using the Lightning Web Component framework, Visualforce pages and Apex controllers. - Implement customization and configuration changes of Salesforce CRM inclusive of, but not limited to custom objects, custom fields, validation rules, profiles, permission set groups, organization wide sharing, flows, custom metadata, and custom settings. - Assist and advise Salesforce administrator(s) on permissions build out for all developed solutions. - Manage incident tickets, debug, and resolve issues relating to Salesforce CRM, Salesforce Experience Cloud, and Salesforce Marketing Cloud solutions. - Engage deployment tools to retrieve and deploy metadata through the Salesforce environment deployment pipeline. - Support upgrades of of managed and unmanaged packages installed in the Salesforce environments. Business Systems and Application Support (15%): - Support the ongoing administration and maintenance of business systems that enable fundraising, constituent engagement, reporting, and operational processes. - Assist with application configuration, customization, integration development, and system enhancements across multiple platforms. - Support data quality, security, and operational best practices across enterprise applications and related systems. - Contribute to cross-functional technology initiatives and special projects as assigned. Application Documentation (15%): - Document solutions thoroughly using flowcharts, layouts, diagrams, charts, code comments, and clearly written code. - Assist with creating and updating training documentation for users of all experience levels. Other duties as assigned. (We can include as a bullet maybe.) Job Competencies And Experience: Education & Certifications- Bachelor’s degree in MIS, Computer Science, Computer Engineering, Information Systems, or 1-3 years related work experience. 1+ years related work experience 3+ years related work experience preferred. Salesforce Certifications Required Platform Developer I Preferred (one or more) Administrator Advanced Administrator Platform App Builder JavaScript Developer Experience Cloud Consultant Marketing Cloud Developer Experience- 1-3 years in a Salesforce Developer or Administrator role with a heavy focus on Salesforce development. Required experience programming in Apex, SOQL, SOSL, Visualforce, AmpScript, JavaScript, HTML, CSS, Git. Additional Preferred skillsets include ASP.NET, C#, and SQL programming. Proven sense of humor and ability to have fun. Organizational Competencies- list: - Effective Communication: description. - Execution & Initiative: description. - Teamwork/Interpersonal Skills: description. - Problem Solving/Judgment: description. - Adaptability/Flexibility: description. - Courage & Conviction: description. - Donor Centered: description. PHYSICAL REQUIREMENTS: Must use a computer terminal and view a computer screen for extended periods of time. Must talk in person or by phone (frequently and sometimes for extended periods) to people on campus and across the country. Must constantly use visual acuity to check printed and designed materials of various types. Must be able to navigate within the OSU Foundation. Typical office working conditions. We need to decide whether to include Physical Requirements as a section. There's no heading for it in the list, but we could still use

  for it? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. Probably we should stick to those headings. Physical Requirements could go under "Requirements" maybe. But we have separate "Requirements" heading maybe for qualifications? Actually "Requirements" could be for qualifications/experience. Physical requirements could be part of "Requirements". However we already have Education & Certifications etc. Might be better to create a "Requirements" section that includes both qualifications and physical requirements. But the instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections: About the role, Responsibilities, Requirements, Qualifications, Skills. But we might be duplicating. Let's think. We need to output only HTML fragment, no extra text. We need to decide a structure that captures all info without redundancy. Option: Use sections:

  About the role

  - include Vision, Mission, Department Purpose, Primary Purpose.

  Responsibilities

  - include Key Areas Of Focus, Business Systems and Application Support, Application Documentation, Other duties as assigned.

  Qualifications

  - include Education & Certifications, Experience, Salesforce Certifications.

  Skills

  - include Organizational Competencies, Technical skills (Apex, etc.) maybe but those are under Experience. We could also include Physical Requirements under Qualifications or Requirements. But we have no separate Requirements section; we could add a

  Requirements

  for physical requirements. However we already have Qualifications. Might be okay to have both Qualifications and Requirements. The instruction says we can use those headings; not required to use all. So we can have About the role, Responsibilities, Qualifications, Skills, Requirements (for physical). That seems fine. But we must ensure we don't create thin sections. Each should have substantive content. Let's craft. About the role: combine Vision, Mission, Department Purpose, Primary Purpose into a few paragraphs. Responsibilities: list bullet points for each duty. Qualifications: list education, experience, certifications. Skills: list organizational competencies (maybe as bullet list with description). Could also include technical skills but they'd be duplicate. Requirements: physical requirements. We must not repeat job title. We must not include boilerplate like Vision/Mission? It's okay. Now produce HTML. We need to wrap each section in

  and then content. For lists, use

  • . For prose, use

    . We must not include any extra text outside HTML. Let's draft. First, About the role:

    Vision: Transform the university through the power of generosity.

    Mission: Unite donor passions with university priorities to elevate the impact of Oklahoma State University.

    Department Purpose: The Application Administration and Development team serves the OSU Foundation, donors, and university partners by providing effective and efficient software applications and processes which support strategic fundraising and advancement operations.

    Primary Purpose: The Salesforce Developer I will work alongside other database and data systems administrators and developers to support the maintenance, utilization, and enhancements of the OSU Foundation’s Salesforce environments including CRM Production and Sandbox organizations, Salesforce Experience Cloud, and Salesforce Marketing Cloud environments while also contributing to the administration, integration, development, and support of other technologies that support Foundation operations. The Salesforce Developer I will be responsible for consulting with the rest of the Information Services team members and internal business customers to assess, recommend, and implement best practice solutions.

    That's fine. Responsibilities: we need to list each duty. We'll create a
    with
    • for each bullet. List: - Develop, maintain, and support Apex classes and triggers with Salesforce cloud computing governing limits in mind. - Develop, maintain, and support an intuitive user interface using the Lightning Web Component framework, Visualforce pages and Apex controllers. - Implement customization and configuration changes of Salesforce CRM inclusive of, but not limited to custom objects, custom fields, validation rules, profiles, permission set groups, organization wide sharing, flows, custom metadata, and custom settings. - Assist and advise Salesforce administrator(s) on permissions build out for all developed solutions.