Content Translator

We need to output HTML fragment with sections: About Bixal? The posting includes "About Bixal" paragraph. Also "Opportunity Overview". Also "Key Responsibilities". Also "Required Qualifications". Also "Compensation". Also "Important Notes" maybe not needed? The instructions: include a section ONLY when posting has real, specific content for it. Use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we can map content to these headings. The posting has "About Bixal" (company description) maybe not exactly "About the role". Could use "About the role" heading for opportunity overview? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings if we have content. We need to decide which sections to include based on content. We have: - About Bixal (company description) could go under "About the role"? Actually "About the role" is about the role, not company. But we could treat "About Bixal" as "About the role"? Might be okay. But we could also not include a heading if not matching exactly? The instruction says use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use

for section headings (e.g. About the role, Responsibilities...). Likely they expect us to use those headings where appropriate. We can also include other headings if needed? Safer to stick to those. We have content for: - About the role: we have "Opportunity Overview" describing role. So we can put that under

About the role

. - Responsibilities: we have "Key Responsibilities". So

Responsibilities

. - Requirements / Qualifications: we have "Required Qualifications". Could split into Requirements and Qualifications but we have both. We could put under

Requirements

and maybe also

Qualifications

if we split. But we have only one block; we could put under Requirements and not duplicate. Or we could put under Qualifications. The instruction: prefer a few substantive sections over many thin ones. So maybe combine Requirements and Qualifications into one section? But they gave separate headings. We could choose to use either Requirements or Qualifications. Since the block is titled "Required Qualifications", maybe use Qualifications heading. Let's use

Qualifications

. - Skills: we could extract skills from qualifications but not separate. Might be thin. Better not to create Skills section if not explicit. - Pay: we have compensation: $50 an hour. So

Pay

with that. - Benefits: posting says "Bixal does not provide benefits or equipment for independent contractors." That's a statement about benefits (none). The instruction: never create Benefits section unless posting actually states them. It does state that there are no benefits. Should we include? It says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them (that there are none). So we could include Benefits section with that statement. However also note "Important Notes" includes that. Could be considered benefits info. We'll include Benefits section with that statement. - Schedule: posting says part-time position at 50% allocation, set your own hours. So we have schedule info. So

Schedule

with that. We must not repeat job title as heading. Not include Job ID etc. Remove boilerplate like Important Notice For Applicants, etc. Also remove "Important Notes" maybe we already used for Benefits/Sched. But we need to preserve substantive information: the part about 1099 independent contractor, reside in US, obtain Public Trust determination, etc. Those are important notes; we need to preserve them somewhere. Could be included under Qualifications? Or maybe under a generic section? But we only have allowed headings. Could we add a paragraph after sections without heading? The instruction: Output ONLY the HTML fragment. It didn't forbid extra paragraphs not under headings. It said use

for section headings (e.g...). Use

