QA Analyst (Part-time or Full-time)
Please mention DailyRemote when applying
AI Summary
The QA Analyst will own day-to-day quality execution across the Haulvana platform, translating product requirements into practical test coverage and driving defect reporting. Responsibilities include manual QA execution, establishing QA gates, and supporting post-publish QA.
About Haulvana
Haulvana is building an operations platform with core product areas that include Customer Portal, Operations & Dispatch, Asset Management, and Maintenance. We are tightening product requirements and release readiness by refining how requirements map to MVP functionality for both engineering and QA.
Role summary
We are hiring a QA Analyst to own day-to-day quality execution across the Haulvana platform. You will translate product requirements into practical test coverage, run structured and exploratory testing, and drive crisp defect reporting and verification so releases are reliable and predictable.
This is a strong fit for someone who enjoys early-stage environments, can operate with minimal overhead, and can create clarity and process without slowing down shipping velocity.
What you will do (responsibilities)
Test planning and coverage
- Build and maintain test plans, test cases, and regression checklists mapped to product requirements (SRS/user stories/acceptance criteria).
- Establish “definition of done” QA gates for new features and fixes (entry/exit criteria, severity rubric, go/no-go recommendation).
Manual QA execution
- Execute functional testing across key modules (Customer Portal, Operations & Dispatch, Asset Management, Maintenance).
- Perform smoke tests on new builds, run regression sweeps before release, and conduct exploratory testing to uncover edge cases.
Defect lifecycle ownership
- Write high-signal bug reports with clear repro steps, expected vs. actual behavior, environment notes, and supporting evidence (screenshots/video/log snippets).
- Triage and retest fixes quickly; validate that fixes do not introduce regressions.
- Operate comfortably in a workflow that may involve Jira and/or integrated ticketing.
Workflow and release discipline
- Work within the team’s task workflow (including Asana or equivalent) and help enforce clean handoffs through QA stages.
- Support post-publish QA gates where “ready for QA” means implementation is complete and required assets are in place (copy/graphics), and only then do items move into a final QA-post step.
Optional, if you have automation experience (nice-to-have)
- Recommend lightweight test automation opportunities (starting with the highest ROI flows) and help implement or maintain them.
What success looks like (first 30–60 days)
- A clear regression checklist exists for the highest-traffic / highest-risk workflows across the core modules.
- Bugs are consistently documented with enough detail that engineering can reproduce quickly without back-and-forth.
- QA gates are respected (items aren’t advanced prematurely), and release readiness is simpler to assess.
- Measurable reduction in escaped defects and re-opened tickets.
Required qualifications
- 2+ years of hands-on QA experience (web applications), including structured manual testing.
- Strong ability to produce precise, actionable bug reports and prioritize by user impact.
- Familiarity with modern agile delivery and working from user stories / acceptance criteria.
- Comfort working in a fast-moving environment with evolving requirements (you can create order without demanding perfect inputs).
- Clear, professional written communication and reliable follow-through.
Preferred qualifications (nice-to-have)
- Experience with test management artifacts: test plans, coverage matrices, traceability to requirements.
- Experience with tools like Jira and/or Asana (or equivalent).
- Exposure to basic QA automation concepts and tools (even if you are not the primary automation owner).
- Prior startup experience (shipping iteratively, balancing speed and quality).
Time commitment and working model
- Part-time or full-time, depending on fit and availability.
- Remote-friendly, with a preference for dependable overlap with the core team’s working hours.
Compensation
- Competitive hourly (part-time) or salary (full-time), commensurate with experience and scope.
How to apply
Please submit:
- A short overview of your QA experience (1–2 paragraphs).
- 1–2 examples of how you write bug reports (you can anonymize).
- Your availability (hours/week) and earliest start date.
Automatically Apply to the Best Remote Jobs
Stop the endless job search. Our AI finds and applies to the best jobs for you.
