Open · 1 project slot

Five-star client reviews · 2,000+ clients served

Engr Mejba Ahmed — AI Developer, Software Engineer and Founder & CEO, at his workstation in Dhaka.

Engr Mejba Ahmed Founder & CEO, ColorPark · AI Developer · Software Engineer

Your AI system, live in weeks — not next quarter.

One engineer scopes it, builds it, ships it — and stays accountable after launch. You talk to the person writing the code, not an account manager relaying status.

Replies within one business day · Dhaka, UTC+6 · overlap with EU and US East

  • 8+ Years
    engineering
  • 1,500+ Projects
    shipped
  • 2,000+ Clients
    served
  • 3 Companies
    founded

Client reviews

Four people who paid, in their own words.

Verified reviews left by clients on the freelance marketplaces, quoted exactly as written. Reviews of delivered work, not engineering references — the technical detail is further down this page.

Rated 5 out of 5.

“Second time hiring this service⁠—perfect and fast delivery again. Thank you!”
tonylee512 Spain

Rated 5 out of 5.

“Everything went smoothly⁠—was a truly positive experience.”
levitompkins Australia

Rated 5 out of 5.

“ColorPark resolved my spam issue promptly⁠—amazing service, thank you!”
tempoaudiogroup United Kingdom

Rated 5 out of 5.

“Easy to work with, explained every step and delivered on time. Highly recommended!”
maxparsimony Greece

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.

Decisions take minutes, not sprints

You get an answer inside one business day, because there is no internal round trip to approve it.

Whoever built it still answers

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.

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

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 and what done looks like. You get a written scope before any code.

  2. Architect

    Data model, service boundaries, failure modes. Decisions get written down with their reasoning.

  3. Ship

    Small releases behind CI into a real environment. Progress every week, not one reveal.

  4. Operate

    Monitoring, runbooks, and a person who answers. Finished means it runs without you watching.

That is what the first two weeks look like. Scope yours on WhatsApp

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, a written scope, a delivery date. Built once, properly.

Best for new builds, migrations, replatforms.

Reply within one business day.

Most common

Monthly retainer

Time reserved for you every month. Features, fixes, upgrades, on-call cover.

Best for live products with a roadmap.

Reply within one business day.

Advisory sprint

A hard review of a system you run: architecture, security, cost. And a plan.

Best for teams with engineers but no direction.

Reply within one business day.

For whoever evaluates this technically

The stack, and the record.

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

Backend
LaravelPythonFastAPINode.jsGo
Frontend
ReactNext.jsVueTypeScript
Cloud
AWSDockerKubernetesTerraform
Data & AI
PostgreSQLRedisOpenAILangChainn8n
  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? Ask me on WhatsApp (opens WhatsApp)

Tell me what needs to work.

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