"The King of Nepal" β
BSc CSIT student turning ambitious ideas into fast, well-crafted software. I build at the intersection of clean engineering and clear thinking β leading teams under pressure, shipping under deadlines, and chasing the kind of problems that don't have obvious answers yet.
I'm Sudarshan Thapa, a Computer Science and Information Technology student from Nepal who treats software the way a good craftsman treats a tool β it should be dependable, honest about what it does, and better every time you pick it up. That mindset is what carried a small team through 36 sleepless hours to a National Hackathon Championship, and it's what still drives every project I open a terminal for.
My curiosity lives mostly at the edges of AI, web development, and applied problem-solving β the places where a good algorithm and a good interface have to agree with each other. I like taking a vague idea, breaking it into components that actually make sense, and shipping something people can click on.
None of that happens alone. I've led teams through tight deadlines, learned as much from debugging someone else's code as my own, and I'm still, deliberately, a student first β chasing the next framework, the next data structure, the next hard problem worth losing sleep over.
Drawn to AI and emerging tools β always testing what's next.
Led a hackathon-winning team through real deadline pressure.
Breaks down ambiguous problems into buildable systems.
Continuously stacking new languages, tools and ideas.
A foundation built specifically for software β from core computing theory to applied systems and project delivery.
Coursework spanning software development, system analysis & design, cryptography, database systems, and information systems & project management β paired with hands-on project work and competitive programming.
Built the mathematical and analytical foundation that led into computer science β first contact with programming and logical problem-solving.
Competitions don't reward good intentions β they reward what you can actually ship. Here's what that's looked like so far.
Placed 1st nationally, leading a team from blank whiteboard to working, judged product in under 48 hours.
Recognized by judging panels for original problem framing and clean, defensible technical execution.
Regularly organizes and leads teams through competitive programming and campus technology events.
A working balance of core computer science, applied web engineering, and the tooling that keeps a project shippable.
Also working with
Fast in a hackathon, careful in production. I'd rather ship a smaller feature that's solid than a large one that's fragile β and I always leave code a little more readable than I found it.
A mix of hackathon builds, coursework systems, and self-directed experiments. More is always in progress β check back often.
Early career, structured around real teams and real deadlines.
Directed a small team through ideation, build, and pitch under a 48-hour deadline, resulting in a national championship win.
This slot is ready for your next internship, freelance engagement, or research assistantship.
Another open slot β swap this in as your experience grows.
Sample entries β swap in real feedback from mentors, teammates, and collaborators as it comes in.
Sudarshan kept our team calm and focused for the entire hackathon. He's the reason we had a working product with hours to spare.
Reliable, curious, and genuinely enjoys solving hard problems. Exactly who you want on a project with a tight deadline.
Open to internships, collaborations, freelance work, and interesting technical conversations.