C-Suite Personal Assistant

We need to output 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. Remove boilerplate: EEO, etc. Must preserve all substantive info. Let's parse the posting. Content: - Intro paragraph: "We’re building technology to help solve cases and advance justice. Othram gives law enforcement agencies access to advanced DNA testing and forensic tools that can help identify unknown individuals, generate leads, and solve difficult cases. Our team brings together forensic science, DNA analysis, genetic genealogy, software, and investigative expertise in one connected system. Othram works with federal partners, agencies in nearly every U.S. state, and investigators around the world. Our technology connects with the world’s largest DNA database of people who have consented to forensic genetic genealogy matching." That's about company, not role. Might be considered "About the role"? Actually there is a section "About This Role". So we can put that intro as part of About the role? The "About This Role" heading is present. The text after that: "Othram is seeking a Personal Assistant to support C-suite leaders by managing administrative, logistical, and personal responsibilities. This hands-on role requires substantial daily local driving and ownership of routine and unexpected requests. This salaried position requires a full-time commitment, typically Monday through Friday, 8 a.m. to 5 p.m., with occasional early mornings, evenings, or weekends based on executives’ needs." That's about the role. So we can put that under

About the role

with paragraphs. Then "What you get to do" list: bullet points. Those are responsibilities. So we can put under

Responsibilities

with

