Job Description & Details
This is a hands-on technical role focused heavily on modernizing legal systems by shifting legacy platforms into SharePoint Online and sunsetting aging InfoPath solutions. If you like untangling old architectures and replacing them with clean automation, this gig will keep you busy and genuinely useful to the team.
What You'll Actually Be Doing
Your day-to-day will revolve around evaluating existing Legal SharePoint sites, planning their migration path, and executing the actual content and structure moves to SharePoint Online. You'll also spend a good chunk of your time digging through legacy InfoPath forms and workflows, figuring out how they tick so you can rebuild them properly using modern tooling. Expect to work closely with stakeholders to understand their current pain points and translate those manual bottlenecks into automated wins.
The Core Tech Stack
SharePoint Online and Power Automate are your bread and butter here. You need deep, practical familiarity with SharePoint's modern architecture, permissions models, and migration strategies. On top of that, knowing your way around Power Automate and the broader Power Platform is critical because you'll be writing the exact replacement workflows for all those retiring InfoPath forms.
Interview Expectations
When you talk to the hiring manager, expect them to ask you how you handle a messy migration where content ownership is unclear and metadata is completely broken. They want to hear a methodical approach to auditing sites before moving them, rather than just lifting and shifting garbage into a new cloud tenant. You'll also likely get grilled on error handling in Power Automate—specifically, how you design flows so they don't silently fail when a user inputs bad data or a permission drops.
Application Advice
Make sure your resume doesn't just list SharePoint as a skill, but explicitly highlights actual migrations you've pulled off from on-prem or older tenants to SharePoint Online. Bring up InfoPath and Power Automate front and center, using exact keywords from the job description so you easily clear the ATS filters. If you have any specific examples of complex workflows you automated to replace legacy forms, spell out the business impact clearly.