01 / ABOUT·ENGINEERING DOSSIER

CLASS OF 2026 · CSIT

HIMANSHU
PATRO

Software engineer building reliable systems around code, AI agents, developer tooling and open-source code intelligence.

JAMSHEDPUR, JHARKHAND, INDIA·B.TECH CSIT · ITER, SOA UNIVERSITY·GRAPHIFY CORE CONTRIBUTOR

01/WHO I AM & PHILOSOPHY

“Software engineering is at its best when it moves beyond building toys and grapples with the unglamorous realities of complex systems: deterministic execution, edge-case failure classification, and rigorous maintainer review.”
— Engineering Journal

I am a Software Engineer based in Jamshedpur, Jharkhand, India, graduating in Computer Science and Information Technology (CSIT, B.Tech 2022–2026) from the Institute of Technical Education and Research (ITER), Siksha 'O' Anusandhan (SOA) University, Bhubaneswar, Odisha, India. My engineering work sits at the intersection of full-stack web platforms, autonomous testing systems, and open-source code intelligence.

Across corporate software engineering internships at Celebal Technologies and Tata Steel Ltd., I developed production-grade web applications, designed secure RESTful APIs with role-based access control (RBAC), and optimized frontend responsiveness and database query indexing for hundreds of organizational users.

As an active open-source contributor with 30+ maintainer-reviewed pull requests in Graphify (a code intelligence and AST analysis framework) alongside work in Agent Orchestrator, Continue, and Headroom, I thrive in complex, unfamiliar codebases—reproducing subtle bugs, strengthening regression suites, and engineering robust, platform-agnostic fixes.

02/BACKGROUND & EXPERIENCE TIMELINE

2024 — 2026

CHRONOLOGICAL PATHWAY /

24TATA STEEL

JULY 2024 — SEPT 2024

Full-Stack MERN Intern. Internal access management dashboard supporting 500+ organizational users.

25CELEBAL TECHNOLOGIES

JUNE 2025 — AUG 2025

Software Development Intern. Enterprise Service Desk Application with dynamic routing (30% faster loads).

26OPEN SOURCE (GRAPHIFY)

SUSTAINED CORE CONTRIBUTIONS

30+ maintainer PRs to Graphify code intelligence core; 50+ overall merged PRs across open source.

2025 · CELEBAL TECHNOLOGIES

Software Development Intern – ReactJS / Full Stack

Remote · June 2025 — August 2025

ENTERPRISE INCIDENT WORKFLOWS

VERIFIED IMPACT

30% faster page loads · 25% faster ticket resolution

Engineered dynamic incident ticket routing and notification workflows.

KEY RESPONSIBILITIES

• Built dynamic ticket routing system with priority tagging and category assignment.
• Integrated real-time notification workflows, reducing incident escalation latency.
• Maintained modular React component architecture in an Agile sprint environment.

2024 · TATA STEEL LTD.

Application Development Intern – Full Stack MERN

Jamshedpur, Jharkhand, India · July 2024 — September 2024

ENTERPRISE ACCESS MANAGEMENT

VERIFIED IMPACT

500+ active users · 20% faster MongoDB queries

Engineered role-based access control and scalable internal REST APIs.

KEY RESPONSIBILITIES

• Implemented JWT & bcrypt.js authentication with role-based permissions (RBAC).
• Engineered and deployed 10+ RESTful APIs in Node.js/Express.js with MongoDB indexing.
• Designed responsive management interfaces using React.js and Tailwind CSS.

03/EDUCATION & ACADEMIC ARCHIVE

BACHELOR OF TECHNOLOGY

Computer Science & Information Technology

Institute of Technical Education and Research (ITER)

Siksha 'O' Anusandhan (SOA) University · Bhubaneswar, Odisha

CGPA: 8.35

CLASS OF 2026 (2022 — 2026)

BASE: JAMSHEDPUR, JHARKHAND, INDIA

ACADEMIC INVOLVEMENT & LEADERSHIP:

