Part Time Evening Office Administrator
Ember Health · New York, NY · 1 mo ago
On-siteAdministrative$35/hrPart-time
We need to output HTML fragment with sections: About the Company, About the position? Actually we should not repeat job title as heading. Use headings for sections: About the role? The posting has "About the Company", "About the position", "Responsibilities", "Attributes", "Experience", "Why the Role is Compelling", "Compensation Package and Benefits". According to rules: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map headings accordingly. We should include sections only if posting has real specific content. We have content for About the Company, About the position (maybe treat as About the role?), Responsibilities, Attributes (maybe Skills?), Experience, Why the Role is Compelling (maybe Benefits?), Compensation Package and Benefits (Pay and Benefits). We should not include sections like Requirements, Qualifications if not present. We have "Experience" which could be considered Requirements/Qualifications. We'll map: About the Company ->
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map headings accordingly. We should include sections only if posting has real specific content. We have content for About the Company, About the position (maybe treat as About the role?), Responsibilities, Attributes (maybe Skills?), Experience, Why the Role is Compelling (maybe Benefits?), Compensation Package and Benefits (Pay and Benefits). We should not include sections like Requirements, Qualifications if not present. We have "Experience" which could be considered Requirements/Qualifications. We'll map: About the Company -> About the Company
. About the position -> maybe About the role
. Responsibilities -> Responsibilities
. Attributes -> Skills
(since attributes are skills/qualities). Experience -> Requirements
(or Qualifications). Why the Role is Compelling -> maybe Benefits
? But it's more about role compelling; could be considered Benefits? However we have separate Compensation Package and Benefits section. So we could treat Why the Role is Compelling as a Benefits
(non-monetary benefits). Compensation Package and Benefits -> we need Pay and maybe Benefits. Since we have both pay and benefits (paid sick time). According to rules, we should not create Pay/Schedule/Benefits sections unless posting actually states them. It does state compensation $35 per hour and includes dedicated paid sick time, not eligible for other benefits. So we can have a Pay
with the $35 per hour statement, and maybe a Benefits
with paid sick time note. But we already used Benefits for Why the Role is Compelling; maybe better to rename that section to "Why the Role is Compelling" as a custom heading? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive list; we can use those headings. It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should stick to those headings; we shouldn't invent other headings like "Why the Role is Compelling". So we need to map content to those allowed headings. If content doesn't fit exactly, we may need to omit heading if no specific content. But we must preserve ALL substantive information; we cannot omit info. So we need to fit the info into allowed headings. Let's see:
- About the Company: fits About the role? Not exactly. But we could use About the role for company description? Actually About the role is about the position. The company description could go under About the role? Might be okay but could be misrepresent. However we could also not have a heading for company and just put it in a
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should stick to those headings; we shouldn't invent other headings like "Why the Role is Compelling". So we need to map content to those allowed headings. If content doesn't fit exactly, we may need to omit heading if no specific content. But we must preserve ALL substantive information; we cannot omit info. So we need to fit the info into allowed headings. Let's see: - About the Company: fits About the role? Not exactly. But we could use About the role for company description? Actually About the role is about the position. The company description could go under About the role? Might be okay but could be misrepresent. However we could also not have a heading for company and just put it in a
before any headings? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use for section headings (e.g. those). Likely they expect we use those headings where appropriate. We could still use About the Company as a heading if we think it's acceptable; but they gave examples, not exclusive. Safer to follow examples: use those headings. So we need to map:
About the Company -> maybe we can put under About the role? But About the role is about the position, not company. However we could treat "About the role" as heading for both company and position? Could combine.
Alternatively we could omit About the Company heading and just put that content in a
before first heading. The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we must use a heading for every section; we can have paragraphs without headings. So we could start with a
containing About the Company. Then
About the role
for About the position. ThenResponsibilities
. ThenSkills
for Attributes. ThenRequirements
for Experience. ThenBenefits
for Why the Role is Compelling (non-monetary benefits). ThenPay
for compensation. Then maybeBenefits
again? Can't duplicate heading? Could combine Pay and Benefits under one Benefits heading? But we have separate Pay and Benefits headings allowed. We could havePay
for $35/hour, andBenefits
for paid sick time and other non-monetary benefits (Why the Role is Compelling). That would be two sections: Pay and Benefits. But we already used Benefits for Why the Role is Compelling; we could rename that to Benefits and include both the non-monetary and paid sick time. Then Pay separate. Let's do: -About the Company paragraph.
-About the role
with About the position paragraph. -Responsibilities
with- ... (list items)
-
Skills
with- ... (attributes)
-
Requirements
with- ... (experience)
-
Pay
with$35 per hour...
-Benefits
with- ... (paid sick time, plus why role compelling points)
We need to ensure we don't include schedule heading because not specified (they gave hours but schedule is described: "Candidates must be available to work between the hours of 3PM and 9PM two to four consistent days per week, averaging approximately 12-24 hours per week." That's schedule info. According to rules, we should include Schedule section only if posting actually states them. It does state schedule. So we should add a
Schedule
with that info. Good. Thus headings: About the role, Responsibilities, Skills, Requirements, Pay, Benefits, Schedule. Also we have About the Company as a paragraph before any heading. Check for duplication: Ensure we don't repeat job title as heading. We aren't. Now we need to extract content precisely. About the Company paragraph: "Ember Health is a fast growing organization administering IV ketamine treatment to people seeking relief from depression in safe, medically monitored clinical environments. At Ember, our treatments have relieved depressive symptoms in 85% of the people we serve. We are building the gold standard of care in this cutting edge field by leading with evidence, designing for optimal patient experience and outcomes, and partnering with a large ecosystem of mental health providers. We strive to live our values by operating with the highest degree of integrity, compassion, and excellence. As this requires distinctive talent, we are building a team slowly and carefully. Each member plays an integral part of creating a truly transformative solution in the field of mental health. To learn more about ketamine for depression, you may visit our frequently asked questions and reference external resources we've organized on the topic." About the position paragraph: "We are looking for a dynamic professional administrator, distinguished by their compassion, commitment, and professional integrity. This role will include office management and administration, as well as patient and provider communications. This is a non-clinical, part time role for our locations in the Upper East Side, Chelsea and Brooklyn Heights in New York City. Candidates must be available to work between the hours of 3PM and 9PM two to four consistent days per week, averaging approximately 12-24 hours per week." Note: The schedule sentence is inside About the position paragraph; we might move schedule to its own section and remove from About the role paragraph to avoid duplication. But we must preserve all info; we can keep schedule info in Schedule section and maybe keep a brief mention in About the role? To avoid duplication, we could keep About the role paragraph without the schedule sentence, and put schedule in its own section. However the instruction says preserve ALL substantive information; we can rephrase but not omit. So we can split: About the role paragraph excludes schedule sentence; schedule sentence goes to Schedule section. That's fine as long as we keep the info. Thus About the role paragraph: "We are looking for a dynamic professional administrator, distinguished by their compassion, commitment, and professional integrity. This role will include office management and administration, as well as patient and provider communications. This is a non-clinical, part time role for our locations in the Upper East Side, Chelsea and Brooklyn Heights in New York City." Now Responsibilities: list items: - Maintain a professional, warm, welcoming office environment - Greet all patients and guests, manage check-ins and payment - Answer all inbound calls to the Ember Health office - Manage patient bookings and appointments - Process new patient information - Collaborate with the daytime care team and other clinics to ensure a seamless patient experience - Respond to select patient communications - Input and update data for client relationship management database - Contribute to scoped projects for enterprise wide initiatives - Schedule meetings on behalf of the clinical team We need to ensure we capture all. Attributes (Skills): list items: - You are warm, compassionate, and empathic. - You have a calming demeanor and a way of building trusting, caring relationships with ease. - You are a skilled communicator. You're both a great listener and an effective speaker and writer. - You treat sensitive information with respect and discretion. - You are mission driven. You are motivated to help change mental health paradigms and serve as an excellent ambassador for a cause you believe in. - You are systematic. You derive pleasure from being highly organized, creating order, and checking things off your list. - You are detail-oriented. You take pride in maintaining a "picture ready" office space and immaculate data entry. - You are thoughtful. You can anticipate the needs of your clinical team and patients, and feel committed to proactively creating a supportive environment for all. - You have great professional integrity. You take ownership over your work, ask for help when you need it, and are committed to your own growth and development. - You are reliable. You consistently show up for work on time and can be counted on by your team. We could combine some sentences but keep as list items. Experience (Requirements): list items: - Prior responsibilities in office administration - Prior experience working in a healthcare setting preferred - Experience or genuine interest in mental health desired Now Pay: "$35 per hour and includes dedicated paid sick time. This position is not eligible for other benefits such as paid vacation time or employer sponsored healthcare coverage." But we also have Benefits section for non-monetary benefits: "Why the Role is Compelling" paragraph: "As the Part Time Evening Office Administrator for Ember Health, you will play an integral role in creating a comforting and professional environment that has a profound impact on people's mental health and wellness. You will help provide expanded access to this crucial treatment, while maintaining a schedule that allows you to protect your daytime hours for other pursuits. You will be supported by a talented clinical team, and be part of a growing, multi-clinic operation realizing
- ... (paid sick time, plus why role compelling points)
We need to ensure we don't include schedule heading because not specified (they gave hours but schedule is described: "Candidates must be available to work between the hours of 3PM and 9PM two to four consistent days per week, averaging approximately 12-24 hours per week." That's schedule info. According to rules, we should include Schedule section only if posting actually states them. It does state schedule. So we should add a
- ... (experience)
-
- ... (attributes)
-