ZipRecruiter

Log In

1

C Embedded Software Engineer Jobs in Springfield, MO

Amphenol

Second Shift Production Technician

Springfield, MO · On-site

$14.50 - $18.25/hr

Support engineers with continuous improvement initiatives, including 5S and process updates ... Operate basic shop tools, machines, and software including Epicor, SolidWorks, and Microsoft Office.

previous page

Showing results 21-39

All JobsC Embedded Software Engineer JobsC Embedded Software Engineer Jobs in Springfield, MO

C Embedded Software Engineer information

See Springfield, MO salary details

$63.7K

$139.5K

$158.3K

How much do c embedded software engineer jobs pay per year?

As of Sep 5, 2026, the average yearly pay for c embedded software engineer in Springfield, MO is $139,522.00, according to ZipRecruiter salary data. Most workers in this role earn between $119,600.00 and $157,400.00 per year, depending on experience, location, and employer.

What is a C embedded software engineer?

C Embedded Software Engineers are professionals who design, develop, and maintain software written in the C programming language for embedded systems. These systems are specialized computing devices, like microcontrollers or processors, found in products such as cars, medical devices, consumer electronics, and industrial machines. Engineers in this role work closely with hardware components, optimizing code to ensure reliability, efficiency, and real-time performance. They often collaborate with hardware engineers and need a strong understanding of both software and hardware integration.

How does a C embedded software engineer typically collaborate with hardware engineers during development?

C Embedded Software Engineers work closely with hardware engineers throughout the development cycle to ensure software and hardware integration runs smoothly. This collaboration often involves reviewing hardware schematics, debugging issues using oscilloscopes or logic analyzers, and adjusting firmware to match hardware constraints. Regular meetings and joint troubleshooting sessions are common, as both teams need to align on hardware capabilities, firmware requirements, and timing considerations. Effective communication and documentation are key to resolving cross-disciplinary challenges quickly and efficiently.

What are the key skills and qualifications needed to thrive as a C embedded software engineer, and why are they important?

To thrive as a C Embedded Software Engineer, you need strong proficiency in C programming, knowledge of embedded systems architecture, and a relevant engineering degree. Familiarity with hardware interfaces, RTOS, debugging tools, version control systems like Git, and sometimes certifications such as Embedded Systems Certification are typically required. Analytical thinking, attention to detail, and effective communication are important soft skills that help in troubleshooting and collaborating with cross-functional teams. These skills and qualities ensure reliable, efficient software development for resource-constrained devices and successful project delivery.

What is the difference between C Embedded Software Engineer vs C Firmware Engineer?

AspectC Embedded Software EngineerC Firmware Engineer
Required CredentialsBachelor's in Computer Engineering or related field; knowledge of embedded CBachelor's in Electrical or Computer Engineering; strong C programming skills
Work EnvironmentEmbedded systems development, often on microcontrollers or SoCsFirmware development directly on hardware, often for devices like IoT or consumer electronics
Industry UsageAutomotive, medical devices, industrial automationConsumer electronics, IoT devices, embedded systems

Both roles involve embedded C programming but differ mainly in focus. C Embedded Software Engineers develop software for embedded systems, while C Firmware Engineers work on low-level firmware directly controlling hardware. The roles often overlap, but the firmware role emphasizes hardware interaction and low-level programming.

What are popular job titles related to C Embedded Software Engineer jobs in Springfield, MO?

For C Embedded Software Engineer jobs in Springfield, MO, the most frequently searched job titles are:

C Embedded Software Engineer jobs near you
Infographic showing various C Embedded Software Engineer job openings in Springfield, MO as of August 2026, with employment types broken down into 100% Full Time. Highlights an 92% In-person, and 8% Remote job distribution, with an average salary of $139,522 per year, or $67.1 per hour.

AI Agent Trajectory Annotator and Reviewer

Bespoke Labs

Springfield, MO

$20 - $30/hr

Full-time

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