Roles at a Glance

EmeSoft’s delivery process involves seven roles. This page is the index: a one-line mission for each, the value chain that connects them, and the common structure every role page follows.

The seven roles

Role	Mission (one line)	Detail
Stakeholders (Product Owner)	Own the product - vision, funding, priorities, backlog, and acceptance.	Open
Project Manager	Keep delivery on track - coordinate, unblock, report.	Open
Business Analyst	Turn business intent into clear, testable requirements.	Open
Solutions Architect / Dev Lead	Own the technical design and lead the team’s engineering.	Open
Developer	Build working, tested software that meets acceptance criteria.	Open
Cloud Engineer (DevOps)	Design, build, deploy, and monitor the cloud system as code.	Open
Quality Engineer (QC / QA / Tester)	Own quality end to end - code review, standards, and test validation.	Open

These seven are present on every project. Some projects add specialized roles on top.

Project-specific roles

Role	When it’s staffed	Mission (one line)	Detail
Data Engineer	Data-centric projects only	Design, build, and maintain the data pipelines that let clients ingest, transform, and use their data for decisions.	Open

How the roles connect

flowchart TB
    ST[Stakeholders / Product Owner]:::dir
    PM[Project Manager]:::dir
    ST --> BA[Business Analyst]:::def
    BA --> SA[Solutions Architect / Dev Lead]:::def
    SA --> DEV[Developer]:::build
    DEV --> Q[Quality Engineer<br/>QC / QA / Test]:::build
    Q --> CE[Cloud Engineer<br/>DevOps]:::build
    CE --> ST
    DE[Data Engineer<br/>data projects only]:::opt
    SA -.-> DE
    DE -.-> CE
    PM -.-> ST
    PM -.-> SA
    PM -.-> DEV
    PM -.-> Q
    PM -.-> CE

    classDef dir fill:#fef3c7,stroke:#d97706,color:#92400e;
    classDef def fill:#dbeafe,stroke:#2563eb,color:#1e3a8a;
    classDef build fill:#dcfce7,stroke:#16a34a,color:#14532d;
    classDef opt fill:#f3e8ff,stroke:#9333ea,color:#581c87,stroke-dasharray: 5 5;

Amber = Direction, blue = Definition & Design, green = Build & Verify. The dashed purple node is an optional, project-specific role (Data Engineer), present only on data projects. See Process Overview for the layered view.

What every role page contains

Each page is structured identically so you always know where to look:

Mission - why the role exists.
Responsibilities - what it’s accountable for.
Inputs / Outputs - what it consumes and produces, and from/for whom.
AI tools & how we use them - named tools, concrete usage, example prompts.
Collaboration - hand-offs and ceremonies.
Definition of Done for the role.
Pitfalls & anti-patterns.

A note on AI across roles

Every role here is AI-augmented, but the kind of help differs: Direction roles use AI mostly for synthesis and communication; Definition roles for drafting and analysis; Build & Verify roles for generation and review. The full picture is in the AI Tooling Map.