Contract opportunity
Freelance Manual QA Tester
Celis Advisory is seeking a manual QA tester for project-based contract work testing end-to-end business workflows across CRM, forms, booking tools, calendars, notifications, and integrations.
The first engagement will support an upcoming client systems build. Additional project work may be available as Celis Advisory grows.
Scope of the role
Independently test the system against the documented business requirements.
Celis Advisory defines the process, business rules, and intended workflow. The QA tester verifies that the completed build behaves as intended and documents defects, gaps, and risks before client acceptance testing.
The work
Responsibilities
You will receive the intended workflow, business rules, and test access. You will create or refine test cases, execute them independently, and report the results clearly.
Test the full workflow
Follow the journey across forms, CRM records, booking tools, calendars, notifications, and connected systems—not just one screen at a time.
Test both sides
Verify the customer experience and the internal operational experience, including what the business owner or team needs to see and do next.
Look beyond the happy path
Explore duplicate submissions, cancellations, missed steps, incomplete information, timing issues, conflicting data, and unexpected user behaviour.
Document what you find
Report issues clearly with steps to reproduce, expected and actual behaviour, severity, evidence, and the business impact.
System coverage
The kinds of things you’ll test
Most projects connect several everyday business tools. A workflow can appear correct in one tool while quietly failing at the handoff to the next.
Testing approach
Questions the tester should investigate
Does the correct person receive the notification? Is the required next action clear? What happens if a customer books twice, uses a different email address, skips a step, or cancels?
Testing should cover functional defects, workflow gaps, unclear behaviour, operational risks, and exception scenarios. Findings should also identify processes that technically work but could still cause missed work or confusion for the customer or internal user.
The right fit
Experience and working style
- ✓Approximately 2–5 years of manual QA, functional testing, UAT, or exploratory testing experience
- ✓Experience testing SaaS tools, business systems, CRM workflows, or integrations
- ✓Strong written communication and disciplined defect documentation
- ✓Comfortable working independently from process maps, business rules, and intended outcomes
- ✓The judgment to identify behaviour that technically works but is operationally confusing or risky
- ✓Reliability, discretion, and care when working inside client environments
This role is focused on manual QA
Automation experience is welcome, but this contract is not for software development or QA automation. The primary requirement is manual, judgment-based testing of connected business workflows.
Engagement
Practical details
Compensation
Typically CAD $30–$45 per hour, depending on experience and project complexity. Fixed project pricing may also be considered for a clearly defined scope.
Project rhythm
Work will be occasional at first, usually around a defined QA cycle before client UAT and go-live. There is potential for repeat projects as Celis grows.
Location
Remote Canadian candidates are welcome. Calgary is preferred for relationship building, but it is not a requirement.
Access and confidentiality
You may work inside client systems using test accounts and sanitized data. Professional discretion and responsible handling of access are essential.
How to apply
Apply for consideration
Complete the application form with your experience, rate, and availability. A cover letter is not required. Shortlisted candidates will be contacted for a conversation before any project engagement begins.
What You'll Need to Include
- Your location and time zone
- LinkedIn profile or résumé
- A short summary of the systems and workflows you have tested
- Your typical hourly or project rate
- Your availability for occasional project work
Screening question
When testing an end-to-end business workflow, what do you look for beyond whether each individual feature works?