Software Engineer (AI Training)
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include About the role as h3. Then we need sections for Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule only if content exists. We need to parse the posting. Content: About The Role: paragraph describing role. What You'll Do: list of duties. Who You Are: list of qualifications/requirements. Nice to Have: list of nice-to-have. Why Join Us: benefits? It's more like reasons to join; could be Benefits section. Also there is Organization, Type, Location, Commitment: these are metadata; we should fold into short p or drop. Not headings. We need to preserve all substantive info. We must not include boilerplate like EEO etc. Not present. We need to output only HTML fragment. We need to decide sections: - About the role (h3) with paragraph(s) from "About The Role" paragraph. - Responsibilities (h3) with ul list from "What You'll Do". - Requirements (h3) maybe combine "Who You Are" (required qualifications) and maybe also "Bachelor's degree..." etc. - Qualifications (h3) maybe for Nice to Have? But they said prefer few substantive sections over many thin ones. Could combine Requirements and Qualifications? But they have separate headings list; we can decide to include Requirements for required, and Qualifications for nice-to-have? Or we could have Skills section for technical skills. Let's think. The posting includes: Who You Are (required): - Proficient in one or more programming languages (list) - Solid understanding of data structures, algorithms, and software design principles - Able to read, write, and reason about code with clarity and precision - Strong problem-solving instincts and a systematic debugging approach - Clear written communicator — you can explain technical decisions in plain language - Self-motivated and reliable when working independently without supervision - Bachelor's degree in Computer Science, Software Engineering, or a related field — or equivalent practical experience Nice to Have: - Experience across multiple languages or tech stacks (full-stack, backend, systems, data engineering) - Familiarity with AI/ML concepts, LLMs, or prompt engineering - Background in code review, technical writing, or mentoring junior developers - Experience with cloud platforms, DevOps, or distributed systems - Competitive programming, open-source contributions, or side projects that demonstrate your craft - Advanced degree in Computer Science or related discipline Why Join Us: - Work on cutting-edge AI projects alongside leading research labs - Fully remote and flexible — set your own hours and work from anywhere - Freelance autonomy with intellectually stimulating, high-impact work - Directly influence how AI writes, understands, and reasons about code - Sharpen your own engineering skills by evaluating diverse problems daily - Potential for ongoing work and contract extension as new projects launch Also there is Organization: Alignerr, Type: Hourly Contract, Location: Remote, Commitment: 10–40 hours/week. This is metadata; we can put in a short p. Pay: Not mentioned. So we should NOT create Pay section. Schedule: Not explicitly given besides commitment 10-40 hours/week; that could be considered schedule? They said only create Schedule section if posting actually states them. The posting states commitment: 10–40 hours/week. That is schedule info. So we could include Schedule section with that detail. However they said prefer few substantive sections over many thin ones. Could we fold schedule into About the role or a metadata p? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." Schedule is not minor metadata? It's about hours. Could be considered metadata. But they said only create Schedule section if posting actually states them. It does state commitment. So we could create Schedule section with that info. However they also said prefer a few substantive sections over many thin ones. If we add Schedule, that's another section. Might be okay. Benefits: Why Join Us could be considered Benefits. So we can have Benefits section with those points. Thus sections: About the role, Responsibilities, Requirements, Qualifications (nice-to-have), Benefits, Schedule. We need to ensure we don't create empty sections. Now we need to output HTML fragment only, no or . Use
for each section heading. Use - for lists. Use
for prose.
We need to preserve all substantive information; do not invent or summarize away detail.
Let's craft.
About the role paragraph: "What if the code you write could directly shape how the next generation of AI understands and generates software? We're looking for Software Engineers in Raleigh to build, evaluate, and improve AI-generated code — helping train AI systems to think like real developers. You'll write solutions, review AI outputs, and provide the expert-level feedback that makes AI coding assistants smarter, safer, and more reliable. This is hands-on engineering work at the frontier of AI development — not theoretical, not bureaucratic, and not boring. This is a fully remote, flexible contract role. If you can write clean code and explain your reasoning, we want to hear from you."
We could also include Organization etc in a short p after About the role? The instruction: fold minor metadata into a short
or drop it. So we can add a p after About the role containing: "Organization: Alignerr • Type: Hourly Contract • Location: Remote • Commitment: 10–40 hours/week". That seems appropriate.
Now Responsibilities: list from "What You'll Do". Items:
- Write, debug, and optimize code across a range of languages, frameworks, and problem domains
- Review and evaluate AI-generated code for correctness, efficiency, readability, and best practices
- Identify bugs, logic errors, security issues, and performance bottlenecks in AI outputs
- Provide structured, detailed feedback explaining why code works — or doesn't
- Design challenging coding prompts and edge-case scenarios to stress-test AI capabilities
- Compare and rank multiple AI-generated solutions based on engineering quality
- Work independently and asynchronously — fully on your own schedule
Make each as
- .
Requirements: from "Who You Are". Items:
- Proficient in one or more programming languages (Python, JavaScript, Java, C++, Go, TypeScript, or similar)
- Solid understanding of data structures, algorithms, and software design principles
- Able to read, write, and reason about code with clarity and precision
- Strong problem-solving instincts and a systematic debugging approach
- Clear written communicator — you can explain technical decisions in plain language
- Self-motivated and reliable when working independently without supervision
- Bachelor's degree in Computer Science, Software Engineering, or a related field — or equivalent practical experience
Qualifications (nice-to-have): list from "Nice to Have". Items:
- Experience across multiple languages or tech stacks (full-stack, backend, systems, data engineering)
- Familiarity with AI/ML concepts, LLMs, or prompt engineering
- Background in code review, technical writing, or mentoring junior developers
- Experience with cloud platforms, DevOps, or distributed systems
- Competitive programming, open-source contributions, or side projects that demonstrate your craft
- Advanced degree in Computer Science or related discipline
Benefits: from "Why Join Us". Items:
- Work on cutting-edge AI projects alongside leading research labs
- Fully remote and flexible — set your own hours and work from anywhere
- Freelance autonomy with intellectually stimulating, high-impact work
- Directly influence how AI writes, understands, and reasons about code
- Sharpen your own engineering skills by evaluating diverse problems daily
- Potential for ongoing work and contract extension as new projects launch
Schedule: from commitment: "10–40 hours/week". Could be a simple
maybe inside Schedule section. Since it's just one line, we could put
10–40 hours/week
. Or we could include in metadata p earlier. But we already have metadata p. However schedule is specifically about hours; we could still include Schedule section with that detail.
But we already have metadata p with commitment. If we also add Schedule section, that duplicates. Better to fold commitment into metadata p and not create Schedule section, to avoid thin section. The instruction: prefer a few substantive sections over many thin ones. So we can omit Schedule section and include commitment in metadata p.
Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits.
Now check if any other info like Pay? Not present, so we omit.
Now ensure we don't repeat job title as heading. We are not.
Now output HTML.
We need to ensure proper nesting: each section: Heading
then content.
For About the role: we have paragraph(s) then metadata p.
Let's write:
About the role
What if the code you write could directly shape how the next generation of AI understands and generates software? We're looking for Software Engineers in Raleigh to build, evaluate, and improve AI-generated code — helping train AI systems to think like real developers. You'll write solutions, review AI outputs, and provide the expert-level feedback that makes AI coding assistants smarter, safer, and more reliable. This is hands-on engineering work at the frontier of AI development — not theoretical, not bureaucratic, and not boring. This is a fully remote, flexible contract role. If you can write clean code and explain your reasoning, we want to hear from you.
Organization: Alignerr • Type: Hourly Contract • Location: Remote • Commitment: 10–40 hours/week
But we used for emphasis; is that allowed? It's still HTML. It's fine.
Alternatively we could just plain text.
Now Responsibilities:
Responsibilities
- Write, debug, and optimize code across a range of languages, frameworks, and problem domains
- Review and evaluate AI-generated code for correctness, efficiency, readability, and best practices
- Identify bugs, logic errors, security issues, and performance bottlenecks in AI outputs
- Provide structured, detailed feedback explaining why code works — or doesn't
- Design challenging coding prompts and edge-case scenarios to stress-test AI capabilities
- Compare and rank multiple AI-generated solutions based on engineering quality
- Work independently and asynchronously — fully on your own schedule
Requirements:
Requirements
- Proficient in one or more programming languages (Python, JavaScript, Java, C++, Go, TypeScript, or similar)
- Solid understanding of data structures, algorithms, and software design principles
- Able to read, write, and reason about code with clarity and precision
- Strong problem-solving instincts and a systematic debugging approach
- Clear written communicator — you can explain technical decisions in plain language
- Self-motivated and reliable when working independently without supervision
- Bachelor's degree in Computer Science, Software Engineering, or a related field — or equivalent practical experience
Qualifications (nice-to-have):
Qualifications
- Experience across multiple languages or tech stacks (full-stack, backend, systems, data engineering)
- Familiarity with AI/ML concepts, LLMs, or prompt engineering
- Background in code review, technical writing, or mentoring junior developers
- Experience with cloud platforms, DevOps, or distributed systems
- Competitive
for prose. We need to preserve all substantive information; do not invent or summarize away detail. Let's craft. About the role paragraph: "What if the code you write could directly shape how the next generation of AI understands and generates software? We're looking for Software Engineers in Raleigh to build, evaluate, and improve AI-generated code — helping train AI systems to think like real developers. You'll write solutions, review AI outputs, and provide the expert-level feedback that makes AI coding assistants smarter, safer, and more reliable. This is hands-on engineering work at the frontier of AI development — not theoretical, not bureaucratic, and not boring. This is a fully remote, flexible contract role. If you can write clean code and explain your reasoning, we want to hear from you." We could also include Organization etc in a short p after About the role? The instruction: fold minor metadata into a short
or drop it. So we can add a p after About the role containing: "Organization: Alignerr • Type: Hourly Contract • Location: Remote • Commitment: 10–40 hours/week". That seems appropriate. Now Responsibilities: list from "What You'll Do". Items: - Write, debug, and optimize code across a range of languages, frameworks, and problem domains - Review and evaluate AI-generated code for correctness, efficiency, readability, and best practices - Identify bugs, logic errors, security issues, and performance bottlenecks in AI outputs - Provide structured, detailed feedback explaining why code works — or doesn't - Design challenging coding prompts and edge-case scenarios to stress-test AI capabilities - Compare and rank multiple AI-generated solutions based on engineering quality - Work independently and asynchronously — fully on your own schedule Make each as
maybe inside Schedule section. Since it's just one line, we could put
10–40 hours/week
. Or we could include in metadata p earlier. But we already have metadata p. However schedule is specifically about hours; we could still include Schedule section with that detail. But we already have metadata p with commitment. If we also add Schedule section, that duplicates. Better to fold commitment into metadata p and not create Schedule section, to avoid thin section. The instruction: prefer a few substantive sections over many thin ones. So we can omit Schedule section and include commitment in metadata p. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits. Now check if any other info like Pay? Not present, so we omit. Now ensure we don't repeat job title as heading. We are not. Now output HTML. We need to ensure proper nesting: each section:Heading
then content. For About the role: we have paragraph(s) then metadata p. Let's write:About the role
What if the code you write could directly shape how the next generation of AI understands and generates software? We're looking for Software Engineers in Raleigh to build, evaluate, and improve AI-generated code — helping train AI systems to think like real developers. You'll write solutions, review AI outputs, and provide the expert-level feedback that makes AI coding assistants smarter, safer, and more reliable. This is hands-on engineering work at the frontier of AI development — not theoretical, not bureaucratic, and not boring. This is a fully remote, flexible contract role. If you can write clean code and explain your reasoning, we want to hear from you.
Organization: Alignerr • Type: Hourly Contract • Location: Remote • Commitment: 10–40 hours/week
But we used for emphasis; is that allowed? It's still HTML. It's fine. Alternatively we could just plain text. Now Responsibilities:Responsibilities
- Write, debug, and optimize code across a range of languages, frameworks, and problem domains
- Review and evaluate AI-generated code for correctness, efficiency, readability, and best practices
- Identify bugs, logic errors, security issues, and performance bottlenecks in AI outputs
- Provide structured, detailed feedback explaining why code works — or doesn't
- Design challenging coding prompts and edge-case scenarios to stress-test AI capabilities
- Compare and rank multiple AI-generated solutions based on engineering quality
- Work independently and asynchronously — fully on your own schedule
Requirements
- Proficient in one or more programming languages (Python, JavaScript, Java, C++, Go, TypeScript, or similar)
- Solid understanding of data structures, algorithms, and software design principles
- Able to read, write, and reason about code with clarity and precision
- Strong problem-solving instincts and a systematic debugging approach
- Clear written communicator — you can explain technical decisions in plain language
- Self-motivated and reliable when working independently without supervision
- Bachelor's degree in Computer Science, Software Engineering, or a related field — or equivalent practical experience
Qualifications
- Experience across multiple languages or tech stacks (full-stack, backend, systems, data engineering)
- Familiarity with AI/ML concepts, LLMs, or prompt engineering
- Background in code review, technical writing, or mentoring junior developers
- Experience with cloud platforms, DevOps, or distributed systems
- Competitive