Portrait of Aya Dweeb

Operations

Operational work across teams, workflows, and digital projects

My contribution to technology projects is operational rather than technical.

I do not develop software or make final architecture decisions. My role is to follow work, organize information, clarify selected requirements, review operational progress, identify incomplete areas, and help connect management priorities with the teams responsible for delivery.

Platform

Internal Operations Platform

Operational workflows and financial visibility

Quanizon is developing an internal operations platform to replace fragmented Excel sheets and disconnected processes.

I contribute operational requirements related to:

  • Attendance and absence
  • Employee records
  • Employee follow-up
  • Tasks and working hours
  • Performance evaluation
  • Project value
  • Actual project hours
  • Delivery cost
  • Project profit or loss
  • Operational and financial reporting

I have explained existing Excel workflows to developers, identified required fields and reports, discussed registration barriers with employees, and contributed to the organization of employee-management screens.

Projects

Selected Projects

  1. 01

    September 2025–Present

    BIM

    Cross-functional delivery follow-up

    ClientBarq IT

    BIM is a software project developed for Barq IT.

    My contribution includes:

    • Following tasks across the full multidisciplinary team.
    • Reviewing whether available features are functioning.
    • Identifying incomplete or inactive features.
    • Participating in early pre-release checks.
    • Identifying issues related to image sending.
    • Identifying issues affecting message writing and use.
    • Reporting findings internally through management.

    The project has not yet completed full delivery, and client communication is handled through the company director.

  2. 02

    November 2025–Present

    RewaqHub

    Early competitive research

    OwnerQuanizon

    I contributed to early product discussions through:

    • Competitor research.
    • Feature comparison.
    • Pricing comparison.
    • Identification of strengths and weaknesses.
    • Early product-scope suggestions.

    Detailed competitors and research findings remain confidential company information.

  3. 03

    January 2026–Present

    HirzHub

    Early product and market research

    OwnerQuanizon

    HirzHub is a company-owned product separate from BIM.

    I contributed through:

    • Early competitor research.
    • Feature and pricing comparisons.
    • Identification of strengths and weaknesses.
    • Suggestions related to possible product scope and features.

    Sensitive market and competitor information is not disclosed publicly.

  4. 04

    February 2026–July 2026

    Alobaid Law Website

    Requirements organization

    ClientAlobaid Law

    I contributed during selected stages by:

    • Reviewing client requests received through management.
    • Converting requests into clearer developer tasks.
    • Organizing changes to imagery and brand presentation.
    • Identifying required logo-size adjustments.
    • Identifying content that required correction.

    My involvement was limited to selected requirement and follow-up stages rather than full final delivery.

  5. 05

    Periodic contributions, 2024–2026

    CFJ Website

    Content and requirement clarification

    ClientCFJ

    I contributed by:

    • Preparing and entering selected content.
    • Organizing data before development.
    • Clarifying selected client requirements.
    • Rewriting requirements in a form that was easier for developers to implement.
    • Supporting periodic project follow-up.
  6. 06

    March 2025

    The Access

    Task and requirement follow-up

    ClientMorison

    I supported selected stages of the project by following employee tasks and reviewing whether completed work matched the available requirements.

Role scope

What My Project Role Includes

  • Operational follow-up
  • Task and progress visibility
  • Requirements organization
  • Early feature review
  • Team communication
  • Reporting blockers
  • Employee and project-hour review
  • Product and competitor research
  • Workflow clarification
  • Final contract negotiation
  • Independent client-account ownership
  • Final product-strategy authority