You’ve probably read a hundred applications from developers who can “build scalable apps” and “write clean code.” That’s not what I do. I focus on a different problem: how do you make your entire engineering team faster consistently? Because shipping features is easy. Building systems that are reusable, maintainable, and truly scalable, the kind that don’t slow down as your product grows that’s where most teams struggle. That’s where I like to work. I build systems, tools, and workflows that remove bottlenecks before they exist. The kind of engineering that compounds over time where every line of code makes the next feature easier, faster, and safer to build. In my current role as a Software Developer, I don’t consider something “done” when it works locally. It’s done when it’s tested, containerized, deployed, and proven in production. That means server-side TDD with Jest, automated CI/CD pipelines, and infrastructure that holds up under real-world pressure. One example of this mindset is AFNO UI: _Website not available. Sign in: https://www.twine.net/signup_ It started with a simple frustration: why are developers still rebuilding the same UI patterns over and over again? So I built a visual system that goes beyond forms covering dynamic tables, drag-and-drop interactions, and complex UI workflows without relying heavily on external libraries. That means fewer dependencies, better control, and systems that are easier to maintain long-term. But more importantly, I built the ecosystem around it, a CLI that handles dependency injection, Tailwind configuration, and setup automatically. No boilerplate. No wasted time. Just clean, reusable code that scales with the project. How I approach engineering: • Design high-concurrency systems using gRPC and GraphQL microservices built for long- term scalability • Build architectures with Redis caching and RBAC/PBAC that stay maintainable as com- plexity grows • Ensure systems are reusable by design modular, well tested, and easy to extend • Reduce unnecessary dependencies to keep systems lightweight and predictable • Own the full pipeline—Docker, GitHub Actions, DigitalOcean/GCP, NGINX • Treat testing as a core part of development, not an afterthought I’ve also explored problems from a research lens working at IIT Bhubaneswar on LLM-driven geospatial inference and contributing to a published book chapter on hybrid machine learning models. That experience sharpened how I think about building systems that are not just functional, but future-proof. I’m not looking to just contribute code. I’m looking to build the kind of systems, tooling, and infrastructure that make your engineering team faster today and even faster six months from now. If that’s the kind of impact you’re hiring for, we should talk. Aniket Kumar Rouniyar services.aniketrouniyar.com.np | github.com/ANI1KET _Email not available. Sign in: https://www.twine.net/signup_ |_Phone details not available. Sign in: https://www.twine.net/signup_ |_Phone details not available. Sign in: https://www.twine.net/signup_…You’ve probably read a hundred applications from developers who can “build scalable apps” and “write clean code.” That’s not what I do. I focus on a different problem: how do you make your entire engineering team faster consistently? Because shipping features is easy. Building systems that are reusable, maintainable, and truly scalable, the kind that don’t slow down as your product grows that’s where most teams struggle. That’s where I like to work. I build systems, tools, and workflows that remove bottlenecks before they exist. The kind of engineering that compounds over time where every line of code makes the next feature easier, faster, and safer to build. In my current role as a Software Developer, I don’t consider something “done” when it works locally. It’s done when it’s tested, containerized, deployed, and proven in production. That means server-side TDD with Jest, automated CI/CD pipelines, and infrastructure that holds up under real-world pressure. One example of this mindset is AFNO UI: _Website not available. Sign in: https://www.twine.net/signup_ It started with a simple frustration: why are developers still rebuilding the same UI patterns over and over again? So I built a visual system that goes beyond forms covering dynamic tables, drag-and-drop interactions, and complex UI workflows without relying heavily on external libraries. That means fewer dependencies, better control, and systems that are easier to maintain long-term. But more importantly, I built the ecosystem around it, a CLI that handles dependency injection, Tailwind configuration, and setup automatically. No boilerplate. No wasted time. Just clean, reusable code that scales with the project. How I approach engineering: • Design high-concurrency systems using gRPC and GraphQL microservices built for long- term scalability • Build architectures with Redis caching and RBAC/PBAC that stay maintainable as com- plexity grows • Ensure systems are reusable by design modular, well tested, and easy to extend • Reduce unnecessary dependencies to keep systems lightweight and predictable • Own the full pipeline—Docker, GitHub Actions, DigitalOcean/GCP, NGINX • Treat testing as a core part of development, not an afterthought I’ve also explored problems from a research lens working at IIT Bhubaneswar on LLM-driven geospatial inference and contributing to a published book chapter on hybrid machine learning models. That experience sharpened how I think about building systems that are not just functional, but future-proof. I’m not looking to just contribute code. I’m looking to build the kind of systems, tooling, and infrastructure that make your engineering team faster today and even faster six months from now. If that’s the kind of impact you’re hiring for, we should talk. Aniket Kumar Rouniyar services.aniketrouniyar.com.np | github.com/ANI1KET _Email not available. Sign in: https://www.twine.net/signup_ |_Phone details not available. Sign in: https://www.twine.net/signup_ |_Phone details not available. Sign in: https://www.twine.net/signup_WWWW…