1

Software Developer Two Jobs in Flint, MI (NOW HIRING)

Controls Engineer I

Lake Orion, MI · On-site

$77K - $99K/yr

Experience with CAD software (e.g., AutoCAD Electrical or SolidWorks). * Current or prior JR ... Join our team of 2,000+ at one of our 20+ facilities around the world and be a part of the most ...

City Engineer

Saginaw, MI · On-site

$95K - $108K/yr

Minimum of two (2) years supervisory experience, preferably in a union environment. Licenses and ... Engineering and office software such as CAD, GIS, and Microsoft Office. Skill in * Preparing clear ...

... : * 2+ years of prior relevant experience. * Bachelor's Degree (Electrical, Mechanical, Civil, or ... Work management software and job estimating software. * CAD tools At Leidos , we pride ourselves on ...

First 2 months - 2 weeks per month / 50% in office for onboarding / process development * Next 1 ... Proficiency in tools like Excel, MathCAD, and structural analysis software (e.g., RAM Elements, RAM ...

Troubleshoot and resolve issues related to vision hardware, software, and robotic integration ... Project department PHYSICAL REQUIREMENTS Activity Amount of Time None Under 1/3 1/3 to 2/3 Over 2/3 ...

Showing results 41-60

Software Developer Two information

See Flint, MI salary details

$46.7K

$108.8K

$161.5K

How much do software developer two jobs pay per year?

As of Sep 12, 2026, the average yearly pay for software developer two in Flint, MI is $108,797.00, according to ZipRecruiter salary data. Most workers in this role earn between $87,500.00 and $126,500.00 per year, depending on experience, location, and employer.

What is the difference between Software Developer Two vs Software Developer Three?

AspectSoftware Developer TwoSoftware Developer Three
ExperienceTypically 2-4 yearsTypically 4-6 years
ResponsibilitiesContributes to projects, writes code, fixes bugsLeads modules, mentors junior developers, designs solutions
Required SkillsProficient in programming languages, basic system designAdvanced coding, system architecture, project management
CertificationsOptional, relevant certifications preferredOptional, often holds advanced certifications

The main difference between Software Developer Two and Software Developer Three lies in experience level, responsibilities, and skill complexity. Software Developer Two is an intermediate role focused on coding and supporting projects, while Software Developer Three involves more leadership, system design, and mentorship responsibilities.

What other jobs can a software developer do?

Software developers can transition into roles such as software engineer, systems analyst, technical lead, or product manager, leveraging their programming, problem-solving, and project management skills. They can also work in specialized areas like cybersecurity, data analysis, or quality assurance, often requiring additional certifications or training. These roles typically involve similar technical environments and collaboration with cross-functional teams.

What cities near Flint, MI are hiring for Software Developer Two jobs?

Cities near Flint, MI with the most Software Developer Two job openings:

AI Agent Trajectory Annotator and Reviewer

Flint, MI

$20 - $30/hr

Full-time

Posted 11 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.