Cette offre d'emploi n'est plus disponible
À propos
We are validating sealed backend programs written in TypeScript with SQLite.
All work is governed by Spine documents and Product Design Documents (PDDs).
This is QA-only work.
No production code changes. No redesigns. No interpretation.
QA will create test data, produce QA documentation, and execute tests in a provided non-production backend environment.
⸻
Role Overview
• Contract QA (Backend Systems)
• Short-term, hour-capped
• Scope: Assigned backend programs only
• Authority sources: Spine + PDD
Your job is to produce a clear, reproducible, audit-ready signal on system correctness — strictly against the Spine and PDD.
⸻
Source of Truth (Critical)
Spine Document → Defines system structure, contracts, and invariants
PDD → Defines program behavior
If something is not explicitly defined in these documents:
Treat it as out of scope.
Do not infer behavior.
Do not fill gaps.
Do not "improve" design.
⸻
Current State
• Existing TypeScript backend codebase
• SQLite database
• Backend programs already implemented
• Sealed Spine documents
• Sealed Product Design Documents (PDDs)
⸻
What You Will Do
1 — Test Against Spine + PDD
Create test coverage that validates:
• Contract adherence
• Structural invariants
• Behavior defined in the PDD
• Deterministic execution
• Failure behavior
Test only what is written.
Ignore what is not.
⸻
2 — Test Data & Fixtures
Create all required test inputs based strictly on the Spine and PDD:
• Valid inputs
• Invalid inputs
• Explicit edge cases
Ensure test data is:
• Minimal
• Explicit
• Reproducible
Document each fixture:
• Purpose
• Expected outcome
• Source reference (Spine or PDD section)
⸻
3 — QA Documentation
Create QA artifacts:
• Test case list
• Step-by-step execution instructions
• Expected vs actual results
• Spine/PDD reference for each test
Documentation must be:
• Clear
• Deterministic
• Runnable by another engineer without guessing
⸻
4 — Backend Execution
• Run tests directly in the provided non-production backend environment
• Execute all testing from a QA-dedicated branch
Validate using:
• Database state
• Logs
• Error output
Confirm:
• Happy path unchanged
• Failures fail loudly
• No partial writes
• Deterministic outcomes
• Contract adherence
⸻
What You Will NOT Do
• No production code changes
• No refactors
• No redesign
• No new frameworks
• No assumptions beyond the Spine or PDD
• No "fixing" behavior
• No interpreting intent
• No changes to environment configuration, runtime flags, or database settings
• No work of any kind on the main branch
Main branch is read-only.
All QA work must occur on a separate branch.
⸻
How to Work
• Spine and PDD are the only authorities
• Perform black-box testing only
• Create and use a QA branch for all activity
Ask questions before assuming:
• Reference exact Spine/PDD section
• Tag clearly: (QUESTION) (BLOCKER) (CONFIRMATION)
If documentation is silent → do not test it.
⸻
Deliverables (Required)
1 — Test Data Package
• All fixtures used
• Clear naming
• Documented intent
• Spine/PDD reference
⸻
2 — QA Test Documentation
• Test cases
• Execution steps
• Expected vs actual results
• Document references
⸻
3 — QA Report
• Pass / Fail summary
• Repro steps for every failure
• File + line references when possible
• Evidence of determinism (repeated runs produce identical results)
Failure classification required:
• Bug
• Spine deviation
• PDD deviation
• Environment issue
Explicit confirmations:
• "Happy path unchanged"
• "No silent failures observed"
• "Contracts upheld"
No documentation = task incomplete.
⸻
Definition of Done
• Another engineer can rerun your tests exactly
• Results are deterministic and evidenced
• Findings are clear and immediately actionable
• Scope respected 100%
• Spine + PDD validated
• No activity occurred on the main branch
⸻
Contract Details
• Trial-based
• Maximum billable time: 24 hours (hard cap)
• Execution window: 1–2 calendar days
• Same-day or next-day turnaround expected
• Task ends when the QA report is submitted or the 6-hour cap is reached (whichever occurs first)
⸻
Required Skills
• Backend QA experience
• Ability to read and execute TypeScript backend code
• SQLite inspection
• Creating backend-runnable test data
• Writing precise QA documentation
• Git (branches only — no main-branch work)
⸻
Fit
This role is ideal if you:
• Are methodical and skeptical
• Respect written contracts
• Document as you test
• Operate without assumptions
• Treat the main branch as untouchable
Not a fit if you like redesigning systems or interpreting intent.
⸻
How to Apply
Answer directly:
Have you executed backend QA strictly against formal system documents (such as a Spine and PDD), without making assumptions beyond what was written, and working exclusively on a branch rather than main?
Contract duration of less than 1 month. with 30 hours per week.
Mandatory skills: deterministic systems
Compétences linguistiques
- English
Avis aux utilisateurs
Cette offre a été publiée par l’un de nos partenaires. Vous pouvez consulter l’offre originale ici.