ATRC's Data & AI Office is a product and platform execution team - not a traditional enterprise data function. We build and operate AI-enabled systems that create measurable operational impact across the organization. Our primary output is working software in production.

What we are building - now:

• An executive reporting portal serving senior leadership, integrating live data from SAP, Microsoft 365, SuccessFactors, and internal systems across multiple operational views (finance & budget, KPIs, technology portfolio, news, wellbeing, and a personalized executive home)

• A sovereign data and AI platform: data warehouse, governed pipelines, metadata catalog, and classification enforcement across all entities

• Data mesh architecture with federated ownership - each entity owns its data products; the platform provides governed access

• Data readiness for the organization's agentic AI platform - clean, structured, governed data so AI agents can operate on trusted sources

• Operational AI agents delivering real value on top of the agentic platform (document triage, anomaly detection, automated briefings, classification automation)

• AI-enabled situational awareness and crisis management systems

• Data governance and classification - managing an active external vendor engagement, bridging framework deliverables into platform-enforced rules, and building the ongoing

  governance operations the organization requires

How we work:

• Small team, high ownership - every engineer owns a module end-to-end

• Two-week sprints with demonstrated output at every review

• Ship and improve - working systems beat perfect designs

• Core team owns all architecture and product decisions; external capacity executes within defined scope

• Decisions take hours, not weeks. Daily technical choices are made by the engineer.

• Feature scope decisions take 24 hours. Architecture pivots take 48 hours. Nothing sits in limbo.

• Oversee 5 other workstreams powered by 3rd party vendors within the ecosystem but whom we are ultimately accountable for

First assignment: build the executive reporting portal. Permanent role: own every production UI the office ships.

Mission

Your first project is the executive reporting portal - a six-tab React application integrating live data from SAP, Microsoft 365, SuccessFactors, and internal systems. You build this working directly with the office's senior technical leadership, who own the data layer and API design. You own the frontend: turning a complete Figma design into a working, responsive, role-based application that senior leadership uses daily.

Once the portal ships, you own all production frontend surfaces across the office: operator dashboards for crisis management, agent monitoring interfaces, internal tools, and any subsequent leadership-facing products. You define the frontend architecture standards for the office.

What This Role Builds - Executive Portal (First Assignment)

• React + TypeScript SPA - six tabs: personalized executive home, KPI dashboard, finance & budget, technology portfolio, news & updates, wellbeing

• Role-based views - executive (read-only summary), operational (read/write), admin (full configuration)

• Azure AD SSO integration (MSAL.js), MFA enforcement, session management

• Data visualizations - pie charts, bar charts, line charts, sparklines, progress bars, ranked leaderboards, posture indicators

• Approval workflows - pending approvals, signature requests, approve/decline actions with audit display

• Mobile responsiveness - all panels usable on a 390px viewport

• Error states - graceful handling when data is stale, partial, or unavailable

What This Role Owns - Permanent

• Frontend architecture standards - component patterns, state management, testing requirements

• CI/CD pipeline - GitHub Actions deploying to Azure App Service

• All production UIs: crisis management operator dashboard, agent interfaces, internal tools

• Frontend performance, accessibility, and cross-browser/device compatibility

Key Decisions

• Component architecture - local vs. global state vs. server-side

• Visualization library choices (Recharts, D3, Chart.js) per use case

• API polling vs. WebSocket for real-time data

• Mobile-first vs. desktop-first priority per view

• Accessibility decisions for time-critical interactions

Does Not Do

• Build or own the backend API (Backend Engineer)

• Extract data from enterprise systems (Data Platform Engineers)

• Define data models or schemas (Principal Data Architect)

• Write AI prompts or classification logic (AI Engineer)

• Define governance policies (Governance Lead)

Ideal Candidate

Has built a data-rich dashboard or executive portal used by non-technical senior leaders.

Understands that executive UI must be immediately legible - no ambiguous colour coding, no unexplained states, no loading spinners that leave users uncertain. Can take a Figma file and have working React components within days. Ships quickly, tests critical flows, and integrates against an API spec identifying missing or inconsistent fields before they become blockers. Has set frontend standards for a small team and is comfortable being the most senior frontend voice in the room.

• React 18 + TypeScript - hooks, context, component composition, performance optimization

• Data visualization - Recharts, D3.js, or Chart.js; knows when to use which

• Tailwind CSS or equivalent - responsive layout, mobile-first design

• Figma-to-code - takes a polished Figma design and faithfully implements it without a designer in the loop

• MSAL.js - Azure AD authentication in SPAs

• REST API integration - fetch/axios, error handling, loading states, optimistic updates

• State management - React Query or Zustand

• GitHub Actions - frontend CI/CD pipeline

• Mobile responsiveness - CSS Grid/Flexbox, viewport testing across devices

• Vitest / React Testing Library

• WebSocket or SSE for real-time data feeds