Quality Assurance Smoke Tester

# Quality Assurance Smoke Tester for Local Business Pro — Home Services CRM / Field Service Software We are looking for a detail-oriented Quality Assurance Smoke Tester to help test Local Business Pro, a CRM and field service management platform built for home service companies. This role is not simple surface-level QA. We need someone who can deeply test how different parts of the software connect together, especially around jobs, estimates, quotes, customer approvals, scheduling, payments, and field service workflows. You should be comfortable thinking through how a real home service business operates from start to finish. For example: A customer calls in. A lead or contact is created. An estimate is built. The customer reviews and approves the estimate. The estimate may require a deposit or payment. The estimate may turn into a job. The job may need scheduling, team assignment, notes, line items, invoices, payments, and follow-up. We need someone who can test those flows from multiple angles and catch where the experience breaks, feels confusing, or creates bad data. ## About Local Business Pro Local Business Pro is software for home service businesses such as plumbing, HVAC, pest control, landscaping, restoration, cleaning, roofing, construction, and similar industries. The software includes tools like: * Contacts and customer records * Jobs and job management * Estimates and quotes * Line items and pricing * Scheduling and appointments * Invoices and payments * Notes, records, and customer history * Customer-facing approval flows * Internal team workflows * Mobile and desktop experiences The goal of this role is to help us make sure the core workflows work correctly before we release updates. ## What You Will Be Testing You will be focused heavily on smoke testing and workflow testing, especially around: * Creating contacts and customers * Creating estimates and quotes * Adding line items, packages, services, discounts, deposits, and payment requirements * Sending or viewing customer-facing estimates * Customer estimate approval flows * Estimate signature or acknowledgment flows * Estimate payment and deposit flows * Converting approved estimates into jobs * Scheduling jobs and appointments * Assigning team members * Updating job statuses * Creating invoices from jobs or estimates * Taking payments * Testing edge cases where things should fail gracefully * Verifying that customer-facing pages match internal records * Checking that data stays consistent across the system We especially want someone who can test the same feature from different business scenarios. For example: * A simple one-time job * A job that starts as an estimate * A job with no payment required upfront * A job with a deposit required * A quote that should not become a job yet * A customer who approves an estimate but still needs to sign something * A job that changes after approval * A technician or office user viewing the same information from another screen * A customer-facing approval path compared to the internal admin view ## What We Need From You We need someone who can: * Follow detailed smoke test instructions * Create realistic test scenarios * Think like a home service business owner, dispatcher, technician, office admin, and customer * Clearly document bugs with steps to reproduce * Explain what you expected to happen versus what actually happened * Record short screen videos when useful * Take screenshots and mark up issues clearly * Test the same workflow from multiple angles * Notice data mismatches between pages * Identify confusing UX, not just technical bugs * Retest fixes after our development team makes changes * Communicate clearly and consistently ## Ideal Experience You are a strong fit if you have experience with any of the following: * QA testing for SaaS software * Field service software * CRM software * Home service businesses * Jobber, Housecall Pro, ServiceTitan, Buildertrend, Service Fusion, FieldPulse, or similar tools * Estimate, quote, invoice, payment, or scheduling workflows * Manual QA testing * Smoke testing * Regression testing * Writing bug reports for developers You do not need to be a developer, but you do need to be technical enough to understand how software workflows connect together. ## This Role Is Intensive This is not a quick checklist role. We need someone who is willing to dig into the product and understand how the pieces fit together. The hardest bugs in our software usually happen between features, not inside one screen. For example: * The estimate looks correct, but the job created from it is missing information. * The customer approved the quote, but the internal status did not update. * A payment was collected, but the invoice does not reflect it correctly. * The admin sees one price, but the customer-facing page shows another. * A job is created, but the schedule, assigned team, or customer record does not connect properly. * The software shows success when something actually failed behind the scenes. We need someone who is curious enough to catch those issues. ## Deliverables For each testing assignment, we expect: 1. A clear summary of what was tested 2. A list of bugs found 3. Steps to reproduce each bug 4. Expected result 5. Actual result 6. Screenshots or screen recordings when helpful 7. Severity level or priority suggestion 8. Notes on confusing workflows or user experience problems 9. Retesting confirmation after fixes are released ## Example Bug Report Format **Title:** Approved estimate does not create job correctly **Steps to Reproduce:** 1. Create a new customer 2. Create an estimate with two line items 3. Require a 50% deposit 4. Open the customer-facing estimate page 5. Approve the estimate and submit payment 6. Return to the admin dashboard 7. Open the customer record and job list **Expected Result:** The estimate should show as approved, the deposit should be recorded, and a new job should be created with the correct customer, line items, total, and status. **Actual Result:** The estimate shows approved, but no job is created. Payment appears under the customer record but is not connected to the estimate. **Severity:** High ## Who This Is Not For This role is probably not a fit if you only want to: * Click through pages quickly * Run basic checklists without thinking about business logic * Report vague bugs like “this does not work” * Avoid learning how the product works * Test only one screen at a time without understanding the full workflow ## Who This Is For This is a great fit if you enjoy: * Breaking software in useful ways * Understanding real business workflows * Thinking through edge cases * Testing customer-facing and admin-facing flows * Helping developers see exactly what went wrong * Making software more reliable before users touch it ## How to Apply Please include the following in your application: 1. Your QA testing experience 2. Any experience with CRM, field service, home service, estimating, invoicing, or scheduling software 3. A short example of a bug report you have written 4. The tools you use for screenshots, screen recordings, and QA documentation 5. Your availability and hourly rate 6. A brief explanation of how you would test an estimate-to-job workflow in a home service business Applications that include a thoughtful answer to #6 will be prioritized. We are looking for someone who can become a long-term QA partner as we continue building and improving Local Business Pro.