tanim.me
Taushif Tanim

AI engineer and product strategist. I design systems end to end — architecture, AI, infrastructure, and the business model behind them.

I build agentic systems, the infrastructure they run on, and the products they ship inside — currently architecting a model-independent agent operating system, alongside an AI language-learning platform and the editorial infrastructure behind an academic publisher.

0

years building

0

ventures & projects

0

founded & cofounded

0+

tools & frameworks

Portrait of Taushif Tanim

About

Systems first, interface second

Cofounder and builder behind Languence and Smart AI Library, and the engineer behind the editorial and peer-review infrastructure running two academic publications. Agentic AI and retrieval systems on one side, the servers and business model holding them up on the other.

More about me →

Selected work

Built and running

Languence

Cofounder & full-stack builder

An AI language-learning platform built around a conversation partner that has to hold context across sessions, adapt to a learner who plateaus, and stay cheap enough per turn to run at scale. Product vision and the entire technical build.

Conversational AIAdaptive learningFull-stack

The ICPK

Cofounder, technical & marketing lead

Editorial, peer-review, and submission infrastructure for the International Center for Promoting Knowledge — multi-role workflows, blind review, and versioned manuscripts, built to survive an academic process rather than a CMS bolted onto a publisher's site.

Publishing infrastructurePeer reviewWorkflow systems

Smart AI Library

Cofounder & technical lead

An editorial platform covering AI — research, tooling, and systems, from foundations to what shipped last week. Product, engineering, and infrastructure owned end to end, with SEO handled by a dedicated cofounder.

Editorial platformAI researchContent systems

Capability

Where the depth is

AI engineering

  • Agentic AI systems
  • Multi-agent orchestration
  • Retrieval-augmented generation
  • Context engineering & persistent memory
  • Model routing & fallback

Systems & infrastructure

  • Distributed system design
  • Rust & C++
  • Node.js, TypeScript & Python
  • PostgreSQL & data modeling
  • Redis, caching & job queues

Product engineering

  • Product & technical architecture
  • Next.js and React at production scale
  • API contracts & schema design
  • Real-time and streaming interfaces
  • Performance engineering

Strategy & growth

  • Product strategy
  • Business-model validation
  • Pricing & unit economics
  • Positioning & narrative
  • Go-to-market for technical products

What I do

What I take on

Agentic AI systems

Agents, retrieval, orchestration, and memory built for the constraints a demo never shows — cost ceilings, latency budgets, tool calls that fail, and users who don't follow the happy path.

AI infrastructure

The layer underneath the model: vector stores, routing and fallback across providers, sandboxed execution, evaluation, and the observability to tell a bad answer from a broken system.

Product architecture

Business-model validation and a system design before any code is written — then the build itself, from schema to interface, with no handoff in between.

Positioning & findability

Technical SEO, content architecture, and narrative that make a product findable and worth the click — including migrations that move a site without surrendering its rankings.

Archive

Everything else

Smaller builds, experiments, and contributions live outside the featured list.

Experience

Experience & timeline

Ongoing

The ICPK

Cofounder, technical & marketing lead — the digital and editorial infrastructure behind an academic publisher.

Ongoing

Languence

Cofounder & full-stack builder — an AI language-learning platform, product vision through production.

Ongoing

Smart AI Library

Cofounder & technical lead — an editorial platform covering AI, owned end to end.

Early stage

Axmion

Founder — architecting a model-independent AI agent operating system.

How I work

The same loop, every time

Not a framework I adopted for this page — it's genuinely how each venture above got built.

01

Analyze

Find the actual problem, the people it belongs to, and the constraints that will decide the design — before proposing anything.

02

Architect

Design the system around how it has to scale and how it will fail, not around what's fastest to start.

03

Validate

Pressure-test the business model and the riskiest assumptions before they cost engineering time.

04

Build

Ship the infrastructure end to end — schema to interface, with the same rigor as the plan.

Feedback

From people I've worked with

Working with Tanim meant the roadmap was airtight before a single line of code was written — that discipline saved us months.

AnonymousProduct Lead

He rebuilt our editorial pipeline without a single day of downtime for reviewers already mid-submission.

AnonymousManaging Editor

Rare to find someone who can move between architecture decisions and actual SEO metrics in the same conversation.

AnonymousMarketing Director

The RAG system he shipped handles edge cases our own team hadn't even mapped out yet.

AnonymousEngineering Manager

Calm under a migration that touched everything — servers, SEO, infrastructure — and none of it broke.

AnonymousHead of Growth

He explains AI tradeoffs in a way non-technical stakeholders actually retain — that's harder than it sounds.

AnonymousFounder

Working with Tanim meant the roadmap was airtight before a single line of code was written — that discipline saved us months.

AnonymousProduct Lead

He rebuilt our editorial pipeline without a single day of downtime for reviewers already mid-submission.

AnonymousManaging Editor

Rare to find someone who can move between architecture decisions and actual SEO metrics in the same conversation.

AnonymousMarketing Director

The RAG system he shipped handles edge cases our own team hadn't even mapped out yet.

AnonymousEngineering Manager

Calm under a migration that touched everything — servers, SEO, infrastructure — and none of it broke.

AnonymousHead of Growth

He explains AI tradeoffs in a way non-technical stakeholders actually retain — that's harder than it sounds.

AnonymousFounder

Get in touch

Let's build something.

Have a product, a migration, or an AI feature that needs someone to take it end to end? I'd like to hear about it.