Staff Attorney - Civil Rights, Edley Center on Law & Democracy (5258C), Berkeley Law - #88850

We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections that have real specific content. The posting includes: About Berkeley (intro), Departmental Overview, Position Summary, Application Review Date, Responsibilities, Required Qualifications, Education/Training, Licenses/Certifications, Salary & Benefits, How To Apply, Other Information, etc. We need to map to headings: "About the role" could be Position Summary? Or maybe combine About Berkeley and Departmental Overview? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose headings that match content. We must not repeat job title as heading. We must not put Job ID etc. We need to include sections only when posting has real specific content. So we need to decide which sections to include. We have content for: - About the role: Could be Position Summary and maybe Departmental Overview? The "About the role" heading could contain Position Summary and maybe Departmental Overview? But we need to preserve all substantive info. We could have separate sections: About the role (Position Summary), Responsibilities, Requirements (maybe combine Required Qualifications, Education/Training, Licenses/Certifications?), Qualifications (maybe same as Requirements?), Skills (maybe part of qualifications), Benefits, Pay, Schedule. But we must avoid duplication. The instruction: Prefer a few substantive sections over many thin ones. So we could combine similar items. Let's think: The posting includes: - About Berkeley (intro about university) - maybe not needed as "About the role"? Could be part of About the role? But it's about the institution, not role. Might be okay to include under About the role? But we could also omit if not directly about role. However we must preserve ALL substantive information; we cannot drop info unless it's boilerplate/navigation/legal/EEO etc. The About Berkeley paragraph is substantive but not about role; still we need to preserve it. Where to put? Could be under About the role heading as a preamble? Or we could create a section "About Berkeley" but not in allowed headings list. 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? It says use

for section headings (e.g. ...). Likely they expect only those headings. So we need to map all content into those sections. Thus we need to fit About Berkeley content into "About the role" maybe as a brief intro. Or we could put it under "About the role" as a paragraph. Similarly Departmental Overview could also go under About the role. Position Summary also under About the role. Application Review Date maybe could be placed under "About the role" as metadata? But we should not put Job ID/requisition numbers as headings; we can fold minor metadata into a short

or drop it. Application Review Date is minor metadata; we could drop it or include in a short p under About the role. Responsibilities: we have a list. Requirements: maybe combine Required Qualifications, Education/Training, Licenses/Certifications into a Requirements section. Qualifications: maybe duplicate; we could skip Qualifications if we already have Requirements. Skills: maybe part of Required Qualifications; we could include under Requirements. Benefits: we have Salary & Benefits section with salary range and benefits info. Pay: we have salary range; could be under Pay. Schedule: we have full-time (40 hours/week) and remote work up to 1 day/week. So schedule info. We need to avoid filler like "commensurate with experience". Not present. We must not include boilerplate like EEO, misconduct, background check etc. Those are legal/EEO boilerplate; we must remove them. Also remove "How To Apply", "Other Information", "Conviction History Background", "Misconduct", "Equal Employment Opportunity". Also remove "Application Review Date"? It's minor metadata; we can drop or fold into short p. Probably drop. We must preserve all substantive information: that includes the salary range, benefits description, remote work eligibility, full-time, responsibilities, required qualifications, education/training, licenses/certifications, department overview, position summary, about Berkeley. We must not invent or summarize away detail. Thus we need to produce HTML with sections:

About the role

About Berkeley ... Departmental Overview ... Position Summary ...

But we need to preserve all details; we can combine into paragraphs but must not lose any detail. Could be multiple paragraphs. Then

Responsibilities

• ... each responsibility

Then

Requirements

We need to include Required Qualifications list, Education/Training, Licenses/Certifications. Could be a

with items. But we must not lose any detail: each bullet from Required Qualifications, each line from Education/Training, Licenses/Certifications. We could structure as
• Advanced knowledge in civil rights law and practice.
... etc. Then separate sublist for Education/Training? Could just include as items. Then

Benefits

For information on the comprehensive benefits package offered by the University, please visit the University of California's Compensation & Benefits website. Under California law, the University of California, Berkeley is required to provide a reasonable estimate of the compensation range for this role and should not offer a salary outside of the range posted in this job announcement. This range takes into account the wide range of factors that are considered in making compensation decisions, including but not limited to experience, skills, knowledge, abilities, education, licensure and certifications, analysis of internal equity, and other business and organizational needs. It is not typical for an individual to be offered a salary at or near the top of the range for a position. Salary offers are determined based on final candidate qualifications and experience. The budgeted annual salary range that the University reasonably expects to pay for this position is $110,000 - $136,710. This is an exempt, monthly-paid position. This is a full-time (40 hours/week) Career position eligible for UC benefits.

