CTO · FOUNDER · ENGINEERPort Louis · working worldwide

// the short version

VINCE

I take expensive software problems all the way to production.

Product, security, infrastructure, and AI systems where a confident mistake costs more than a slow answer. I build the system, lead the team, and stay for production.

proof before adjectives40+ production systems · 2020 to now
00the operating system

How the work
moves.

inputExpensive problemWho loses time, money, or trust?
stream aProductMake the useful moment visible.
stream bSystemBuild the boring parts that keep it running.
stream cRiskDefine failure, access, privacy, and recovery.
independent gateEvidenceTests · citations · records · review
outputProductionThen document, demonstrate, and distribute.
rule 01locked

Start with the expensive problem.

Missed orders, wrong payroll answers, weak access controls, repeated UI bugs. The cost of doing nothing tells me whether the work matters.

rule 02locked

Show the useful moment early.

A product should make sense in one screen or one short flow. If the result needs a long explanation, the product still needs work.

rule 03locked

Draw the real graph.

Independent work runs side by side. Real dependencies stay ordered. Shared files, approvals, and merge points get explicit owners.

rule 04locked

Verify on evidence.

Tests that ran, citations a person can open, audit records, production logs, and human review. A model agreeing with itself is not proof.

rule 05locked

Pay for control when it matters.

Free tiers are fine for experiments. Customer data, uptime, privacy, and predictable capacity need a production decision and a fallback.

rule 061 → many

Turn work into reusable proof.

One shipped system can become a case study, a field note, a demo, a hiring story, and a sales answer. The work stays the source.

01the subject

What stays
redacted.

This is the short version. The work is public; the personal details are not. The black bars keep it that way. Tap or hover them.

I am the CTO at Nourishubs, the founder of Bienzoli, and a senior engineer at SD Worx. I build products, lead technical teams, and deal with production when it gets messy.

nameVince Erkadoo
age22
location20°09′S 57°30′E · Port Louis, Mauritius
roleCTO · Founder · Senior Engineer. Builds systems. Leads the people who build them.
output40+ systems in production, 4 countries
educationMSc Software Project Management (UoM, → 2027) · BSc Web & Multimedia · Stanford ML
motivePeople are stuck in work that wastes them. Software is the way out.
everything else█████████████████████████
02the record

Where it shipped.

Nourishubs

Chief Technology Officer (Contract)

  • ·Joined as Technical Lead and moved into the CTO role. Lead 10 engineers, designers, and QA on a school meals platform live in 4 countries.
  • ·Own the architecture and final approval across Next.js, Python, Node.js, and .NET services.
  • ·Built and released the React Native mobile app for iOS and Android, including App Store and Play Store rollouts.
  • ·Directed the ISO 27001 implementation end to end, mapped onto 4 national privacy laws. See case 001.
  • ·Run production infrastructure on Docker, Kubernetes (AWS EKS), and Azure. Resolved outages at cluster level.
  • ·Use Claude Code, Cursor, and Codex for development, QA, and incident response, with engineers reviewing the output.
  • Next.jsReact NativeNode.js.NETPythonAWS EKSDockerISO 27001
Jun 2025 · present
  • ·Founded Bienzoli, a free POS, invoicing, and inventory product for Mauritian small businesses. It handles barcode scanning, stock, quotes, and CRM from a phone.
  • ·Built the whole platform solo with Next.js, Prisma, PostgreSQL, a PWA front end, and cookie free analytics.
  • ·Run the product, brand, launch films, and sales work in English, French, and Kreol.
  • ·Delivered an ecommerce, CRM, and invoicing system for an auto parts client through the agency arm.
  • Next.jsPrismaPostgreSQLPWAStripe
2025 · present

SD Worx

Senior Software Engineer

  • ·Built an HR and payroll assistant that cites policy sources, refuses unsupported questions, and is measured on wrong answer rate. See case 002.
  • ·Designed a component library inspired by shadcn/ui. It is now the shared design base across products. See case 003.
  • ·Built and maintain an HR vacancy site: Drupal headless CMS + Next.js front end.
  • ·Mentor 3 juniors. CI/CD with Docker + Azure DevOps cut deployment times by more than 50%.
  • Next.jsDrupal.NETNode.jsAzureRAG
Jun 2024 · present

Zapproach

Full Stack Software Engineer

  • ·Led development of NPCC Enterprise Go Digital, a national procurement portal with sealed bids, evaluation scoring, RBAC, and immutable audit logs.
  • ·Led development of an electronic wallet with ledgered transactions, 3D Secure payments, reconciliation webhooks, idempotency keys, and KYC.
  • ·Built a government tender PMIS covering the procurement lifecycle, committee approvals, and Power BI reporting.
  • ·.NET Web APIs in Onion Architecture. React, Vue, React Native, Blazor. LangChain on Azure OpenAI, YOLOv8.
  • .NETVueReactNode.jsLangChainYOLOv8
Aug 2022 · Jun 2024

Zapproach

Junior Front End Developer

  • ·Built the front end of a PCI certified payment gateway with stronger client side security.
  • ·Responsive design, performance tuning, WCAG/ARIA accessibility.
  • JavaScriptCSS3ARIAPCI
