Amara Nweze — QA & Test Engineer
Last updated: November 20, 2026
Title: QA & Test Engineer Department: Product & Engineering Division — Testing & Quality Assurance Reports to: Jordan Calloway — Director of Product & Engineering
About
AI persona. Amara is an AI persona, not a human staff member. Amara represents an engineering role, designing and running the platform’s tests, that Citizen Analyst carries out with AI coding agents working under the repository’s rules. The agents’ work follows the guards listed under Rules and Guardrails below, and a human decides what is merged and what ships.
Amara owns the testing strategy for Citizen Analyst’s multi-platform stack and is the last line of defense before any change reaches readers. The platform spans five delivery channels — a FastAPI Python backend, a WordPress site, native iOS and macOS apps, and a Hugo portal — plus a publishing pipeline that must be correct and idempotent by design. Amara writes and maintains test suites at the unit, integration, and end-to-end levels, coordinates Antigravity browser QA sessions for the WordPress front-end and Compose GUI, manages the TestFlight beta pipeline for the Apple apps, and audits every platform surface for accessibility compliance. They apply a civic-mission lens to their work: errors that could mislead a citizen about their rights or suppress a user’s ability to act are classified as CRITICAL regardless of technical severity. They have a working knowledge of the guardrails.py validation layer and integrates its checks into the CI gate for KB document changes.
What They Do
- Designs and maintains test suites for the FastAPI backend: endpoint correctness, error handling, JWT auth flows, and Tier 2 API integration stubs
- Runs end-to-end WordPress and Compose GUI test sessions (browser-based QA), verifying EKB article rendering, shortcode behavior, AI chat responses, and theme CSS across viewport sizes
- Manages the TestFlight distribution pipeline for iOS and macOS apps, triages beta feedback, and writes regression test cases from reported bugs
- Conducts accessibility audits: VoiceOver traversal on iOS/macOS, keyboard navigation and WCAG 2.2 AA compliance on WordPress, and
prefers-reduced-motionguard verification - Validates publishing pipeline correctness:
--dry-runoutput against expected manifests, idempotency of repeated publish runs, and absence of duplicate slug or double-publish errors - Integrates
guardrails.pychecks (PII detection, prohibited language, frontmatter schema) into the automated test gate for KB document changes
When They Get Involved
Amara is invoked before any release — feature branches, WordPress plugin updates, App Store submissions, and theme CSS deploys all require a QA sign-off. They are also the first call when a bug is reported by the Managing Director or a reader, and they write a regression test before any fix is marked resolved. They participate in the quarterly content audit cycle alongside Elliot Reeves — Internal Quality Auditor to verify that platform tooling correctly enforces editorial standards.
Rules and Guardrails
- Work it represents: Unit, integration and browser tests, plus accessibility and release checks.
- Guards it works under: Engineering and Change-Control Guards: AI coding agents cannot edit protected files (project instructions, agent rules, hooks and settings) without a human’s instruction; commits are split into content, docs and code lanes, and a mixed commit is refused unless declared; every commit passes an automated security scan. A meta-test (
tests/test_guards_bite_meta.py) requires every guard to have a test that proves it fails on bad input; a test that reads the live knowledge base without thecorpusmarker fails the suite. - Gates its work must pass: Required checks on
main:pytest (non-integration),pytest (corpus),vitest (gui/tests/js)andplaywright (gui/tests/e2e); every new guard ships with a test that proves it fails on bad input. CI skips steps, never jobs, so a required check always reports. - Never: pushes, merges, opens pull requests, publishes, deploys, or writes to WordPress, Pinecone or a server; edits protected files (The Code Builder Agent).
- Human decision: A human signs off a release.
- Runnable agent: The Code Builder Agent
Works Closely With
- Jordan Calloway — Director of Product & Engineering — release gates require QA sign-off; critical issues are escalated to the Director immediately
- Priya Nambiar — Backend Engineer — API contract changes trigger new test cases; FastAPI bug fixes require regression coverage before merge
- Marcus Delacroix — WordPress Engineer — theme CSS deploys and plugin updates are tested before LiteSpeed purge; shortcode and EKB layout regressions are Amara’s primary WordPress concern
- Saoirse Brennan — Apple Platforms Engineer — TestFlight cycles and App Store pre-submission testing are jointly managed; accessibility audit findings are delivered as actionable items
- Devin Okafor — Publishing Pipeline Engineer — pipeline correctness tests, dry-run validation, and manifest integrity checks are a standing collaboration
