ZipRecruiter

Log In

1

Live In Software Engineer Pharmacy Jobs in Ripley, TN

Walmart

Pharmacy Technician

Blytheville, AR · On-site

$16 - $29/hr

... Overview Pharmacy associates focus on the needs of our customers as they entrust us with their ... Live Better U is a Walmart-paid education benefit program for full-time and part-time associates in ...

Helenoftroy

Sr. AI Analytics Engineer

Arlington, TN · Hybrid

Whether you are just starting your career or in need of a challenge, we recognize, develop, and ... software, automation, or AI solutions. * 2+ years of hands-on AI / GenAI solution delivery ...

Walmart

Certified Pharmacy Technician

Brownsville, TN · On-site

$20.50 - $33.50/hr

... Overview Pharmacy associates focus on the needs of our customers as they entrust us with their ... Live Better U is a Walmart-paid education benefit program for full-time and part-time associates in ...

previous pagenext page

Showing results 21-40

All JobsLive In Software Engineer Pharmacy JobsLive In Software Engineer Pharmacy Jobs in Ripley, TN

Live In Software Engineer Pharmacy information

See Ripley, TN salary details

$55.8K

$129.7K

$180.7K

How much do live in software engineer pharmacy jobs pay per year?

As of Sep 6, 2026, the average yearly pay for live in software engineer pharmacy in Ripley, TN is $129,695.00, according to ZipRecruiter salary data. Most workers in this role earn between $105,500.00 and $152,100.00 per year, depending on experience, location, and employer.

What is a live in software engineer pharmacy?

A Live In Software Engineer in a Pharmacy is a software professional who resides on-site or very close to a pharmacy to provide technical support, maintain pharmacy management systems, and develop software solutions tailored to pharmacy operations. Their responsibilities may include troubleshooting software issues, integrating new technologies, ensuring data security, and optimizing workflow processes. By being available around the clock, they help ensure uninterrupted pharmacy operations and rapid response to any technical emergencies.

What are the key skills and qualifications needed to thrive as a live in software engineer pharmacy?

To thrive as a Live-In Software Engineer in a Pharmacy, you need strong programming skills, a solid understanding of pharmacy operations, and typically a degree in computer science or a related field. Familiarity with pharmacy management systems, healthcare data standards (like HL7), and relevant certifications such as HIPAA compliance are important. Excellent problem-solving, adaptability, and communication skills help you address technical issues quickly while collaborating effectively with pharmacy staff. These skills ensure reliable software solutions that support safe, efficient, and compliant pharmacy operations.

What are some unique challenges faced by live in software engineers working in a pharmacy setting?

Live-In Software Engineers in a pharmacy setting often encounter the challenge of integrating software solutions with specialized pharmaceutical systems while ensuring compliance with healthcare regulations. Balancing on-call technical support with personal time can be demanding, as immediate response is sometimes required for critical system issues. Additionally, close collaboration with pharmacists and healthcare staff is essential to understand workflow requirements and implement user-friendly, secure interfaces. This role provides unique insight into healthcare technology and offers opportunities to directly impact patient care through innovative solutions.

What is the difference between Live In Software Engineer Pharmacy vs Live In Software Engineer Hospital?

AspectLive In Software Engineer PharmacyLive In Software Engineer Hospital
CertificationsRelevant software development certifications, pharmacy industry knowledgeRelevant software development certifications, healthcare industry knowledge
Work EnvironmentPharmacy settings, retail or hospital pharmaciesHospital environments, clinical settings
Employer & Industry UsagePharmacy chains, pharmaceutical companiesHospitals, healthcare providers
Search & Comparison IntentComparing roles within pharmacy tech and software developmentRoles within hospital healthcare IT systems

Both roles involve software engineering in healthcare settings, but Live In Software Engineer Pharmacy focuses on pharmacy systems and pharmacy-specific workflows, while Live In Software Engineer Hospital emphasizes hospital-wide healthcare IT solutions. The choice depends on the industry focus and work environment preference.

What cities near Ripley, TN are hiring for Live In Software Engineer Pharmacy jobs?

Cities near Ripley, TN with the most Live In Software Engineer Pharmacy job openings:

Live In Software Engineer Pharmacy jobs near you

AI Agent Trajectory Annotator and Reviewer

Bespoke Labs

Jackson, TN • On-site

$20 - $30/hr

Full-time

Posted 6 days ago

Job description

Type: Contract, hourly

Location: Remote

Hours: 20–30 per week

Pay: $20–30/hour, based on experience and language coverage

Start: Immediate

ABOUT THE ROLE

We evaluate how well advanced AI coding agents solve real engineering problems. An agent is given a real open source codebase inside a container and a hard task, then works on its own for 80 to 250 steps. A trajectory is the full record of that run — every command, result, and decision.

You will do two jobs, and you should expect either on any given day.

•Annotate — Read a trajectory nobody has looked at yet and judge it step by step.

• Review — Take an existing annotation, written by our AI tooling or another person, and confirm, correct, or reject it.

TASKS YOU'LL SEE

• Feature build — Add a working feature to a live library without breaking anything that already worked.

• Rebuild — Work out what a compiled tool does by running it, then rebuild it to match its output, exit codes, and file effects.

• Bug hunt — Find and fix twenty undocumented bugs across a dozen files with no test suite, then record what caused them.

Mostly Python and Go, with some Rust, C, and Ct+. A trajectory runs about 100 steps.

WHAT YOU JUDGE IN A TRAJECTORY

• Was the command right for the state the environment was actually in?

• Did the agent read the previous output correctly?

• Was the step wrong, or only inefficient — these are scored differently.

• Where did the run first go off course — usually earlier than where it visibly broke.

• Did the agent notice its own mistake and recover, or keep building on a false assumption?

• Did it game the grader instead of solving the task (e.g., weakening a test or hardcoding an expected value)?

WHAT WE NEED FROM YOU

• Experience — 2+ years in software engineering, DevOps, or site reliability, with real debugging in real codebases.

• Languages — Strong in Python or Go, and able to read a language you've never used.

• Linux — Comfortable with logs, running processes, build failures, and containers.

• Workflow — Everyday Git, diffs, pull requests, and issue tracking.

• Debugging — Able to work with no test suite and no error message pointing at the cause.

• Focus — Able to hold context across a long run, because step 74 can depend on step 12.

• Writing — Clear English, since every judgement needs an explanation another engineer can check.

Apply