Senior Executive Assistant

We need to output HTML fragment with sections: About the role? Actually we have "About Bedrock" description, then "Position Summary", "Essential Functions", "Position Requirements", "Position Qualifications", "Work Environment". Also maybe "Benefits", "Pay", "Schedule" only if present. The posting does not mention pay, benefits, schedule specifics (except work environment mentions in-person five-day-a-week). That could be schedule? It says "This position is in-person, five-day-a-week at our offices & properties. All team members are expected to work on site Monday through Friday during standard business hours." That's schedule info. So we can include a Schedule section with that. Benefits not mentioned. Pay not mentioned. So we include sections: About the role? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which headings to use based on content. We have "About Bedrock" which is about company; could be "About the role"? Actually "About the role" is generic; but we have "Position Summary". Could map to "About the role". Or we could keep "Position Summary" as heading? The instruction says use those example headings, but not strictly limited? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those headings where appropriate. So we need to map content: - About the role: could include Position Summary and maybe About Bedrock? But About Bedrock is company info, not role. Might be better to have "About the role" for Position Summary. And maybe a separate "About Bedrock" not needed? The instruction says include a section ONLY when posting has real, specific content for it. We have About Bedrock content; we could put it under a heading like "About Bedrock" but that's not in the list. However we could still use

with that heading? The examples are not exhaustive; they say e.g. So we can use other headings as needed. But better to follow the pattern: use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can also add other headings if needed, but they said prefer a few substantive sections over many thin ones. So we could combine About Bedrock into About the role? Might be odd. Perhaps we can have "About Bedrock" as a heading, but it's not in the list; but they didn't forbid other headings. They said use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That implies we should use those headings for those types of content; but we can also use other headings if needed. However to be safe, we can map: - About the role: Position Summary (maybe also include About Bedrock as context). But we could also have a separate "About Bedrock" heading; it's substantive. - Responsibilities: Essential Functions. - Requirements: Position Requirements. - Qualifications: Position Qualifications. - Skills: maybe part of Qualifications; but we could separate Skills if present. The posting includes skills within Qualifications; we could still have a Skills section pulling out skill bullet points. But to avoid thin sections, we could keep Qualifications and include skills there. - Benefits: none. - Pay: none. - Schedule: Work Environment includes schedule info; we can put schedule there. Thus we will output:

About the role

Position Summary: ... plus maybe About Bedrock? Could combine. Better: Provide About Bedrock as a paragraph under About the role? Might be confusing. Alternatively, we could have:

About Bedrock

...

About the role

Position Summary: ...

But the instruction says use those example headings; but not strictly required. I'd include About Bedrock as its own heading; it's substantive. Thus sections: - About Bedrock - About the role (Position Summary) - Responsibilities (Essential Functions) - Requirements (Position Requirements) - Qualifications (Position Qualifications) - Schedule (Work Environment) We'll output each as

heading followed by appropriate

or

