Junior Developer

We need to output HTML fragment with sections: About the role? The posting includes description paragraphs. We need headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: description (intro) maybe "About the role". Then responsibilities: bullet list under "What You'll Do". Then qualifications: "What We're Looking For" includes required and preferred qualifications. Could split into Requirements and Qualifications? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills). We need to decide which sections we have content for. We have: - About the role: introductory paragraph(s) before "What You'll Do". Could be considered About the role. - Responsibilities: under "What You'll Do" with bullet points. - Requirements: maybe "Required Qualifications" list. - Qualifications: maybe "Preferred Qualifications" list. - Skills: maybe "Technology You'll Use" list. - Benefits: maybe "Why You'll Love Working Here" includes benefits like remote work, meaningful work, etc. Could be Benefits. - Pay: not mentioned. - Schedule: mentions "Part-time with the ability to increase to full time". That's schedule info. So we can include Schedule section. We must not include sections with filler like "commensurate with experience". Not present. We must not repeat job title as heading. Not include Job ID. We must remove boilerplate: cookie/navigation/legal/EEO etc. Not present. We must preserve all substantive info. We need to use

for each section heading. Use

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

  for prose. We need to output only HTML fragment. Let's craft:

  About the role

  We're So Glad You're Here! 📍Fully remote for candidates residing in AZ, CA, CO, IL, TX⏰ Part-time with the ability to increase to full time At Direct2Care, we're looking for a Junior Developer who loves getting to the bottom of things. When a customer says their member count doesn't look right, new customers haven't received their invitations, or a census file processed but the expected members aren't showing up, you'll be the person who investigates what actually happened. You'll serve as the bridge between our customer-facing teams and Digital Infrastructure, owning technical requests from initial intake through resolution or escalation. You'll investigate data, logs, user records, and system activity to separate true software defects from data or configuration questions, and resolve as much as possible without requiring engineering intervention. This is an ideal role for someone who is technically curious, highly analytical, and deeply committed to getting the answer right. If you enjoy digging into SQL, tracing issues across systems, documenting what you learn, and translating technical findings into clear answers for non-technical people, we'd love to meet you.

  But note we already have schedule info in that paragraph; maybe we separate schedule later. However schedule info is "Part-time with the ability to increase to full time". Could be placed in Schedule section. We could keep that sentence in About the role but then schedule section would be duplicate. Better to extract schedule sentence to Schedule section and keep About the role without schedule. Let's parse. Original intro: "We're So Glad You're Here! 📍Fully remote for candidates residing in AZ, CA, CO, IL, TX⏰ Part-time with the ability to increase to full time At Direct2Care, we're looking for a Junior Developer who loves getting to the bottom of things...." We can split: About the role: description of role and mission. Schedule: part-time ability to increase to full time. Location: remote for certain states. We could include location in About the role or maybe separate? Not required to have location heading. We'll keep location in About the role. Thus About the role paragraph: "We're So Glad You're Here! 📍Fully remote for candidates residing in AZ, CA, CO, IL, TX At Direct2Care, we're looking for a Junior Developer who loves getting to the bottom of things. When a customer says their member count doesn't look right, new customers haven't received their invitations, or a census file processed but the expected members aren't showing up, you'll be the person who investigates what actually happened. You'll serve as the bridge between our customer-facing teams and Digital Infrastructure, owning technical requests from initial intake through resolution or escalation. You'll investigate data, logs, user records, and system activity to separate true software defects from data or configuration questions, and resolve as much as possible without requiring engineering intervention. This is an ideal role for someone who is technically curious, highly analytical, and deeply committed to getting the answer right. If you enjoy digging into SQL, tracing issues across systems, documenting what you learn, and translating technical findings into clear answers for non-technical people, we'd love to meet you." Then Schedule section: "

  Schedule

  Part-time with the ability to increase to full time.

  " Now Responsibilities: under "What You'll Do". We'll create

  Responsibilities

  then
  • each bullet. Bullet points: - Own the Technical Support Queue - Serve as the primary intake point for technical requests from Customer Success, Sales, Operations, and external partners. - Turn incoming requests into clear, actionable Linear tickets with the information needed to investigate effectively. - Document reproduction steps, affected organizations, environments, system surfaces, labels, and estimates. - Keep the queue organized by identifying duplicates and checking for existing issues before creating new tickets. - Investigate & Resolve Tier 1/2 Issues - Reproduce reported problems before escalating them to engineering. - Determine whether an issue represents a true system defect, a data discrepancy, a configuration issue, or expected system behavior. - Use read-only SQL, reporting tools, logs, and administrative systems to investigate customer and system issues. - Trace members and data through census and eligibility processes to identify where discrepancies occurred. - Resolve the majority of inbound technical requests independently whenever possible, - Follow the Evidence - Run read-only SQL queries against reporting replicas and use Metabase to investigate data. - Review CloudWatch logs and Cognito user status. - Investigate message and invitation delivery through Twilio and Amazon SES. - Trace member records through census ingestion and related workflows. - Verify important findings through two independent sources before communicating conclusions. - Escalate the Right Issues - Recognize when an issue requires an engineering change and escalate it appropriately. - Give engineers the evidence they need to act quickly rather than requiring them to restart the investigation. - Include reproduction steps, relevant queries, log evidence, affected record counts, potential impact, and what has already been ruled out. - Build the Playbook - Turn recurring technical questions and investigations into clear, reusable runbooks. - Document troubleshooting steps so common issues can be resolved quickly and consistently. - Continuously improve internal documentation as systems, processes, and customer needs evolve. - Help create a scalable support model that reduces unnecessary engineering interruptions. We need to flatten into simple
  • items; we can keep sub-bullets as separate
  • but maybe keep as separate lines. We'll just list each bullet as
  • . Might be many but okay. Now Requirements: "Required Qualifications" list. List: - 2+ years of experience in technical support, production support, data operations, or a similar analyst role within a software company. - Working knowledge of SQL, including joins, GROUP BY, and window functions. - Strong understanding of data relationships and the ability to recognize when a query could produce misleading results. - Comfortable working in a terminal and navigating cloud-based consoles. - Ability to read application logs, follow traces, and investigate technical issues independently. - Strong analytical and problem-solving skills. - Excellent written English and the ability to explain technical findings clearly to non-technical stakeholders. - High attention to detail and a strong commitment to accuracy. - Ability to handle sensitive information with discretion and professionalism. - Comfortable working with protected health information and following HIPAA-related data handling requirements. Now Qualifications: "Preferred Qualifications" list. List: - Experience with employer benefits, eligibility files, census files, or roster data feeds. - Familiarity with AWS, particularly CloudWatch, Cognito, RDS, and S3. - Experience with Linear, Metabase, HubSpot, or Twilio. - Experience writing lightweight scripts in Python or Bash to automate repetitive investigations or data pulls. Now Skills: "Technology You'll Use" list. List: - SQL - AWS - CloudWatch - Cognito - RDS - S3 - Metabase - Linear - HubSpot - Twilio - Amazon SES - MyClinic Healthcare Backoffice - Python and/or Bash Now Benefits: "Why You'll Love Working Here" paragraph. We can turn into

    Benefits

    We believe great work happens when people are trusted, supported, and given room to grow. Here's what you can expect: 🏡 Remote work environment with the flexibility to do your best work from wherever you call home 🧠 Meaningful technical work where your analysis directly impacts customers and the business 🚀 Opportunity to make a meaningful impact at a growing, mission-driven healthcare company 🤝 Collaborative team that values ownership, curiosity, accuracy, and continuous learning 🛠️ Hands-on exposure to data, cloud infrastructure, technical troubleshooting, and healthcare technology 📈 Opportunity to grow your technical expertise and career as Direct2Care continues to scale

    We should keep emojis? They are part of content; we can keep them. Now ensure we don't repeat content. We have schedule separate. Check for any duplicated lines: we removed "We're So Glad You're Here! 📍Fully remote for candidates residing in AZ, CA, CO, IL, TX⏰ Part-time with the ability to increase to full time" from About the role but we kept location and removed schedule. We kept location emojis but removed the clock emoji? We kept location emojis but removed the clock emoji (⏰). That's fine. Now ensure we didn't invent or summarize away detail. We preserved all. Now output HTML fragment only. Let's craft final HTML. We'll need to wrap each section in appropriate tags. We'll produce:

    About the role

    ...

    Schedule

    Part-time with the ability to increase to full time.

    Responsibilities

    • Own the Technical Support Queue
    • Serve as the primary intake point for technical requests from Customer Success, Sales, Operations, and external partners.
    • Turn incoming requests into clear, actionable Linear tickets with the information needed to investigate effectively.
    • Document reproduction steps, affected organizations, environments, system surfaces, labels, and estimates.
    • Keep the queue organized by identifying duplicates and checking for existing issues before creating new tickets.
    • Investigate & Resolve Tier 1/2 Issues
    • Reproduce reported problems before escalating them to engineering.
    • Determine whether an issue represents a true system defect, a data discrepancy, a configuration issue, or expected system behavior.
    • Use read-only SQL, reporting tools, logs, and administrative systems to investigate customer and system issues.
    • Trace members and data through census and eligibility processes to identify where discrepancies occurred.
    • Resolve the majority of inbound technical requests independently whenever possible,
    • Follow the Evidence
    • Run read-only SQL queries against reporting replicas and use Metabase to investigate data.
    • Review CloudWatch logs and Cognito user status.
    • Investigate message and invitation delivery through Twilio and Amazon SES.
    • Trace member records