Job Description
for paragraphs,
for section headers, - for lists, no CSS classes, no inline styles, no s, no
tags. Preserve all original content word-for-word. Return only HTML.
First, I need to parse the input text. It's a mix of HTML tags and plain text. The input already contains some HTML tags like
, , , , , , - , . But the instruction says to format as clean semantic HTML, so I should strip out the existing HTML tags and restructure properly. However, the rule says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". That includes the text content, but the existing HTML tags are formatting, not content. I think I should treat the input as raw text with some HTML tags, but I need to output clean HTML without those tags. The input includes tags like
, , etc. I should ignore those and just extract the text content, then structure it.
But the instruction: "You receive a plain-text job description." However, the provided job description includes HTML tags. That might be a mistake; perhaps the input is already HTML but they want it cleaned. The rules say "Return ONLY the HTML. No markdown fences, no explanation, no preamble." So I need to produce HTML.
I'll parse the text, identify sections, and wrap accordingly.
Let me go through the content:
1. "Job Summary:" - section header, then a paragraph.
2. "Accountabilities:" - section header, then "Technical Requirements:" maybe sub-header? But the rule says use
for section headers like Responsibilities, Qualifications, etc. "Accountabilities" could be a header. Then there's a list of bullet points (ul/li). The input already has - but I'll restructure.
3. "Applied Knowledge & Skills:" - header, then list.
4. "Supervision Given/Received:" - header, then list.
5. "Education: ** **" - header, then list.
6. "Experience: **" - header, then list.
7. "Typical Physical Demands:" - header, then list.
8. "Technology to be Used:" - header, then list.
9. "Travel Requirements:" - header, then list.
10. "How to Apply:" - header, then paragraph (includes bold text).
11. Salary range paragraph.
12. Disclaimer paragraph.
13. Equal opportunity employer paragraph.
14. Safeguarding paragraph.
15. Criminal histories paragraph.
16. Security notice paragraph with email link.
17. Benefits paragraph with link.
18. Final paragraph with link.
I need to preserve all text exactly. For links, I should keep the anchor tags? The rule says no CSS classes, no inline styles, no s, no
tags. But anchor tags are allowed? They are semantic HTML. The input includes tags. I should preserve them as they are part of the content. However, the rule says "Use for introductory paragraphs and general text, Use
for section headers, Use - for list items". It doesn't forbid . I think I should keep the links as they are.
But the input has some HTML entities like @ for @, and ' for '. I should preserve them as they appear in the text? The rule says preserve ALL original content word-for-word. So I should keep the entities as they are.
Also, there are some stray characters like " " (non-breaking space). I'll keep them.
Now, I need to output HTML without any extra tags. I'll write the HTML directly.
Let's structure:
Job Summary
Regional Technical Officer, Tuberculosis (TB) provides technical expertise and support for implementing and scaling up comprehensive TB prevention, screening, diagnosis and treatment, within the EpiC Project in Tanzania. This role supports the integration of TB and HIV services across Police and Prison (PnP) health facilities and strengthens TB services within public health facilities to ensure early case detection, diagnosis, timely treatment initiation and completion. The role works closely with the Ministry of Health, the Police Medical Unit (PMU), the Prisons Health and Nutrition Unit (PHNU), the Prime Minister’s Office–Regional Administration and Local Government (PMO-RALG), Regional and Council Health Management Teams (RHMTs/CHMTs), facility teams, and implementing partners to strengthen the delivery of high-quality, equitable, and client-centered TB services, including TB/HIV collaborative activities in accordance with national guidelines and global recommendations.
Accountabilities
Technical Requirements:
- Provides technical support to regional technical teams, health facilities and community platforms in the planning, implementation, monitoring, and scale-up of TB interventions.
- Supports implementation of quality TB screening, active case finding, diagnosis, treatment, TB preventive treatment (TPT), TB/HIV collaborative services, DR-TB, and TB infection prevention and control (IPC) in line with national standards.
- Ensures TB service delivery is implemented in accordance with Tanzania MOH/NTLP guidelines and approved project standards.
- Support integration of TB services within HIV in public, PnP facilities, and community platforms to improve TB case identification, linkage, treatment initiation, adherence, and continuity of care.
- Conduct mentorship, coaching, supportive supervision, on-the-job training, and clinical case reviews to strengthen health worker capacity and improve the quality of TB services.
- Routinely review TB program data and performance, including TB screening, case notification, diagnosis, treatment initiation, TPT, treatment outcomes, and TB/HIV indicators, to identify gaps and recommend corrective actions.
- Supports facilities to develop and implement site-level improvement plans and follow up on agreed actions to address identified TB service delivery gaps.
- Supports the implementation of TB/HIV collaborative activities, including TB screening among PLHIV, HIV testing among TB clients, linkage to ART, TPT provision, adherence, retention, and appropriate referral and follow-up.
- Supports identification, referral, treatment monitoring, and follow-up of clients with drug-resistant TB in collaboration with facility teams and relevant TB program structures.
- Promotes accurate, complete, and timely documentation and reporting of TB services through routine and digital health information systems.
- Conducts data quality checks and supports reconciliation of TB program data across registers, reporting tools, and electronic systems to improve data accuracy and use.
- Work closely with R/CHMTs, facility teams, and other implementing partners to coordinate implementation of TB activities and address service delivery challenges.
- Document and share lessons learned, best practices, innovations, and successful TB interventions to support continuous quality improvement and scale-up.
- Demonstrate effective teamwork, accountability, communication, analytical, problem-solving, coordination, and stakeholder engagement skills in supporting TB program implementation.
Applied Knowledge & Skills
- Knowledge of TB prevention, screening, diagnosis, treatment, TB/HIV collaborative services, and DR-TB management, including national service delivery guidelines and quality standards.
- Knowledge of Tanzania MOH/NTLP guidelines, reporting requirements, and quality standards related to TB and TB/HIV programs
- Ensure Leadership, team management, collaboration, and stakeholder engagement skills.
- Strong knowledge of quality assurance and continuous quality improvement principles.
- Excellent verbal, written, and interpersonal communication skills, with the ability to effectively communicate technical information clearly to R/CHMT and health care providers.
- Demonstrates cultural sensitivity and diversity as well as understanding of the political, contextual, and ethical issues in assigned work.
- Strong organizational and analytical skills with the ability to interpret data, identify issues, and provide recommendations for improvement.
- Demonstrated project management skills.
- Collaborative influencing skills, and ability to work effectively across multidisciplinary teams and build productive relationships with stakeholders.
- Demonstrated proficiency in Microsoft Office Suite (Word, Excel, PowerPoint, and Outlook).
- Ability to identify operational and programmatic challenges, conduct root-cause analysis, develop practical solutions, solve problems and implement corrective actions to improve program performance.
- Fluency in English and Kiswahili.
Supervision Given/Received
- Mentors’ health facility staff and strengthens their technical capacity and performance.
- Reports to the Regional Senior Technical Officer – Clinical Services.
Education
- Medical Degree (MD) or Nursing degree from a recognized institution
- A master’s degree in public health (MPH) or international equivalent is an added advantage.
Experience
- Minimum of four (4) years of progressive experience in TB and TB/HIV programming, including prevention, diagnosis, and treatment, preferably within donor-funded public health programs.
- Demonstrated experience providing technical assistance and capacity strengthening to government health authorities, RHMTs/CHMTs, health facility teams, and implementing partners to improve TB and TB/HIV service outcomes.
- Demonstrated ability to analyze, interpret, and utilize TB program data to identify gaps, monitor performance, and drive program improvement.
- Experience mentoring and providing technical guidance to junior staff and facility-level teams.
Typical Physical Demands
- Typical office environment.
- Ability to spend long hours looking at computer screens and doing repetitive work on a keyboard.
- Ability to sit and stand for extended periods of time.
- Ability to lift/move up to 5 lbs.
Technology to be Used
- Personal Computer/Laptop, Microsoft applications (i.e., Office 365, SharePoint, Skype/Zoom/Teams), cell phone/mobile technology, and standard office equipment.
Travel Requirements
- 10% - 25% domestic travel to councils and health facility project sites to provide technical assistance, supportive supervision, stakeholder engagement, and implementation support.
How to Apply
FHI360 offers a competitive compensation package, and qualified candidates are invited to apply online by submitting an application letter, CV/resume, photocopies of certificates, and the names and contact details of three professional referees. FHI 360 is an Equal Opportunity Employer. Closing Date: 26 October 2026. Only short listed candidates will be contacted.
The expected hiring salary range for this role is TZS 52,000,000 - 65,000,000 for annual basic salary. When determining an offer amount, FHI 360 factors in multiple considerations, including but not limited to: relevant years of experience and education possessed by the applicant, internal equity, market pay, and budget. For internal candidates, salary placement will also follow FHI 360’s current promotional increase guidelines.
This job posting summarizes the main duties of the job. It neither prescribes nor restricts the exact tasks that may be assigned to carry out these duties. This document should not be construed in any way to represent a contract of employment. Management reserves the right to review and revise this document at any time.
FHI 360 is an equal opportunity employer whereby we do not engage in practices that discriminate against any person employed or seeking employment based on race, color, religion, sex, sexual orientation, gender identity, national or ethnic origin, age, marital status, physical or mental disability, protected Veteran status, or any other characteristic protected under applicable law.
Our values and commitments to safeguarding: FHI 360 is committed to preventing any type of abuse, exploitation and harassment in our work environments and programs, including sexual abuse, exploitation and harassment. FHI 360 takes steps to safeguard the welfare of everyone who engages with our organization and programs and requires that all personnel, including staff members and volunteers, share this commitment and sign our code of conduct. All offers of employment will be subject to appropriate screening checks, including reference, criminal record and terrorism finance checks. FHI 360 also participates in the Inter-Agency Misconduct Disclosure Scheme (MDS), facilitated by the Steering Committee for Humanitarian Response. In line with the MDS, we will request information from job applicants’ previous employers about any substantiated findings of sexual abuse, exploitation and/or harassment during the applicant’s tenure with previous employers. By applying, job applicants confirm their understanding of these recruitment procedures and consent to these screening checks.
FHI 360 will consider for employment all qualified applicants, including those with criminal histories, in a manner consistent with the requirements of applicable state and local laws.
FHI 360 will never ask you for your career site username or password, and we will never request money, goods or services during the application, recruitment or employment process. If you have questions or concerns about correspondence from us, please email CareerCenterSupport@fhi360.org.
FHI 360 fosters the strength and health of its workforce through a competitive benefits package, professional development and policies and programs that support a healthy work/life balance. Join our global workforce to make a positive difference for others — and yourself.
Please click here to continue searching FHI 360's Career Portal.
Note: The last paragraph has a
and a non-breaking space. I should not include
. I'll just keep the text as a paragraph, but the
is a line break. Since rule says no
tags, I'll omit it. The text " " maybe just a space. I'll include the text before the
and after? Actually the input: "Please click here to continue searching FHI 360's Career Portal.
". So there is a line break and a non-breaking space. I'll just put the whole sentence in a paragraph, ignoring the
and the trailing space.
Also, there are some bold and italic tags in the original. The rule says preserve all original content word-for-word. That includes the formatting? The content is the text, not the tags. But the tags like , are formatting. However, the instruction says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". That might mean keep the text exactly as it appears, including any HTML tags? But the output should be clean semantic HTML. The input already has HTML tags. The user likely wants us to clean up the HTML, not keep the messy tags. The rules: "Use for introductory paragraphs and general text, Use
for section headers, Use - for list items". So we should not keep the original , , tags. But the text inside them is content. For example, "Job Summary:" is wrapped in . We'll just output the text as header. For the "How to Apply" paragraph, there is bold text. Should we keep the bold? The rule doesn't forbid or . It says no CSS classes, no inline styles, no s, no
tags. It doesn't say no or . But it says "clean semantic HTML". Typically, semantic HTML uses and . However, the rule doesn't specify. I think we can keep the bold and italic if they are in the original text? But the original text includes them as tags. The instruction: "Preserve ALL original content word-for-word". That could be interpreted as preserve the text content, not the markup. Since we are generating new HTML, we can decide to keep the emphasis. But the rule says "Use for introductory paragraphs and general text". It doesn't mention inline formatting. I think it's safer to keep the bold and italic as they appear in the text, but as HTML tags. However, the original has nested tags like . That's messy. I'll keep the text as is, but if there are bold sections, I'll wrap them in tags. But the rule says "clean semantic HTML". Might be better to not include any formatting tags, just plain text. But the content includes "FHI 360 is an Equal Opportunity Employer. Closing Date: 26 October 2026." which is bold in the original. That might be important. I'll keep the bold tags for that sentence. Similarly, the salary paragraph is italic and bold. I'll keep those tags.
But the rule says "No CSS classes, no inline styles, no s, no
tags". It doesn't forbid , , . So I'll keep them
Apply Now ↗
How well do you match?
Get an instant AI match score for this role — free, takes 3 minutes.
Tailor your CV for this role
The concierge rewrites your whole CV and writes a matching cover letter for this job — opens right here, nothing to paste.
Tailor My CV to This Job ✍️
Free cover letter for this job
Upload your CV and get a tailored cover letter in seconds — free, no account needed.
Generate a Cover Letter 📝
tags. Preserve all original content word-for-word. Return only HTML. First, I need to parse the input text. It's a mix of HTML tags and plain text. The input already contains some HTML tags like
,
, , , , , etc. I should ignore those and just extract the text content, then structure it.
But the instruction: "You receive a plain-text job description." However, the provided job description includes HTML tags. That might be a mistake; perhaps the input is already HTML but they want it cleaned. The rules say "Return ONLY the HTML. No markdown fences, no explanation, no preamble." So I need to produce HTML.
I'll parse the text, identify sections, and wrap accordingly.
Let me go through the content:
1. "Job Summary:" - section header, then a paragraph.
2. "Accountabilities:" - section header, then "Technical Requirements:" maybe sub-header? But the rule says use for introductory paragraphs and general text, Use Regional Technical Officer, Tuberculosis (TB) provides technical expertise and support for implementing and scaling up comprehensive TB prevention, screening, diagnosis and treatment, within the EpiC Project in Tanzania. This role supports the integration of TB and HIV services across Police and Prison (PnP) health facilities and strengthens TB services within public health facilities to ensure early case detection, diagnosis, timely treatment initiation and completion. The role works closely with the Ministry of Health, the Police Medical Unit (PMU), the Prisons Health and Nutrition Unit (PHNU), the Prime Minister’s Office–Regional Administration and Local Government (PMO-RALG), Regional and Council Health Management Teams (RHMTs/CHMTs), facility teams, and implementing partners to strengthen the delivery of high-quality, equitable, and client-centered TB services, including TB/HIV collaborative activities in accordance with national guidelines and global recommendations. Technical Requirements: FHI360 offers a competitive compensation package, and qualified candidates are invited to apply online by submitting an application letter, CV/resume, photocopies of certificates, and the names and contact details of three professional referees. FHI 360 is an Equal Opportunity Employer. Closing Date: 26 October 2026. Only short listed candidates will be contacted. The expected hiring salary range for this role is TZS 52,000,000 - 65,000,000 for annual basic salary. When determining an offer amount, FHI 360 factors in multiple considerations, including but not limited to: relevant years of experience and education possessed by the applicant, internal equity, market pay, and budget. For internal candidates, salary placement will also follow FHI 360’s current promotional increase guidelines. This job posting summarizes the main duties of the job. It neither prescribes nor restricts the exact tasks that may be assigned to carry out these duties. This document should not be construed in any way to represent a contract of employment. Management reserves the right to review and revise this document at any time. FHI 360 is an equal opportunity employer whereby we do not engage in practices that discriminate against any person employed or seeking employment based on race, color, religion, sex, sexual orientation, gender identity, national or ethnic origin, age, marital status, physical or mental disability, protected Veteran status, or any other characteristic protected under applicable law. Our values and commitments to safeguarding: FHI 360 is committed to preventing any type of abuse, exploitation and harassment in our work environments and programs, including sexual abuse, exploitation and harassment. FHI 360 takes steps to safeguard the welfare of everyone who engages with our organization and programs and requires that all personnel, including staff members and volunteers, share this commitment and sign our code of conduct. All offers of employment will be subject to appropriate screening checks, including reference, criminal record and terrorism finance checks. FHI 360 also participates in the Inter-Agency Misconduct Disclosure Scheme (MDS), facilitated by the Steering Committee for Humanitarian Response. In line with the MDS, we will request information from job applicants’ previous employers about any substantiated findings of sexual abuse, exploitation and/or harassment during the applicant’s tenure with previous employers. By applying, job applicants confirm their understanding of these recruitment procedures and consent to these screening checks. FHI 360 will consider for employment all qualified applicants, including those with criminal histories, in a manner consistent with the requirements of applicable state and local laws. FHI 360 will never ask you for your career site username or password, and we will never request money, goods or services during the application, recruitment or employment process. If you have questions or concerns about correspondence from us, please email CareerCenterSupport@fhi360.org. FHI 360 fosters the strength and health of its workforce through a competitive benefits package, professional development and policies and programs that support a healthy work/life balance. Join our global workforce to make a positive difference for others — and yourself. Please click here to continue searching FHI 360's Career Portal. for introductory paragraphs and general text, Use for introductory paragraphs and general text". It doesn't mention inline formatting. I think it's safer to keep the bold and italic as they appear in the text, but as HTML tags. However, the original has nested tags like . That's messy. I'll keep the text as is, but if there are bold sections, I'll wrap them in tags. But the rule says "clean semantic HTML". Might be better to not include any formatting tags, just plain text. But the content includes "FHI 360 is an Equal Opportunity Employer. Closing Date: 26 October 2026." which is bold in the original. That might be important. I'll keep the bold tags for that sentence. Similarly, the salary paragraph is italic and bold. I'll keep those tags.
But the rule says "No CSS classes, no inline styles, no Get an instant AI match score for this role — free, takes 3 minutes. The concierge rewrites your whole CV and writes a matching cover letter for this job — opens right here, nothing to paste. Upload your CV and get a tailored cover letter in seconds — free, no account needed.,
, for section headers like Responsibilities, Qualifications, etc. "Accountabilities" could be a header. Then there's a list of bullet points (ul/li). The input already has
tags. But anchor tags are allowed? They are semantic HTML. The input includes tags. I should preserve them as they are part of the content. However, the rule says "Use for section headers, Use
Job Summary
Accountabilities
Applied Knowledge & Skills
Supervision Given/Received
Education
Experience
Typical Physical Demands
Technology to be Used
Travel Requirements
How to Apply
and a non-breaking space. I should not include
. I'll just keep the text as a paragraph, but the
is a line break. Since rule says no
tags, I'll omit it. The text " " maybe just a space. I'll include the text before the
and after? Actually the input: "Please click here to continue searching FHI 360's Career Portal.
". So there is a line break and a non-breaking space. I'll just put the whole sentence in a paragraph, ignoring the
and the trailing space.
Also, there are some bold and italic tags in the original. The rule says preserve all original content word-for-word. That includes the formatting? The content is the text, not the tags. But the tags like , are formatting. However, the instruction says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". That might mean keep the text exactly as it appears, including any HTML tags? But the output should be clean semantic HTML. The input already has HTML tags. The user likely wants us to clean up the HTML, not keep the messy tags. The rules: "Use for section headers, Use
tags. It doesn't say no or . But it says "clean semantic HTML". Typically, semantic HTML uses and . However, the rule doesn't specify. I think we can keep the bold and italic if they are in the original text? But the original text includes them as tags. The instruction: "Preserve ALL original content word-for-word". That could be interpreted as preserve the text content, not the markup. Since we are generating new HTML, we can decide to keep the emphasis. But the rule says "Use
tags". It doesn't forbid , , . So I'll keep themHow well do you match?
Tailor your CV for this role
Free cover letter for this job
Let jobs find you
Leave your email and our AI matches you to new jobs across 24 African markets — free. You wait for the call.
Add your CV for real matches
Upload your CV and we score every new job against your real experience — only strong matches reach your inbox. Optional, but it makes your matches far sharper.
You're in.
We'll email you the moment a job matches your profile. Check your inbox for a welcome from My Job Concierge.
I'm ECHO, your MJC career assistant. I can help you find jobs, explore career tools, and connect with opportunities across Africa.