Step 1 of 5
Earned
Cloud foundation
AWS Certified Cloud Practitioner
Exam CLF-C02
Validates foundational AWS cloud, security, architecture, billing, and support knowledge.
Official certificationSilindokuhle Lammack Mapiyeye
I help businesses build production-ready SaaS platforms with Laravel, Next.js, APIs, RBAC, payments, dashboards, and cloud deployment.
AWS Certified Cloud Practitioner; DVA-C02 in progress, followed by DOP-C02, MLA-C01, and SCS-C03.
Laravel and Next.js SaaS systems
APIs, auth, RBAC, payments, AI
AWS Certified Cloud Practitioner
Engineering Depth
The portfolio is structured to show Laravel/Next.js delivery, API design, RBAC, integrations, queues, cloud operations, and practical proof through real projects.
Core stack
Laravel, Next.js, TypeScript
Focused on SaaS features, API design, product workflows, and frontend delivery.
Product depth
RBAC, payments, AI, queues
Backend-heavy features shaped around real SaaS workflows and maintainable delivery.
Cloud and operations
AWS CCP, DVA-C02 in progress
Cloud decisions are backed by certification progress, release confidence, monitoring, and production support.
Profile
See where I fit, inspect the work behind the claims, and choose the fastest way to start a conversation.

