Software Engineer Task Author (AI Training)

<strong>About The Role<br><br></strong>Alignerr is building a dataset of expert tasks that train and evaluate advanced AI agents on real enterprise engineering work. As a Task Author based in Bangalore, you will design and calibrate authentic engineering challenges — diagnosing failing integrations from logs, tracing bugs through codebases, and writing and verifying real fixes — that genuinely push the limits of capable AI agents.<br><br>Bangalore's engineering talent is world-class, and this role is designed for working engineers with real industry experience in backend systems, SaaS infrastructure, APIs, or enterprise software. This is not a generalist or instructional role — it requires hands-on engineering skill.<br><br><ul><li>Organization: Alignerr</li><li>Type: Hourly Contract</li><li>Location: Remote</li><li>Commitment: Flexible, task-based<br><br></li></ul><strong>Key Responsibilities<br><br></strong><ul><li>Author realistic engineering task prompts covering integration failures, log-based debugging, bug traces through source code, and configuration or integration fixes</li><li>Write scoring rubrics that define exactly what a correct fix or diagnosis looks like and how it is verified — including live environment validation where applicable</li><li>Set up task environments with realistic codebases, logs, alerts, and system states that place an AI agent in a plausible engineering situation</li><li>Solve each task yourself — write the actual fix and confirm it works — to validate the task is sound and the rubric is accurate</li><li>Calibrate task difficulty by adjusting code complexity, log volume, failure modes, or ambiguity until the task reliably challenges the model to the intended degree</li><li>Review and correct AI-drafted task prompts or rubrics when provided<br><br></li></ul><strong>Qualifications<br><br></strong><ul><li>Working software engineer with hands-on, industry-level experience — this is not a theoretical or instructional role</li><li>Fluency in Git, version control workflows, and code review practices</li><li>Strong debugging skills: comfortable reading logs, using observability tools, and tracing failures through a codebase</li><li>Experience with infrastructure, integrations, and configuration code (APIs, services, config files, CI/CD)</li><li>Ability to write and verify a code fix in a live or simulated environment</li><li>Ability to define precise, checkable correctness criteria for engineering outcomes</li><li>Strong written communication skills in English<br><br></li></ul><strong>Nice to Have<br><br></strong><ul><li>Experience in enterprise SaaS, fintech, or industrial IoT engineering contexts common in Bangalore's tech ecosystem</li><li>Background with monitoring and observability platforms such as Datadog, Grafana, or PagerDuty</li><li>Familiarity with cloud infrastructure on AWS, GCP, or Azure<br><br></li></ul><strong>Why Join Us<br><br></strong><ul><li>Work on cutting-edge AI projects alongside leading research labs</li><li>Fully remote and flexible — work when and where it suits you</li><li>Freelance autonomy with the structure of meaningful, well-defined task-based work</li><li>Contribute directly to how AI systems understand and perform real software engineering</li><li>Potential for ongoing work and contract extension as new projects launch</li></ul>

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