Technical support
and software training.
I’m Rizwan Sayani, a QA lead with 15 years in software testing and more than 12 years supporting CIBC online banking.
I investigate software issues, coach testers and write guidance that helps teams get the work done. This portfolio shows how I approach support, learning and delivery.
Kitchener-Waterloo, Ontario · Open to remote roles in Canada
Selected work
Choose the example most relevant to your role.
API Camp is an existing personal project. The other examples are illustrative work samples using fictional situations. No internal employer material is included.
Learning design
API Camp
Try a response check
Check a response for West, October. Edit the JSON directly or load a case. The checker explains syntax, missing-field and data errors.
Change a response field, then check it against the request.
What this shows
How I break down a technical topic, build guided practice and explain why a result needs checking. I also built the CIBC QE Learning Hub with 40+ courses and 60+ working examples; its internal content is not reproduced here.
I developed API Camp as a practice site for people learning API testing and related QA skills. It combines short exercises, editable starter code, hints, solutions and progress tracking.
The aim is to give someone a useful next step when they get stuck. A hint comes before the full solution; a check gives them something concrete to investigate. The project includes API, Python and browser-testing material.
Technical writing
Illustrative work sample · Fictional product: Harbour Workspace
An invited colleague cannot open the workspace
Use this guide when someone receives an invitation but sees an access error. A workspace administrator may need to help with the final checks.
Check the invitation and sign-in email
- Compare the email address on the invitation with the account used to sign in.
- If the email addresses don’t match, sign out and sign in with the invited address. Avoid creating a second account as a workaround.
- If the invitation has expired, ask the administrator to send a new one and use the latest link.
Try an access investigation
Choose a fictional case, review the checks and generate the next action. The support note is ready to download after a check.
Check workspace membership
Ask the administrator to confirm the invitation is pending or the colleague is an active member. Check that the assigned role allows access to this workspace. Keep permissions limited to what the person needs.
If the company uses single sign-on
Use the company sign-in option. If an identity-provider error appears, record the message and time, then ask IT to confirm the account is assigned to the application.
If access still fails
Send support the workspace name, invited address through an approved channel, time and time zone, exact error and steps already tried. Remove personal information from screenshots. Never send passwords, verification codes, cookies or access tokens.
How I would keep the article useful
Ask someone unfamiliar with the flow to follow it. Check that every step matches the current interface. Review related support questions for recurring confusion and revise the guide when the sign-in flow changes.
Incident response
Illustrative work sample · Synthetic customer and fleet data
Three vehicles stop updating on a dashboard
At 10:00 ET, a customer reports that three vehicles have not updated since 09:40. Other vehicles still update. Connectivity, delayed incoming data and a dashboard problem are all possible causes.
Start with the scope
Confirm the affected records and last-seen times through an approved channel. Compare one affected record with a working one. Check whether the vehicles share a location or configuration and whether another authorized user sees the same problem.
Customer updates
Select an update to see how the message changes as evidence arrives. These are fictional investigation stages.
Cause not yet confirmed
We’re investigating delayed dashboard updates for the three vehicles you identified. Other vehicles in your account are still updating. I’m checking the last-received times and whether the problem affects the dashboard or incoming data. I’ll update you by 10:45 ET, even if the investigation is still in progress.
Give engineering an actionable handoff
Include the customer impact, first observed time, affected records, a working comparison, reproduction steps and relevant sanitized logs. Separate confirmed facts from possible causes. Record the owner of the next step and the next customer-update time.
Check the outcome
After a proposed fix, confirm timestamps advance and the customer sees current data. Check whether historical records still need attention. Record the cause only after it is confirmed.
Implementation planning
Illustrative work sample · Fictional employee portal
A department pilot before a wider launch
This plan starts with 25 users in one department. The customer owns content approval, identity configuration and access policy. The four-week outline is an example, not a delivery estimate.
Week 1 · Clarify
Agree goals, scope, users and decision owners. Confirm sign-in requirements. Inventory priority pages and name an approver for each. Record dependencies and exclusions.
Week 2 · Prepare
Check roles and sign-in in a test environment. Prepare and approve pilot content. Agree how users will report problems and who will respond. Keep a shared decision log.
Week 3 · Pilot
Ask users to sign in, find a policy, read an announcement and report an access problem. Record expected and actual results. Give each issue an owner and due date.
Week 4 · Review
Compare results with agreed targets. Resolve blocking issues. Confirm support ownership and rehearse the rollback procedure before asking the sponsor for a launch decision.
Support handoff
Share the configuration summary, known issues, escalation contacts and user guidance. Set targets for task completion, sign-in success and support response before the pilot, then review actual results against them.
Training and facilitation
Illustrative work sample · Fictional reporting product
Create and verify a saved report view
A 15-minute session for new administrators. By the end, each participant should save a view for a specified region and month, then explain how they checked it.
- 0–3 minutes · Establish the task
- Show a manager’s request: “I need last month’s results for the West region.” Ask which details must be confirmed. Explain the reporting period and region labels using synthetic data.
- 3–6 minutes · Demonstrate
- Choose the region and period, inspect the result and save a named view. Show why a view can save successfully while still using the wrong month.
- 6–11 minutes · Practise
- Give each person a different region and month. Ask them to create a view and explain their checks to a partner. Ask where they are uncertain before repeating the demonstration.
- 11–15 minutes · Check understanding
- Show a view with the wrong month. Ask participants to find and correct the error, then name one check they will use before sharing a report.
Try the learning check
The request is for West, October. The saved view displays West, September. What needs to change?
Choose an answer to see the explanation.
Review after the session
Record how many participants finished without prompting and which steps needed help. Ask, “Which part would you need to look up tomorrow?” Use the answers to revise the demonstration or reference guide. This sample has not been delivered, so no learner outcomes are claimed.