Custom Software Application Development
Budget: ₹400 – ₹750 INR
Role: Document/data-matching engineer (contract, MVP-first)
Core skills (must have)
Solid Python; comfortable building and shipping a working pipeline end-to-end.
OCR / text extraction from images and screenshots (Tesseract, PaddleOCR, or cloud document AI like Google Document AI / AWS Textract). Screenshots are clean inputs, so this is competence, not heroics.
Data matching / entity resolution: fuzzy string matching, normalization of names/numbers/dates, similarity scoring — the real heart of the job.
Confidence scoring and thresholding: building a "match / probable / flag for review" output, not just yes/no.
Comfortable using LLMs/embeddings for semantic comparison where rules fall short.
I am looking for someone in India to match timzone. Mumbai based dev is preferred
How I Work — Project Engagement Principles
Please read before we start. These are how I run every project so we are aligned from day one. None of this reflects on you personally — it is simply how I keep delivery clean, predictable, and fair to both of us.
1. The code lives in the project repository
All work is committed to a repository I own, from the first commit. You are added as a contributor with the access you need. There is no separate or private copy — the project always lives in one shared place.
2. No single point of failure
Work is documented well enough that another developer could pick it up. I may bring in a second contributor when it makes sense, and that is normal — not a sign of distrust. Knowledge stays with the project, not locked in one person.
3. Transparency and communication
We hold a short weekly check-in with a working demo and a brief written status. You are comfortable explaining the reasoning behind your technical decisions when asked. Clear answers matter more than perfect ones.
4. Milestones and payment
Work is scoped into milestones with agreed dates. Payment is tied to milestone acceptance, not deferred entirely to the end. Small, visible steps keep us both honest about progress.
5. Availability and priority
We agree realistic timelines and the time you can commit. If you take on other work that could affect delivery, you tell me in advance. Surprises about availability are the one thing that breaks trust fastest.
6. Decisions and client communication
I am the decision-maker and the point of contact for the client. You keep me informed; you do not communicate with the client or change scope on my behalf unless we have agreed it. One clear line of decision-making keeps the project sane.
If these work for you, we will get along very well. If any of them do not, please tell me now — it is far better to align before we begin than to discover a mismatch mid-project.
Core skills (must have)
Solid Python; comfortable building and shipping a working pipeline end-to-end.
OCR / text extraction from images and screenshots (Tesseract, PaddleOCR, or cloud document AI like Google Document AI / AWS Textract). Screenshots are clean inputs, so this is competence, not heroics.
Data matching / entity resolution: fuzzy string matching, normalization of names/numbers/dates, similarity scoring — the real heart of the job.
Confidence scoring and thresholding: building a "match / probable / flag for review" output, not just yes/no.
Comfortable using LLMs/embeddings for semantic comparison where rules fall short.
I am looking for someone in India to match timzone. Mumbai based dev is preferred
How I Work — Project Engagement Principles
Please read before we start. These are how I run every project so we are aligned from day one. None of this reflects on you personally — it is simply how I keep delivery clean, predictable, and fair to both of us.
1. The code lives in the project repository
All work is committed to a repository I own, from the first commit. You are added as a contributor with the access you need. There is no separate or private copy — the project always lives in one shared place.
2. No single point of failure
Work is documented well enough that another developer could pick it up. I may bring in a second contributor when it makes sense, and that is normal — not a sign of distrust. Knowledge stays with the project, not locked in one person.
3. Transparency and communication
We hold a short weekly check-in with a working demo and a brief written status. You are comfortable explaining the reasoning behind your technical decisions when asked. Clear answers matter more than perfect ones.
4. Milestones and payment
Work is scoped into milestones with agreed dates. Payment is tied to milestone acceptance, not deferred entirely to the end. Small, visible steps keep us both honest about progress.
5. Availability and priority
We agree realistic timelines and the time you can commit. If you take on other work that could affect delivery, you tell me in advance. Surprises about availability are the one thing that breaks trust fastest.
6. Decisions and client communication
I am the decision-maker and the point of contact for the client. You keep me informed; you do not communicate with the client or change scope on my behalf unless we have agreed it. One clear line of decision-making keeps the project sane.
If these work for you, we will get along very well. If any of them do not, please tell me now — it is far better to align before we begin than to discover a mismatch mid-project.