Role Charter

Emre Role Charter

Technical Delivery Lead | QA & Verification | Offshore Dev Management (0→1 Build Engine)

Outcome

Own technical execution quality and verification across our 0→1 builds - so we ship faster, cleaner, and with fewer surprises at handover.

Why This Role Exists

Our Product Innovation function is shipping multiple MVPs in parallel (prototype → MVP → handover). This role exists to increase engineering throughput and quality by managing 3rd-party/offshore execution, enforcing QA and technical verification, and producing technical/UX evidence that strengthens our design and delivery decisions.

How Atoum & Emre Work Together

  • Atoum drives product direction + UX experience and owns the sprint outcomes.
  • Emre runs the engineering execution layer: offshore team output, QA gates, and verification.
  • If something smells off (requirements, flows, feasibility, security), Emre flags immediately and proposes options - no silent assumptions.

Owns

  • Offshore/3rd-party engineering management: intake, tasking, reviews, and delivery assurance (especially APIs and backend work).
  • QA & fact-checking: verify requirements, test builds, validate edge cases, and challenge assumptions early.
  • Technical evidence: architecture notes, API specs, implementation verification, and readiness for IT handover.
  • UX support outputs: UX audits, journey mapping, and usability evidence that backs design decisions.
  • Release readiness support: pre-handover checklists, regression tests, and sign-off confidence.

Doesn't Own

  • Final product scope decisions (owned by Atoum + Product Owner/Venture Builder).
  • Stakeholder negotiations and business approvals (owned by Atoum/PO/VB).
  • Operating the product post-handover (owned by IT in 1→N).

Operating Flow

1

Validated idea comes in with PRD/context (via PO/VB/Musa/Sarah).

2

Atoum defines sprint scope and the user stories/backlog for build.

3

Emre splits work into: internal build tasks vs offshore tasks (esp. APIs/backend/integrations).

4

Emre briefs offshore team with acceptance criteria, test cases, and definition of done.

5

Offshore delivers via PRs; Emre runs code reviews + QA validation + regression checks.

6

Atoum integrates into the product experience; Emre verifies end-to-end flows and edge cases.

7

Before handover: Emre signs off engineering/QA readiness and supports packaging for IT.

Deliverables

A. Offshore / 3rd-party Engineering Management

  • Onboard offshore team (repo access, branching strategy, environments, coding standards).
  • Create clear task briefs: context + acceptance criteria + test cases + constraints.
  • Run daily async check-ins (or 15-min standup when needed) focused on blockers and delivery.
  • Review PRs (code quality, security hygiene, performance basics, correct behavior).
  • Ensure deliverables match API contracts, data models, and error handling expectations.

B. QA, Verification & Fact-checking

  • Translate stories into testable acceptance criteria and test cases (happy path + edge cases).
  • Own regression testing discipline across the pipeline (don’t break other MVPs).
  • Verify integrations and data correctness (payloads, validation, retries, logging).
  • Challenge unclear requirements early - propose fixes and document decisions.
  • Maintain a lightweight defect log and ensure fixes are confirmed, not assumed.

C. Technical Evidence & Readiness

  • Maintain API specs (OpenAPI/Swagger where applicable) and ensure implementation matches.
  • Document architecture notes for each product (services, dependencies, data flow).
  • Confirm deployment readiness: env vars, secrets, logging, monitoring hooks (as needed).
  • Support IT handover by verifying runbook-lite, known limitations, and tech debt notes.

D. UX Support Outputs (to back design decisions)

  • Run UX audits for revamps: issues, heuristics violations, friction points, quick wins.
  • Create journey maps and flow diagrams that explain the ‘why’ behind UX decisions.
  • Validate that the implemented UX matches the intended journey (consistency, clarity, edge cases).

Cadence

  • Daily (async): Offshore progress + blockers + PR review queue.
  • 2x/week: QA/verification checkpoint across active products (30 min).
  • Per sprint: kickoff alignment (scope + dependencies) + pre-handover readiness review.
  • Ad hoc: design/UX evidence work when a revamp needs justification.

Success Metrics

  • Engineering throughput: offshore tasks shipped per sprint with low rework.
  • Quality: defect escape rate decreases; fewer UAT surprises.
  • Verification: acceptance criteria met with evidence; no ‘it should work’ assumptions.
  • Handover readiness: IT accepts handover with minimal gaps; clear tech notes and API specs.
  • UX evidence: audits/journeys produced when needed and used in decision-making.

30 / 60 / 90 Day Plan

First 30 daysSet the execution layer

Offshore onboarding playbook; repo standards; QA Gate v1; first product end-to-end verification + sign-off.

Days 31–60Scale delivery with confidence

Own offshore delivery for 2–3 products; regression discipline; API spec templates; UX audit template + 1 audit.

Days 61–90Institutionalize quality

Automated smoke/regression basics where possible; consistent PR review SLA; pre-handover checklist adopted; journey mapping pack for revamp workstreams.

Offshore Engineering Rules

  • Work only through PRs - no direct pushes to protected branches.
  • Every PR must map to a defined task with acceptance criteria.
  • Coding standards and naming conventions follow our repo conventions.
  • No dependencies added without approval (security + maintenance).
  • If requirements are unclear: stop and ask - do not guess.

Principles

  • Speed with proof: ship fast, but every claim is testable and verified.
  • No ambiguity tolerated: unclear requirement = stop and clarify, not guess.
  • One standard: offshore team follows our conventions - not their own.
  • Protect Atoum’s focus: you run the execution + QA layer so Atoum stays on product delivery and UX quality.