Available Signal
Open to permanent-role conversations and focused contract or freelance work that fits around current commitments.
Public Positioning
Full-Stack SaaS Engineer
A practical full-stack profile focused on SaaS systems, delivery depth, and production-minded implementation.
Primary Work
Laravel, Next.js, APIs
Backend-heavy product work with frontend delivery, integrations, queues, caching, RBAC, and deployment support.
Trust Signal
Proof over decoration
Verified case studies, public repositories, a current CV, and direct contact paths make the work easy to inspect.
Profile Assets
Explore the case studies and public repositories, download the latest CV, or start a project conversation directly.
About
I bring together product engineering, backend architecture, and infrastructure thinking so software decisions remain valuable beyond the first release.
Mindset
I approach product work by understanding business constraints, data flow, operational risks, and the long-term cost of implementation choices.
Translate requirements into maintainable architecture
Reduce delivery friction for future contributors
Design with operational ownership in mind
Execution
From Laravel backends and Next.js interfaces to AWS deployment paths, I connect product delivery with the environments that keep systems reliable. I am AWS Certified Cloud Practitioner and preparing for AWS Certified Developer - Associate.
Application and API architecture
Frontend systems with strong UX discipline
Deployment-aware implementation decisions
Impact
I prioritize patterns that improve release confidence, clarify system boundaries, and make complex products easier to evolve.
Scalability-oriented architecture
Operational resilience and observability mindset
Mentorship and technical leadership
Skills Analytics
The skills section combines visual breadth with the engineering priorities that shape how systems are designed, optimized, and shipped.
Radar Overview
The chart emphasizes how frontend, backend, DevOps, cloud, API, and delivery disciplines reinforce each other in production environments.
Frontend
Component systems, server rendering, modern UX implementation, and production-ready interfaces for high-signal digital products.
Backend
Robust application logic, service boundaries, database-aware implementation, and API integration patterns designed for reliability.
DevOps
Delivery pipelines, infrastructure topology, release automation, and environment management aligned to business continuity.
Performance improvements
Optimization-led delivery
Application and API work is framed around throughput, maintainability, and reduced bottlenecks.
System scalability
Architecture for growth
Service boundaries, cloud topology, and deployment patterns are chosen with scale readiness in mind.
Deployment efficiency
Automation-first mindset
Release workflows are treated as product-critical systems rather than afterthoughts.
Experience
Each role is framed around context, execution, and impact so recruiters and hiring managers can quickly see both technical depth and ownership scope.
Promilezi
Built and evolved product systems across Laravel, React, and Next.js while contributing to infrastructure decisions, API integration strategy, and developer mentorship.
Challenge
Deliver product functionality quickly without compromising maintainability, integration flexibility, or the long-term scalability of the platform.
Architecture impact
Scalability-oriented decisions
Technical choices were framed around extensibility and system growth readiness.
Delivery value
End-to-end feature ownership
Frontend, backend, and integration concerns were handled as one coherent delivery stream.
Leadership signal
Mentorship and guidance
Developer support reinforced consistency and implementation quality across the team.
Execution
Implemented full-stack features across frontend and backend surfaces.
Contributed to architecture decisions that improved extensibility and ownership clarity.
Worked through API integration challenges with an emphasis on stable, scalable application flows.
Supported team capability through mentoring and reinforcement of sound engineering patterns.
Outcome Framing
Stronger alignment between product delivery and technical architecture.
Greater confidence in scaling feature work across a growing system surface area.
Better maintainability through architecture-conscious implementation and team guidance.
Worldwide Advisory Services
Worked on Laravel and Blade-driven systems with an emphasis on disciplined delivery, practical collaboration, and continuity from wireframes to implementation.
Challenge
Maintain delivery speed and implementation quality inside an established product environment where clarity, iteration discipline, and collaboration mattered.
Implementation quality
Maintainable PHP delivery
Systems work stayed grounded in practical patterns suitable for continued evolution.
Workflow value
Wireframe-to-build continuity
Planning fidelity helped reduce wasted iteration during implementation.
Team fit
Agile execution discipline
Delivery aligned well with structured product collaboration and iteration cycles.
Execution
Built and maintained features in Laravel and Blade-based product flows.
Worked within agile delivery rhythms to move requirements into production-ready implementations.
Used wireframes and planning artifacts to reduce ambiguity before development effort was committed.
Focused on pragmatic, maintainable system improvements rather than one-off solutions.
Outcome Framing
Improved continuity from planning to production implementation.
Reduced delivery friction through clearer translation of UI intent into maintainable code.
Supported more predictable execution inside a collaborative product workflow.
Invoke Solutions
Worked across application delivery and operational systems using AWS, Docker, Jenkins, and hands-on server management for Linux and Windows environments.
Challenge
Bridge the gap between shipping application code and maintaining reliable cloud infrastructure, deployment workflows, and environment consistency.
Deployment efficiency
Automation-first workflows
CI/CD processes reduced release friction and improved repeatability.
Infrastructure scope
AWS-backed operational ownership
Cloud decisions were connected directly to deployment and runtime needs.
Platform resilience
Environment consistency
Docker and server operations improved confidence across delivery environments.
Execution
Contributed to AWS infrastructure across EC2, ECS, S3, VPC, and related deployment concerns.
Used Docker to improve consistency between environments and support repeatable delivery workflows.
Built and maintained Jenkins-based CI/CD processes for safer, more efficient releases.
Handled server management responsibilities across both Linux and Windows systems.
Outcome Framing
Improved release consistency by treating deployment workflows as core engineering systems.
Strengthened environment reliability through automation-oriented operational practices.
Expanded full-stack capability through direct infrastructure ownership.
ICEP
Focused on Node.js backend development, REST APIs, and database design, establishing the service-oriented foundation that later expanded into full-stack and DevOps breadth.
Challenge
Build reliable backend services with clean data modeling and practical API design in a way that supported future extensibility.
Backend foundation
API-first development
RESTful thinking shaped how services were modeled and integrated.
Data discipline
Structured database design
Data modeling choices supported cleaner application behavior and maintenance.
Career leverage
Foundation for broader systems work
Early backend depth became a platform for later full-stack and DevOps capability.
Execution
Developed Node.js backend functionality with emphasis on clear service responsibilities.
Implemented REST API patterns suitable for application integration and maintainability.
Worked on database design choices that supported stable data flows and application logic.
Outcome Framing
Established strong backend fundamentals that informed later architectural work.
Built practical experience in clean API design and service boundaries.
Strengthened understanding of how data design affects application reliability.
DevOps
This section shows how CI/CD, cloud architecture, containerization, and server operations support reliable releases and scalable systems.
Delivery Workflow
The DevOps story is framed as a lifecycle: automate the build path, validate early, package consistently, deploy intentionally, and support the runtime environment with real operational ownership.
Build
Turn application changes into repeatable artifacts through structured automation and disciplined packaging.
Validate
Use pipeline checks and environment consistency to reduce avoidable release issues before deployment.
Package
Use Docker-driven packaging to improve parity and simplify movement across environments.
Deploy
Ship through AWS-aware infrastructure decisions that support scalability, reach, and operational control.
Operate
Support systems through server management, troubleshooting, and a reliability-first operations mindset.
Release confidence
Automation-backed delivery
Pipelines reduce manual risk and make deployment behavior more predictable.
Environment parity
Container-driven consistency
Docker helps align development and runtime expectations more closely.
Infrastructure alignment
AWS certified foundation
AWS services are framed as architecture decisions, backed by Cloud Practitioner certification and DVA-C02 preparation.
CI/CD
Jenkins-based automation is positioned as a delivery system that reduces manual friction and improves release confidence.
Automated build and deployment flow
Release consistency across environments
Safer iteration with clearer operational control
Platform value
Delivery speed backed by process reliability
Containers
Containerization is used to reduce environment drift and support predictable handoff from development into runtime environments.
Environment consistency
Cleaner packaging for deployments
Reduced setup friction across systems
Platform value
Platform consistency across build and runtime stages
Cloud
Cloud decisions are framed around system requirements using EC2, ECS, S3, VPC, and CloudFront as practical infrastructure building blocks, strengthened by AWS Cloud Practitioner certification and Developer Associate preparation.
Infrastructure topology aligned to workloads
Scalable deployment surfaces
Operational design tied to product outcomes
Platform value
Architecture choices grounded in real platform needs
Operations
Operational ownership extends beyond provisioning into environment management, runtime reliability, and practical troubleshooting across server platforms.
Cross-platform server administration
Operational issue resolution
Reliability-minded environment management
Platform value
Practical ownership of live infrastructure concerns
AWS certification roadmap
The roadmap follows the work I want to own: build AWS applications first, automate and operate them reliably, add production machine learning capability, then deepen cloud security.
Step 1 of 5
Earned
Cloud foundation
Exam CLF-C02
Validates foundational AWS cloud, security, architecture, billing, and support knowledge.
Official certificationStep 2 of 5
In progress
Application development
Exam DVA-C02
Deepens practical skill in developing, deploying, securing, and troubleshooting AWS applications.
Official certificationStep 3 of 5
Planned
Delivery and operations
Exam DOP-C02
Builds advanced capability in CI/CD, observability, resilient systems, and automated operations.
Official certificationStep 4 of 5
Planned
Production machine learning
Exam MLA-C01
Extends the path into implementing, deploying, and maintaining production machine learning solutions.
Official certificationStep 5 of 5
Planned
Cloud security
Exam SCS-C03
Completes the roadmap with deeper protection of AWS workloads, data, identities, and applications.
Official certificationCredential status is explicit: Cloud Practitioner is earned, Developer Associate is in progress, and the remaining badges show the planned learning path rather than certifications currently held.
Projects
Each highlight is designed to communicate the type of product, platform, and delivery work that has shaped this portfolio.
Beauty Salon Management
A major full-stack proof project for salon operations, tenant-aware workflows, Paystack payment integration, Spatie-powered access control, and management dashboards.
Booking payment flow, wallet payments, cash tracking, product sales, and refunds
Spatie Permission, tenant-scoped users, and admin/provider operations
Lead proof of commercial SaaS architecture across customer, staff, owner, and super-admin workflows
Impact focus
Primary project proof asset for SaaS, payments, RBAC, and multi-tenant operations
Document Search Portal
A PHP and Angular document search application with PDF/TXT upload, MySQL FULLTEXT search, fallback matching, suggestions, highlighting, pagination, and cached results.
REST API with focused backend services
PDF/TXT parsing and searchable document content
Search suggestions, highlighting, caching, and responsive states
Impact focus
Second proof asset after the salon SaaS platform
Risk Management / RBAC
A verified Laravel API and Next.js platform with protected risk, control, action-plan, and dashboard workflows for role-aware users.
Sanctum authentication with seeded admin and super-admin permission differences
Service-layer APIs, resources, migrations, seeders, and feature tests
Browser-verified risk, control, action-plan, and dashboard pages
Impact focus
Verified technical proof for Laravel APIs, RBAC, protected workflows, and Next.js integration
DevPrep AWS Study System
A React and TypeScript study system that turns AWS Developer Associate DVA-C02 preparation into a structured 14-day workflow with persistent progress.
Daily plans, visible session timing, tips, and questions
Domain learning, service comparisons, practice, review, and mock exams
Responsive product states, local progress persistence, and 18 passing Vitest tests
Impact focus
Live product proof for React, TypeScript, responsive state design, testing, and AWS learning workflows
Featured Case Study
A multi-tenant SaaS platform for beauty salons with customer booking, RBAC, provider approval, payments, product sales, staff leave, reporting, and role-specific dashboards.

