B.Sc. in Computer Science and Engineering
Daffodil International University
Relevant Coursework: Data Structures, Algorithms, Database Systems, Machine Learning, Software Engineering
Experience
Work history
Production systems, teams, and outcomes. Each role below includes responsibilities and what I learned.
-
Founder · OPENCODEHUB
OpenCodeHub an open-source startup building a free, self-hosted alternative to GitHub. Run it on your own infrastructure with SSH access, CI pipelines, and AI-assisted code review your code never touches our servers. We're growing a community layer around it: a place to discover and share projects without giving up ownership of your files
Free, self-hosted alternative to GitHub with SSH access, CI pipelines, and AI-assisted code review, plus a community layer for discovering and sharing projects. Users host their own code; OpenCodeHub never stores or touches user files.
Key Responsibilities
- Architect and maintain the core self-hosted Git platform, including SSH access and CI pipeline support
- Build and iterate on the AI-assisted code review feature
- Set technical direction and roadmap as sole creator of the project
- Review community contributions and manage open-source issues/PRs
- Design the community/discovery layer while preserving the no-data-stored architecture
- Write documentation and onboarding guides for self-hosters
opencodehub.space ↗Key Learnings
- Designing SSH-based auth without ever touching or storing user code is harder than it looks ,the architecture has to prove it, not just claim it
- Building CI pipelines that work generically across self-hosted setups means less control than a hosted platform, which changes how you design defaults
- AI-assisted code review adds real value but has to stay optional, since self-hosters vary widely in what infrastructure they're willing to run
- Growing an open-source community takes different skills than shipping code , issue triage and contributor onboarding are their own discipline
- Solo-maintaining a project forces ruthless prioritization; you can't build everything, so the roadmap has to reflect what users actually ask for, not what's technically interesting
-
Co-Founder & Lead Data/Backend Engineer · BoringRats (Acquired ✓)
Co-founded and scaled BoringRats to 1M+ active users. Designed real-time event ingestion pipelines, user analytics warehouses, and MLOps workflows. Built scalable backend systems and led infrastructure management before successful acquisition in Nov 2025.
Key Responsibilities
- Co-founded Boringrats and led all backend architecture from zero to 1M+ active users
- Built distributed backend systems using Python, FastAPI, PostgreSQL, Redis and Docker
- Designed and implemented RESTful APIs handling 10K+ requests/minute with <100ms latency
- Set up CI/CD pipelines, containerized services, and cloud deployments on [AWS]
- Led the company to acquisition by an international firm within 2 years of founding under NDA
boringrats.dev ↗Key Learnings
- Learned how to build backend systems that keep working as the number of users grows.
- Got hands-on experience making APIs faster and improving database performance.
- Learned to automate deployments, use Docker, and run reliable production systems.
- Grew from writing code to making technical decisions, working with a team, and solving real business problems.
-
Full Stack Developer · Freelance
Delivered 8+ full-stack projects for US and UK SaaS/e-commerce clients. Reduced page load times by 40% with React optimization. Built REST APIs serving 10K+ daily requests using Django and PostgreSQL.
Education