Proactive Technology Management

Support Engineer

• Setting Up Customer Networks (cloud to keyboard)
• Windows Server Installation
• Configuration Maintenance
• Ongoing Support (access points, firewalls, and switches)
• Remote troubleshooting of client, as well as on-site when required
• Monday - Friday schedule
• One Saturday per month for the first 18 months

IT Support Technician – Dental IT, 365 & Networking

Full-stack Engineer

• The Role
• You are an embedded builder who bridges frontier AI products and production-grade reality inside our clients' operations. After our Fusion Discovery practice ships the prioritized roadmap, you are the named technical principal who turns that roadmap into running software — code, deploy, integrate, ship — inside the client's Azure subscription, against their data, under their compliance constraints, on the calendar they signed up for.
• You are the FDE in the literal sense the term means in 2026: an embedded operator with a founder's mindset who owns outcomes end to end. Discovery hands you a scoped milestone roadmap and a Statement of Work. You take it from there. You can expect to travel up to 30% of the time with this position.
• What This Role Is — And What It Is Not The FDE market is hot in 2026 and the role definition varies wildly across companies. PTM's flavor is specific, and we are explicit about it.
• You will: write production code that ships into the client's runtime. Build agentic systems with PydanticAI. Stand up event-driven ETL on Azure Container App Jobs. Scaffold lovable.dev → Static Web App frontends backed by FastAPI or ASP.NET Core BFFs (Backends-for-Frontends). Provision the whole stack with Bicep + azd. Wire structured logging, LLM cost telemetry, and the auth gateway from commit #1. Own the engagement's technical outcome.
• You will not: run discovery interviews, facilitate executive prioritization workshops, or produce the Solution Architecture Document. Our Fusion Discovery practice does that upstream and hands you their output. You may sit in on the final readout to take ownership of the implementation phase. The customer-facing volume sits with Discovery. You carry the technical volume.
• If you came into the FDE category because you want to be the engineer who actually ships the system the slideware promised — at a firm where validators are written before production code, every interface gets a documented contract, and the first commit boots a working full local stack — this is the role.
• The Outcome We Hire You For
• In your first twelve months, you will serve as the technical lead on three to five Fusion Development engagements. Each one ships:
• - A working production deployment in the client's Azure subscription, deployed via azd up and reproducible on demand.
• - Vertical slices of demonstrable client value delivered against the milestone roadmap from Discovery.
• - At least one KPI moved, with structured telemetry to prove it.
• - A clean handoff document for ongoing operations: runbooks, infrastructure contracts, and the digital twin of the decisions made along the way.
• What You Will Actually Do
• Approximate time split: ~45% writing code, ~30% integration, infrastructure, and observability plumbing, ~15% client technical touchpoints (architecture standups, demo days, escalations), ~10% specifications, interface contracts, and engagement reflections. The customer-facing volume is lower than Big Lab FDE pool roles because PTM's Discovery practice carries the customer-facing volume upstream.
• - Convert the Discovery roadmap into an executable engineering plan with swimlanes, interface contracts, and validator-first todos.
• - Scaffold the first commit as a working local full stack — frontend, backend, database, auth gateway, observability, IaC (Infrastructure as Code) — bootable with one command on a fresh clone. We do not believe in scaffold-then-wire-later.
• - Implement Python services (FastAPI BFFs, event-driven ETL on Azure Container App Jobs, PydanticAI agentic systems) under our RPIR validator-first loop: Research, Plan, Implement validators RED, implement production code GREEN, Review.
• - Build ASP.NET Core BFFs when the client's existing investment or team strength calls for it. Use .NET Aspire AppHost for local orchestration when there are three or more services or any polyglot mix.
• - Wire frontends scaffolded via lovable.dev into your BFF, hosted on Azure Static Web Apps.
• - Stand up the Azure footprint with Bicep + azd: subscription-level deployments, module contracts, mandatory tagging, Key Vault-backed configuration, and what-if gates on every pull request.
• - Instrument structured logging from commit #1 (structlog with callsite metadata), wire OTEL (OpenTelemetry) to the Aspire dev dashboard locally and to Azure Monitor in production, and emit LLM cost telemetry on every model call.
• - Stand up the auth gateway: Traefik with ForwardAuth in containers, Microsoft Entra ID by default, with Auth0, Okta, Google Workspace OIDC, AWS Cognito, or generic OIDC as first-class alternates when the client's identity posture calls for it.
• - Pair-program with the second engineer on the engagement under Maker-Checker. Solo delivery is not a PTM pattern.
• - Address the blockers that prevent AI from reaching enterprise-grade maturity in real environments: data readiness, integration complexity, state management, identity boundaries, observability gaps, and LLM cost runaway.
• - Feed lessons back into PTM's living digital twin — the Fusion Covenant, the persona library, the agentic-coding template, the methodology. Every engagement you ship updates our rules.
• The Stack You Will Work In
• PTM is Azure-first and opinionated. The stack is documented. Deviations require architect approval with written rationale captured in the SAD.
• - Backend: Python (FastAPI, Pydantic, PydanticAI for agentic systems) and ASP.NET Core (latest LTS) for BFFs and APIs. Choose by client posture and team strength.
• - Frontend: React + Vite scaffolded via lovable.dev, hosted on Azure Static Web Apps.
• - Data: Azure SQL, Dataverse, Microsoft Fabric OneLake, Azure AI Search. PostgreSQL when extensions justify it (Azure Flexible Server or self-hosted on Azure VM). Pure Python ETL with duckdb + delta-rs over PySpark unless the client has a Fabric mandate.
• - AI: Azure AI Foundry primary; OpenAI and Anthropic direct as alternates. PydanticAI for agentic systems with typed state, structured outputs, and tool calls. 12-factor agents principles.
• - Infrastructure: Bicep + azd, GitHub Actions, Docker + Azure Container Registry. .NET Aspire AppHost for local orchestration when warranted.
• - Observability: Azure Monitor, Log Analytics, Application Insights JS SDK on the frontend. Structured JSON logs with correlation IDs from day one. LLM cost telemetry mandatory on every model call.
• - Identity: Entra ID default. Auth0, Okta, Google Workspace OIDC, AWS Cognito, and generic OIDC are first-class alternates. Traefik + ForwardAuth as the containerized gateway pattern.
• - Local orchestration: .NET Aspire AppHost when there are three or more services, docker compose for homogeneous pairs, uv run for single-service spikes.
• - One-off scripts: uv with PEP 723 inline metadata. Never a half-built requirements.txt.

