1

Software Developer No Technical Interview Entry Jobs in Laredo, TX

Engineering Associate II

Laredo, TX · On-site

$65 - $90/hr

... Technical Specifications, TxDOT specifications, Subdivision Ordinance. * Must be familiar with ... Performs drafting duties utilizing AUTOCAD Civil 3D, Arc GIS and other available drafting software.

New

You will assist Resident Engineers, Project Managers, field engineers, inspectors, and technical ... No supervisory experience required. * Must be actively preparing for professional engineering ...

You will assist Resident Engineers, Project Managers, field engineers, inspectors, and technical ... No supervisory experience required. * Must be actively preparing for professional engineering ...

Showing results 41-60

Software Developer No Technical Interview Entry information

See Laredo, TX salary details

$25.9K

$88K

$212K

How much do software developer no technical interview entry jobs pay per year?

As of Sep 5, 2026, the average yearly pay for software developer no technical interview entry in Laredo, TX is $88,013.00, according to ZipRecruiter salary data. Most workers in this role earn between $55,700.00 and $93,000.00 per year, depending on experience, location, and employer.

What is a software developer no technical interview entry?

'Software Developer No Technical Interview Entry' jobs are software development positions that do not require candidates to complete traditional technical interviews, such as coding challenges or algorithm tests. Instead, the hiring process may focus on assessing soft skills, previous experience, or portfolio work. These roles are often designed to lower barriers for entry-level developers or those changing careers. Employers may use alternative methods like take-home assignments, project reviews, or behavioral interviews to evaluate candidates. This approach aims to create a more inclusive and accessible hiring process for aspiring software developers.

What are the key skills and qualifications needed to thrive as a software developer no technical interview entry?

To thrive as a Software Developer in roles without a technical interview, you need a solid understanding of programming fundamentals, problem-solving abilities, and often a relevant degree or coding bootcamp experience. Familiarity with version control systems like Git, common programming languages (such as Python, Java, or JavaScript), and basic software development tools is typically expected. Strong communication, teamwork, and a willingness to learn help you stand out in collaborative development environments. These skills ensure you can contribute effectively to projects, adapt to evolving technologies, and integrate smoothly with diverse teams.

What can I expect from the onboarding process as a software developer no technical interview entry?

As a Software Developer hired through a No Technical Interview Entry process, you can typically expect a comprehensive onboarding program that focuses on familiarizing you with the company’s development tools, coding standards, and workflows. You may participate in mentorship programs, training sessions, or pair programming to help bridge any skill gaps and integrate smoothly into the team. Collaboration and open communication are often emphasized, and you'll likely be encouraged to ask questions and seek feedback as you ramp up. This supportive environment helps build your confidence and ensures you’re set up for success from day one.

What are popular job titles related to Software Developer No Technical Interview Entry jobs in Laredo, TX?

For Software Developer No Technical Interview Entry jobs in Laredo, TX, the most frequently searched job titles are:

What job categories do people searching Software Developer No Technical Interview Entry jobs in Laredo, TX look for?

The top searched job categories for Software Developer No Technical Interview Entry jobs in Laredo, TX are:

What cities near Laredo, TX are hiring for Software Developer No Technical Interview Entry jobs?

Cities near Laredo, TX with the most Software Developer No Technical Interview Entry job openings:

AI Agent Trajectory Annotator and Reviewer

Bespoke Labs

Laredo, TX • On-site

$20 - $30/hr

Full-time

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