• for any list of duties/requirements/benefits, and

  for prose. So we can have

  paragraphs for prose not under headings. So we can include important notes as paragraphs after sections. Thus structure:

  About the role

  Opportunity Overview paragraph...

  Responsibilities

  • ... each responsibility

  Qualifications

  • ... each qualification

  Pay

  $50 an hour.

  Benefits

  Bixal does not provide benefits or equipment for independent contractors.

  Schedule

  Part-time position at 50% allocation; you can set your own hours as a 1099 independent contractor.

  Then after that, we can include additional paragraphs for important notes: "This is a 1099 consulting opportunity, not a full-time or part-time employment position. Bixal does not provide benefits or equipment for independent contractors. All applicants must reside in and be authorized to work in the United States. Must be able to obtain and maintain a favorable Public Trust determination in support of a federal government contract." Also maybe the earlier statement about official communication etc. That is boilerplate? It's about application process; maybe we should remove as per instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The "Important Notice For Applicants At Bixal..." is about official communication; could be considered scam-warning boilerplate? Likely to remove. So we drop that. We also need to include the description about Bixal mission-driven organization etc. That's under "About Bixal". Should we include that? It's substantive about company. Could be placed under About the role? Or we could add a separate

  About Bixal

  but not in allowed headings. Maybe we can include it as a paragraph under About the role? The About the role section should describe the role, not company. But we could add a separate paragraph before About the role heading? The instruction: do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. It didn't forbid other headings besides the listed ones, but they gave examples. Safer to stick to those headings and put company description as a paragraph under About the role or maybe as a separate

  before any heading. We could do:

  About Bixal: Bixal is a mission-driven organization...

  Then

  About the role

  with opportunity overview. Let's craft. Now need to preserve all substantive information: ensure we don't lose any details. Let's extract details: About Bixal paragraph: "Bixal is a mission-driven organization that partners with leading federal agencies to design and deliver people-centered digital solutions. We are a diverse group of strategists, designers, technologists, and data scientists who believe in using design and technology to make government services more accessible and effective for all." Opportunity Overview: "Bixal supports a large, federally funded public information and communications program that serves families and professionals across the country. The program's digital ecosystem includes a high-traffic public website, mobile applications, an online professional community, and a customer support center, reaching millions of visitors each year. A significant share of the audience is Spanish-speaking, and the program is committed to delivering accurate, high-quality, and culturally responsive information in both English and Spanish across every channel. Bixal is seeking a detail-oriented, culturally fluent Spanish Content Translator to support this program. This role is central to ensuring Spanish-speaking users receive the same high-quality, accurate, and accessible information as English-speaking users. This is a part-time position at 50% allocation, ideal for an experienced translator who wants steady, meaningful work supporting a high-visibility public-facing platform. As a 1099 independent contractor, you will operate independently, provide your own tools, set your own hours, and invoice Bixal for completed work." Key Responsibilities list: - Produce high-quality Spanish translations of website content, including web pages, PDFs, video captions/subtitles, and learning modules, working within a translation management platform. - Maintain and continuously improve a glossary of terms to ensure consistent terminology and translation quality across all program digital properties. - Provide live simultaneous Spanish interpretation for webinars and webcasts throughout the year, with audiences ranging from the hundreds to several thousand participants. - Translate and review Spanish-language content for email campaigns, social media, and the customer service center's public-facing responses and knowledge base. - Partner with the UX research team to support usability testing, interviews, and surveys with Spanish-speaking users, ensuring translated materials are tested for clarity and cultural relevance. - Review translated content for compliance with plain-language standards and accessibility requirements. - Collaborate with content strategists, designers, and engineers to ensure translated materials are published accurately and on schedule. - Perform other duties as required. Required Qualifications list: - Native or professional-level fluency in both Spanish and English (written and spoken), with demonstrated translation and interpretation experience. - Professional translation or interpretation certification preferred (e.g., ATA certification or equivalent). - Experience with translation management systems (e.g., Lingotek or similar) strongly preferred. - Prior experience providing live/simultaneous interpretation for webinars, conferences, or public events. - Strong writing skills with close attention to accuracy, tone, and cultural nuance. - Familiarity with plain-language and accessibility standards is a plus. - Experience translating content for a government or public-sector client is a plus. - Bachelor's degree in translation, linguistics, communications, or a related field, or equivalent professional experience. - Must be able to obtain and maintain a favorable Public Trust determination in support of a federal government contract. Compensation: "$50 an hour." Important Notes (we will incorporate): - This is a 1099 consulting opportunity, not a full-time or part-time employment position. - Bixal does not provide benefits or equipment for independent contractors. - All applicants must reside in and be authorized to work in the United States. - We leverage technology, communications, data, and human-centered design to help governments and leading organizations be more efficient, effective, and impactful. (This is a tagline maybe boilerplate? It's at end; could be considered boilerplate but it's about company mission; we already have About Bixal. Might be redundant; we could drop as it's repetitive.) We already have Benefits section about no benefits. Also we have Schedule section about part-time 50% allocation, set own hours. We also need to mention that as a 1099 independent contractor you will operate independently, provide your own tools, set your own hours, and invoice Bixal for completed work. That's already in Opportunity Overview; we can keep there. Now ensure we don't include any boilerplate like "Important Notice For Applicants At Bixal..." etc. Now construct HTML. We'll start with a paragraph for About Bixal. Then

  About the role

  with paragraph containing Opportunity Overview. Then

  Responsibilities

  with
  • ... each. Then

    Qualifications

    with
    • ... each. Then

      Pay

      with

      $50 an hour.

      Then

      Benefits

      with

      Bixal