• . We need to preserve all substantive information, not invent or summarize away detail. So we need to copy the text exactly? We can preserve meaning but not necessarily verbatim? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep the details, but we can rephrase slightly as long as we don't lose detail. Safer to copy the sentences. We'll need to convert lists to
  • . The Essential Functions is a list of bullet points (each starting with a capital verb). We'll turn each line into
  • . Similarly Position Requirements is a list? It's a paragraph with semicolons? Actually it's: "Minimum of 5 years of related executive administrative support experience required; prior support of a CEO, Chief Officer, C-suite executive, or similarly senior leader strongly preferred.Demonstrated experience managing highly confidential information, complex calendars, executive communications, meeting preparation, and stakeholder relationships.Advanced proficiency in Microsoft Outlook, Word, Excel, and PowerPoint required.Flexible schedule; occasional early morning, evening, or off-hours support may be required based on business needs." We can split into bullet points: each sentence separated by period. We'll make
  • for each. Position Qualifications includes sections: JOB BAND / PROBLEM-SOLVING, KNOWLEDGE, SKILLS, ABILITIES, KEY COMPETENCIES with sub-bullets. We'll need to preserve all detail. Could turn each bullet into
  • under appropriate headings? But we only have one heading for Qualifications; inside we can have
    • for each bullet. However there are subheadings like JOB BAND / PROBLEM-SOLVING: etc. We could keep those as bold text inside
    • or as . Since we cannot use markdown, we can use . We'll output like:
    • JOB BAND / PROBLEM-SOLVING: Exercises independent judgment ...
    Similarly for others. Work Environment: includes schedule info and physical demands. We'll put under Schedule heading? Actually we have Schedule heading for schedule info; but Work Environment also includes physical demands. Could combine under Schedule? Or we could have a Work Environment heading. The instruction says use headings like Schedule, Benefits, Pay. But we can also have Work Environment if needed. To avoid many thin sections, we could put schedule info under Schedule and physical demands under maybe a separate "Work Environment" heading? But that adds another section. Could combine both under Schedule heading? The schedule info is about in-person five-day-a-week; physical demands are not schedule. Might be better to have a "Work Environment" heading for that content, and schedule info under Schedule heading. That's two sections. But we already have many sections; maybe we can combine schedule and physical demands under Work Environment heading, and not have separate Schedule heading. The instruction says include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we need to decide if schedule content is present: yes, "This position is in-person, five-day-a-week at our offices & properties. All team members are expected to work on site Monday through Friday during standard business hours." That's specific schedule info. So we should have a Schedule section with that. Physical demands: "Prolonged periods of sitting and computer use; occasional movement between buildings; ability to lift up to 15 lbs. occasionally." That's work environment details. Could go under Work Environment heading. But we could also include them under Schedule? Not ideal. We could have Schedule section with the schedule sentences, and Work Environment section with physical demands. That's two sections. But we already have many sections; maybe we can merge physical demands into Schedule section as additional detail; still schedule heading but includes both schedule and physical demands. That's okay. Thus Schedule heading will contain both schedule and physical demands. Now we need to output only HTML fragment, no /, no markdown fences. Let's craft. We'll start with:

    About Bedrock

    Bedrock is an award-winning real estate developer focused on comprehensive city building initiatives in Detroit and Cleveland. Its work includes creating iconic cityscapes, rehabilitating historic properties, and making space for the community—all with the philosophy to operate for more than profit. Since 2011, Bedrock has invested and committed more than $7.5 billion to develop and restore more than 140 properties, totaling over 21 million square feet of office, retail, residential, hospitality, industrial, data centers and parking. In 2024, Bedrock was named one of the world’s Most Innovative Companies by Fast Company. For additional information about Bedrock, please visit bedrockdetroit.com or connect with us on Facebook, Instagram, LinkedIn and X.

    About the role

    The Senior Executive Assistant position provides high-level administrative, operational, and relationship-management support to the Chief Executive Officer. This role serves as a trusted representative of the CEO and the organization, helping manage executive priorities, communications, scheduling, meeting preparation, stakeholder requests, and day-to-day administrative execution. Success in this position requires strong judgment, discretion, confidentiality, responsiveness, and the ability to anticipate needs in a dynamic, fast-paced environment.

    Responsibilities

    • Serves as the primary administrative partner to the CEO, anticipating needs, managing competing priorities, and helping ensure the CEO is prepared for meetings, commitments, and follow-up actions.
    • Owns complex calendar management, proactively balancing competing priorities, protecting focused work time, and ensuring alignment with organizational objectives.
    • Reviews, prioritizes, and manages inbox communications, drafting responses on the CEO's behalf and routing items to appropriate team members for action while preserving appropriate visibility into communications.
    • Intakes and organizes a high volume of internal and external communications, including email, voicemail, and meeting requests; identify priority communications and prepares and communicates to the CEO as needed.
    • Builds and maintains strong relationships with internal and external stakeholders, serving as a trusted representative of both the organization and the CEO through professionalism, discretion, and sound judgment.
    • Coordinates executive-level requests, meetings, tours, and stakeholder interactions, including facilitating matters that may not directly involve the CEO and redirecting stakeholders to the appropriate leaders when needed.
    • Coordinates logistics and prepares materials for meetings, calls, events, executive visits & tours, and executive engagements, including agendas, briefing materials, presentations, action items, and follow-up documentation.
    • Drafts, edits, and formats correspondence, presentations, and other materials with precision, professionalism, and attention to audience, tone, and confidentiality.
    • Develops, improves, and maintains administrative processes that support efficiency, organization, confidentiality, and smooth day-to-day execution for the CEO and Office of the CEO.
    • Prepares business and personal travel arrangements, including itineraries, air and hotel accommodations, transportation, and related logistics.
    • Supports expense management, purchase orders, invoices, corporate card statements, and related administrative processes in partnership with Finance and other internal teams.
    • Handles highly confidential and sensitive information with sound judgment and appropriate discretion, including matters delegated by the CEO or Office of the CEO.
    • Supports special projects and other administrative or operational priorities as needed.
    • All other duties as assigned.

    Requirements

    • Minimum of 5 years of related executive administrative support experience required; prior support of a CEO, Chief Officer, C