Provider Approval
Super-admin provider review with pending, approved, rejected, and suspended counts.

Booking Confirmation
Confirmed booking reference with customer, salon, service, date, time, and status.

Product Sales
Tenant-scoped POS products, sales totals, cart state, and safe product image fallbacks.

Marketplace
Customer-facing promotions, services, discounts, imagery, favorites, and booking CTAs.

Users & RBAC
Owner user management and role-aware staff/admin access proof.

Mobile Product Flow
Customer product route verified at 390px with no horizontal overflow.
My Role
Designed, implemented, verified, and packaged the project proof for portfolio use.
Built frontend product surfaces across public, customer, staff, owner/admin, and super-admin workflows.
Verified Laravel API behavior for booking, payments, products, staff leave, provider approval, role scopes, and seeded demo data.
Published sanitized public proof repositories after keeping the original backend history private for secret-safety reasons.
Key Features
Customer booking flows with available slots, staff assignment, booking references, and confirmation screens.
Paystack card-payment initialization and verification, plus wallet and cash payment flows.
Product marketplace, inventory management, product sales, purchase history, and refund paths.
Role-aware admin, customer, staff, and super-admin dashboards with protected navigation.
Tenant profile, provider approval, staff leave, reviews, rewards, referrals, reporting, and global search modules.
Responsive customer views verified at 390px mobile width.
Technical Decisions
Lead the project section with this platform because it shows commercial SaaS depth across money movement, operations, access control, and tenant-aware data.
Used Laravel Sanctum for API authentication and Spatie Permission for roles and permission checks.
Modeled tenant ownership through tenant IDs, tenant profile routes, provider approval workflows, and tenant-scoped backend queries.
Separated card, wallet, and cash payment behavior so booking confirmation can match the payment method's real-world flow.
Used clean public proof repositories instead of exposing original backend history that contained an old test-key risk.
Verified Proof
Browser logged in as Owner, Customer, and Super Admin and confirmed role-specific navigation.
Frontend lint/build passed in both original and clean public proof repositories.
Targeted backend workflow tests passed across booking, payments, product sales, provider approval, staff leave, and role scopes.
Selected screenshots are committed into the public frontend proof README.
Featured Case Study
A full-stack document search application for uploading PDF/TXT files, parsing document content, and returning useful search results with suggestions, highlighting, pagination, and cached responses.
PDF/TXT upload and content extraction.
MySQL FULLTEXT search with LIKE fallback for short queries.
Search suggestions, highlighted result context, pagination, and sorting.
Featured Case Study
A Laravel API and Next.js frontend proof project for authentication, protected workflows, roles, permissions, risk registers, controls, action plans, and dashboard summaries.
Authentication flow between Laravel API and Next.js frontend.
Protected route workflow for authenticated product screens.
Seeded roles and permissions for admin and super-admin proof.
Live Product Proof
A live guided AWS Developer Associate DVA-C02 study product with daily sessions, practice, review, mock exams, skill tracking, and readiness signals.
Daily study plans with a persistent session timer, tips, and questions.
Domain learning, AWS service comparisons, practice questions, spaced review, and mock exams.
Skill tracking, study history, progress persistence, and readiness signals.
Verified AI Prototype
A Next.js 16 GRC dashboard prototype with Mazwi, a module-aware assistant backed by a server-side OpenAI streaming route and seeded enterprise demo data.
GRC dashboards and workflows for risk, asset, incident, audit, compliance, governance, and performance modules.
Mazwi assistant with route-aware module context, quick suggestions, chat history, preferences, voice-input UI, and Markdown responses.
Streaming `/api/chat` route with seeded business context and response-driven heatmap, chart, metric, progress, and table triggers.
Live Portfolio Proof
A Next.js portfolio system built to position Silindokuhle as a Full-Stack SaaS Engineer, collect project proof, and support future contract/freelance opportunities.
One-page portfolio with hash navigation, profile snapshot, skills visualization, experience, projects, architecture, and contact sections.
Reusable data-driven project proof cards that can expand as screenshots, metrics, and live demos become available.
Responsive layout and anchor behavior verified on mobile viewport sizes.
Case Study Explorer
Use this panel to compare role, stack, build decisions, proof status, and links without leaving the portfolio.
Selected Project
A multi-tenant SaaS platform for beauty salons with customer booking, RBAC, provider approval, payments, product sales, staff leave, reporting, and role-specific dashboards.

