ZipRecruiter

Log In

1

Internship Python C Developer Jobs in Myrtle Beach, SC

TransPerfect

Junior QA Engineer

Myrtle Beach, SC

Jira, Azure DevOps, or similar Basic understanding of browser developer tools for frontend ... Python Understanding of CI/CD pipelines and how automated tests fit in A Design Mindset We need QA ...

TransPerfect

Junior QA Engineer

Myrtle Beach, SC · On-site

Jira, Azure DevOps, or similar • Basic understanding of browser developer tools for frontend ... or Python • Understanding of CI/CD pipelines and how automated tests fit in A Design Mindset We ...

previous page

Showing results 21-32

All JobsPython C Developer JobsInternship Python C Developer JobsInternship Python C Developer Jobs in Myrtle Beach, SC

Internship Python C Developer information

See Myrtle Beach, SC salary details

$11

$52

$77

How much do internship python c developer jobs pay per hour?

As of Sep 13, 2026, the average hourly pay for internship python c developer in Myrtle Beach, SC is $52.76, according to ZipRecruiter salary data. Most workers in this role earn between $43.46 and $59.90 per hour, depending on experience, location, and employer.

What does an internship Python C developer do?

An Internship Python C Developer is typically responsible for assisting in the development and maintenance of software applications using both Python and C programming languages. Interns in this role often work under the guidance of senior developers to write code, fix bugs, perform testing, and contribute to project documentation. They gain hands-on experience with software development processes and tools while learning best practices in coding, debugging, and collaborating in a professional environment. This internship is ideal for students or recent graduates looking to build practical skills in both Python and C programming.

What are the key skills and qualifications needed to thrive as an internship Python C developer?

To thrive as an Internship Python C Developer, you need a solid understanding of Python and C programming languages, basic software engineering concepts, and ideally a relevant academic background in computer science or engineering. Familiarity with version control systems like Git, development environments, and debugging tools is typically required. Strong problem-solving skills, a willingness to learn, and effective communication set standout interns apart. These skills are crucial for contributing to development teams, adapting quickly, and delivering quality code in a collaborative environment.

What types of projects and tasks can an internship Python C developer expect to work on during their placement?

As an Internship Python C Developer, you will typically work on a variety of projects ranging from debugging and optimizing existing codebases to developing new features under the guidance of senior developers. Common tasks include writing unit tests, assisting in code reviews, integrating Python scripts with C modules, and troubleshooting performance issues. You'll often collaborate with cross-functional teams such as QA, DevOps, and other developers, giving you exposure to the full software development lifecycle. This hands-on experience helps you build a solid technical foundation and develop problem-solving skills that are highly valued in the industry.

What are popular job titles related to Internship Python C Developer jobs in Myrtle Beach, SC?

For Internship Python C Developer jobs in Myrtle Beach, SC, the most frequently searched job titles are:

What job categories do people searching Internship Python C Developer jobs in Myrtle Beach, SC look for?

The top searched job categories for Internship Python C Developer jobs in Myrtle Beach, SC are:

What cities near Myrtle Beach, SC are hiring for Internship Python C Developer jobs?

Cities near Myrtle Beach, SC with the most Internship Python C Developer job openings:

Internship Python C Developer jobs near you

AI Agent Trajectory Annotator and Reviewer

Conway, SC

Bespoke Labs
See more jobs at Bespoke Labsexternal

$20 - $30/hr

Full-time

Posted 13 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