Tanvir Ahsan
Lead ArchitectPrincipal Software Engineer & AI Architect
Dhaka / Global Edge
Hybrid Retrieval (BM25 + RRF)3072D Vector EmbeddingsNext.js Edge SSRSystem Architecture
SquadAI & Vector Architecture Squad
142 verified sprintsLead Architect
Core operational team · Delivery command
The core team that owns the work.
AhsanWeb is not a marketplace of anonymous freelancers. This is the core operational team that scopes the architecture, assembles the squad, reviews the evidence and signs off the handoff. The wider Borderless Engineering Guild scales execution; this group owns the standard.
Strategy, implementation and verification sit in the same room, even when the room is a distributed async thread across four time zones.
Initializing core workspace
10
Core operators
5
Specialist squads
100+
Guild bench
Async-first
Operating model
Core command
Leads who carry the technical standard.
Each lead owns a specialist track, reviews the work of the guild bench and remains accountable for the final evidence pack.
Alif
IR StrategistLead Information Retrieval Engineer & Technical Partner
Dhaka / Hybrid
Crawl Log ForensicsBot Access HeadersV8 ProfilingCrawl Budget Engineering
SquadCore Information Retrieval & SEO Squad
98 verified sprintsLead Architect
M. R. Talukder
Edge SpecialistStaff Multi-Framework JS & Edge Architect
Global Remote
Next.jsNuxt 3SvelteKitRemix
SquadAll JS Frameworks & Edge Architecture Squad
84 verified sprintsStaff Engineer
Dr. F. K. Chowdhury
Lead ScientistLead AI Benchmark & Citation Scientist
London / Remote
AI Search Citation AnalysisEmbedding Similarity AnalysisGolden-Set EvaluationPython LLM Pipelines
SquadEmpirical Research & Benchmark Squad
76 verified sprintsLead Architect
S. N. Haque
Ontology LeadStaff Knowledge Graph & Entity Architect
Global Remote
Schema.org @graphWikidata AlignmentEntity DisambiguationSPARQL
SquadEntity Knowledge Graph & Schema Squad
64 verified sprintsStaff Engineer
Core bench
The specialists who make the standard repeatable.
Vector indexing, edge serialization, JS framework delivery, citation forensics and schema validation are staffed by named operators, not anonymous ticket handlers.
A. K. Ziyad
Vector CoreSenior Vector Database & Indexing Engineer
Global Remote
PineconeQdrantHNSW Tuning
SquadAI & Vector Architecture Squad
53 verified sprintsSenior Specialist
N. E. Rahman
Edge & CDNSenior Crawl Infrastructure & CDN Engineer
Global Remote
Fastly VCLCloudflare RulesAI-Bot Response Serialization
SquadCore Information Retrieval & SEO Squad
48 verified sprintsSenior Specialist
R. S. Mostafa
Frontend CoreSenior Full-Stack JS & Islands Architecture Engineer
Global Remote
SvelteKit 2Astro IslandsNuxt 3 SSR
SquadAll JS Frameworks & Edge Architecture Squad
57 verified sprintsSenior Specialist
H. Y. Kabir
Citation TraceCitation Forensics Specialist
Global Remote
AI Overview MonitoringCitation Source ExtractionMRR & nDCG Metrics
SquadEmpirical Research & Benchmark Squad
41 verified sprintsCore Contributor
K. J. Anam
Schema EngineerJSON-LD & Microdata Specialist
Global Remote
TechArticle SchemaSoftwareApplication SchemaBreadcrumbList Validation
SquadEntity Knowledge Graph & Schema Squad
39 verified sprintsCore Contributor
Operating principles
Small core. Explicit ownership. High evidence.
The operating model is deliberately narrow at the top. The core team protects architectural quality while the guild provides elastic specialist capacity.
01
One accountable owner
Every engagement has a named lead who owns the outcome end to end. There is no handoff into a general delivery queue and no ambiguity about who answers when a gate fails.
02
Architecture before output
The core team fixes the retrieval model, rendering strategy and measurement plan before production work begins. Speed comes from fewer reversals, not from skipping design.
03
Evidence over status
A deliverable is complete when it can be reproduced against a frozen baseline. Crawl diffs, citation tests, retrieval evals and Core Web Vitals traces are the language of delivery.
04
Craft over bureaucracy
The driving force behind this model is a deep focus on coding and craftsmanship, while ensuring a work environment free from bureaucratic complexities.
Delivery sequence
How the core team runs an engagement.
The same six-stage sequence applies to a crawl-budget recovery, a hybrid retrieval rebuild or a career-defining enterprise migration. The artefacts change; the control points do not.
Open the operations center01
Technical intake
Engagement leadScope, access map and measurable definition of done
02
Squad assembly
Core leadSmallest capable squad, named reviewers and RACI
03
Baseline freeze
Track specialistCrawl, citation, retrieval or performance baseline
04
Build and review
Specialist + independent reviewerWorking increment with architecture decision record
05
Verification gate
Independent reviewerBefore/after evidence tied to the original baseline
06
Handoff and watch
Engagement leadRunbook, owner map and 30-day monitoring window
Decision rights
Who decides what.
Every technical domain has one final owner. This is how the team avoids consensus paralysis without creating unaccountable authority.
| Decision | Owner | Authority |
|---|---|---|
| Architecture and retrieval design | Tanvir Ahsan | Final technical sign-off |
| Crawl, indexation and IR strategy | Alif | Track decision and baseline approval |
| Framework and edge rendering | M. R. Talukder | Implementation standard and performance gate |
| Citation measurement and evaluation | Dr. F. K. Chowdhury | Benchmark design and evidence review |
| Entity and schema architecture | S. N. Haque | Ontology and validation sign-off |
Work with the core team
Bring a real retrieval, rendering or citation problem.
We will tell you which core lead should own it, what evidence is required and whether the guild has the right specialist capacity to run it.