Provider Approval
Super-admin provider review with pending, approved, rejected, and suspended counts.

Booking Confirmation
Confirmed booking reference with customer, salon, service, date, time, and status.

Product Sales
Tenant-scoped POS products, sales totals, cart state, and safe product image fallbacks.

Marketplace
Customer-facing promotions, services, discounts, imagery, favorites, and booking CTAs.

Users & RBAC
Owner user management and role-aware staff/admin access proof.

Mobile Product Flow
Customer product route verified at 390px with no horizontal overflow.
My Role
Designed, implemented, verified, and packaged the project proof for portfolio use.
Built frontend product surfaces across public, customer, staff, owner/admin, and super-admin workflows.
Verified Laravel API behavior for booking, payments, products, staff leave, provider approval, role scopes, and seeded demo data.
Published sanitized public proof repositories after keeping the original backend history private for secret-safety reasons.
Key Features
Customer booking flows with available slots, staff assignment, booking references, and confirmation screens.
Paystack card-payment initialization and verification, plus wallet and cash payment flows.
Product marketplace, inventory management, product sales, purchase history, and refund paths.
Role-aware admin, customer, staff, and super-admin dashboards with protected navigation.
Tenant profile, provider approval, staff leave, reviews, rewards, referrals, reporting, and global search modules.
Responsive customer views verified at 390px mobile width.
Technical Decisions
Lead the project section with this platform because it shows commercial SaaS depth across money movement, operations, access control, and tenant-aware data.
Used Laravel Sanctum for API authentication and Spatie Permission for roles and permission checks.
Modeled tenant ownership through tenant IDs, tenant profile routes, provider approval workflows, and tenant-scoped backend queries.
Separated card, wallet, and cash payment behavior so booking confirmation can match the payment method's real-world flow.
Used clean public proof repositories instead of exposing original backend history that contained an old test-key risk.
Verified Proof
Browser logged in as Owner, Customer, and Super Admin and confirmed role-specific navigation.
Frontend lint/build passed in both original and clean public proof repositories.
Targeted backend workflow tests passed across booking, payments, product sales, provider approval, staff leave, and role scopes.
Selected screenshots are committed into the public frontend proof README.
Architecture
The section maps how experience layers, backend services, data concerns, and delivery infrastructure fit together to support maintainable software systems.
Experience Layer
Interfaces are structured to support usability, performance, and stable integration with backend systems.
Next.js and React applications
Reusable UI systems
Performance-aware rendering
Application Layer
Laravel and Node.js services are designed around explicit responsibilities, clear integration paths, and resilient business logic.
REST APIs and integrations
Maintainable service logic
Scalable application flows
Data and Throughput
Databases, caches, and infrastructure choices are aligned to application behavior rather than added as generic complexity.
MySQL and Redis patterns
Data access discipline
Bottleneck-aware design
Delivery and Infrastructure
AWS topology, Docker workflows, and Jenkins automation are treated as core product infrastructure, supported by AWS Cloud Practitioner certification and Developer Associate study.
AWS services mapping
Containerized workflows
Release automation and control
Contact
Currently available for freelance SaaS builds, Laravel APIs, dashboards, payment workflows, and Next.js product interfaces.
Let’s Connect
Send the goal, workflow, timeline, and budget range if you have one. I will help turn it into a clear technical path.
Best fit
Full-stack SaaS, Laravel/Next.js, API, integration, RBAC, payments, AI, and deployment work.
Value focus
Maintainable APIs, useful product workflows, release confidence, and clear handover.
Availability
Currently available for focused freelance and contract work with clear scope, milestones, and handoff.
Project Email
Messages go to the main email account used across the portfolio.
slmapiyeye@gmail.com
Best for recruiter outreach, contract conversations, and direct engineering opportunities.
linkedin.com/in/silindokuhle-mapiyeye
Use LinkedIn for networking, recruiter outreach, contract conversations, and public professional context.
+27 67 944 1219
Best for quick project questions, availability checks, and fast follow-up conversations.
GitHub
github.com/silindokuhleL
Public repositories, case-study candidates, and project proof for Laravel, Next.js, API, and SaaS work.