Jobs · Administrative · Florida

Malay Transcriber

Productive Playhouse · Orlando, FL · 1 mo ago
Administrative$21/hrFull-time
We need to output HTML fragment with sections only if real content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only those sections that have real specific content. Let's parse the posting: - Location: Orlando, FL office (not remote) – location info, but we are told not to repeat job title as heading, and not to put Job ID etc. We can fold minor metadata into a short

or drop it. Probably we can include location in a

at top? 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." So we can include location in a

before sections. - Status: Project-based – maybe minor metadata, can be in

. - Pay: $21.00 USD per hour – this is specific pay, so we should include a Pay section with that content. - Benefits: Flexible schedule – Benefits section. - Hours: 8-40 per week – Schedule section. - Requirement: Fluent reading, writing, understanding, and typing in Malay (ms_my) – this is a requirement, could go under Requirements. - Why Join Us? Daily Perks & Occasional Treats..., Culture & Connection..., Growth & Impact: This is like Benefits? Actually these are perks/benefits/culture. Could be part of Benefits section or maybe separate? The instruction says Benefits section only if posting actually states them. It does state benefits: Flexible schedule, Daily Perks & Occasional Treats, Culture & Connection, Growth & Impact. So we can include Benefits section with those bullet points. - "We are seeking a detail-oriented and motivated Malay Transcriber to join our team." This is about the role; could be About the role section. - Then responsibilities list: many bullet points. - Qualifications & Skills: list. - Requirements: list (including high school diploma, etc.) - Physical Requirements: list. - About Us: description. We need to decide which sections to include: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for: - About the role: we have a paragraph describing the role: "We are seeking a detail-oriented and motivated Malay Transcriber to join our team. In this role, you will be responsible for converting audio and video recordings into written text accurately and efficiently, while maintaining knowledge of client-specific conventions and standards. The ideal candidate will have strong listening skills, excellent grammar, and a keen eye for detail." That's substantive. - Responsibilities: we have a list of duties (Key Responsibilities). So include. - Requirements: we have "Requirement: Fluent reading, writing, understanding, and typing in Malay (ms_my)" plus later "Requirements" section with high school diploma etc. So combine. - Qualifications & Skills: we have a section titled "Qualifications & Skills:" with bullet list. So include Qualifications and Skills maybe combined? The instruction says separate headings for Qualifications and Skills. But we could put both under one heading? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should have separate headings if we have content for each. The posting has "Qualifications & Skills:" as a combined heading. We could split into Qualifications and Skills sections, but we need to ensure we don't create empty sections. We have content that includes both qualifications and skills mixed. We could put all under Qualifications, and leave Skills empty? Not allowed. Better to combine them under one heading, but the instruction expects separate headings if we have content. However we could treat "Qualifications & Skills" as one section heading "Qualifications" and include skills there, and not create a separate Skills heading because we don't have distinct skills-only content. The instruction: "Prefer a few substantive sections over many thin ones." So we can combine. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. Possibly also About Us? Not in list of allowed headings; we could treat as About the role? But About Us is separate. The allowed headings list does not include About Us, but we could still include it? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for those sections. Probably we should stick to those. About Us could be considered "About the role"? Not exactly. Might be better to omit About Us as it's not requested. However we must preserve ALL substantive information; we cannot omit About Us description. But we could incorporate it into About the role section? The About Us is about the company, not the role. The instruction says preserve ALL substantive information; do not invent or summarize away detail. If we omit About Us, we lose info. So we need to include it somewhere. Perhaps we can add a section "About the company" but not in allowed list. However the instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exhaustive. So we can add other headings as needed, but we should follow the pattern. Safer to include an

