Full-Stack .NET/Azure Architect for Membership Platform

We are building a large-scale membership and operations management platform designed to support an international organization with multiple offices in different countries.

The system will allow users to register online, apply for membership, participate in events and activities, communicate with local offices, and manage their involvement in the organization.

The platform must support thousands of members, multiple offices, and structured management roles while maintaining high security and scalability.

This is not a simple CRUD website — it is a full operational platform.

We are looking for an experienced .NET / Azure architect or senior developer to help design and potentially build the system.

Architecture Direction

The system will start as a Modular Monolith (v1) but must be designed microservice-ready so modules can be extracted into independent services in the future.

We want clean architecture with clear module boundaries and good long-term maintainability.

Planned Technology Stack

Backend
• ASP.NET Core / .NET

Frontend
• Blazor

API Layer
• GraphQL

Cloud
• Microsoft Azure

Hosting
• Azure App Service

Database
• SQL Server and/or Cosmos DB

Architecture style
• Modular Monolith
• Domain Driven Design (DDD) principles
• Event-driven communication internally where appropriate

DevOps
• GitHub for CI/CD

Core Platform Features

The system will contain several major modules.

Identity & Access Management

• User registration and login
• Role-based access control
• Different permission levels for local and global administrators
• Office-based visibility and permissions

Membership Management

• User profiles
• Membership applications
• Application review workflows
• Membership approval process
• Membership history tracking
• Education and training records
• Participation in events and activities
• Records of contributions within the organization

Multi-Office Structure

The system must support multiple offices located in different countries.

Features include:

• Members assigned to specific offices
• Local office management roles
• Central/global management oversight
• Office-specific dashboards and management tools

Events & Activities

The system must support event and activity management.

Examples include:

• Online events
• In-person events
• Free events
• Paid events
• Attendance tracking
• QR code attendance scanning
• Manual attendance management
• Visibility levels (all members, specific offices, restricted groups)

Payments & Donations

Financial functionality will include:

• Membership payments
• Donations
• One-time payments
• Recurring payments

Requirements:

• Multiple currencies
• Local payment options possible
• Integration with payment providers such as Stripe or PayPal

Complaints & Case Management

The platform must include a complaints management module to handle internal issues in a structured and transparent way.

Key capabilities:

• Members or administrators can submit complaints
• Complaints include description, category, related member (if applicable), and supporting evidence
• Each complaint follows a tracked workflow (Submitted → Under Review → Investigation → Resolved/Closed)
• Authorized staff can review cases, add notes, attach documents, and escalate when necessary
• All actions must be logged for audit purposes

Impact on Membership

Complaint outcomes may affect membership status, including:

• Warning issued
• Temporary suspension
• Activity restrictions
• Membership termination

Each member profile should maintain a complaint history showing cases, outcomes, and actions taken.


Communication System

The platform will include internal communication tools.

• Notifications and alerts
• Announcements
• Newsletters
• Messaging between users and reviewers
• Office-specific or global communications

Surveys & Reporting

Administrative tools will include:

• Survey creation
• Data collection
• Reporting dashboards
• Operational insights and exports

Office Transfer Workflow

Members should be able to request transfers between offices.

Example workflow:

Member submits transfer request

Current office reviews request

Target office accepts or rejects

Member record is updated

Member Data

The platform will manage detailed member information including:

Basic Information
• Name
• Gender
• Date of birth
• Place of birth
• Relationship status

Contact Information
• Phone number
• Email
• Address

Membership Data
• Membership ID
• Membership history
• Office assignment

Activity Data
• Participation in events
• Education/training history
• Contribution records

Sensitive files may include identity document photos and profile photos, which must be securely stored.

Security & Design Requirements

The system must follow good engineering practices.

• Secure storage of sensitive data
• Encryption where appropriate
• Clean modular architecture
• Clear separation of modules/domains
• Scalable system design
• Audit logging and traceability
• Production-ready code standards

What We Need From the Freelancer

We are looking for help with architecture design and possibly development.

Initial responsibilities may include:

• Reviewing and refining system architecture
• Defining module boundaries (bounded contexts)
• Designing database schemas
• Designing GraphQL APIs
• Defining workflow processes
• Structuring the codebase
• Creating technical documentation
• Setting up the initial solution skeleton

Later phases may include development of core modules.

Ideal Candidate

Strong experience with:

• .NET / ASP.NET Core
• Azure architecture
• Blazor
• GraphQL APIs
• Domain-driven design
• Modular monolith architecture
• Scalable enterprise systems

Experience building membership platforms, CRM-like systems, or operational management platforms is a strong advantage.

When Applying Please Include

• Summary of relevant experience
• Examples of .NET / Azure projects
• Experience with modular monolith or microservice-ready systems
• Your recommended architecture approach
• Whether you can help with both design and development
• Estimated timeline for architecture phase