Technology Department, Tanzania.IT Quality Assurance Officer
KCB Group
Job Description
,
, - . Must preserve all original content word-for-word, no additions or removals. Must not add CSS classes, inline styles, no , no
. Must use for section headers like KEY RESPONSIBILITIES, DAILY RESPONSIBILITIES, MINIMUM POSITION QUALIFICATION REQUIREMENTS, etc. Also subheaders like "a. Academic & Professional", "b. Experience". Those could be considered section headers? The instruction: Use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). So we should treat each bold heading as a section header and wrap in . Also the subheadings "a. Academic & Professional" and "b. Experience" maybe also as ? They are sub-sections under MINIMUM POSITION QUALIFICATION REQUIREMENTS. Could treat them as as well. But we need to preserve content exactly, including spaces and entities like &. We must not remove entities? They are part of original content; we must preserve them. However HTML will treat as a space; it's okay to keep them. We must not add
. Also we must not keep any inline styles or classes. So we need to strip all style attributes, class attributes, etc. Also need to remove empty
tags? The instruction: Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. That suggests we should keep even empty paragraphs? But they are not content; they are formatting. However they said "Preserve ALL original content word-for-word". The empty
contains a non-breaking space entity; that is content. Should we keep it? It might be considered formatting but it's part of original. However the output must be clean semantic HTML; we could keep them as
. But they said no
tags, but is okay. We'll keep them.
We need to convert the given HTML into our target HTML.
Let's extract the textual content, preserving entities.
Original snippet:
KEY RESPONSIBILITIES
... etc.
We need to strip style attributes etc. So we will produce:
KEY RESPONSIBILITIES
- Champion and coordinate business requirements reviews across functional teams and ensures that the business requirements are complete, precise, and testable.
- Works with project team to define and create overall project test strategy/test plan, plan test schedules or strategies and Identifies test resources, estimates test effort in accordance with project scope or delivery dates and ensures that the test strategy is achieved.
- Develop, document, and maintain functional and non-functional test cases, test scripts and other test artifacts like test data, data validation, harness scripts and automated scripts.
- Works collaboratively with the business units and project teams to execute and validate test cases based upon business requirements and ensures that the test cases are traceable to the requirements.
- In collaboration with GEA and other critical stakeholders, tune the SQA processes, adopt tools and define re-usable templates in-line with the adoption and maturity of the SQA Framework.
- Define test process including required test activities and deliverables, conduct Test Readiness Assessment, establish test beds and ensure that test beds are available for all planned white box and black box testing activities.
- Provide support to Co Banking application (T24) issues, user profile management and tracking of all changes as requested by business team and as per the DCOE change process.
- Prepare, share and review test results periodically, report any defects, bugs, errors, configuration issues, and interoperability flaws and develop test acceptance reports for projects and software changes and ensure UAT optimal availability of UAT environments.
- Works with business units to perform post deployment sanity and regression tests and post-implementation review within defined period to confirm that the deployed solution works as per the business requirements.
- Participates in formulation and Implementation of Software process improvement policies and strategies for IT division.
DAILY RESPONSIBILITIES
- Develop, distribute, and coordinate in-depth business requirement reviews across functional teams and ensures that the business requirements are comprehensive, precise and testable.
- Develop, document and maintain functional and non-functional test cases, test scripts and other test artifacts like the test data, data validation, harness scripts and automated scripts.
- Provide support to Co Banking application (T24) issues, user profile management and tracking of all changes as requested by the business team. Share with IT Service Delivery Manager the list of T24 System changes and their status and ensure optimal availability of UAT environments.
- Prepare, share and review test results periodically, report any defects, bugs, errors, configuration issues, and interoperability flaws and develop test acceptance reports for projects and software changes.
- Evaluating application release deliverables against expected quality standards of output and escalating any problems for resolution and subsequent achievement of commitments
MINIMUM POSITION QUALIFICATION REQUIREMENTS
a. Academic & Professional
... then the table content. We need to represent table content as paragraphs? The instruction: Use for introductory paragraphs and general text. Use
- for list items. For tables, we could just keep the content as paragraphs, preserving the text. We must not use
tags? Not prohibited, but they said use for paragraphs and
- for list items. They didn't forbid tables, but to keep clean semantic HTML, we could just convert the table into paragraphs. However we must preserve all original content word-for-word. If we drop the table tags, we are removing content (the table markup). That would be removing content, which is not allowed. So we must keep the table content exactly as originally, but we cannot keep style attributes etc. We need to strip attributes but keep the table structure? The instruction: Use
for introductory paragraphs and general text. Use
- for list items. It didn't say we cannot use
. It said no CSS classes, no inline styles, no s, no
tags. It didn't forbid . So we can keep but remove all attributes (like style, class, border, cellspacing, cellpadding, width, etc). Also we need to keep the content inside etc. Also we need to keep the wrapper? It had class="table". We must remove class attribute. Also we need to remove any style attributes inside etc. So we will produce a maybe? But they said no s, but is allowed. Not prohibited. We'll keep but remove class attribute. Also we need to remove any inline styles inside , , etc.
Thus we will output something like:
... we need to remove style attribute. So just maybe keep rowspan attribute? Attributes like rowspan, colspan are structural, not style. We can keep them. The instruction didn't forbid keeping structural attributes like rowspan, colspan. It only said no CSS classes, no inline styles, no s, no
tags. So we can keep rowspan, colspan, etc. Also we can keep border attribute? border is presentational; but it's not CSS class or inline style? It's an attribute. Might be considered presentational but not explicitly forbidden. Safer to remove presentational attributes like border, cellpadding, cellspacing, width, style, class. Keep only structural like rowspan, colspan.
Thus we will produce .
Similarly for other we keep maybe no attributes.
We also need to keep the content inside tags inside each cell, but we need to strip style attributes from those
tags.
Thus we will produce something like:
Education
Bachelor’s degree
Information Technology
Computer Science
Computer Engineering or any IT related
RQ
... etc.
We need to preserve the original content word-for-word, including spaces and entities inside the text. We must keep the & inside "Academic & Professional". Also we must keep the sequences.
We also need to preserve the original line breaks? Not needed.
We also need to preserve the empty
tags.
Now we need to output only the HTML, no explanation.
Let's construct final HTML.
We'll start with the initial
then KEY RESPONSIBILITIES
then list items as above.
We need to ensure we keep the exact text inside each - , including any entities. In the first li we had "business requirements are". That's two separated by spaces? Actually original: "business requirements are". We'll keep that.
Also note some li had trailing spaces? We'll keep as is.
Now after responsibilities list, we have
then DAILY RESPONSIBILITIES
then list.
After that we have
then MINIMUM POSITION QUALIFICATION REQUIREMENTS
then a. Academic & Professional
then the table figure.
After that we have
then b. Experience
then another table figure.
Then there are several
at end.
We need to preserve them.
Now let's construct the HTML.
We'll need to be careful to escape nothing; just output as is.
Let's write:
KEY RESPONSIBILITIES
- Champion and coordinate business requirements reviews across functional teams and ensures that the business requirements are complete, precise, and testable.
- Works with project team to define and create overall project test strategy/test plan, plan test schedules or strategies and Identifies test resources, estimates test effort in accordance with project scope or delivery dates and ensures that the test strategy is achieved.
- Develop, document, and maintain functional and non-functional test cases, test scripts and other test artifacts like test data, data validation, harness scripts and automated scripts.
- Works collaboratively with the business units and project teams to execute and validate test cases based upon business requirements and ensures that the test cases are traceable to the requirements.
- In collaboration with GEA and other critical stakeholders, tune the SQA processes, adopt tools and define re-usable templates in-line with the adoption and maturity of the SQA Framework.
- Define test process including required test activities and deliverables, conduct Test Readiness Assessment, establish test beds and ensure that test beds are available for all planned white box and black box testing activities.
- Provide support to Co Banking application (T24) issues, user profile management and tracking of all changes as requested by business team and as per the DCOE change process.
- Prepare, share and review test results periodically, report any defects, bugs, errors, configuration issues, and interoperability flaws and develop test acceptance reports for projects and software changes and ensure UAT optimal availability of UAT environments.
- Works with business units to perform post deployment sanity and regression tests and post-implementation review within defined period to confirm that the deployed solution works as per the business requirements.
- Participates in formulation and Implementation of Software process improvement policies and strategies for IT division.
DAILY RESPONSIBILITIES
- Develop, distribute, and coordinate in-depth business requirement reviews across functional teams and ensures that the business requirements are comprehensive, precise and testable.
- Develop, document and maintain functional and non-functional test cases, test scripts and other test artifacts like the test data, data validation, harness scripts and automated scripts.
- Provide support to Co Banking application (T24) issues, user profile management and tracking of all changes as requested by the business team. Share with IT Service Delivery Manager the list of T24 System changes and their status and ensure optimal availability of UAT environments.
- Prepare, share and review test results periodically, report any defects, bugs, errors, configuration issues, and interoperability flaws and develop test acceptance reports for projects and software changes.
- Evaluating application release deliverables against expected quality standards of output and escalating any problems for resolution and subsequent achievement of commitments
MINIMUM POSITION QUALIFICATION REQUIREMENTS
a. Academic & Professional
Education
Bachelor’s degree
Information Technology
Computer Science
Computer Engineering or any IT related
RQ
Professional Qualifications
International Software Testing Qualifications Board (ISTQB) certificate.
Project Management
ITIL
RQ
Master’s degree
Business Administration or Project Management
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 📝
My Job Concierge
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.
Almost there
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.
ECHO
Your MJC Assistant
I'm ECHO, your MJC career assistant. I can help you find jobs, explore career tools, and connect with opportunities across Africa.
. Must use
for section headers like KEY RESPONSIBILITIES, DAILY RESPONSIBILITIES, MINIMUM POSITION QUALIFICATION REQUIREMENTS, etc. Also subheaders like "a. Academic & Professional", "b. Experience". Those could be considered section headers? The instruction: Use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). So we should treat each bold heading as a section header and wrap in . Also the subheadings "a. Academic & Professional" and "b. Experience" maybe also as ? They are sub-sections under MINIMUM POSITION QUALIFICATION REQUIREMENTS. Could treat them as as well. But we need to preserve content exactly, including spaces and entities like &. We must not remove entities? They are part of original content; we must preserve them. However HTML will treat as a space; it's okay to keep them. We must not add
. Also we must not keep any inline styles or classes. So we need to strip all style attributes, class attributes, etc. Also need to remove empty
. Also the subheadings "a. Academic & Professional" and "b. Experience" maybe also as ? They are sub-sections under MINIMUM POSITION QUALIFICATION REQUIREMENTS. Could treat them as as well. But we need to preserve content exactly, including spaces and entities like &. We must not remove entities? They are part of original content; we must preserve them. However HTML will treat as a space; it's okay to keep them. We must not add
. Also we must not keep any inline styles or classes. So we need to strip all style attributes, class attributes, etc. Also need to remove empty
as well. But we need to preserve content exactly, including spaces and entities like &. We must not remove entities? They are part of original content; we must preserve them. However HTML will treat as a space; it's okay to keep them. We must not add
. Also we must not keep any inline styles or classes. So we need to strip all style attributes, class attributes, etc. Also need to remove empty
tags? The instruction: Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. That suggests we should keep even empty paragraphs? But they are not content; they are formatting. However they said "Preserve ALL original content word-for-word". The empty
contains a non-breaking space entity; that is content. Should we keep it? It might be considered formatting but it's part of original. However the output must be clean semantic HTML; we could keep them as
. But they said no
tags, but is okay. We'll keep them. We need to convert the given HTML into our target HTML. Let's extract the textual content, preserving entities. Original snippet:
KEY RESPONSIBILITIES
- ... etc.
We need to strip style attributes etc. So we will produce:
- Champion and coordinate business requirements reviews across functional teams and ensures that the business requirements are complete, precise, and testable.
- Works with project team to define and create overall project test strategy/test plan, plan test schedules or strategies and Identifies test resources, estimates test effort in accordance with project scope or delivery dates and ensures that the test strategy is achieved.
- Develop, document, and maintain functional and non-functional test cases, test scripts and other test artifacts like test data, data validation, harness scripts and automated scripts.
- Works collaboratively with the business units and project teams to execute and validate test cases based upon business requirements and ensures that the test cases are traceable to the requirements.
- In collaboration with GEA and other critical stakeholders, tune the SQA processes, adopt tools and define re-usable templates in-line with the adoption and maturity of the SQA Framework.
- Define test process including required test activities and deliverables, conduct Test Readiness Assessment, establish test beds and ensure that test beds are available for all planned white box and black box testing activities.
- Provide support to Co Banking application (T24) issues, user profile management and tracking of all changes as requested by business team and as per the DCOE change process.
- Prepare, share and review test results periodically, report any defects, bugs, errors, configuration issues, and interoperability flaws and develop test acceptance reports for projects and software changes and ensure UAT optimal availability of UAT environments.
- Works with business units to perform post deployment sanity and regression tests and post-implementation review within defined period to confirm that the deployed solution works as per the business requirements.
- Participates in formulation and Implementation of Software process improvement policies and strategies for IT division.
- Develop, distribute, and coordinate in-depth business requirement reviews across functional teams and ensures that the business requirements are comprehensive, precise and testable.
- Develop, document and maintain functional and non-functional test cases, test scripts and other test artifacts like the test data, data validation, harness scripts and automated scripts.
- Provide support to Co Banking application (T24) issues, user profile management and tracking of all changes as requested by the business team. Share with IT Service Delivery Manager the list of T24 System changes and their status and ensure optimal availability of UAT environments.
- Prepare, share and review test results periodically, report any defects, bugs, errors, configuration issues, and interoperability flaws and develop test acceptance reports for projects and software changes.
- Evaluating application release deliverables against expected quality standards of output and escalating any problems for resolution and subsequent achievement of commitments
- for list items. For tables, we could just keep the content as paragraphs, preserving the text. We must not use
tags? Not prohibited, but they said use
for paragraphs and
- for list items. They didn't forbid tables, but to keep clean semantic HTML, we could just convert the table into paragraphs. However we must preserve all original content word-for-word. If we drop the table tags, we are removing content (the table markup). That would be removing content, which is not allowed. So we must keep the table content exactly as originally, but we cannot keep style attributes etc. We need to strip attributes but keep the table structure? The instruction: Use
for introductory paragraphs and general text. Use
- for list items. It didn't say we cannot use
. It said no CSS classes, no inline styles, no
s, no
tags. It didn't forbid. So we can keep
but remove all attributes (like style, class, border, cellspacing, cellpadding, width, etc). Also we need to keep the content inside
etc. Also we need to keep the wrapper? It had class="table". We must remove class attribute. Also we need to remove any style attributes insideetc. So we will produce a
maybe? But they said nos, butis allowed. Not prohibited. We'll keepbut remove class attribute. Also we need to remove any inline styles inside, , etc. Thus we will output something like:
... we need to remove style attribute. So just maybe keep rowspan attribute? Attributes like rowspan, colspan are structural, not style. We can keep them. The instruction didn't forbid keeping structural attributes like rowspan, colspan. It only said no CSS classes, no inline styles, no s, no
tags. So we can keep rowspan, colspan, etc. Also we can keep border attribute? border is presentational; but it's not CSS class or inline style? It's an attribute. Might be considered presentational but not explicitly forbidden. Safer to remove presentational attributes like border, cellpadding, cellspacing, width, style, class. Keep only structural like rowspan, colspan. Thus we will produce. Similarly for other we keep maybe no attributes. We also need to keep the content inside tags inside each cell, but we need to strip style attributes from those
tags. Thus we will produce something like:
... etc. We need to preserve the original content word-for-word, including spaces and entities inside the text. We must keep the & inside "Academic & Professional". Also we must keep the sequences. We also need to preserve the original line breaks? Not needed. We also need to preserve the emptyEducation
Bachelor’s degree
Information Technology
Computer Science
Computer Engineering or any IT related
RQ
tags. Now we need to output only the HTML, no explanation. Let's construct final HTML. We'll start with the initial
thenKEY RESPONSIBILITIES
then- list items as above.
We need to ensure we keep the exact text inside each
- , including any entities. In the first li we had "business requirements are". That's two separated by spaces? Actually original: "business requirements are". We'll keep that.
Also note some li had trailing spaces? We'll keep as is.
Now after responsibilities list, we have
thenDAILY RESPONSIBILITIES
then- list.
After that we have
- Champion and coordinate business requirements reviews across functional teams and ensures that the business requirements are complete, precise, and testable.
- Works with project team to define and create overall project test strategy/test plan, plan test schedules or strategies and Identifies test resources, estimates test effort in accordance with project scope or delivery dates and ensures that the test strategy is achieved.
- Develop, document, and maintain functional and non-functional test cases, test scripts and other test artifacts like test data, data validation, harness scripts and automated scripts.
- Works collaboratively with the business units and project teams to execute and validate test cases based upon business requirements and ensures that the test cases are traceable to the requirements.
- In collaboration with GEA and other critical stakeholders, tune the SQA processes, adopt tools and define re-usable templates in-line with the adoption and maturity of the SQA Framework.
- Define test process including required test activities and deliverables, conduct Test Readiness Assessment, establish test beds and ensure that test beds are available for all planned white box and black box testing activities.
- Provide support to Co Banking application (T24) issues, user profile management and tracking of all changes as requested by business team and as per the DCOE change process.
- Prepare, share and review test results periodically, report any defects, bugs, errors, configuration issues, and interoperability flaws and develop test acceptance reports for projects and software changes and ensure UAT optimal availability of UAT environments.
- Works with business units to perform post deployment sanity and regression tests and post-implementation review within defined period to confirm that the deployed solution works as per the business requirements.
- Participates in formulation and Implementation of Software process improvement policies and strategies for IT division.
- Develop, distribute, and coordinate in-depth business requirement reviews across functional teams and ensures that the business requirements are comprehensive, precise and testable.
- Develop, document and maintain functional and non-functional test cases, test scripts and other test artifacts like the test data, data validation, harness scripts and automated scripts.
- Provide support to Co Banking application (T24) issues, user profile management and tracking of all changes as requested by the business team. Share with IT Service Delivery Manager the list of T24 System changes and their status and ensure optimal availability of UAT environments.
- Prepare, share and review test results periodically, report any defects, bugs, errors, configuration issues, and interoperability flaws and develop test acceptance reports for projects and software changes.
- Evaluating application release deliverables against expected quality standards of output and escalating any problems for resolution and subsequent achievement of commitments
thenMINIMUM POSITION QUALIFICATION REQUIREMENTS
thena. Academic & Professional
then the table figure. After that we have
thenb. Experience
then another table figure. Then there are several
at end. We need to preserve them. Now let's construct the HTML. We'll need to be careful to escape nothing; just output as is. Let's write:KEY RESPONSIBILITIES
DAILY RESPONSIBILITIES
MINIMUM POSITION QUALIFICATION REQUIREMENTS
a. Academic & Professional
Education
Bachelor’s degree
Information Technology
Computer Science
Computer Engineering or any IT related
RQ
Professional Qualifications
International Software Testing Qualifications Board (ISTQB) certificate.
Project Management
ITIL
RQ
Master’s degree
Business Administration or Project Management
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 📝My Job ConciergeLet jobs find you
Leave your email and our AI matches you to new jobs across 24 African markets — free. You wait for the call.
Almost thereAdd 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.
ECHOYour MJC AssistantI'm ECHO, your MJC career assistant. I can help you find jobs, explore career tools, and connect with opportunities across Africa.
- , including any entities. In the first li we had "business requirements are". That's two separated by spaces? Actually original: "business requirements are". We'll keep that.
Also note some li had trailing spaces? We'll keep as is.
Now after responsibilities list, we have
- for list items. It didn't say we cannot use
- for list items. They didn't forbid tables, but to keep clean semantic HTML, we could just convert the table into paragraphs. However we must preserve all original content word-for-word. If we drop the table tags, we are removing content (the table markup). That would be removing content, which is not allowed. So we must keep the table content exactly as originally, but we cannot keep style attributes etc. We need to strip attributes but keep the table structure? The instruction: Use
KEY RESPONSIBILITIES
DAILY RESPONSIBILITIES
MINIMUM POSITION QUALIFICATION REQUIREMENTS
a. Academic & Professional
... then the table content. We need to represent table content as paragraphs? The instruction: Usefor introductory paragraphs and general text. Use