Salesforce Developer - Digital Learning - UTK

We need to produce HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Also remove repeated paragraphs. We need to parse the posting. Let's extract core content: First paragraph: "Supports the Digital Learning department by leading strategic efforts to implement and support Salesforce platforms. This position is responsible for solution architecture, configurations, development, release management, implementation of changes and owning the the DL instance of Salesforce. Responsible for research of new emerging technologies with regards to Salesforce Education Cloud, Data Cloud, and Marketing Cloud. Position will work in lockstep with Digital Learning’s units, campus partners, and external vendors to provide technical support in the implementation and support of the Salesforce platform." Then there is a paragraph about University of Tennessee, Knoxville description. That's likely boilerplate about the university, but it's substantive info about employer. Should we keep? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The university description is not boilerplate; it's about the employer. Might be considered relevant. However we need to decide if we include it. The sections we can output: About the role (maybe a summary), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have info about responsibilities: solution architecture, configurations, development, release management, implementation of changes, owning DL instance, research of new emerging technologies (Education Cloud, Data Cloud, Marketing Cloud), work with units, campus partners, external vendors to provide technical support. Also later there is "Additional Information On All Postings Provided By UTK Technical Research, designs, and communicates solution architecture approach. Develops proof of concepts (POC) and changes to release into preproduction and production environments. Peer review changes to ensure standards and best practices are met. Develops and enforces standard operating procedures for release management and source control. Implements and maintains Salesforce security and governance best practices, including profiles, permission sets, permission set groups, sharing rules, role hierarchy, and field-level security. Creates documentation and testing plans. Assists with User Acceptance Testing (UAT) and release training. Provides troubleshooting and platform support. Analytical Gather and analyze business requirements to design scalable, effective solutions. Troubleshoot and optimize Salesforce system performance. Data modeling and understanding how to structure data efficiently within Salesforce. Monitor and analyze the performance of Salesforce implementations. Analyzing user feedback and system interaction patterns to improve the usability of Salesforce features. Anticipate challenges in system integrations or customizations. Collaboration and Communication Strong ability to work with cross-functional teams, including administrators, stakeholders, and end-users, to align technical solutions with business needs. Effective communication to translate technical concepts for non-technical audiences. Team-oriented approach for working in Agile or Scrum environments. Mentors and provides work direction to others. Project Management and Adaptability Familiarity with project management methodologies to manage tasks and timelines efficiently. Adaptability to learn and implement new Salesforce features or updates as they are released. Prioritize tasks and work in a fast-paced, evolving environment." That seems like more detailed responsibilities and skills. We also have Required Qualifications: Education: Bachelor’s Degree Salesforce Platform Developer I certification Required. Required Experience And Skills: Experience in Salesforce Education Cloud or (Sales and Service Cloud) Comprehensive understanding of Salesforce architecture, features, and capabilities, including Sales Cloud, Service Cloud, and Experience Cloud. Knowledge of Salesforce declarative tools (e.g., Salesforce Flow) and programmatic tools (Apex, Lightning Web Components, SOQL). Knowledge of integration techniques, including REST/SOAP APIs, middleware tools, and ETL processes. Experience on of Salesforce DevOps practices, including CI/CD and Salesforce DX. Experience on Lightning Web Components (LWC Knowledge of object-oriented programming, design patterns, and coding best practices. Knowledge of Agile/Scrum methodologies and version control systems (e.g., Git). Applicants must be legally authorized to work in the United States on a full-time basis without need now or in the future for sponsorship for employment-based visa status. Preferred Qualifications: Education: Bachelor’s Degree Experience And Skills Experience in Marketing Cloud, Data Cloud, and Mulesoft. Three or more years of progressively responsible development experience in Salesforce Experience working in a higher education setting. Understanding of ETL (extract, transform, load) technologies and practices. Experience deploying changes to Salesforce utilizing GIT as source control. Demonstrated proficiency in Microsoft Office applications, primarily Excel. Demonstrated successful management of multiple short-term and long-term projects, independent completion of projects with accuracy, thoroughness and creativity, and timely meeting of deadlines under pressure Experience with complex data sets including manipulating, merging, restructuring and analyzing large data sets. Salesforce Administrator certification and any additional certifications a plus Work Location Hybrid Compensation And Benefits: UT market range: MR 12 Anticipated hiring range: $90-$100k, depending on experience Find more information on the UT Market Range structure here Find more information on UT Benefits here Application Instructions: To express interest, please apply with the noted below attachments: Resume Cover Letter About The College/Department/Division: Digital Learning at UT, is a unit charged with advancing UT’s commitment to discovery, creativity, learning, and engagement, specifically for online learners. Using advanced and innovative technologies, Digital Learning at UT will provide scalable solutions that enhance the online learning experience and reduce barriers to student access and success, providing a tremendous impact to online learners across the state and the nation. At Digital Learning, we want to be bold and impactful, transforming the future of online education through innovative thinking and collaborative problem-solving. Join our dynamic and inclusive Digital Learning team where we take pride in teamwork, excellence, and a shared commitment to shaping the future through education and innovation. Additional Information On All Postings Provided By UTK Technical ... (the long list we saw earlier). That seems like more detailed responsibilities/skills. We need to decide sections. We have: - About the role: Could be the initial summary: "Supports the Digital Learning department by leading strategic efforts to implement and support Salesforce platforms. This position is responsible for solution architecture, configurations, development, release management, implementation of changes and owning the DL instance of Salesforce. Responsible for research of new emerging technologies with regards to Salesforce Education Cloud, Data Cloud, and Marketing Cloud. Position will work in lockstep with Digital Learning’s units, campus partners, and external vendors to provide technical support in the implementation and support of the Salesforce platform." We could also include the About The College/Department/Division description as part of About the role or maybe as a separate section? The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content accordingly. Responsibilities: list of duties: solution architecture, configurations, development, release management, implementation of changes, owning DL instance, research of new emerging technologies (Education Cloud, Data Cloud, Marketing Cloud), work with units, campus partners, external vendors to provide technical support, develop proof of concepts, peer review changes, develop and enforce SOPs for release management and source control, implement and maintain Salesforce security and governance best practices, creates documentation and testing plans, assists with UAT and release training, provides troubleshooting and platform support, gather and analyze business requirements, troubleshoot and optimize Salesforce system performance, data modeling, monitor and analyze performance, analyze user feedback, anticipate challenges in system integrations, collaborate with cross-functional teams, communicate technical concepts, mentor, project management, adaptability, prioritize tasks. Requirements: maybe required qualifications: Education: Bachelor’s Degree, Salesforce Platform Developer I certification. Also legal work authorization. Qualifications: maybe preferred qualifications? Or we could combine Required and Preferred under Qualifications? The instruction says we can have Requirements and Qualifications sections. Usually Requirements = required qualifications, Qualifications = preferred qualifications. We'll follow that. Skills: maybe list of skills: knowledge of Salesforce declarative tools, programmatic tools, integration techniques, DevOps, CI/CD, Salesforce DX, Lightning Web Components, OOP, design patterns, Agile/Scrum, Git, etc. Also preferred skills: Marketing Cloud, Data Cloud, Mulesoft, 3+ years Salesforce dev, higher ed experience, ETL, Git, MS Office Excel, project management, complex data sets, Admin certification. Benefits: we have "UT market range: MR 12" and "Find more information on UT Benefits here". Not specific benefits listed. The instruction: never create Benefits section unless posting actually states them. It mentions UT Benefits link but no specifics. So we should not create Benefits section because no concrete benefits described. Similarly Pay: we have "Anticipated hiring range: $90-$100k, depending on experience". That's specific pay range. So we can include Pay section with that info. Also UT market range MR 12 maybe also pay info. We'll include Pay. Schedule: we have Work Location Hybrid. That's not schedule. No schedule info like full-time, part-time, shift. So we should not create Schedule section. Thus sections: About the role, Responsibilities, Requirements (required qualifications), Qualifications (preferred qualifications), Skills (maybe combine required and preferred skills? But we already have required experience and skills under Requirements; preferred experience and skills under Qualifications. Could also have a Skills section for technical skills list. However we might avoid duplication. The instruction: Prefer a few substantive sections over many thin ones. We could combine Required and Preferred into Requirements and Qualifications, and maybe not have separate Skills. But we have a lot of skill details; we could put them under Requirements and Qualifications as appropriate. Let's decide: - About the role: summary paragraph (maybe also include About The College/Department/Division? Could be part of About the role). We'll include that as a paragraph. - Responsibilities: bullet list (

• ) of duties. - Requirements: bullet list of required qualifications: Education: Bachelor’s Degree, Salesforce Platform Developer I certification, legal work authorization (must be authorized to work in US). Also maybe mention "Experience in Salesforce Education Cloud or (Sales and Service Cloud)"? That's under Required Experience And Skills. So include that as required experience. - Qualifications: bullet list of preferred qualifications: Bachelor’s Degree (again), Experience in Marketing Cloud, Data Cloud, Mulesoft, 3+ years progressive Salesforce dev, higher ed setting, ETL understanding, Deploy changes using Git, MS Office Excel proficiency, project management, complex data sets, Salesforce Admin certification plus any additional certifications. - Skills: maybe we could include a Skills section for technical skills like knowledge of Salesforce declarative tools, programmatic tools, integration techniques, DevOps, CI/CD, Salesforce DX, Lightning Web Components, OOP, design patterns, Agile/Scrum, Git, etc. But many of those appear under Required Experience And Skills. Could be considered part of Requirements. To avoid many thin sections, we could merge skills into Requirements and Qualifications. However the instruction says we can use Skills heading if there is real specific content. We have specific content for skills (knowledge of tools, etc.). So we could have a Skills section. But we must not create sections with filler text. We have concrete skill details. Thus we could have: - About the role (summary) - Responsibilities (duties) - Requirements (required qualifications/experience) - Qualifications (preferred qualifications) - Skills (technical skills) - Pay (salary range) We'll omit Benefits and Schedule. Now we need to ensure we don't repeat info unnecessarily but preserve all substantive info. We'll need to include all details from the posting. Let's extract all substantive info pieces: From initial summary: - Supports Digital Learning department by leading strategic efforts to implement and support Salesforce platforms. - Responsible for solution architecture, configurations, development, release management, implementation of changes and owning the DL instance of Salesforce. - Responsible for research of new