Founder & CEO · ColorPark

AI systems for companies that depend on them.

One engineer who scopes the problem, writes the code, ships it to production, and stays accountable for how it runs. You work with the person writing the code, not an account manager relaying status.

Open — 1 project slot

Engr Mejba Ahmed — AI Developer, Software Engineer and Founder & CEO, at his workstation in Dhaka.
Engr Mejba Ahmed AI Developer Software Engineer Founder & CEO
  • 8+ Years engineering
  • 1,500+ Projects shipped
  • 2,000+ Clients served
  • 3 Companies founded

Founder-led

No account layer between you and the code.

Scoping happens with the engineer

The person estimating your build is the person who will write it. Estimates come back tighter, because nobody is guessing on someone else's behalf.

Decisions take minutes, not sprints

A schema change, a provider swap, a scope cut. You get an answer inside one business day, because there is no internal round trip to approve it.

Whoever built it still answers

Handover does not mean the knowledge walks out. I still maintain systems I shipped years ago, for clients who never had to re-explain them.

I don't ship AI demos. I ship systems that still run at 3 a.m. — monitored, maintained, and boring in the best possible way.
Engr Mejba Ahmed

Capabilities

Four things I build, end to end.

Most projects need three of these four at once. One person holding all four is why the seams between them stop being your problem.

AI Development

Agents that do real work against your data, not a chat box bolted to a landing page.

AI agents · LLM integrations · automation pipelines · chatbots

Software Engineering

Business systems that hold up under load, audit, and the third round of requirements.

Laravel · Next.js · Python and FastAPI · enterprise apps

Cloud & DevOps

Infrastructure you can rebuild from a repository, and a deploy nobody is afraid to run on a Friday.

AWS · Docker · Kubernetes · Terraform · CI/CD

Security Engineering

We find what an attacker would find, then close it and prove it stayed closed.

Penetration testing · hardening · managed security

Ventures

Where the work actually happens.

  • Ramlit Limited

    Software engineering and cloud delivery for global clients.

    Founder & CEO

  • ColorPark.io

    Creative design agency for brand, product UI, and marketing.

    Founder & CEO

  • xCyberSecurity.io

    Penetration testing and managed security operations.

    Founder & CEO

  • WPdevszone

    WordPress development and maintenance for content businesses.

    Founder

ElectronicFirst.com FZ LLC

Global digital commerce platform.

Deputy Head of Software Development · 2017 to present

How I work

Four steps. No surprises at the end.

  1. Scope

    We map the problem, the constraints, and what done looks like. You get a written scope before any code, so the estimate is something you can hold me to.

  2. Architect

    Data model, service boundaries, failure modes. Decisions get written down with the reasoning, so the next engineer inherits context instead of archaeology.

  3. Ship

    Small releases behind CI, into a real environment you can click through. You see progress every week, not in one reveal at the end.

  4. Operate

    Monitoring, alerts, runbooks, and a person who answers. A system is not finished when it deploys. It is finished when it runs without you watching it.

That is what the first two weeks look like. Book a call to scope yours.

Engagement

Three ways to work together.

The same engineer in all three. What changes is the commitment, the cadence, and how much of the running I keep afterwards.

Project build

A defined outcome with a written scope, a fixed shape, and a delivery date. Best when you know what you need and want it built once, properly.

Best for new builds, migrations, and replatforms.

Scope a build

Monthly retainer

A standing block of my time each month for the systems you already depend on. Features, fixes, upgrades, and the on-call attention that keeps small problems small.

Best for live products with a roadmap and real users.

Discuss a retainer

Advisory sprint

A short, hard review of a system you already run: architecture, security, cost, and what breaks first. You get a written plan your team can execute without me.

Best for teams with engineers but no direction.

Book an advisory sprint

Stack

The tools I reach for, in that order.

Backend
LaravelPythonFastAPINode.jsGo
Frontend
ReactNext.jsVueTypeScript
Cloud
AWSDockerKubernetesTerraform
Data & AI
PostgreSQLRedisOpenAILangChainn8n

Credentials

The record, briefly.

Dates, institutions and titles, stated plainly so you can check them before the call rather than after it.

  1. April 2018

    B.Sc. in Computer Science & Engineering

    Daffodil International University

  2. 2017 — present

    Deputy Head of Software Development

    ElectronicFirst.com FZ LLC, a global digital commerce platform

  3. Ongoing

    Founded three companies

    Ramlit Limited, ColorPark.io, and xCyberSecurity.io

  4. Base

    Mirpur, Dhaka, Bangladesh

    Remote-first, working with clients worldwide

Questions

The six things people ask first.

What timezone do you work in, and when are you available?

I work from Dhaka, UTC+6, and keep deliberate overlap with Europe and the US East Coast. Expect a reply within one business day, and calls booked in your working hours rather than mine.

Is there a minimum engagement?

Project builds start at a scope worth writing down, which in practice means two weeks or more. Retainers run monthly with one month of notice either way. An advisory sprint is the smallest way in, and it is the most common first step. I hold one project slot at a time, so the availability line at the top of this page is a real constraint rather than decoration.

Who actually writes the code?

I do. On larger builds I bring in engineers from Ramlit Limited, and I stay the technical owner: I review every merge, and I remain the person you talk to.

What happens after launch?

Your choice. I hand over documentation and runbooks and step back, or I stay on retainer and operate it. Either way, nothing goes live without monitoring and a tested way to roll it back.

Who owns the code and the IP?

You do, on final payment: repositories, infrastructure definitions, and credentials. Handover is a scheduled task with a checklist, not an email on the last day.

How do we start?

Send a short note about the problem and the deadline. If it is a fit, we book a call, and you get a written scope before you commit to anything.

Still unsure whether it is a fit? Book a call and ask.

Tell me what needs to work.

One call, no pitch deck. If I am not the right person for the job, I will say so on the call and point you somewhere better.