Interface
Multi-department interface, server and client rendering depending on each screen's real need.
Data flows, cloud, applied AI, security, governance and deployment — the depth behind the demonstration.
1. Functional Architecture
Every layer has a clear responsibility — operational systems stay the source of truth, integration never duplicates authority, and AI only steps in once the data is reliable.
2. Technical Architecture
Multi-department interface, server and client rendering depending on each screen's real need.
BigQuery as the consolidated analytical source of truth; on-prem SQL Server stays the operational system of record — no duplicated authority.
Serverless deployment, file storage, asynchronous events, scheduled jobs, secrets never hardcoded.
AI-assisted extraction and reasoning — always paired with deterministic validation, never shipped raw.
Federated authentication, role-based permissions — never implicit access to sensitive data.
Continuous integration and deployment, versioned and traceable images before anything reaches production.
3. Data
The question isn't "where does the data live" but "who owns it." BigQuery consolidates for analysis and cross-department visibility; existing operational systems stay the authority on their domain.
Architecture decision example — illustrative
4. Cloud
Cloud Run means paying for actual usage instead of always-on capacity — relevant for variable operational load. Pub/Sub decouples components so a slowdown in one service doesn't block another; Secret Manager keeps credentials out of the code.
5. Applied AI
Document AI extracts information from incoming documents; Vertex AI / Gemini reasons over the consolidated context. In both cases, deterministic validation protects critical business rules — the same principle as the previous page: AI proposes, it never executes an operationally impactful action alone.
6. Security
Okta/OIDC for federated authentication instead of a homegrown password system. RBAC so every role sees exactly what it needs — never more. Secrets live in Secret Manager, never in code or a versioned config file.
7. Governance
Every data domain has a clear owner. Important architecture decisions are documented, not just implemented — so the next person understands why, not just what.
8. CI/CD
9. Steve's Actual Role
| Domain | Contribution |
|---|---|
| Functional and technical architecture | End-to-end design, from business need to implementation. |
| Data and cloud | Chose BigQuery as the analytical source of truth; Cloud Run / GCS / Pub-Sub architecture. |
| Applied AI | Integrated Document AI and Vertex AI / Gemini, with deterministic validation. |
| Security and governance | OIDC authentication, RBAC permissions, secrets management. |
| CI/CD | Azure DevOps pipelines, versioned images via Artifact Registry. |
10. Target Roles
Operations
Digital Transformation
Business / Technology Intersection
Continuing Education
Between March and June 2026, structured training covering cloud infrastructure, security, networking, Kubernetes, Terraform and generative AI — all completed and passed.
Training completed
Completed March 2026 — Google Cloud
Certifications in progress
Next step
Describe the current situation — a real operational problem is enough of a starting point.