About Us. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule, About Us. We must not include empty headings. Now we need to format lists with
  • . For prose, use

    . We need to drop boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting includes a Disclaimer about background screening, diversity statement, accommodations contact. That's boilerplate/EEO; we should remove. Also remove "Why Join Us?" heading? We'll incorporate its content into Benefits. Now craft HTML. Start with a

    for location and status maybe: "Location: Orlando, FL office (not remote). Status: Project-based." Then sections. Let's extract content precisely. About the role: combine the introductory sentences. From posting: "We are seeking a detail-oriented and motivated Malay Transcriber to join our team. In this role, you will be responsible for converting audio and video recordings into written text accurately and efficiently, while maintaining knowledge of client-specific conventions and standards. The ideal candidate will have strong listening skills, excellent grammar, and a keen eye for detail." That's good. Responsibilities: list from "Key Responsibilities" bullet points. Let's list them: - Listen to audio recordings and accurately transcribe spoken content into text format, following project-specific guidelines, including formatting, punctuation, and grammar. - Perform superior transcription work for all assigned client projects, adhering to client-specific Written Domain Conventions. - Maintain continuous knowledge of extensive client-written Doman Conventions and “clean room” policies. Refer to current training materials and guidelines as needed to ensure compliance and quality. - Review and proofread transcripts for accuracy and completeness. - Report any technical issues or concerns to the appropriate channels promptly. - Suggest opportunities for process improvement to enhance efficiency and quality. - Manage time effectively to meet established deadlines and maintain high levels of productivity and quality. - Handle confidential information with discretion and adhere to all privacy and security guidelines. - Participate in other projects and tasks as assigned. Note there is a typo "Doman Conventions" but we keep as is. Requirements: we have: - Requirement: Fluent reading, writing, understanding, and typing in Malay (ms_my) - High school diploma or equivalent, additional training in linguistics, transcription, or related fields is a plus. - Must be authorized to work in the United States; the company does not provide any work sponsorship. - Minimum age: 18 years or older. - Reliable transportation to commute to on-site facilities, as required. - Proficiency in reading and typing in the specific language applied for, with the ability to understand a wide range of accents and dialects; candidates will be required to pass a language assessment test. Also there is "Physical Requirements" separate list; but we could include under Requirements or separate section? The instruction only lists Requirements heading; we could include physical requirements under Requirements as well. But we might also create a separate "Physical Requirements" heading if we want to preserve. However not in allowed list but could be added. To keep few sections, we can include physical requirements under Requirements as a sublist? But we need to use

    • for any list. We could have a nested list? Simpler: include physical requirements as part of Requirements list. Physical Requirements list: - Ability to move around the office and other work environments, including standing and walking for extended periods. - Ability to remain seated for extended periods while working on a computer, including typing and screen-focused tasks. - Ability to bend, reach, and perform tasks that require physical agility within a typical office setting - Manual dexterity to operate a keyboard and mouse efficiently. - Ability to wear headphones for extended periods while listening to audio content. - Capacity to perform repetitive tasks, such as typing, with sustained concentration. We'll include those as list items. Qualifications & Skills: list: - Typing speed of 40 WPM in Malay (ms_my) or higher is preferred. - Exceptional written and verbal communication skills, with strong attention to punctuation, grammar, and spelling. - Ability to quickly learn and adapt to client-specific style guides and written domain conventions. - Strong research abilities, particularly for verifying the accurate spelling of names, locations, and products. - Proficiency with both Mac and PC platforms, Microsoft Office Suite, and Google Workspace. - Excellent interpersonal skills with the ability to communicate effectively across all levels of the organization. - Strong relationship-building skills, capable of fostering connections across diverse perspectives and methods. - Demonstrated ability to consistently meet deadlines and maintain high standards of work. - Ability to listen to and handle sensitive information with professionalism and maintain strict confidentiality. We'll put under Qualifications heading. Benefits: from "Benefits: Flexible schedule" plus Why Join Us? content. Benefits items: - Flexible schedule - Daily Perks & Occasional Treats: Fully stocked snack bars to keep you powered up every day, plus periodic team lunches and social events on the house. - Culture & Connection: Join a friendly, collaborative environment where team members genuinely support one another. - Growth & Impact: We invest in our people. We prioritize internal promotions and clear career pathways so you can build a long-term future here. Also maybe "With Productive Playhouse, native Malay speakers can make extra money by working flexible hours!" but that's more about pay. We'll format as list. Pay: "$21.00 USD per hour" Schedule: "Hours: 8-40 per week" About Us: description from "About Us" paragraph. Let's extract: "As a global data company, Productive Playhouse “PPH”, is pioneering our approach to language and data services, while incorporating their roots as a production company. Originally creating content to support children's language acquisition, our commitment to excellence, forward-thinking strategies, and world-wide cultural experience has proven key for delivering exceptional service. Originally founded as an educational production company, Productive Playhouse made a mark with our award winning children’s series, which taught fundamental subjects through engaging and effective programming. This early success paved the way for our evolution into a comprehensive data services provider. Since 2011, Productive Playhouse has expanded rapidly to offer an extensive suite of data services. Our current offerings include transcription, translation, linguistic analysis, rating, systems testing, localization, field and studio recording, language skill verification, and specialized data handling with a focus on sensitivity and diversity. Our commitment to innovation means we continually enhance our service portfolio to meet the evolving needs of our clients. At Productive Playhouse, we are proud of our reputation for addressing

Similar jobs

Malay Over the Phone Interpreter

Global Impact Group LLCRaleigh, NC· 2 mo ago
RemoteInformation Technology$25–$30/hrapply on global-language-system-llc.careerplug.com

Transcriber

Delta Alpha Pi-Gamma Omicron ChapterIndiana, United States· 2 mo ago
Administrativeapply on sds.utk.edu