Senior Administrative Assistant
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. We need to include sections only when posting has real, specific content. So we need to parse content.
We have:
- About Acadia Pharmaceuticals (company description). Could be "About the role"? Actually "About Acadia Pharmaceuticals" is about company, not role. But we can treat as "About the role"? The instruction says use headings like About the role, Responsibilities, etc. 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)." It suggests those are examples; we can use those headings if appropriate. We have content about company, position summary, primary responsibilities, education/experience/skills, physical requirements, compensation (salary range, bonus, equity), benefits (list), etc.
We should not include boilerplate like EEO, legal, etc. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.
Thus we need to keep:
- About Acadia Pharmaceuticals (company description) maybe as a paragraph under a heading like "About the Company"? But not in list. Could we use "About the role"? Not exactly. Maybe we can omit that heading and just put the company description as a
without heading? The instruction says use headings for sections; but we can have a
without heading if it's just intro? Probably okay. Better: Use heading "About the role" for position summary? Actually position summary is separate. Could treat "About Acadia Pharmaceuticals" as "About the Company" but not in examples. Might be okay to use a custom heading? 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 examples. Safer to stick to those. So we need to map content to those headings.
We have:
- Position Summary: could be under "About the role". That seems appropriate.
- Primary Responsibilities: under "Responsibilities".
- Education/Experience/Skills: could be under "Requirements" or "Qualifications" or "Skills". We have education/experience/skills list. Could split: Requirements (education/experience) and Skills (proficiency). But we can combine into one "Requirements" section.
- Physical Requirements: maybe not needed as separate heading unless we have specific content; we have physical requirements paragraph. Could include under "Requirements" or maybe we can omit because it's not in examples? But we have content; we could include under "Requirements" as part of that.
- Pay: we have salary range and mention of discretionary bonus and equity awards. So we can have a Pay section.
- Benefits: we have list of benefits for US-based employees. So Benefits section.
- Schedule: not mentioned; we have occasional travel, occasional overtime, but not schedule specifics. So we should not create Schedule section.
- Qualifications: maybe we can treat education/experience as Qualifications. But we already have Requirements. Might be redundant. Better to follow examples: we can have Requirements and Skills separate. Let's parse:
Education/Experience/Skills bullet list includes:
- High school diploma required; associate's or bachelor's degree preferred
- Minimum 4 years of administrative experience supporting senior-level leaders
- Experience supporting senior-level leaders and working with internal and external stakeholders
- Experience preparing presentations, reports, and business correspondence
- Ability to independently manage complex schedules, competing priorities, and multiple projects
- Experience handling confidential and sensitive business information
- Proficiency with Microsoft Office Suite, including Outlook, Word, Excel, and PowerPoint
- Experience coordinating meetings, events, and travel arrangements, including international travel
- Experience processing expense reports and managing business expenses through Concur or similar systems
- Strong organizational skills with exceptional attention to detail and follow-through
- Ability to work independently and collaboratively in a fast-paced environment
- Ability to travel occasionally as business needs require
These are a mix of requirements and skills. Could split: Requirements (education, experience) and Skills (proficiency, abilities). But we can just put all under "Requirements". The instruction says prefer a few substantive sections over many thin ones. So maybe we have sections: About the role (position summary), Responsibilities, Requirements, Pay, Benefits. That's five sections.
We also have Physical Requirements paragraph; we could incorporate into Requirements as a note.
We must not include boilerplate like EEO, legal, etc. So we cut everything after "What we offer US-based Employees:"? Actually we need to keep benefits list. The benefits list includes: Competitive base, bonus, new hire and ongoing equity packages; Medical, dental, and vision insurance; Employer-paid life, disability, business travel and EAP coverage; 401(k) Plan with a fully vested company match 1:1 up to 5%; Employee Stock Purchase Plan with a 2-year purchase price lock-in; 15+ vacation days; 13 -15 paid holidays, including office closure between December 24th and January 1st; 10 days of paid sick time; Paid parental leave benefit; Tuition assistance.
We should keep that as Benefits.
Pay section: Salary Range $30.87—$38.61 USD, plus mention of discretionary bonus and equity awards. We'll include that.
We must not include "Actual amounts will vary depending on experience, performance, and location." That's somewhat vague but still part of pay description; we can keep it as it's substantive? It says actual amounts will vary depending on experience, performance, and location. That's not filler like "commensurate with experience". It's okay.
We must not include "In addition to a competitive base salary, this position is also eligible for discretionary bonus and equity awards based on factors such as individual and organizational performance." That's part of pay.
Now we need to output HTML fragment only, no /, no markdown.
We'll structure:
About the role
Position summary text...
Responsibilities
- ... ...
Requirements
- ... ...
Pay
Salary range ...
Benefits
- ... ...
before the first heading. That's acceptable: we can have a
without heading. The instruction says use
for section headings (e.g. About the role, Responsibilities...). It doesn't say every paragraph must be under a heading. So we can have an introductory
for company description. Then we have Position Summary: "We are seeking a highly organized and proactive Senior Administrative Assistant to provide advanced support to senior leaders and their teams. This role manages complex administrative activities, coordinates critical business operations, and handles confidential information with professionalism and discretion. The ideal candidate thrives in a fast-paced environment, anticipates business needs, and contributes to the success of both leadership and cross-functional teams." We can put that under About the role heading. Now Responsibilities: list of bullet points from "Primary Responsibilities". Let's extract each line: - Provide administrative support to assigned leaders and business functions, including coverage for administrative team members as needed - Manage complex calendars, scheduling priorities, and meeting coordination for senior leaders - Coordinate domestic and international travel arrangements, including itineraries and logistics - Prepare reports, presentations, correspondence, and other business documents using information from multiple sources - Coordinate logistics for on-site and off-site meetings, conferences, leadership events, and company functions - Process and reconcile expense reports and corporate credit card transactions through Concur - Prepare and manage department-related documentation, including contracts, purchase orders, scopes of work, and service agreements - Track departmental expenses and support budget management activities - Partner with cross-functional teams to support projects, initiatives, and operational priorities - Perform other duties as assigned We'll put each as