Engineering

Developers

Who actually writes your software, how the work is run, and an open door for freelance developers who want projects through GhazTech.

Open to freelance collaborators Replies within one working day Remote-first · Tamil Nadu Practising since 2024

Mohamed Ghazzali

Founder & Developer · GhazTech

  • Based inPonnamaravathi, Pudukkottai District, Tamil Nadu
  • PractisingIndependently since 2024
  • Works inDesktop software, web, automation, databases, AI-assisted tools
  • LanguagesEnglish and Tamil — in the software as well as the conversation
  • Direct lineEvery enquiry is read and answered by this account, not a helpdesk

GhazTech is a one-person practice. Scoping, building, handover and support are all done by the same developer, which is why the person you speak to on day one is the person still answering your call a year later.

Email directly See the work
How The Work Is Run

Four things that are true of every project

  • One person, start to finish

    No account manager in the middle, no brief passed between people. The developer who scoped it writes it, installs it and supports it.

  • Version-controlled from the first commit

    Every project lives in its own repository with a readable history, so a change can be traced, reviewed or reversed rather than guessed at.

  • Tested on the machines it will actually run on

    Software is checked on the hardware, operating system and screen sizes in your office — not only on the developer's own setup where everything is new and fast.

  • Handover includes the source

    You receive the code, the build instructions and the database structure. Nothing is held back as leverage to keep you on a contract.

Where Freelancers Plug In

Seven disciplines we sub-contract

When a project is larger than one pair of hands, these are the pieces that get handed out. Open a card to see what a brief in that discipline actually looks like.

A typical brief
A billing or stock module with a printable output, a local data store, and a keyboard-driven screen that a non-technical operator can use all day.
What we hand you
Wireframes, the data model, and a working install of the existing system so you can match its behaviour instead of inventing it.
Good fit if
You have shipped installed software before and are comfortable with packaging and updates.
A typical brief
A set of pages or a self-contained tool built against an agreed design system, delivered as static files or a small deployable app.
What we hand you
The design tokens, the component conventions already in use, and the copy. You are not asked to art-direct from nothing.
Good fit if
You write semantic HTML by choice, and you check your work on a mid-range phone before calling it done.
A typical brief
A screen or module added to an existing hybrid shell, behaving identically whether it is opened on a laptop or a phone.
What we hand you
The shell, the build pipeline and the release process. You work inside it rather than standing up your own.
Good fit if
You are comfortable with responsive layout and with the quirks of running web code outside a browser tab.
A typical brief
A report that is currently assembled by hand each month — merged, validated, formatted and produced from a single action, with the messy real-world rows handled.
What we hand you
Anonymised copies of the client's actual workbooks, including the awkward historical ones, plus the output they expect to see.
Good fit if
You have automated somebody else's spreadsheet before and know how defensive that code has to be.
A typical brief
Modelling a new area of the business, or migrating records out of an ageing system without losing the history attached to them.
What we hand you
The existing schema, sample data, and the reports the client cannot lose. Backups are ours to manage, not yours to worry about.
Good fit if
You treat someone else's production data as irreplaceable and write migrations that can be run twice safely.
A typical brief
One narrow, well-defined task inside an existing product, with a clear rule for what happens when the model is unavailable or plainly wrong.
What we hand you
The feature boundary, the accuracy bar it has to clear, and the fallback path the software takes when it does not.
Good fit if
You are more interested in the failure cases than the demo, and you can keep the cost per request predictable.
A typical brief
A month of posts and reels for one client, or a Google Business Profile and site structure rebuilt so a local search actually finds them.
What we hand you
The client's brand, the photographs, the posting calendar and the words they use about themselves. Accounts stay in the client's name throughout.
Good fit if
You can write for a Tamil Nadu audience in English or Tamil, and you measure results rather than posting and hoping.
From Application To Payment

How a freelance engagement runs

Five steps, written down so nobody has to guess what happens next or when money changes hands.

  1. You apply

    The form below, or a direct email. A portfolio link matters far more than a long covering note.

  2. A short call

    Twenty minutes to talk through what you have built and how you prefer to work. No whiteboard puzzles.

  3. One paid task

    A small, real, scoped piece of work at your quoted rate. Paid whether or not it leads to more.

  4. On the bench

    You sit in the pool for your discipline and are contacted when a matching project is signed.

  5. Delivery & payment

    Agreed scope, agreed date, agreed figure — settled on acceptance, not months afterwards.

What we look for

Evidence over enthusiasm

  • Something we can open. A live link, a repository, a downloadable build — anything real beats a list of technologies.
  • Work for a real user. A tool somebody who is not a developer actually depends on, even a small one.
  • A rate you can stand behind. Quote honestly. We would rather pay a fair figure than renegotiate mid-project.
  • Straight answers about availability. Part-time is fine. Silence for a week is not.
  • Care with client data. Most of this work touches money, stock or student records.
What you get

A scoped brief and a firm date

  • A written brief. Scope, acceptance criteria and deadline agreed before you start, not discovered along the way.
  • The client handled for you. Requirements, meetings and change requests come through GhazTech.
  • Credit on the work. Your name on the delivery record, and a reference you can use.
  • Payment on acceptance. Not on the client's payment cycle, and not conditional on the next phase being signed.
  • A developer account. Once you are on the bench you can sign in, see available tasks and claim them yourself.

Already on the bench? Sign in to your developer account.

Join The Bench

Apply to work with GhazTech

This is not a large network and there is no queue of recruiters. The form goes straight to the person who decides which projects get sub-contracted.

Fill in what you can — the meter tells you how complete your application is before you send it. Anything left blank simply means more questions come back by email.

Students: if you are looking for experience rather than paid contract work, the internship and training track is the better door.

Application strength 0%
Start with your name and email.
At least 2 — up to 8.
A link we can open counts for more than anything else here.
A short, specific paragraph beats a full CV at this stage.
Opens your email app with the application filled in.
Students & Freshers

Internships & training

Not ready to contract yet? GhazTech runs a separate track for students and recent graduates — guided project work on real briefs, with a completion certificate rather than an invoice at the end.

Guided project work Real client briefs Completion certificate
See the internship track
Before You Apply

Questions developers ask

The five that come up every time. Anything else, put it in the form.

Ask something else

Honestly: not always. GhazTech is a young practice and sub-contracting happens when a signed project is bigger than one developer can deliver on time. Applying puts you on the bench for your discipline so you are contacted when that happens — it is not a guarantee of immediate work, and we would rather say so than waste your time.

At the rate you quoted, on acceptance of the agreed scope — not when the end client settles their own invoice. The trial task is paid on the same terms even if no further work follows. Figures and dates are put in writing before you begin.

No. Requirements, meetings, revisions and scope disputes all come through GhazTech. You get a written brief and a single point of contact, which is the arrangement most freelancers say they want and rarely get.

The work is remote-first, so no. What matters is overlapping working hours for the occasional call and being reachable within a day. A few projects need someone physically present for installation in Tamil Nadu — those are flagged as such when they are offered.

Then the freelance bench is the wrong door — it is contract work with client deadlines attached. The internship and training track is built for exactly that position: guided work on real briefs, with a certificate at the end. Plenty of people move from one to the other.

Have a project instead?

If you are looking to hire GhazTech for a project rather than freelance with us, get in touch directly.

Contact GhazTech