Software Engineering Expert (AI Training, $50–65/h)

<p><strong>Software Engineering Expert - AI Model Evaluation</strong> · Contract · Remote · $50–65/h</p><p><br></p><p>Role Overview</p><ul><li>Huzzle is seeking software engineers to test how well frontier AI systems handle real engineering work, and to document where they fall short.</li><li>You will not be building products. You will be finding the point at which an AI system stops being reliable at engineering, and proving that point objectively.</li><li>Each submission has three parts: a realistic technical request, documented evidence of where the model failed it, and a scoring rubric that lets any reviewer grade a future attempt consistently.</li><li>Because this is code, most rubric criteria are verified by running it. The grading is unusually objective, which is what makes the work satisfying.</li><li>Full training and worked examples are provided. Prior AI or data-annotation experience is not required.</li></ul><p><br></p><p>Key Responsibilities</p><ul><li>Test technical requests against a frontier AI model and review its output with the scrutiny you would apply to code you were merging.</li><li>Document exactly where and how it failed, with the line, the failing condition, or the missing behaviour that demonstrates it. Precision matters more than volume.</li><li>Author scoring rubrics with objective criteria another engineer could apply without repeating your work — ideally by executing the code against a named case.</li><li>Write the underlying requests: realistic technical tasks requiring live research or real web interaction — actual API behaviour, current documentation, published licences, real datasets — plus implementation and a working file deliverable. Typically a Python script, but also CSVs, config, SQL or technical memos.</li><li>Escalate task difficulty where the model succeeds, until a genuine gap is exposed. Note that models are strong at conventional coding problems; the gaps are in edge cases, real-world API behaviour and constraint discipline, not in algorithms.</li><li>Log hours accurately and respond to review feedback within the working day. This is a two-week sprint.</li></ul><p><br></p><p>Ideal Qualifications</p><ul><li>5+ years writing production software, or equivalent demonstrable depth.</li><li>Strong Python. Comfortable consuming third-party APIs, handling errors and edge cases, and managing dependencies.</li><li>The instinct to check what an API actually returns rather than trust what the documentation implies.</li><li>Excellent written English and unusual precision with detail.</li><li>3–6 hours per day available across the engagement.</li><li>A public code portfolio (GitHub or equivalent) is helpful but not required.</li></ul><p><br></p><p>Contract and Payment Terms</p><ul><li>You will be engaged as an independent contractor.</li><li>Fully remote, completed on your own schedule within the engagement window.</li><li>The engagement may be extended, shortened or concluded early depending on programme needs and performance.</li></ul><p><br></p><p>About Huzzle</p><p>Huzzle partners with leading AI organisations to evaluate and improve frontier models using deep human expertise. Contributors work directly on the assessment of advanced AI systems in their own field, are paid competitively, and help define the standards by which those systems are measured.</p>

Back to blog

Other Jobs To Apply

No other job posts for this day.

Common Interview Questions And Answers

1. HOW DO YOU PLAN YOUR DAY?

This is what this question poses: When do you focus and start working seriously? What are the hours you work optimally? Are you a night owl? A morning bird? Remote teams can be made up of people working on different shifts and around the world, so you won't necessarily be stuck in the 9-5 schedule if it's not for you...

2. HOW DO YOU USE THE DIFFERENT COMMUNICATION TOOLS IN DIFFERENT SITUATIONS?

When you're working on a remote team, there's no way to chat in the hallway between meetings or catch up on the latest project during an office carpool. Therefore, virtual communication will be absolutely essential to get your work done...

3. WHAT IS "WORKING REMOTE" REALLY FOR YOU?

Many people want to work remotely because of the flexibility it allows. You can work anywhere and at any time of the day...

4. WHAT DO YOU NEED IN YOUR PHYSICAL WORKSPACE TO SUCCEED IN YOUR WORK?

With this question, companies are looking to see what equipment they may need to provide you with and to verify how aware you are of what remote working could mean for you physically and logistically...

5. HOW DO YOU PROCESS INFORMATION?

Several years ago, I was working in a team to plan a big event. My supervisor made us all work as a team before the big day. One of our activities has been to find out how each of us processes information...

6. HOW DO YOU MANAGE THE CALENDAR AND THE PROGRAM? WHICH APPLICATIONS / SYSTEM DO YOU USE?

Or you may receive even more specific questions, such as: What's on your calendar? Do you plan blocks of time to do certain types of work? Do you have an open calendar that everyone can see?...

7. HOW DO YOU ORGANIZE FILES, LINKS, AND TABS ON YOUR COMPUTER?

Just like your schedule, how you track files and other information is very important. After all, everything is digital!...

8. HOW TO PRIORITIZE WORK?

The day I watched Marie Forleo's film separating the important from the urgent, my life changed. Not all remote jobs start fast, but most of them are...

9. HOW DO YOU PREPARE FOR A MEETING AND PREPARE A MEETING? WHAT DO YOU SEE HAPPENING DURING THE MEETING?

Just as communication is essential when working remotely, so is organization. Because you won't have those opportunities in the elevator or a casual conversation in the lunchroom, you should take advantage of the little time you have in a video or phone conference...

10. HOW DO YOU USE TECHNOLOGY ON A DAILY BASIS, IN YOUR WORK AND FOR YOUR PLEASURE?

This is a great question because it shows your comfort level with technology, which is very important for a remote worker because you will be working with technology over time...