Dharun Narayanan

Software Engineer at Microsoft

I build AI experiences for everyday work, agentic tools for engineering teams, secure systems that hold up, full stack products end to end, and things people actually like using.

Good engineering is invisible. Bad engineering is somebody's bad day.

About

I design and ship systems where the engineering is rigorous and the experience is humane.

Builds as Software Engineer · AI Engineer · Machine Learning Engineer · Security Researcher · Full Stack Developer · Human Centred Builder

The thread through all of it is human centred design: whatever I build, the person on the other side of the screen comes first.

Based in Bellevue, Washington

Education

1 of 3

  1. M.S. Computer Science

    Oregon State University, USA

    2023 to 2025

    GPA 3.93 / 4.00

  2. B.Tech Computer Science

    Amrita Vishwa Vidyapeetham, India

    2019 to 2023

    GPA 3.69 / 4.00

  3. Higher Secondary

    Rasi International School, India

    2017 to 2019

    89% aggregate

What I work with

Three disciplines that only hold together as a set. Choose a group and its ring comes forward.

Showing all 37 skills.

Languages

  • Python, core skill
  • TypeScript, core skill
  • Java, core skill
  • JavaScript
  • C / C++
  • SQL
  • Dart

Frameworks and Web

  • React, core skill
  • Node.js
  • Flutter
  • HTML
  • CSS
  • REST APIs

AI and Machine Learning

  • PyTorch, core skill
  • Deep Learning, core skill
  • NLP
  • Computer Vision
  • scikit learn
  • Pandas

Security

  • Security Engineering, core skill
  • Vulnerability Analysis
  • Intrusion Detection
  • Offensive Security
  • Threat Modelling

Cloud and DevOps

  • Azure, core skill
  • AWS, core skill
  • DynamoDB
  • SQS
  • Docker
  • Ansible
  • Firebase
  • Git

Craft and Practice

  • Human Centred Design, core skill
  • UX Research
  • Accessibility
  • Technical Writing
  • Mentoring

At Microsoft

I work on the Copilot experience in OneDrive and SharePoint, and on how my team builds it: an agentic harness that takes a change from an idea to a pull request.

  1. Spec, with an agentAn engineer and an agent shape the change together.
  2. ApproveThe engineer reads the spec and signs off.
  3. ImplementAgents build it in the monorepo, with the tools it takes.
  4. Pull requestThe work arrives as a pull request, ready for review.

Under the hood the harness runs investigations across several agents at once, orchestrates them, and adjudicates the results at every stage. Each hand off goes to the model class best suited to it.

Where I have built things

Eight roles across industry, research, teaching and security operations, newest first.

  1. Feb 2026 to PresentCurrent

  2. Sept 2024 to Dec 2025

    Graduate Research Assistant

    Oregon State University

    Researched provenance based intrusion detection, reconstructing system level causality graphs to surface the intrusions that signature matching misses.

  3. Jun 2025 to Sept 2025

    Software Engineer Intern

    Microsoft

    Delivered an online evaluation framework for the autofill columns feature in SharePoint Online, using a large language model to categorise columns at scale, and built the interactive internal dashboards the team used to read user engagement.

    • TypeScript
    • GPT 4.1
    • Data Viz
  4. Jan 2025 to Apr 2025

    Software Development Engineer Intern

    Amazon

    Built an internal tool, surfaced through Amazon's front end MVC framework, that shows verification status for VetDiet pet prescription orders.

    • AWS SQS
    • DynamoDB
    • Java

Projects

Twelve projects across AI and machine learning, security and full stack.

Let's build something.

I'm always up for interesting conversations: research collaborations, thorny engineering problems, or just comparing notes. If you've got something you think I'd find interesting, I probably will.

Find me

Write to me