Search

Microsoft Solutions Architect

PublishedPublished: 6/14/2022
Technology

Job Description

ABOUT THE ROLE

\n

eSoftware Associates Inc. is a nationwide U.S.-based Microsoft partner delivering Power Platform, SharePoint, Microsoft 365, and Azure solutions to commercial, nonprofit, and public-sector clients. We are adding a senior architect who designs solutions and builds them personally, leading Copilot agent and Power Platform delivery across concurrent client engagements. We are open to full-time, part-time, or contract engagement, and the structure is agreed with the selected candidate. The work is the same either way: defined scope, committed dates, and production solutions.

\n


\n

WHAT YOU WILL DO

\n

• Design and build - own engagements from requirements through design, build, testing, deployment, and post-launch support. This is a hands-on role, not an oversight role.

\n

• Deliver Copilot agents - agents grounded on client SharePoint and enterprise data, taking actions through Power Automate and custom connectors, deployed in Teams and Outlook.

\n

• Lead technically - set build standards, review other developers’ work, and supply hour-level estimates before proposals are finalized.

\n

• Work with clients - run discovery and working sessions, demonstrate solutions, and document the work so another developer can maintain it.

\n


\n

CORE SKILLS

\n

Experience

\n

    \n
  • Seven or more years delivering Microsoft solutions as a hands-on developer or architect, across multiple clients rather than a single internal environment.
  • \n

\n

Copilot Studio

\n

    \n
  • Agents you personally built and placed into production: instructions, topics, knowledge sources, and actions. Conversational and autonomous agents. One production agent you can walk through carries more weight than years listed.
  • \n

\n

Solution architecture

\n

    \n
  • You translate a business requirement into the right Microsoft design, and you recognize when Copilot Studio is, and is not, the right tool for the problem.
  • \n

\n

Power Platform

\n

    \n
  • Five or more years hands-on: canvas and model-driven Power Apps, Power Automate, Dataverse data models, and custom connectors built for real business processes.
  • \n

\n

ALM and governance

\n

    \n
  • Managed solutions, environment strategy, environment variables, connection references, and deployment pipelines. DLP policies and managed environments. Production changes are deployed, not rebuilt by hand.
  • \n

\n

SharePoint and Microsoft 365

\n

    \n
  • SharePoint Online as a platform you build on, not only a data source: information architecture, permissions, Teams, and Microsoft Graph integration.
  • \n

\n

Identity and security

\n

    \n
  • Entra ID, app registrations, and OAuth. Agents and apps honor each user’s own access rights, and you verify that behavior before release.
  • \n

\n

Pro-code and Azure AI

\n

    \n
  • C# and .NET or TypeScript, SPFx, and PowerShell with PnP. Azure OpenAI and AI Search where the solution calls for them.
  • \n

\n

Client delivery

\n

    \n
  • Multiple clients, including tenants you do not administer and restricted connector policies. You explain decisions in plain language and raise scope questions in writing.
  • \n

\n


\n

ENGAGEMENT EXPECTATIONS

\n

• Status reporting - a written weekly update covering completed work, planned work, and open blockers.

\n

• Time tracking - hours logged daily, or as work is completed, in ESW’s time tracking system.

\n

• Budget notice - written notice when logged hours approach 75% of the estimate with scope outstanding.

\n

• Client communication - project correspondence through Basecamp; engagement ownership remains with ESW.

Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...