Job Opportunities API

The Public Ledger of Openings

← Back to the ledger

Sr. Power Platform Support Engineer

Resilientco
CompanyResilientco
CategoryUncategorised
LocationArgentina
RemoteRemote
EmploymentContract
LevelNot stated
SalaryNot stated by the employer
Posted28 Jul 2026
Last verified30 Jul 2026
SourceEmployer career page (lever)
Applications are handled by the employer, not by us.Apply on the employer's site →
Description
Summary The Power Platform Support Engineer keeps the production Power Platform estate — Power Apps, Power Automate, Power Pages, and Dataverse — healthy, available, and trusted, inside a governed Center of Excellence (CoE) that the hiring manager chairs. This is an operations and support role, not a net-new build role. We need someone who can triage and resolve incidents and service requests against SLA, diagnose why a flow failed or an app broke, untangle authentication and connection issues, monitor platform health before users feel the impact, and support 50+ developers and citizen builders — all while keeping the environment from drifting into technical debt. Responsibilities • Triage, investigate, and resolve incidents (INC) and service requests (REQ) for Power Apps, Power Automate, Power Pages, and Dataverse within agreed SLA targets • Diagnose and fix Power Automate flow failures — expired OAuth tokens, broken connection references, throttling and API limits, malformed inputs, and gaps in error handling — and restore service quickly • Troubleshoot Canvas and Model-Driven app issues: delegation warnings, slow load times, data and permission errors, and browser/mobile client behavior • Monitor platform health through CoE Starter Kit analytics — proactively surfacing failing flows, orphaned apps, over-privileged connections, and capacity risks before they become incidents • Manage connections, connection references, and service account / authentication issues, coordinating with Security when OAuth or DLP controls are involved • Handle environment and access operations: access requests, environment provisioning requests, and DLP exception handling within CoE governance • Serve as first-line technical support for citizen developers — unblocking them, routing them through the CoE intake pipeline, and escalating without taking the build away from them • Perform bug fixes and minor enhancements to existing apps and flows, deploying changes through the established ALM pipeline (Dev > Test > Prod) rather than editing directly in production • Troubleshoot Power BI operational issues — dataset refresh failures, gateway connectivity, and row-level security problems • Maintain the knowledge base: known-error articles, troubleshooting runbooks, and end-user self-help documentation • Participate in root cause analysis and problem management — turning repeat incidents into permanent fixes — and escalate to developers or architects when an issue requires solution redesign Requirements • 3+ years supporting or administering Power Platform in a production enterprise environment — not personal projects or trial tenants • Strong troubleshooting instincts: can read a flow’s run history, interpret error messages, reproduce an issue, and isolate root cause instead of guessing • Power Automate support depth: authentication and OAuth token issues, connection references, throttling and API limits, retry behavior, and reading failed run outputs • Canvas and Model-Driven app troubleshooting: delegation, performance, security roles, and data/permission diagnosis • Dataverse support: security roles, table and column permissions, business rule behavior, and data integrity issues • CoE Starter Kit familiarity for monitoring and analytics — able to use it to find problems, not just read about it • DLP policy awareness: understands how connector classification causes solutions to break, and how to work within policy rather than around it • SharePoint Online as a data source and integration target: lists, document libraries, and known performance limits • ITSM discipline: comfortable working an incident/request/problem queue against SLAs, documenting tickets clearly, and communicating status to end users and stakeholders • Clear written communication for non-technical users and for knowledge-base articles • Able to give and receive substantive reviews without defensive friction STRONGLY
HOUSE ADYou found the opening. Now track it.Tracker, radar and AI drafts in one place.erioun.com →