Clinical Support Specialist - Medical Assistant (Temp-to-Hire)

We need to output HTML fragment with sections: headings using

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. Must include only sections with real specific content. Must not include filler like "commensurate with experience". Must preserve all substantive info. Remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines, application instructions. We need to parse the posting. Key sections: - About the role: description of role, mission, etc. Could be first paragraph after "Why is Arine a Great Place to Work?" Actually that is about company. The role description starts after "The Role". So we can have About the role: maybe combine mission and role description. - Responsibilities: list of duties (What You’ll Be Doing). Should be

• . - Requirements: maybe "Who You Are And What You Bring" includes qualifications, skills, etc. Could split into Qualifications and Skills. But we can have Requirements section for mandatory qualifications, and Skills for nice-to-haves? The instruction: prefer few substantive sections over many thin ones. So we can combine qualifications and skills into one Requirements section? But they ask to use headings like Qualifications, Skills, Benefits, Pay, Schedule if content exists. We need to decide based on content. We have: - Qualifications: Bachelor's degree in Health Sciences or related field preferred. Healthcare certification preferred (e.g., Certified Pharmacy Technician, Certified Medical Assistant, Behavioral Health Technician). Candidates with equivalent medical, healthcare, call center, customer service, or patient-facing experience are encouraged to apply. - Skills: Ability to prioritize effectively and work in a fast-paced environment; Knowledge of basic medical terminology and medication names (brand and generic); Excellent written and oral communication skills; Strong interpersonal and customer service skills, with ability to build rapport, demonstrate empathy, remain patient-focused during high-volume phone interactions; Demonstrated reliability, accountability, and follow-through; High attention to detail with strong commitment to documentation accuracy; Comfort working in a metrics-driven environment where outcomes and quality are tracked; Strong computer skills, including proficiency in Google Workspace and Mac (Apple) environment, with comfort using collaboration and contact-center tools such as Slack and Five9, navigating multiple browser-based systems simultaneously, utilizing keyboard shortcuts, maintaining a high typing speed (WPM), and performing basic technical troubleshooting to stay productive in a phone-based environment; Comfort learning and using new technologies, including clinical software platforms; A team player mindset with ability to work independently; Openness to coaching, feedback, and continuous learning; Ability to work 40 hours/week (within company operating hours of Monday-Friday, 6AM-6PM Pacific Time, with up to two rotating Saturday shifts/month). - Nice-to-Haves: Experience with other electronic medical records; Experience in an ambulatory care setting, including taking medication histories; Experience working in a high-volume, metrics-based healthcare call center or similar patient-facing environment. - Remote Work Requirements: An established private work area that ensures information privacy; Reliable internet capable of low latency with ability to carry video and voice calls without breaking up; This role is remote, but you will be required to come to on-site meetings multiple times per year. This may be during the interview process, onboarding, and for team meetings. - Perks: Joining Arine offers you a dynamic role and the opportunity to contribute to the company's growth and shape its future. You'll have unparalleled learning and growth prospects, collaborating closely with experienced Clinicians, Engineers, Software Architects, and Digital Health Entrepreneurs. This position is temp-to-hire for an expected duration of 6 months, with the possibility of extension or conversion to a permanent role based on performance and business needs. Throughout the temporary period, you will receive full benefits starting from day one. The posted range represents the expected hourly rate for this position and does not include any other potential components of the compensation package, benefits, and perks. Ultimately, the final pay decision will consider factors such as your experience, job level, location, and other relevant job-related criteria. The hourly pay rate for this position is: $20-22/hour. - Seasonality & Schedule: description of seasonal business cycle, peak season May through early December, holiday shutdown 2-3 weeks late Dec-early Jan, etc. - Benefits: mention full benefits starting day one (health, etc). Not detailed but we have mention of full benefits. Could include Benefits section. - Pay: hourly pay rate $20-22/hour. - Schedule: mention 40 hours/week, Monday-Friday 6AM-6PM PT, up to two rotating Saturday shifts/month; also seasonal schedule details. We need to avoid filler like "commensurate with experience". Not present. We must not include boilerplate like EEO, equal opportunity, etc. Also remove "Information Security Roles And Responsibilities" maybe? That is a section but it's about security training; could be considered boilerplate? It's specific to Arine but maybe still considered boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Information Security Roles And Responsibilities" is not exactly EEO but could be considered policy; but it's substantive? It's about training. Might be considered boilerplate but it's specific to Arine. However it's not about the role; it's a general policy. Probably we should remove it as it's not directly about the job. Also "Check our website at https://www.arine.io." is promotional, maybe remove. Also "This is a unique opportunity to join a growing start-up..." is fluff but maybe keep? It's about company; could be considered boilerplate? Might be okay to keep as part of About the role? But we can keep a brief description. We need to preserve ALL substantive information; do not invent or summarize away detail. So we must keep details like the mission, the problem stats, etc. Those are substantive about company. We can include them in About the role or maybe a separate "About Arine" but not in headings list. Since headings list includes About the role, we can put company mission there. We must not repeat job title as heading. No job title given explicitly; it's likely "Clinical Care Specialist" or similar but not in text. So fine. We must not put Job ID/requisition numbers as headings; none present. We must output ONLY HTML fragment, no /, no markdown fences. Thus produce something like:

  About the role

  ... description ...

  Responsibilities

  • ... each duty ...

  Qualifications

  • ... each qualification ...

  Skills

  • ... each skill ...

  Benefits

  ... full benefits starting day one ...

  Pay

  The hourly pay rate for this position is: $20-22/hour.

  Schedule

  ... schedule details ...

  We might also include a section for Remote Work Requirements? Not in headings list; but we could incorporate into Schedule or maybe as part of Requirements? The instruction says use headings for those specific categories; if not present, we should not create extra headings. So we can embed remote work requirements within Schedule or maybe as a paragraph under Schedule? But better to include under Schedule? Actually schedule is about hours; remote work requirements are separate. Could we add a heading "Remote Work Requirements"? Not in the allowed list; but the instruction says use headings 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)." It implies those are the expected headings; we should stick to them. So we should not create extra headings like Remote Work Requirements. We can incorporate that info into Schedule or maybe under Requirements? Probably under Schedule we can mention remote work expectations. Similarly, Nice-to-Haves could be part of Skills or Qualifications? Could add under Skills as "Nice-to-haves". But we could also add a separate "Skills" heading and include both required and nice-to-haves? The instruction: prefer a few substantive sections over many thin ones. So we could combine Qualifications and Skills into one "Requirements" section. But they gave separate headings for Qualifications and Skills; we can use both if we have content. Let's decide to have Qualifications (required) and Skills (required + nice-to-haves). But we might duplicate. Better: Use Qualifications for degree/certification/experience. Use Skills for abilities, technical, soft skills, schedule, remote work. Then Benefits, Pay, Schedule separate. But schedule is also part of Skills? Could be separate. Let's outline: About the role: paragraph describing Arine mission, role purpose. Responsibilities: bullet list of duties (What You’ll Be Doing). Qualifications: bullet list of required qualifications (degree, certification, equivalent experience). Skills: bullet list of required skills (communication, medical terminology, reliability, attention to detail, metrics-driven, computer skills, team player, openness to coaching, ability to work 40h/week, remote work requirements, nice-to-haves maybe). Could separate nice-to-haves as a sublist? But we can keep them as bullet points. Benefits: paragraph about full benefits starting day one, learning growth prospects, temp-to-hire etc. Pay: paragraph about hourly rate $20-22/hour. Schedule: paragraph about 40 hours/week Monday-Friday 6AM-6PM PT, up to two rotating Saturday shifts/month, seasonal business cycle, peak season May-early Dec, holiday shutdown late Dec-early Jan, etc. We must ensure we don't include filler like "commensurate with experience". Not present. Now we need to extract exact phrasing where possible, but we can rephrase slightly as long as we preserve all substantive information. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should not omit details; we can rephrase but must keep all info. Safer to copy the sentences verbatim where possible. Let's gather content. About the role: Could combine first paragraphs: "Pronunciation: a:rine [uh-reen]. Noun: Arine is a name of Basque origin meaning "light." Arine illuminates the possibilities with medication management to deliver comprehensive economic and health outcomes. Based in San Francisco, Arine is a rapidly growing healthcare technology and clinical services company with a mission to ensure individuals receive the safest and most effective treatments for their unique and evolving healthcare needs. Frequently, medications cause more harm than good. Incorrect drugs and doses costs the US healthcare system over $528 billion in waste, avoidable harm, and hospitalizations each year. Arine is redefining what excellent healthcare looks like by solving these issues through our software platform (SaaS). We combine cutting edge data science, machine learning, AI, and deep clinical expertise to introduce a patient-centric view to medication management, and develop and deliver personalized care plans on a massive scale for patients and their care teams. Arine is committed to improving the lives and health of complex patients that have an outsized impact on healthcare costs and have traditionally been difficult to identify and address. These patients face numerous challenges including complicated prescribing issues across multiple medications and providers, medication challenges with many chronic diseases, and patient issues with access to care. Backed by leading healthcare investors and collaborating with top healthcare organizations and providers, we deliver recommendations and facilitate clinical interventions that lead to significant, measurable health improvements for patients and cost savings for customers." Then "Why is Arine a Great Place to Work?" bullet points: Outstanding Team and Culture..., Making a Proven Difference..., Market Opportunity..., Momentum That Matters... We could include that