Faheem Musthafa

Full-stack Developer · Lincole Group · Malappuram

I came to building software by first learning how it breaks.

My first programs were Python scripts that poked at networks — a packet sniffer, a cipher tool, a password checker. That turned into a cyber-security internship at Prodigy InfoTech in 2024, nights on Hack The Box and TryHackMe, and eventually ShadowHound, a recon toolkit for authorised pentests.

Somewhere in there I noticed I liked building the thing more than breaking it. Since 2025 I've been shipping full-stack products: hackathon builds like RouteReport Live, then client work — ERP and school systems, AI tools like RateCheck and Kerala AI Checker, a farm site, an invoice generator. Today I'm a full-stack developer at Lincole Group and take on freelance work alongside it.

  1. Where I am

    Malappuram, Kerala, IndiaIST · UTC+5:30Remote

    Malappuram, in the north of Kerala. I work remotely with clients and teams elsewhere; my day runs on IST, which overlaps the European morning and the Gulf working day.

  2. The path

    Four years, one direction: from looking for holes to building things that don't have them.

    1. 2023

      First tools

      Packet sniffer, Caesar-cipher utility, password checker. Learned Python by writing things that poke at networks.

    2. 2024

      Security intern

      Cyber-security internship at Prodigy InfoTech. CodeX Wi-Fi pentest kit, PassGuardian. Nights on HTB and TryHackMe.

    3. 2025

      Recon toolkit

      Shipped ShadowHound — modular recon and vuln discovery for authorised pentests. First hackathon builds.

    4. 2026

      Building for clients

      Full-stack products end to end: RateCheck, The Signal, Kerala AI Checker, ERP and LMS systems.

  3. Now

    Lincole Group · Full-stack DeveloperOpen for freelance

    I build internal systems and web products end to end at Lincole Group. Alongside that I take freelance and contract work: full-stack apps, AI-powered tools, SaaS MVPs, ERP and internal systems, backend and cloud infrastructure.

  4. How I work

    • Threat model first. Before the first line of a feature I ask how it could be abused. Designing the abuse out is cheaper than patching it in.
    • End to end. Frontend, API, database, deployment, DNS. I'd rather own the whole path than hand off at a boundary and hope.
    • Boring infrastructure. Postgres, Docker, a plain Linux box or a managed platform. I self-host what I can on my own hardware and pick the dull, well-documented option when it's a toss-up.
    • Write it down. A README that actually explains the thing, and decisions noted where they were made. The next person is usually me.

  5. Tools

    TypeScript end to end, Python where it earns its place, Postgres under everything. The security kit still comes out for audits.

    Now · Product engineering

    • TypeScript
    • Next.js
    • React
    • FastAPI
    • PostgreSQL
    • Supabase
    • Docker
    • GCP
    • Cloudflare

    Then · Offensive security

    • Python
    • Bash
    • Nmap
    • Scapy
    • Wireshark
    • Burp Suite
    • Aircrack-ng
    • Linux

  6. Learning

    On the desk right now: GCP and Terraform for infrastructure I can rebuild from a file, DevSecOps, and system design for the multi-tenant products I keep being asked for.

    • Terraform
    • DevSecOps
    • System design

  7. Say hello

    Email is the best way to reach me. Tell me what you're building and where it's stuck.

    faheemcp241@gmail.com