Curiosity came first.
I began by trying to understand how software works beneath the interface: how data moves, how applications make decisions, how systems fail, and how individual components become complete products.
RishvinPortfolio
I’m Rishvin Reddy — a Computer Science and Engineering student, systems builder, and founder working acrosscybersecurity, IoT, blockchain, full-stack engineering, and automation.
My focus is not technology for its own sake. I care about architecture, security, reliability, and whether a system can survive beyond the demo.
9.01
CGPA / 10
2028
Expected Graduation
01
Design Patent Milestone
04+
Core Engineering Domains
A progression from learning how technology works to engineering how interconnected systems should behave.
I began by trying to understand how software works beneath the interface: how data moves, how applications make decisions, how systems fail, and how individual components become complete products.
As my work expanded into cybersecurity, IoT, databases, blockchain, backend systems, and full-stack development, I became more interested in the relationships between components than isolated technologies.
A sensor is only useful when its data pipeline is reliable. Authentication is only meaningful when the surrounding application is secure. Automation is only valuable when failure states are observable and recoverable.
A major milestone in my journey was my work on an IoT Connectivity Device that reached the design-patent process in India. The experience strengthened my interest in connected systems and changed how I approached engineering: not simply as writing code, but as designing complete technical solutions.
Today, I work across software engineering, cybersecurity, connected devices, blockchain systems, and engineering automation while pursuing my B.Tech in Computer Science and Engineering at Woxsen University.
I am not trying to collect technologies. I am learning how to combine them into systems that work.
My academic path combines computer science fundamentals with cybersecurity, connected systems, and decentralized technologies. I use coursework as a foundation, then extend it through projects, experiments, and independent engineering.
2024 — 2028
Blockchain, IoT & Cybersecurity
Woxsen University
My strongest work happens at the boundaries between disciplines: software and hardware, security and usability, automation and reliability, experimentation and production engineering.
Security
Exploring secure authentication, attack-surface visibility, vulnerability workflows, web security, digital forensics, threat intelligence, and security automation.
Connected Systems
Building sensor-driven systems that connect physical devices, control logic, communication layers, dashboards, and real-world operational workflows.
Software
Designing applications across frontend interfaces, backend services, APIs, databases, authentication, deployment, and operational concerns.
Decentralized Systems
Studying decentralized architectures, smart-contract systems, trust models, blockchain-backed applications, and where distributed ledgers create genuine technical value.
My projects span different domains, but the recurring theme is systems thinking: multiple components, explicit data flows, operational constraints, and measurable outcomes.
Explore complete portfolioA security automation architecture exploring asset discovery, attack-surface analysis, vulnerability workflows, threat intelligence, normalization, orchestration, and multi-tenant security operations.
An IoT prototype combining environmental sensing, automated control logic, irrigation actuation, monitoring, and connected-device design.
A connected voting-system prototype combining fingerprint identity, embedded hardware, Wi-Fi communication, backend services, and database-backed workflows.
A workflow-driven content automation system designed around orchestration, persistence, idempotency, error handling, observability, and recoverable execution.
I am developing an engineering philosophy centered on reliability, explicit trade-offs, security, and systems that remain understandable as complexity grows.
Automation should encode a understood process, not hide a broken one.
Authentication, authorization, secrets, validation, and auditability should be designed into the system.
Retries, idempotency, state transitions, and recovery paths matter because real systems fail.
Logs, metrics, explicit states, and useful failure information reduce operational ambiguity.
Maintainable systems outperform impressive but opaque implementations.
Execution creates feedback. Feedback creates better engineering decisions.
I created Rishvin Labs as an engineering identity for exploring, building, and documenting ambitious technical systems across software, cybersecurity, IoT, automation, and emerging infrastructure.
It represents the direction I am growing toward: multidisciplinary engineering, strong technical execution, and products designed around real operational problems.
Operating Thesis
Build before claiming expertise.
Treat security as architecture.
Engineer for failure and recovery.
Prefer working systems over impressive demos.
Security
Systems
Connected Devices
Career
My long-term direction is to work on consequential technology: secure software, connected infrastructure, intelligent automation, and products that solve meaningful operational problems.
I want to become the kind of engineer who can move from first principles to architecture, from architecture to implementation, and from implementation to systems people can actually depend on.
I’m interested in engineering internships, cybersecurity opportunities, research collaborations, open-source work, and technically serious projects where I can contribute, learn, and take ownership.
Technologies Used Across Projects & Experiments