Salesforce Administrator

We need to output HTML fragment with sections: About the role (but we shouldn't repeat job title; we can have heading "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include heading "About the role". We must not repeat the job title as a heading. So we can have

About the role

then paragraph(s). Then Responsibilities heading, then list. Then Requirements/Qualifications? The posting has "About you:" which includes experience, skills, etc. That could be Requirements or Qualifications. We'll treat as Requirements. Also there is "Why join us?" which includes benefits/perks. So we can have Benefits heading. Also there is salary range info: we can put under Pay heading. Also schedule info: remote/hybrid with location requirement. That's schedule. So we need sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Ensure we only include sections with real content. All have content. We must remove boilerplate: EEO, accommodations, etc. Also remove "Please let us know if you require accommodations during the interview process." That's boilerplate? It's about accommodations; maybe keep? It's not EEO but still maybe considered boilerplate. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Accommodations request could be considered application instruction? Probably remove. Also "We recognize that people come with experience and talent beyond just the technical requirements of a job..." that's encouraging to apply; maybe keep? It's not boilerplate but could be considered fluff. Might keep as part of About you? But we can incorporate into Requirements? It's not a requirement. Safer to keep as part of About you? But we have no section for that. Could include in Requirements as a note? Might be considered filler. I'd remove that paragraph. Also "Diversity of experience and skills combined with passion is a key to innovation and excellence. Therefore, we encourage people from all backgrounds to apply to our positions." That's also encouraging application; could be removed as boilerplate? Not exactly EEO but similar. Might remove. Also "Pursuant to California Labor Code § 432.3, the salary range for this position is $82,000 - $134,000." Keep for Pay. Also "Additional compensation may include bonuses, commissions, equity, or other benefits." Keep in Pay or Benefits? Could be Pay. Also "Unison provides equal employment opportunity..." that's EEO; remove. Now construct HTML. We need to preserve all substantive information. Let's extract: About the role paragraph: "We are seeking a dynamic Salesforce Administrator who shares our passion for enabling homeownership. In this role, you will tackle challenges that reward creative thinking and inspired execution. You thrive in a collaborative, cross-functional environment, bringing intellectual curiosity, analytical rigor, and deep empathy to every team and customer interaction. As a forward-thinking problem solver who excels in agile settings, you enjoy embracing new tools and supporting others as they learn to adopt them. If you are excited by the prospect of joining a data and technology-driven company, we would love to connect. This position may be performed Remotely within the United States -OR- as a hybrid position with a requirement of 3 full days in our Omaha, Nebraska or San Francisco, CA office." Note: The last sentence about remote/hybrid could go to Schedule section. But it's also in About the role. We could keep it there, but then Schedule section would be duplicate. Better to split: Keep About the role without location detail, and put location in Schedule. However instruction: Preserve ALL substantive information; do not invent or summarize away detail. So we need to keep that info somewhere. We can keep it in About the role and also have Schedule section referencing remote/hybrid? That would duplicate. Better to move it to Schedule and keep About the role without that sentence. But then we would be removing that sentence from About the role, which is substantive. We could keep it in About the role and not have a separate Schedule section if we consider it covered. But we need to include Schedule section only if posting has real specific content for it. It does have remote/hybrid detail. So we need a Schedule section. We can keep the sentence in Schedule and omit from About the role. However we would be removing that sentence from About the role, which is substantive. But we could rephrase About the role to exclude that sentence, but that would be removing content. Not allowed. So we need to keep it somewhere; we could keep it in About the role and also have Schedule section that repeats it? That would duplicate content, which is not allowed? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is not explicitly forbidden but might be considered redundant. Better to avoid duplication. We could keep the sentence in About the role and then Schedule section could be empty? Not allowed. So we need to decide: maybe treat the remote/hybrid as part of About the role, and not create a separate Schedule section. But the instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It doesn't forbid having a section that overlaps content; but we should avoid thin sections. However we have other schedule info? Only that sentence. If we put it in About the role, we could still have Schedule section but would need to put something else; we could put the same sentence there, but that duplicates. Might be okay but not ideal. Alternatively, we could split: About the role paragraph without the location sentence, and Schedule section with that sentence. Then we are not duplicating; we have moved content. That's preserving all info, just relocated. Is that allowed? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Moving content is not inventing or summarizing away; it's just reordering. Should be fine. Thus we will have About the role paragraph without the location sentence. Then Schedule section with that sentence. Now Responsibilities: list items as given. Let's list them exactly: - Provide feedback and direction to management regarding identified trends and knowledge gaps - Perform database maintenance tasks, including diagnostic tests and duplicate entry cleansing. - Document processes, including error reports and changes to field history tables - Take on tickets to develop our Salesforce instance relevant to your skill level - Provide Salesforce training and end-user support - Have a deeper understanding of the administration of the tools Business Systems manages, including their purpose within Unison - Manage all incoming inquiries from team members related to system issues - Escalate to management all unresolved issues, where appropriate - Understand how our Salesforce organization is structured - Be able to prepare reports for other teams - Support management of Salesforce roles and profiles - Be familiar with the tools that Business Systems manages, and be able to provision users Note some have periods; we can keep as is. Now Requirements/Qualifications: from "About you:" bullet list. We need to capture: - 3-5 years experience as a Business Systems Administrator with at least 3 years of experience with Salesforce (preferably as an administrator or developer), with a Salesforce certification - Ability to read and understand languages such as Apex, Java, Javascript, SQL, HTML, and CSS - Experience with any of the following systems (preferred): 360SMS; Cirrus Insight; FormAssembly; Gearset; Gong; Nintex; Outreach; Provar; Skuid; and Talkdesk - Knowledge of real estate transactions and/or mortgage industry experience - Impeccable organization skills and multi-tasking abilities - Attentive to details, with ability to identify trends and patterns - Able to complete work independently and coordinate within the team Also maybe include "We recognize that people come with experience and talent beyond just the technical requirements of a job..." but we decided to remove as fluff. Now Benefits: from "Why join us?" and "Perks of the Unison employee include:" plus maybe other benefits. Paragraph: "The Unison team draws on a deep and wide range of talent across several disciplines. Visionaries in investment management, product development, and financial technology are joined by innovative real estate and consumer finance experts creating a unique culture." That's fluff but maybe keep as part of About us? Could be omitted? It's substantive? It's describing culture; maybe keep as part of About us? But we have no About us section; we could incorporate into Benefits? Might be considered filler. However we have "Perks of the Unison employee include: competitive salaries, 100% paid medical and dental benefits, generous PTO policy, paid parental leave program, and fantastic downtown SF and Omaha locations, as well as being an integral part of a well-funded market leader with incredible momentum." Also "About us:" paragraph about Unison mission, growth, awards. That's substantive about company; could be placed under About us but we don't have that heading. Could we add an About us section? Not in allowed headings list but we could still use h3 for any heading? The instruction says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exhaustive; we could add About us if we want. However they said "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are typical but not exclusive. Safer to stick to those headings. So we could put the About us info under Benefits? Not ideal. Maybe we can create a section "About the company" but not listed. Might be considered extra heading not in examples; risk. Better to incorporate into Benefits or maybe omit? The instruction: Preserve ALL substantive information. So we need to keep that info. We could put it under Benefits as additional description, but it's not a benefit. Could create a section "About the company" but risk being considered non-standard. However the instruction didn't forbid other headings; just gave examples. I think it's safe to add an About us section with h3. But to be safe, maybe we can put it under Benefits as a paragraph describing company culture and perks. However the Benefits section already includes perks; we can add a paragraph about company mission and awards there. That would still preserve info. Thus Benefits section will include: description of Unison team, perks, mission, growth, awards. Now Pay section: salary range and additional compensation. Schedule section: remote/hybrid detail. Now we need to output only HTML fragment, no html/body tags, no markdown. Let's craft. Structure:

About the role

We are seeking a dynamic Salesforce Administrator who shares our passion for enabling homeownership. In this role, you will tackle challenges that reward creative thinking and inspired execution. You thrive in a collaborative, cross-functional environment, bringing intellectual curiosity, analytical rigor, and deep empathy to every team and customer interaction. As a forward-thinking problem solver who excels in agile settings, you embrace new tools and support others as they learn to adopt them. If you are excited by the prospect of joining a data and technology-driven company, we would love to connect.

Responsibilities

• Provide feedback and direction to management regarding identified trends and knowledge gaps
• Perform database maintenance tasks, including diagnostic tests and duplicate entry cleansing.
• Document processes, including error reports and changes to field history tables
• Take on tickets to develop our Salesforce instance relevant to your skill level
• Provide Salesforce training and end-user support
• Have a deeper understanding of the administration of the tools Business Systems manages, including their purpose within Unison
• Manage all incoming inquiries from team members related to system issues
• Escalate to management all unresolved issues