Forward Deployed Engineer – Implementation Technical Lead

Artificial Intelligence

• Run the 30-day AI Jumpstart Discovery cycle: kickoff, eight to fifteen department-level event-storming interviews, AI-assisted analysis, executive prioritization workshop, and final readout.
• Apply our pain-first discovery method. You surface drudgery, manual handoffs, bottlenecks, and broken approvals before any tool conversation. The "tool-first" trap is the failure mode we exist to prevent.
• Facilitate executive prioritization workshops that resolve a portfolio of 15 to 30 candidates into a ranked Top 5: three quick wins (high value, low risk) and two strategic bets (high value, high complexity), each defensible with math.
• Co-design current-state and future-state BPMN (Business Process Model and Notation) maps with department owners, applying our Digital Assembly Line model to identify where AI, document understanding, and programmatic automation replace manual toil.
• Translate findings into ROI projections the CFO will accept — labor reallocation, cycle-time reduction, denial-rate movement, throughput per FTE, audit exposure, prior-auth turnaround, whatever the workflow demands.
• Direct the four-agent deliverable pipeline that converts transcripts into client-ready artifacts (opportunity extraction → current/future BPMN → department reports → org-wide consolidation). You do not operate it line by line — that is what the Product Analyst on your engagement does — but you set quality, own QA against transcripts, and sign off before anything reaches the client.
• Address the blockers that prevent AI from reaching enterprise-grade maturity in real operations: data readiness, integration complexity, change-management friction, HIPAA and PHI boundaries, governance constructs the client cannot articulate yet.
• Act as the feedback loop into PTM's Fusion methodology and tooling. Every engagement you run produces field signal that updates our interview guide, our prompt library, our BPMN style guide, and our healthcare-vertical playbook. Your work compounds across the practice.
• Carry the relationship from Discovery into the implementation Statement of Work. You participate in scope development and maintain continuity into the build phase.

Forward Deployed Engineer – AI Consultant

Consultant

