Business Technology Analyst partnering with business and IT stakeholders to develop, enhance, and support technology solutions using Microsoft Power Platform and related Microsoft 365 applications.
Compensation
We offer attractive, competitive compensation and benefits including, medical, dental, 401k, short-term disability, AD&D, tuition reimbursement, and more.
Responsibilities
Partner with business users to understand business needs and translate requirements into effective technology solutions.
Develop, enhance, and support Microsoft Power Apps, Power Automate workflows, SharePoint solutions, and related Microsoft 365 applications.
Troubleshoot and resolve application, workflow, security, permission, integration, and data-related issues.
Analyze existing business processes and applications to identify opportunities for automation, modernization, and improved efficiency.
Support modernization of legacy SharePoint, Nintex Forms, and Nintex Workflows using Microsoft Power Platform technologies.
Requirements
Bachelor's degree required. Degree in Computer Science, Information Systems, Electrical Engineering, or equivalent preferred
Nice to have: Microsoft Certified: Power Platform Developer Associate (PL-400/AB-400)
Nice to have: Power Platform Fundamentals (PL-900)
Nice to have: Intelligent Applications Builder Associate (AB-410)
Nice to have: Copilot and Agent Administration Fundamentals (AB-900)
Design and build Dataverse schemas, Power Automate flows, security roles, and generative code pages for Power Platform modernization workstreams.
Decode and faithfully replicate the behavior of existing, already-deployed systems by reading their exported source directly, not just working from requirements documents.
Go beyond no-code and low-code tooling when needed by authoring raw Dataverse Web API and metadata calls, debugging flows through run history and API tooling, and diagnosing undocumented platform behavior through direct testing.
Own the technical integrity of cross-environment integrations, JIT identity provisioning, service-account patterns, and the security model, including roles and privilege scoping.
Identify and clearly document design divergences from source systems, distinguishing verified behavior, new functionality, accepted simplifications, and assumptions.
Requirements
Nice to have: public-sector or government modernization
Nice to have: audit- and compliance-grade data trails
