Junior Developer

Solve Problems. Find the Answer. Help Customers (and Engineers) Move Faster.

At Direct2

Care, we’re on a mission to make healthcare accessible for the millions of hardworking Americans who can’t afford to get sick. We provide affordable, 24/7 virtual healthcare solutions that help businesses support their teams with everyday medical care, mental health services, and workplace injury guidance, without the cost or complexity of traditional health insurance. We’re a collaborative, mission-driven team that values innovation, ownership, and customer obsession.

As we continue to grow, we’re looking for people who are passionate about making a meaningful impact, for our customers, their employees, and the future of accessible healthcare.

Fully remote for candidates residing in AZ, CA, CO, IL, TX

Part-time with the ability to increase to full time

At Direct2

Care, 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.

• 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.

• 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,

• Run read-only SQL queries against reporting replicas and use Metabase to investigate data.
• Review Cloud Watch 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.

• Recognize when an issue requires an engineering change and accelerate escalation 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.