• **The role in one sentence**Lead a 90-day engagement that turns a Fortune-class regulated enterprise’s unmanaged Power Platform, Copilot Studio, and M365 estate into a governed, classified, observable, ROI-tracked capability — and convert into a PTM full-time hire on successful delivery.
• **Why this role exists**Proactive Technology Management (PTM) Fusion has committed to a 90-day Power Platform and Copilot Studio governance program for a Fortune-class regulated enterprise client. The engagement runs in two phases:
• - **Phase 1 — Discovery & Assess (30 days).** Inventory and risk-rank the estate (apps, flows, agents, environments, sensitivity-labeled data flows). Map current ALM, identity, Center of Excellence (CoE) Kit, and Microsoft Purview posture against PTM and Microsoft baselines. Quantify Copilot Studio agent exposure and observability gaps. Deliver a prioritized governance backlog with measurable ROI.
• - **Phase 2 — Implement & Govern (60 days).** Stand up the CoE Kit, Power Platform DLP and environment strategy, and Purview-aligned classification, labeling, and retention policy. Wire Application Lifecycle Management (ALM) pipelines for both makers and pro-developers. Operationalize Copilot Studio agent governance — authentication, content moderation, audit. Light up an Azure Monitor and Log Analytics observability surface tied to the agreed value metric.
• **What you'll deliver**
• - A risk-ranked inventory of every app, flow, agent, environment, **sensitivity label, and DLP policy** across the client tenant.
• - A current-state assessment of ALM, identity, Power Platform DLP, **Microsoft Purview information protection, retention, audit, and Compliance Manager posture** — mapped to PTM and Microsoft reference architectures.
• - A prioritized governance backlog with one-line ROI rationale per item, ready to drive Phase 2 scope confirmation.
• - A deployed and operating Power Platform CoE Kit with environment strategy, tenant- and environment-level DLP policies, and connector classification rationale.
• - ALM pipelines (Power Platform Pipelines or ALM Accelerator + GitHub Actions / Azure DevOps) serving both citizen-developer and pro-developer paths.
• - **A Purview governance baseline:** sensitivity label taxonomy with auto-labeling rules, M365 DLP policies covering Exchange / SharePoint / OneDrive / Teams / Endpoint, retention label and policy framework, audit (Standard or Premium) configuration, and Compliance Manager assessment posture.
• - **Copilot Studio agent governance** with authenticated Entra-bound knowledge sources, content controls, audit logging, Purview-for-Copilot DSPM-for-AI configuration, and red-team review of high-exposure agents.
• - **A live observability surface** built on **Azure Monitor, Log Analytics, Application Insights, and Power BI** — including diagnostic settings on Power Platform, KQL workbooks for governance KPIs, alert rules on policy drift, and an executive dashboard reporting against the value metric agreed during Discovery.
• - Solution Architecture Document (SAD), Solution Design Document (SDD), and milestone roadmap authored against PTM templates and reviewed under our Maker-Checker discipline.
• **Who you are**You can hold a discovery conversation with a Chief Information Officer in the morning, run an Event Storming session with a finance director after lunch, and ship a Dataverse security-role design before dinner. You communicate in plain language to business owners and in precise technical terms to engineers, often in the same meeting.
• You believe governance is a value engine, not a brake. You measure success in ROI delivered, not artifacts produced.

Senior Consultant – Power Platform, Copilot Studio, Purview

Compliance

• Lead the Microsoft Purview and M365 compliance lane of a 90-day governance engagement that turns a Fortune-class regulated enterprise’s data, DLP, and Copilot exposure surface into a classified, labeled, retained, audited capability.
• The engagement runs in two phases: Discovery & Assess (30 days) and Implement & Govern (60 days).
• Inventory the client’s M365 information protection posture, deliver a prioritized governance backlog, and stand up a label taxonomy and auto-labeling policy.
• Collaborate with a Power Platform CoE / ALM specialist, working on a shared Solution Architecture Document and milestone roadmap.

Senior Consultant – Microsoft Purview, M365 Compliance Governance

• Lead the Power Platform Center of Excellence and Application Lifecycle Management lane of a 90-day governance engagement.
• Inventory and risk-rank the estate (apps, flows, agents, environments).
• Map current ALM, identity, and CoE Kit posture against PTM and Microsoft baselines.
• Quantify Copilot Studio agent exposure, observability gaps, and maker behavior.
• Deliver a prioritized governance backlog with measurable ROI.
• Stand up the CoE Kit, environment strategy, and Power Platform DLP during Implementation.
• Operationalize Copilot Studio agent governance — authentication, content moderation, audit.
• Light up an Azure Monitor and Log Analytics observability surface tied to the agreed value metric.
• Coordinate with a Microsoft Purview / M365 compliance specialist for data classification, DLP, and retention.
• Deliver architecture artifacts to a CTO-level audience: C4 diagrams, SADs, SDDs.

Senior Consultant – Power Platform CoE, ALM, Copilot Studio

• Providing excellent customer service and technical support in various client environments
• Working closely with a single client supporting multiple locations around Newark
• Shadowing and learning team processes during the initial weeks
• Participating actively in troubleshooting and on-site projects
• Assisting in setting up customer networks from cloud to keyboard
• Maintaining configuration and providing ongoing support for network infrastructure