Senior SharePoint Consultant

About us

Infomineo is a pioneering global AI-enhanced research company that transforms how businesses access, analyze, and act on critical intelligence. We've evolved from traditional business research outsourcing to become the strategic partner that combines cutting-edge artificial intelligence with deep human expertise. We offer 3 services to our global clients (leading consulting companies, Fortune 500 companies, and government entities): AI and Data Advisory, Next-Gen Insights and Resource Scaling. This is made possible by relying on 3 pillars of excellence: 1) 350+ industry experts spread across 5 offices (Cairo, Casablanca, Mexico City, Dubai, Barcelona), 2) Our proprietary AI orchestrator, 3) Extensive knowledge assets combining 500,000+ delivered case studies and database subscriptions.

Ready to kick start your career with us?

Requirements

About this role

A client runs a SharePoint intranet maintained by a single person who has no coding or design background. We are delivering a pilot: a redesigned homepage, then one working use case. If the client is happy, the remaining use cases follow as a larger programme.

The constraint that defines this role: their security policy gives us no accounts and no access to their tenant, and no client data may leave their environment. You will build everything in our own Microsoft 365 tenant and hand it over as a deployable package. Their maintainer presses the buttons. You will never see production.

· Duration: Pilot of roughly 4 to 6 weeks, with a strong likelihood of extension into the full rollout (1 year).

· Commitment: Full-time or close to it across the pilot window.

· Location: Remote, with some sessions scheduled around the client's working hours.

· Team: You, an Infomineo graphic designer, and an engagement lead. You are the only SharePoint specialist on the project.

What will you do?

Take end-to-end ownership of the SharePoint pilot, covering the following areas:

1. Pilot Delivery

· Homepage build: Deliver a modern communication site homepage from approved designs - layout, theming, navigation, native web parts, and any custom components the design genuinely requires.

· First use case: Scope and build one client use case end to end, chosen with the engagement lead once the homepage lands.

· Scope discipline: Push back when a request adds custom code for cosmetic gain. Out of the box wins unless there is a real reason it cannot.

1. Build and Hand Over Across a Tenant Boundary

· Mirror environment: Stand up and maintain a working replica of the client's site structure in our tenant, populated with synthetic content only.

· Portable artefacts: Package every deliverable so it survives the move - PnP provisioning templates, .sppkg files, site scripts, theme JSON, design assets.

· Runbooks: Write deployment instructions precise enough for a non-technical person to follow unsupervised, including rollback steps.

· Drift management: Anticipate where the client's real tenant will differ from ours - policies, existing branding, permissions, retention - and design around it rather than discovering it on deployment day.

1. Implementation Craft

· Design fidelity: Turn mockups into working pages that match the spec on spacing, type scale, states and behavior. Raise conflicts with the designer early rather than approximating.

· Responsive and accessible: Every page works on mobile and meets WCAG 2.1 AA. That is a requirement, not a stretch goal.

· Supported customization: Achieve the look through themes, site designs and SPFx. No CSS injection hacks that break at the next Microsoft release.

· Performance: Keep page load sensible and watch what your web parts do to first render.

1. Client Enablement

· Paired deployment: Run screenshare sessions where the client's maintainer drives and you navigate. Deploy through them, not around them.

· Practical teaching: Explain what you built in terms the maintainer can act on. Assume no coding background and no appetite for jargon.

· Documentation that lasts: Leave behind material the client can still use after the engagement ends.

1. Shaping the Rollout

· Estimation: Give honest effort estimates for the remaining use cases based on what the pilot actually taught you.

· Reusability: Build the homepage so its components and patterns carry into later phases instead of being rewritten.

· Risk flagging: Tell the engagement lead early when something will not work, will cost more than quoted, or depends on a client decision nobody has made.

Who are you?

EDUCATION & PROFESSIONAL EXPERIENCE

Bachelor's or master’s degree in computer science, Information Systems, Software Engineering, or a related field. 5+ years of professional experience working with SharePoint, including at least 3 years working with SharePoint Online and modern SharePoint experiences. Proven experience delivering SharePoint intranets, communication sites, or modern digital workplace solutions. A portfolio of delivered SharePoint intranet or communication-site projects that you can demonstrate and discuss. Previous consulting or contract delivery experience. Experience working with security-constrained, regulated, or otherwise restricted client environments is highly desirable. Experience working as the primary or sole SharePoint specialist on a project is highly desirable. Professional proficiency in English; French or another relevant client language is a plus.

TECHNICAL SKILLS

Strong hands-on experience with SharePoint Online modern experiences. Strong understanding of communication sites, team sites, hub sites, site designs, site scripts, navigation, themes, page layouts, lists, libraries, and native web parts.

Proven production experience developing SPFx web parts and extensions. Strong hands-on experience with React and TypeScript. Experience with the complete SPFx build, bundle, package, and deployment workflow. Solid HTML and CSS fundamentals. Practical understanding of accessibility and experience delivering WCAG 2.1 AA-compliant interfaces.

Strong hands-on experience with PnP PowerShell. Experience creating repeatable and maintainable provisioning processes.

Understanding of Graph API permissions, delegated/application permissions, and tenant administrator consent. Familiarity with REST APIs and authentication concepts is expected.

Good understanding of the SharePoint App Catalog and SPFx approval process. Understanding of what a tenant administrator must approve before custom code or integrations can run. Familiarity with SharePoint permissions, application permissions, API scopes, and tenant-level configuration. Experience in preparing deployment packages and technical documentation for administrators.

Working knowledge of Power Automate and Power Apps. Ability to recognise when Power Platform provides a simpler or more cost-effective solution than custom SPFx development. Understanding of SharePoint integration with Power Platform and associated deployment considerations.

INTERPERSONAL SKILLS

Comfortable taking ownership as the sole SharePoint specialist on an engagement. Able to work independently without direct access to the client's production environment. Strong troubleshooting skills, including the ability to diagnose issues from screenshots, logs, configuration information, and user feedback. Excellent written communication skills, with the ability to produce precise and practical deployment documentation. Able to teach and enable a client maintainer without assuming prior coding or SharePoint expertise. Pragmatic and able to distinguish between genuine technical requirements and unnecessary customization. Proactive in identifying dependencies, risks, and decisions that could affect delivery.

Benefits

· Real ownership: One specialist, one client, clear deliverables. Nobody sits between you and the work.

· A puzzle worth solving: Delivering into a tenant you cannot touch is a real engineering problem. Getting the handover model right is most of the value we are selling.

· Runway beyond the pilot: The pilot is the audition for a multi-use-case rollout.