📍 Bhubaneswar & Jamshedpur, India · 🌐 Open to Remote — India & Global
I am a full-stack engineer based between Bhubaneswar and Jamshedpur, India, building AI-powered systems, blockchain banking infrastructure, and scalable web applications. I focus on turning real-world infrastructure problems — mobility, finance, workforce, and urban systems — into production-grade products with serious technical depth.
My engineering philosophy is simple: build things that matter, at scale, with precision. I do not build toy projects or academic demos. Every line of code I write is aimed at solving a problem that affects real people, real industries, and real economies.
Over the past few years, I have built across verticals that most engineers treat as separate disciplines — smart city mobility APIs, ML-driven workforce platforms for the steel industry, and now decentralized banking infrastructure targeting the United States financial system. These are not surface-level integrations. They involve deep system design, regulatory awareness, algorithm engineering, and thoughtful product decisions.
I am actively looking to join teams working on advanced, ambitious projects. If you are building non-trivial systems in AI, blockchain, fintech, or infrastructure and need a serious full-stack contributor, reach out. I am ready to move fast, go deep, and ship things that work in production.
What makes me different from most full-stack engineers:
- I think in systems, not just in features. Before writing code, I design for scale, fault tolerance, and evolution.
- I work across the entire stack — from React component architecture and Redux state management to distributed backend design, database optimization, and ML API integration.
- I understand regulated industries. Building for the steel workforce sector and US financial markets has given me exposure to compliance requirements, audit trails, and data governance that most engineers never encounter.
- I study the fundamentals aggressively — currently working through advanced graph algorithms, flow networks, ARM architecture, and distributed systems theory.
- I ship. Not just prototypes, not just demos — working systems deployed to real infrastructure.
| Language | Proficiency | Primary Use |
|---|---|---|
| JavaScript / TypeScript | Expert | Full-stack web, APIs, tooling |
| C++ | Advanced | DSA, competitive programming, systems |
| Python | Advanced | ML/AI, data pipelines, scripting |
| Java | Proficient | Backend services, Android |
| Solidity | Intermediate | Smart contracts, DeFi protocols |
I build frontend systems with a focus on performance, accessibility, and maintainability. My React work goes beyond component construction — I architect state management systems using Redux Toolkit, implement code splitting and lazy loading at scale, optimize rendering pipelines, and integrate complex real-time data flows via WebSocket and Server-Sent Events. Three.js work includes 3D city visualization for the Smart City project.
Backend work centers on building APIs that are reliable, observable, and scalable. I have built RESTful and GraphQL APIs serving high-read-volume use cases, implemented rate limiting and caching strategies with Redis, designed multi-tenant data architectures, and built event-driven systems using message queues.
Database design is a core strength — I model schemas for both normalized relational data and document-oriented workloads. I have designed sharding strategies for MongoDB at scale, implemented Redis caching layers that reduced API response times by 60%+, and built read replicas and connection pooling setups for production systems under load.
My blockchain work is focused on the practical application layer — compliant DeFi infrastructure, identity protocols, and tokenized real-world assets. I write and audit Solidity contracts, work with ethers.js and web3.js for frontend integration, use Hardhat for testing and deployment, and understand EVM internals at the opcode level for gas optimization.
I build CI/CD pipelines using GitHub Actions, containerize applications with Docker, and deploy across Vercel (frontend), Railway (backend), and Netlify. I understand infrastructure costs and make deployment decisions that balance performance, reliability, and operational cost.
The intersection of decentralized finance and the US regulatory framework is the most technically and intellectually challenging space I have worked in. Building compliant blockchain banking products for the US market requires understanding not just smart contract development, but also:
Bank Secrecy Act (BSA): The BSA is the foundational US anti-money laundering law. Any entity operating as a Money Services Business (MSB) — which most crypto-to-fiat services qualify as — must register with FinCEN, implement a written AML program, file Currency Transaction Reports (CTRs) for cash transactions over $10,000, and file Suspicious Activity Reports (SARs) when suspicious activity is detected.
FinCEN Guidance on Virtual Currency: FinCEN's 2013 guidance and subsequent rulings establish that administrators and exchangers of virtual currency are MSBs subject to BSA requirements. My DeFi Banking Gateway is being built to comply with these requirements from day one — not as a retrofit, but as a core design constraint.
OFAC Sanctions Screening: The Office of Foreign Assets Control maintains the SDN (Specially Designated Nationals) list — entities and individuals that US persons and companies are prohibited from transacting with. Every transaction in the Gateway is screened against the current SDN list in real time.
AML/KYC Program Requirements: Under 31 CFR 1022.210, MSBs must establish AML programs including internal policies and procedures, designation of a compliance officer, ongoing training, and independent audit. The Gateway includes built-in tooling to support all four pillars.
SEC and CFTC Considerations: Depending on the nature of tokens offered, the Securities and Exchange Commission (SEC) and Commodity Futures Trading Commission (CFTC) may have jurisdiction. The Gateway is being designed to only interact with tokens that have a clear commodity characterization (Bitcoin, Ethereum) or with regulated stablecoins, explicitly avoiding anything with security token characteristics to stay outside SEC jurisdiction.
This is not just legal awareness — it shapes architectural decisions at every layer.
When I approach a new system, I follow a structured design process:
Phase 1: Requirements Clarification
- Functional requirements: what does the system need to do?
- Non-functional requirements: latency, throughput, availability, consistency requirements?
- Scale estimates: read/write ratio, data volume, user count?
- Compliance requirements: data residency, audit logging, regulatory constraints?
Phase 2: High-Level Architecture
- Identify the core data entities and their relationships
- Choose data stores based on access patterns (not habit)
- Design the API surface — RESTful for CRUD, GraphQL for complex queries, WebSocket for real-time
- Identify the system's bottlenecks before they appear
Phase 3: Detailed Component Design
- Database schema with indexing strategy
- Caching layer design: what to cache, TTL strategy, cache invalidation
- Authentication and authorization model
- Background job architecture for async processing
Phase 4: Scaling and Reliability
- Horizontal vs. vertical scaling decisions per component
- Load balancing strategy
- Failure modes and recovery procedures
- Observability: metrics, logging, tracing
- Deployment strategy: blue-green, canary, rolling
This is not a checklist I follow for every small project — it is the mental model I apply proportionally based on the complexity and criticality of what I am building.
Planned open source releases from my current work:
I write about the intersection of engineering and real-world systems — not beginner tutorials, but deep dives into architectural decisions, regulatory constraints, and problems that don't have Stack Overflow answers.
| Building compliant DeFi products for US markets — what FinCEN, BSA, and OFAC regulations actually require and how to implement them at the architecture level. | How flow network theory applies to real systems — traffic routing, workforce matching, and fraud detection using max-flow, bipartite matching, and GNNs. | The gap between government smart city visions and engineering reality — sensor integration, traffic modeling, and APIs that plug into municipal systems. |
| Distributed systems trade-offs — sharding, caching strategies, event sourcing, and the CAP theorem applied to real product decisions. | Why the steel industry's technology needs are fundamentally different from tech sector defaults — domain-specific ML, compliance constraints, and operational realities. | Self-sovereign identity architecture, zero-knowledge proofs in practice, and DeFi apps that are both compliant and privacy-preserving. |
Technical blog coming soon. Follow on X for updates.
I am looking to work with teams and engineers focused on advanced development — not feature sprints on CRUD apps, but projects involving genuine engineering depth. Specifically:
What I am looking for:
- AI/ML systems with real-world deployment challenges — not just Python notebooks, but production ML pipelines handling live data at scale
- Blockchain/DeFi infrastructure, especially US-regulated products that combine smart contract development with compliance engineering
- High-scale system design projects where the architecture decisions are genuinely hard — sharding, eventual consistency, real-time data processing
- Smart city / mobility technology, particularly integrations with government data systems or sensor networks
- Research-backed engineering — projects where the problem is hard enough that reading papers is part of the job
What I bring:
- Full-stack capability: I can own a feature from database schema to deployed UI
- Cross-domain thinking: I connect ideas from finance, systems, algorithms, and product
- Speed without sloppiness: I move fast but I document, test, and design for maintainability
- Communication: I write clearly and explain technical decisions to non-technical stakeholders
If your team is working on something like this, reach out via LinkedIn or email.
| Platform | Link | Purpose |
|---|---|---|
| linkedin.com/in/ankitsharma706 | Professional network, collaboration requests | |
| X (Twitter) | x.com/ankit_sharma708 | Tech thoughts, project updates, writing |
| ankitwhatsapps@gmail.com | Direct outreach, collaborations | |
| Portfolio | caffenia.vercel.app | Live project demo |
| Buy Me a Coffee | buymeacoffee.com/ankitsharma7 | Support open source work |
My work is built on the open source community, academic researchers, and the engineering community who share knowledge freely. Special appreciation for the teams behind React, Node.js, MongoDB, Ethereum, PyTorch, and the countless libraries that make modern development possible.
Inspired by writing from Martin Kleppmann (distributed systems), Vitalik Buterin (blockchain research), Kipf & Welling (graph neural networks), and the FinCEN regulatory guidance archive that shaped the compliance architecture in my fintech work.