—Smart India Hackathon (SIH) College-level round qualifier & technical lead for e-PMSSS

—Google Developer Student Clubs (GDSC) core community member & peer learning contributor

—Google Cloud Arcade (2024 & 2025) certifications in cloud infrastructure, Kubernetes, and AI/ML services

—Coursework: Data Structures & Algorithms, Operating Systems, Database Management Systems, Computer Networks, Software Engineering

04/TECHNICAL MATRIX & TOOLKIT

SYSTEMS SPECS

Technical competencies categorized by engineering domains. No arbitrary progress bars or inflated percentages:

01 / LANGUAGES & COMPILERS

TypeScript / JavaScript

Python 3.11+

Java

C / C++

HTML5 / CSS3 / SQL

02 / CODE INTEL & PARSING

Tree-Sitter Grammars

AST Extraction & Visitors

NetworkX & Graph Theory

Symbol Resolution Tables

Deterministic Build Caching

03 / AGENTS & BROWSER CDP

Chromium DevTools Protocol (CDP)

Patchright & Playwright

Autonomous Action Loops

DOM Assertion Triaging

Multimodal LLM Reasoning

04 / FULL-STACK PLATFORMS

Next.js 16 (App Router)

React 19 & State Engines

Node.js & Express.js

FastAPI (Python)

RESTful API Architecture

05 / STORAGE & INFRASTRUCTURE

MongoDB & Schema Indexing

PostgreSQL & Prisma

Docker & Containerization

Server-Sent Events (SSE)

Git & Monorepo Tooling

06 / TESTING & VERIFICATION

pytest & Unit Isolation

Playwright End-to-End

Structured Trace Generation

CI/CD GitHub Actions

Maintainer Pull-Request Review

05/HOW I WORK · ENGINEERING PRINCIPLES

RULE 01

1. Map Before Modifying

When tackling an unfamiliar codebase, I trace data flow, inspect call trees, and map AST visitors or runtime lifecycles before editing a single line.

— Read architecture documentation and trace entrypoints end-to-end

— Inspect existing test fixtures to understand expected invariants

— Isolate exact components responsible for state transformations

RULE 02

2. Reproduce with Minimal Test Cases

I never patch symptoms blindly. Every bug investigation begins by constructing a minimal, reproducible test case that reliably fails before any fix is applied.

— Write standalone reproduction scripts or isolated unit tests

— Verify failures against exact expected edge-case inputs

— Eliminate external dependencies to isolate root cause mechanisms

RULE 03

3. Address Root Causes, Not Symptoms

Superficial workarounds accumulate tech debt. I investigate why the invariant broke—whether due to resolver order, chunk scoping, or async timeout—and fix the core mechanism.

— Fix underlying logic rather than adding arbitrary delays or null checks

— Enforce fail-closed guarantees when partial failures occur

— Ensure changes maintain architectural consistency across the project

RULE 04

4. Write Targeted Regression Tests

A bugfix without a regression test will eventually regress. Every contribution is verified by automated tests that permanently protect against recurrence.

— Add explicit assertions covering boundary conditions and edge cases

— Verify both positive outcomes and clean failure handling

— Confirm test suites pass across operating systems (Linux and Windows)

RULE 05

5. Make Atomic, Defensible Changes

Clean pull requests respect maintainer time. I keep PRs strictly scoped to one problem, provide clear commit messages with technical context, and explain trade-offs transparently.

— Maintain tight diffs without unrelated formatting noise

— Structure commit messages following conventional commits

— Document the problem, investigation, change, and validation in PR summaries

RULE 06

6. Validate via Type Checks, Linters & Production Builds

Code is only complete when all verification gates pass cleanly without warnings, type errors, or bundle bloat.

— Run strict TypeScript compiler checks (`tsc --noEmit`)

— Ensure zero ESLint warnings and clean code styling

— Validate production builds (`next build`) to ensure runtime and SSG correctness