Sep 2021 · Aug 2022

Linkeo

Web Developer

  • ·Built responsive client sites with SEO and conversion focused design that lifted organic traffic for local businesses.
  • CMSSEO
May 2021 · Sep 2021

Freelance

Web Developer

  • ·Took WordPress and custom sites from Figma or Sketch prototypes through mobile first builds, hosting, and handover.
  • WordPressFigma
Aug 2020 · May 2021
03case files

Three case studies.

40+
systems in production
4
countries deployed
10+
engineers led
27001
ISO · security, led
001case file · nourishubs · iso 27001
led implementation

Security that matches the code.

// the problem

Nourishubs handles children's data in 4 countries. Each country has its own privacy law, so one generic compliance checklist was never going to be enough.

// what he did

  • 01Led the ISO 27001 information security implementation across the stack.
  • 02Mapped the systems, assets, threats, owners, and controls in the risk assessment.
  • 03Defined access rules and kept evidence of who could reach each system.
  • 04Prepared the records and evidence needed for audit.
  • 05Mapped the international standard onto local law in every country of operation.

// why it matters

I led the security work at 22 while running the 10 person engineering team. Reading the code made the policies more realistic, and writing the policies exposed gaps in the code.

proof

Risk register, access records, control owners, and audit preparation across four countries.

constraint

One management system had to respect four different national privacy laws.

ISO 27001Risk assessmentAccess controlAudit prepAzureDocker
002case file · sd worx · hr and payroll assistant
in progress

An assistant that knows when to stop.

// the problem

HR and payroll answers sit across dense policy documents. Staff lose time finding the right rule, and a confident wrong answer can affect someone's pay.

client internals: ████ nda ████

// what he did

  • 01Built document ingestion, chunking, embeddings, and retrieval over the policy set.
  • 02Grounded answers with citations. Every claim points back to the document that says so.
  • 03Guardrails: it answers from policy or it doesn't answer. No improvising with people's pay.
  • 04Measured wrong answer rate against a fixed test set before judging the demo.

// why it matters

This is still in development inside a major HR and payroll company. The work is mostly about retrieval quality, clear refusals, and repeatable testing. The chat interface is the easy part.

proof

A fixed question set measures confident wrong answers. Every supported answer cites the policy source.

constraint

In progress and under NDA. No client internals or invented performance claims.

RAGEmbeddingsVector retrievalAnswer validationCitationsTest harness
003case file · sd worx · component library
shipped · in production

One system. Every product.

// the problem

Teams were rebuilding the same interface patterns across projects. That created design drift, repeated bugs, and avoidable review work.

// what he did

  • 01Built a component library inspired by shadcn/ui, including tokens, primitives, and reusable patterns.
  • 02Made it the shared source for interface work across projects.
  • 03Trained 3 junior engineers to use and extend it.

// why it matters

Teams can build new screens from known parts, and fixes apply across the products that use them. The library also gives junior engineers a clear standard to follow.

proof

The shared tokens, primitives, and patterns are used across products and by the 3 junior engineers I mentor.

constraint

The record proves adoption, not an invented percentage for time saved or defects removed.

ReactTypeScriptDesign tokensNext.jsDrupal
04the build log

Things I made.

// live in production · click through

// personal builds

TechKours

2025 · present

Platform that closes the gap between theory and shipping. Real projects, real mentorship, front to back.

Next.jsMongoDBPrismaStripeOpenAI

Mobet

2024 · present

Sports betting research and bankroll tracker that collects trusted tips and curates daily picks.

Next.jsRedisStripeOpenAI

MoTalent

2024 · present

Job board with tailored matches, employer profiles, and detailed filtering.

Next.jsPrismaOpenAI

MoNature

2024
★ hackathon winner

Social platform for conservation. Auth, donations, cloud media. IEEE Hackathon winner.

Next.jsCloudinaryStripe

MoTravel

2024

Travel booking built on Amadeus APIs, with live flight and hotel data plus secure payments.

Next.jsAmadeusMongoDB

MoPet

2025

Pet adoption and donation platform with campaigns, a vet finder, and assisted pet matching.

NestJSSupabaseStripeOpenAI
05answers from the portfolio dossier

Ask the concierge.

Ask about my work, projects, or experience. Answers come from a fixed dossier. Direct questions get direct answers.

// awaiting query

generated answers use a fixed dossier. anything else is redacted.

06field notes

Written down.

Each note starts with work I have done: a system shipped, a failure found, or a decision I had to defend. The same evidence becomes a case study, a short explanation, or a direct answer when someone asks.

all field notes →
07recruiter role check

Paste the job.
See the match.

Paste a job description and compare it with my actual record. The result gives you a match score, supporting evidence, and the gaps I would need to close.

// job description
0 chars
// verdict

the machine is waiting.

08get in

Bring a real
question.

Send the problem, who it affects, and what failure costs. I will answer directly. I ignore vague solicitation.

vincecodeBLACKOUT v1.0 · build. say less.© 2026 · 20°09′S 57°30′E