Bilingual Clinical Pharmacist (Temp-to-Hire)

We need to output HTML fragment with sections: headings using

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. Key sections: - About the role: description of role, mission, etc. The posting starts with "Pronunciation..." then description of company, then "Why is Arine a Great Place to Work?" then "The Role". Probably "About the role" could be the paragraph after "The Role". But we need to decide. We have sections: "The Role" (intro), "What You’ll Be Doing" (responsibilities), "Who You Are And What You Bring" (requirements/qualifications/skills), "Nice-to-Haves", "Remote Work Requirements", "Perks", "The posted range represents the expected hourly rate..." (Pay), "Seasonality & Schedule" (Schedule). Also "Benefits" maybe from "Throughout the temporary period, you will receive full benefits starting from day one." Also "Perks" includes learning and growth prospects, etc. We need to include sections only if they have real specific content. Avoid filler like "commensurate with experience". Not present. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not include markdown fences. We need to output only HTML fragment. Let's extract content. First, company description: "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." That's about the company. Could be "About the role"? Actually "About the role" is more about the job. But we could treat this as "About the company". However the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are examples; we could also use other headings if needed? It says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect those headings only. But we can also include other headings if needed? Safer to stick to those headings. However we have content that doesn't fit exactly those categories: company overview could go under "About the role"? Might be okay to put company description under "About the role". Or we could omit it? But we must preserve ALL substantive information. So we need to include company description somewhere. Could put under "About the role" heading. Then "Why is Arine a Great Place to Work?" could be part of "About the role" or maybe "Benefits"? But it's more about culture. Could be part of "About the role" as well. Then "The Role" intro: "Are you passionate about improving patients' lives? Join our Clinical Care team at Arine! As a Bilingual Clinical Pharmacist, you will utilize Arine's software platform to optimize patient outcomes, enhance patient care, and efficiently deliver our core clinical services. You will have a direct impact on the patients you serve while staying continuously up-to-date on developments in the fast-moving drug field, including emerging patterns, treatment guidelines, and best practices. Under the supervision of a Pharmacist Lead, you will provide expert-level medication therapy consultations to patients and providers, complete medication reviews and adherence counseling, collaborate with the Engineering team and leadership to improve Arine's software platform, and help guide the Clinical Support team. This is a patient-facing, phone-based role where you will spend a significant portion of your day engaging with patients, providers, and pharmacies. We are seeking a patient-centric, compassionate clinician who is self-motivated, receptive to coaching and feedback, and thrives on helping others navigate complex medication challenges. Success in this role requires strong clinical judgment, attention to detail in documentation, comfort working with technology, and the ability to adapt in a fast-paced environment. You will be expected to manage your workload independently while demonstrating accountability and reliability in your work. Arine fosters a metrics and feedback-driven environment where ongoing coaching is used to support individual growth, performance improvement, and development." That could be part of "About the role" as well. Then "What You’ll Be Doing" list of duties: bullet points. Then "Who You Are And What You Bring" list of qualifications. Then "Nice-to-Haves" list. Then "Remote Work Requirements" list. Then "Perks" paragraph. Then Pay: "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: $57-65/hour." Then "Seasonality & Schedule": description. Also "Benefits": "Throughout the temporary period, you will receive full benefits starting from day one." Also maybe "Perks" includes learning and growth prospects. We need to decide which headings to use. We have: - About the role (could contain company overview, why great place to work, role intro) - Responsibilities (What You’ll Be Doing) - Requirements (maybe combine Who You Are And What You Bring + Nice-to-Haves? But Nice-to-Haves are optional; we could still include under Requirements or separate? The instruction says use headings like Requirements, Qualifications, Skills. Could split: Requirements (mandatory), Qualifications (maybe education/licensure), Skills (abilities). But we can also just put all under Requirements if we want fewer sections. However they said prefer a few substantive sections over many thin ones. So we could combine into Requirements (including qualifications and skills). But we need to preserve all info; we can still list them. We could have sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Also maybe Remote Work Requirements could be part of Requirements or separate? Could be under Requirements as well. But we need to avoid headings with filler. All sections have content. Let's plan:

  About the role

  Company description + why great place to work + role intro.

  Responsibilities

  • ... each duty from "What You’ll Be Doing"

  Requirements

  • ... mandatory qualifications from "Who You Are And What You Bring"
  Maybe also include Nice-to-Haves as a separate subheading? But we could add another heading "Preferred Qualifications" but not in list. Could we add a heading "Preferred Qualifications"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings but says "e.g." So we could add "Preferred Qualifications" as a heading if we want. But to keep few sections, we could include Nice-to-Haves under Requirements as well, maybe label them as "Nice-to-haves (preferred)" within the list items. But we need to preserve the distinction? Not required; we just need to preserve all substantive info. So we can list them all under Requirements, maybe separate with a note. Alternatively we could have separate sections: Requirements and Qualifications. But that may be thin. Better: Have Requirements (mandatory) and Qualifications (education/licensure) and Skills (abilities). But that's many sections. Given instruction to prefer few substantive sections, we can combine. Thus:

  Requirements

  • Doctor of Pharmacy (PharmD) from an accredited college/university
  • Licensed Pharmacist and in good standing (multiple state licenses are a plus)
  • Bilingual fluency in English and either Spanish, Mandarin or Cantonese. Must be comfortable speaking to patients in that language regarding their medications and healthcare
  • Knowledge of CMS quality measures, Star Ratings, HEDIS metrics, and Medicare Part C and Part D medication measures
  • Knowledge of chronic disease states across multiple therapeutic areas (e.g., cardiology, pulmonology, endocrinology, behavioral health), including management of patients with polypharmacy
  • Knowledge of prescription and non-prescription drugs and drug products and their indications, efficacy, dosage, mechanisms of action, major contraindications and potential side effects
  • Ability to review and assess the appropriateness of prescriptions, considering the influence of patient age, sex, concomitant disease states, concurrent drug therapy, foods, and diagnostic procedures on drug activity and disposition
  • Ability to engage with patients, promote adherence, and apply motivational interviewing and counseling techniques
  • Excellent written and oral communication skills, with the emotional intelligence to build rapport, navigate sensitive interactions, and remain patient-focused
  • Experience working with patients of different cultural, religious, and socio-economic backgrounds
  • Demonstrated reliability, accountability, and follow-through
  • High attention to detail with a strong commitment to documentation accuracy
  • Comfort working in a metrics-driven environment where outcomes and quality are tracked
  • Ability to work independently - applying sound judgment, organizing and prioritizing competing responsibilities, and meeting deadlines with minimal oversight
  • Ability to work effectively within a team, foster effective working relationships, and build consensus
  • Openness to coaching, feedback, and continuous learning
  • Ability to adapt and thrive in a fast-paced environment, managing multiple Medicare measures and clinical priorities while navigating evolving workflows and technologies
  • Knowledge of local, state, and federal regulatory requirements related to areas of functional responsibility
  • 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
  • Willingness and ability to obtain registered pharmacist license in other states, as needed
  • 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)
  Then we could add a separate

  Preferred Qualifications

  for