But we also have remote work up to 1 day/week. That could be under Schedule. Thus Benefits section could include the benefits description (the paragraph about benefits website). But the salary range is Pay. Thus we need Pay section: maybe just the salary range. Schedule section: full-time (40 hours/week) and remote work up to 1 day/week. Thus we need to split. Thus:

Pay

The budgeted annual salary range that the University reasonably expects to pay for this position is $110,000 - $136,710. This is an exempt, monthly-paid position.

Schedule

This is a full-time (40 hours/week) Career position eligible for UC benefits. This position is eligible for up to 1 day/week of remote work within the United States. Exact arrangements are determined in partnership with your supervisor to meet role responsibilities and department needs and are subject to change.

But note: The sentence about benefits also appears in Schedule; we might duplicate. Actually the original says: "This is a full-time (40 hours/week) Career position eligible for UC benefits." That's about benefits and schedule. We could keep that in Schedule, and Benefits section could just refer to benefits website. Thus Benefits section:

For information on the comprehensive benefits package offered by the University, please visit the University of California's Compensation & Benefits website.

Now we need to ensure we didn't drop any substantive info: The sentence about California law requiring estimate, etc. That is substantive about salary range; we placed in Pay section. Good. The sentence about not typical to be offered at top of range, salary offers determined based on qualifications, etc. That's also substantive about Pay; we could include in Pay section as well. Thus Pay section could contain all those sentences. Now Benefits section: just the benefits website sentence. Now Schedule: full-time, remote work. Now Requirements: we need to include Required Qualifications list, Education/Training, Licenses/Certifications. Let's extract Required Qualifications list: - Advanced knowledge in civil rights law and practice. - Expertise in legal research, analysis, and advocacy strategy development. - Strong communication and interpersonal skills to communicate effectively with all levels of staff and influence, both verbally and in writing. - Ability to exercise sound judgement, use discretion and maintain all confidentiality. - Advanced project management and organizational skills. - Experience practicing civil law (litigation and or legislation/policy). - Ability to multi-task with demanding timeframes. - Advanced analytical and problem-solving skills, with the ability to develop creative and strategic solutions. - Proven abilities in collaboration, facilitation, and strategic and creative thinking. - Thorough understanding of complex legal issues. - In-depth research skills to draft accurate, complete and persuasive legal documents, such as pleadings, legal responses, affidavits, position statements and briefs. - Demonstrated commitment to the highest ethical standards. - Strong attention to detail. - Computer and technical skills, including proficiency in using standard productivity, communication, and video conferencing platforms (e.g., Microsoft Office Suite, Google Workspace, Zoom); ability to learn and effectively use new software systems and digital tools as required to meet evolving program needs. - Demonstrated ability to collaborate and work effectively with individuals and groups from a wide range of backgrounds, experiences, and perspectives. - Demonstrated commitment to fostering an inclusive and supportive environment that promotes collaboration and mutual respect among all members of the UC Berkeley community and its stakeholders. - Must demonstrate strong interpersonal skills, including the ability to engage with and understand individuals from varied academic, socioeconomic, cultural, disability, gender, and ethnic backgrounds. Education/Training: "Advanced degree in a related area, such as a Juris Doctor." Licenses/Certifications: "A member in good standing of the CA Bar Association" We could combine these into a single list under Requirements. Now Skills: maybe we could have a separate Skills section for computer/technical skills and interpersonal skills, but we already have them in Required Qualifications. To avoid thin sections, we could omit Skills section. Thus we have sections: About the role, Responsibilities, Requirements, Pay, Benefits, Schedule. Check if any other substantive content: Position Summary we included in About the role. Departmental Overview included. About Berkeley included. Application Review Date we dropped (minor metadata). How To Apply dropped. Other Information dropped. Conviction History Background dropped. Misconduct dropped. EEO dropped. Now we need to ensure we didn't miss any substantive info like "This position is covered by the collective bargaining agreement between UAW (United Auto Workers) and the University of California Regents for RP or SV." That's substantive about union coverage. Should we keep? It's not boilerplate? It's specific info about union coverage. It's not EEO/legal boilerplate? It's about collective bargaining. Might be considered substantive. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The collective bargaining agreement info is legal but not exactly boilerplate; it's specific to the position. Might be considered substantive. However it's about employment terms; could be considered part of Benefits or Schedule? Could be placed under Benefits maybe. But we already have Benefits section limited. Could add a sentence: "This position is covered by the collective bargaining agreement between UAW and the University of California Regents for RP or SV." That is substantive. Also "This is not a visa opportunity. This position does not include sponsorship of a new consular H-1B visa petition that would require payment of the $100,000 supplemental fee." That's also substantive about visa sponsorship. Might be considered substantive