Power Platform Architect - Remote USA/Canada Contract — Columbus
Traveler-Friendly Insight
This role is remote but geographically restricted to the USA or Canada, which significantly limits flexibility for digital nomads. The core constraint is a 6-hour overlap with the US Eastern Time zone, meaning you must be available during ET business hours — roughly 9 AM–3 PM ET minimum. This essentially anchors you to North American or closely aligned time zones.
For nomads already based in the Americas, the timezone requirement is workable. However, popular nomad hubs in Europe (Lisbon, UTC+1) or Southeast Asia (Bangkok, UTC+7) are effectively ruled out unless you're willing to keep unconventional hours.
Visa considerations: Since the employer explicitly requires USA or Canada residency (or at minimum a legal right to work there), tourist or digital nomad visas in third countries would not satisfy this requirement. You would need to be physically or legally established in one of these two countries.
Workload structure: The part-time commitment (30 hrs/week Phase 1, 10 hrs/week Phase 2) could suit a contractor juggling multiple clients. Phase 2 especially — at only 10 hours/week — leaves room for parallel projects.
- No travel perks, coworking allowances, or equipment stipends mentioned
- Contract/consulting nature (via Toptal) means no traditional benefits
- Best suited for North American-based nomads or contractors with a stable US/CA base
Headquarters: Toptal (Remote)
We are looking for a Power Platform Solutions Architect for a global pharmaceutical company. The goal is to assess and modernize an existing Power Platform solution, define the target architecture, and lead the technical design of a scalable and secure implementation.
Required Skills:
- Deep hands-on experience with Microsoft Power Platform, including Power Apps (canvas and model-driven), Power Automate, Dataverse, Power Pages, and Power BI
- Strong experience designing Dataverse schemas and security roles
- Azure architecture experience with API Management, Azure Functions, Key Vault, Entra ID/SSO, and Azure Monitor/Application Insights
- Experience designing enterprise integration architectures, including integrations where counterpart APIs or contracts are uncertain, changing, or being migrated
- Experience integrating enterprise applications with ERP systems
- Experience designing identity and access models for licensed and unlicensed user audiences
- Strong understanding of Microsoft Power Platform licensing models, including per-user Dataverse licensing and capacity/session-based Power Pages licensing
- Experience evaluating existing solutions and defining modernization, remediation, or rebuild strategies
Optional Skills (not mandatory):
- SAP integration experience
Deliverables:
- Lead the technical assessment of the existing Power Apps application, Power Automate flows, data layer, Power BI reporting, and four integration touchpoints
- Support the Regulatory data-profiling spike and incorporate findings into the target solution architecture
- Define and evaluate costed patch and rebuild options and support the final technical recommendation
- Produce a detailed and staffed Phase 2 implementation plan
- Design the consolidated Dataverse entity model and define workflow and business-logic architecture
- Define the target integration architecture across the four integration touchpoints
- Configure the Entra ID access model for licensed and unlicensed audiences
- Configure the shared Azure API Management, Key Vault, and monitoring architecture supporting the integrations
- Produce the technical handover documentation for the implemented solution
General Information:
- Location: USA or Canada only
- Overlap: 6 hours with the East Coast time zone (USA ET)
- Commitment: Approximately 30 hours per week during Phase 1 and 10 hours per week during Phase 2
Frequently Asked Questions
Is this a fully remote position?
How many hours per week does this role require?
Is SAP experience required for this role?
What is the hiring process for this role?
What are the main deliverables expected from this architect role?