• each. Then "What we are looking for": bullet points. Those are requirements/qualifications/skills. We need to decide sections. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills). We can split into Requirements, Qualifications, Skills as appropriate. The bullet list includes: Prior experience supporting senior executives..., A valid driver’s license..., Ability to pass a background check., Strong organizational skills..., Sound judgment..., Excellent written and verbal communication..., Ability to manage multiple, changing priorities... We could categorize: Requirements: Prior experience..., valid driver's license..., ability to pass background check. Qualifications: Strong organizational skills..., attention to detail..., reliable follow-through. Skills: Sound judgment..., initiative..., resourcefulness..., excellent communication..., ability to manage multiple priorities... But we need to avoid thin sections. Perhaps combine Requirements and Qualifications into one section? But we have to follow instruction: Use headings for section headings (list). It says "Prefer a few substantive sections over many thin ones." So we could combine into one "Requirements and Qualifications" but heading must be exactly one of the listed? It 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 are typical. Safer to use those headings only if we have content. We could put all bullet points under

  Requirements

  and maybe also

  Skills

  if we split. But we need to avoid thin sections. The bullet list is fairly long; splitting may still be substantive. Let's decide: Use Requirements for experience, license, background check. Use Skills for organizational, judgment, communication, managing priorities. Qualifications maybe not needed. But we need to include Qualifications heading only if we have specific content. Could we treat "Strong organizational skills, attention to detail, and reliable follow-through" as qualifications? Might be okay. Alternatively, we could combine Requirements and Qualifications into one heading "Requirements". But then we lose Qualifications heading. The instruction says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we must use all; just examples. So we can choose which to include. Thus we can have sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule? We need to see if Pay and Schedule have content. Pay: The posting mentions "Compensation And Benefits Competitive salary and benefits package". That's vague but mentions competitive salary and benefits package. It does not give specific numbers. The instruction says: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Here they state "Competitive salary and benefits package". That's somewhat vague but still states that there is a competitive salary and benefits package. Is that considered filler? It's not a specific number but it's a statement that they offer competitive salary and benefits. The instruction says avoid filler like "commensurate with experience", "not specified", etc. "Competitive salary and benefits package" is somewhat generic but still states they have a competitive salary and benefits. I'd argue it's enough to include a Benefits section (since they mention benefits). Pay maybe not specific enough; but they mention salary as part of compensation. Could we include Pay section with that statement? It might be considered filler. Safer to include Benefits section (since they mention benefits package) and maybe not Pay. Schedule: they mention typical Monday-Friday 8-5 with occasional early mornings, evenings, weekends. That's specific enough for Schedule. So we can include Schedule. Benefits: they list "Competitive salary and benefits packageFlexible, unlimited PTOOpportunities for professional growth within a mission-focused organizationWork in a collaborative and innovative environment at the forefront of science and technology". That's a run-on sentence but includes benefits: flexible unlimited PTO, professional growth opportunities, collaborative innovative environment. So we can include Benefits. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Schedule. Possibly also Qualifications? We could incorporate qualifications into Requirements or Skills. Let's decide to have Requirements (experience, license, background check) and Skills (organizational, judgment, communication, managing priorities). We'll omit Qualifications heading. Now we need to format. We must not include boilerplate: EEO statement, equal opportunity, etc. Also remove "Build what matters..." paragraph? That's more marketing but still substantive about mission. Could be part of About the role? It's after compensation. It's about mission. Might be considered part of company description. Could keep as part of About the role? But we already have About the role covering role description. The "Build what matters..." is more about company culture. Could be considered part of Benefits? Not exactly. Might be considered extra but still substantive. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep it. Where to place? Could be its own section like "About the company" but not in allowed headings. Could incorporate into About the role as extra paragraph. Or maybe we can add a section "About Othram" but not in list. Better to keep within About the role as additional paragraph. Also "Othram is based in The Woodlands, TX. Unless otherwise stated, we prioritize candidates who can commit to being in our office daily." That's location and work expectation. Could be part of About the role or maybe Schedule? It's about location and in-office expectation. Could be a separate section like "Location" but not in list. Could add to About the role. Thus About the role will contain multiple paragraphs: company intro, role description, location, work expectation, mission statement. Now we need to output HTML fragment only, no /, no markdown. Let's craft.

  About the role

  We’re building technology to help solve cases and advance justice. Othram gives law enforcement agencies access to advanced DNA testing and forensic tools that can help identify unknown individuals, generate leads, and solve difficult cases. Our team brings together forensic science, DNA analysis, genetic genealogy, software, and investigative expertise in one connected system. Othram works with federal partners, agencies in nearly every U.S. state, and investigators around the world. Our technology connects with the world’s largest DNA database of people who have consented to forensic genetic genealogy matching.

  Othram is seeking a Personal Assistant to support C-suite leaders by managing administrative, logistical, and personal responsibilities. This hands-on role requires substantial daily local driving and ownership of routine and unexpected requests. This salaried position requires a full-time commitment, typically Monday through Friday, 8 a.m. to 5 p.m., with occasional early mornings, evenings, or weekends based on executives’ needs.

  Othram is based in The Woodlands, TX. Unless otherwise stated, we prioritize candidates who can commit to being in our office daily.

  Build what matters. At Othram, you’ll work with talented people using science and technology to answer difficult questions and advance justice. The work is challenging, meaningful, and built to make a lasting impact. If you’re curious, driven, and motivated by an important mission, you may find your place here.

  Then Responsibilities:

  Responsibilities

  • Manage calendars, appointments, meetings, reservations, and professional or personal events.
  • Drive daily throughout the local area to complete errands, purchases, deliveries, returns, and other time-sensitive tasks.
  • Arrange flights, lodging, ground transportation, and itineraries, including last-minute changes.
  • Anticipate needs, deadlines, scheduling conflicts, and logistical challenges; track commitments and follow-up through completion.
  • Prioritize requests, escalate urgent matters, and resolve routine matters independently when appropriate.
  • Coordinate with employees, vendors, service providers, schools, and external contacts on behalf of the executives.
  • Maintain organized records, receipts, contacts, and other important documentation.
  • Support special projects and tasks beyond traditional administrative duties.
  • Streamline routines and improve organization to reduce demands on executive time.
  • Protect confidential company, family, and personal information with the highest level of discretion.
  Then Requirements:

  Requirements

  • Prior experience supporting senior executives, entrepreneurs, or other high-demand individuals.
  • A valid driver’s license, impeccable driving record, and reliable transportation.
  • Ability to pass a background check.
  Then Skills:

  Skills

  • Strong organizational skills, attention to detail, and reliable follow-through.
  • Sound judgment, initiative, and resourcefulness to anticipate needs, persist through unfamiliar or time-sensitive requests, and determine when executive involvement is needed.
  • Excellent written and verbal communication skills and professionalism with individuals at all levels.
  • Ability to manage multiple, changing priorities in a fast-paced environment with accuracy and composure.
  Then Benefits:

  Benefits

  • Competitive salary and benefits package
  • Flexible, unlimited PTO
  • Opportunities for professional growth within a mission‑focused organization
  • Work in a collaborative and innovative environment at the forefront of science and technology
  Then Schedule:

  Schedule

  Typically Monday through Friday, 8 a.m. to 5 p.m., with occasional early mornings, evenings, or weekends based on executives’ needs.

  Check we didn't repeat job title. Good. We removed EEO etc. We kept all substantive info. Make sure no extra whitespace issues. Output only HTML. Let's produce