Software engineer. AI in production. CS @ Northeastern.
Seven stories. Each one real.
π Where it started
IB Diploma 44/45. Tokyo β Boston, alone at 18.
π§βπ« Teaching Assistant
1 year, 4 months teaching CS fundamentals while still a student myself.
π» Code4Community
4 microservices. 5-person team. Led the architecture of a mobile app for Boston nonprofits.
βΎ Boston Red Sox
API latency: 1.2s β 121ms. Journalists at Fenway depended on it.
π United Nations, Geneva
I was 19. The person next to me was negotiating arms treaties.
π’ NExT Consulting
63% faster decisions in chemical plants. When a pump fails, minutes matter.
π AgentOps Hackathon
Built a safe AI agent in 3 hours. Won 2nd place.
2022 β 2024
Grew up in Tokyo. Moved to Boston alone at 18 to study CS at Northeastern. IB Diploma: 44/45 β top 1% globally.
Teaching CS fundamentals while still a student myself.
To explain recursion to someone who's never written a loop β you have to understand it at a different level. Not memorized. Not functional. Understood. Teaching forced that on me for 16 months straight.
My first real team. Built a mobile app for Boston nonprofits. I led the architecture.
microservices. 5-person team. Design to deployment.
The decisions I made would outlive me on the codebase. Every module boundary, every API contract β the next team would inherit them. That was the moment I stopped thinking like a student and started thinking like an engineer.
Mentored a teammate from zero TypeScript to shipping features independently β pair programming, code reviews, enough context to make decisions alone.
Teaching one person to contribute is a multiplier. You don't just get a task done β you get a teammate who can now do it without you.
Jan 2024 β Sep 2024
The Boston Red Sox needed live batting lineups for journalists during games. The old method was a handwritten whiteboard. If this went down mid-game, the press couldn't report.
The first time I pushed to production at Fenway, I refreshed the page myself just to make sure it worked. No staging environment that matched. No way to undo. Real users. Real stakes.
Added Redis caching and Celery async workers. Response time: 1.2s β 121ms. Live at Fenway Park.
90% faster means a journalist can report the lineup change before the first pitch. That doesn't sound like engineering. But that's exactly what engineering is for.
Summer 2023
Northeastern selected me for a month at the United Nations in Geneva. I sat with diplomats, Nobel laureates, and officials debating AI regulation and autonomous weapons.
I was 19. The person next to me was negotiating arms treaties. We were both talking about AI. That's not a metaphor. That was the room.
I used to just think about the product.
Geneva changed how I build. Now I ask: who's on the other end? What can they afford to lose? What can't they?
Jul 2025 β Dec 2025
Chemical plants sending thousands of sensor readings per second. The data was messy and inconsistent, in a domain I knew nothing about.
A chemical engineer doesn't care about your tech stack. They care if the pump is going to fail β and whether they'll know in time to stop it.
Faster decisions during critical equipment failures. Operators can act immediately.
63% faster isn't a metric on a slide. It's the difference between catching a fault and missing it.
Students matched with their first career experience.
New students have no history. Started with text matching, then shifted to collaborative filtering β βstudents like you also liked this.β Good matches from day one, better over time.
2,547 matches made β
At Northeastern, co-op is career-defining. A bad match wastes a semester. A good match changes the trajectory of someone's career. The engine found one student a position aligned with her background. She got the role.
Mar 2025
Built a working AI shopping agent in 3 hours and won 2nd place β not for speed, but for what I built into it.
3 HRS$ init agent --framework openai-agents-sdk
> Shopper agent scaffolded β
> Adding input guardrails...
> Prompt injection test: BLOCKED β
> Harmful request test: BLOCKED β
> Prototype functional in 3 hours β
> Result: 2nd Place π
Most hackathon demos ship a prototype and call it done. This one had safety built in from line one. Not because the rubric required it. Because that's the right way to build.
AI agents can be tricked through prompt injection. I built safety layers that inspect every input before it reaches the AI β blocking attempts to override instructions or extract data.
Anyone can build fast. The question I keep asking is: what happens when someone tries to break it? That question is what separates a demo from a product you can trust.
Real users. Real load. Real stakes. If you're building something that needs to work in production β not just in a demo β let's talk.
Technologies Used
Campus free food shouldnβt die in a group chat. Photo-first feed, map pins, 5-up uploads, room + headcount fields, feed / post / profile nav. Proof and place before you walkβfewer empty trips. See the posting flow and feed cards in the shot.
View Project βTechnologies Used
One tweet shouldnβt stay trapped in one format. Three-pane app: source feed, tabbed editor (LinkedIn / IG carousel / newsletter / quote), AI tone presets, approve / reject / export, live IG preview with Inter + aspect toggles. Repurpose once; ship carousels and long posts without retyping. Trace the pipeline from source card to exported slides.
View Project βTechnologies Used
Focus breaks without honest logging are just vibes. Session timer, 15-minute check-ins, pause/stop, calendar with timestamped blocks (breaks vs deep work). You get a defensible day logβnot a guilt dashboard. Walk through session β check-in β calendar trail.
View Project βTechnologies Used
Staging ideas shouldnβt start from a blank room photo. Design grid with style cards + βTry It!β; Stage tab for camera / gallery import and a managed photo rail with status chips. Pick a look, drop a room, iterate before you buy furniture. Follow Design β Stage in the two-screen walkthrough.
View Project βTechnologies Used
Long reads deserve reel-level motion, not endless chrome. Full-bleed story, category tabs, breaking + source chips, serif headline over hero, side rail (share / like / explore / save). Scan categories fast; stay inside one thumb-friendly column. Swipe the Business vs Tech states in the pair of screens.
View Project βTechnologies Used
Podcast gold is buried past minute fortyβfind it automatically. Paste a YouTube URL β ASR + diarization β top 3 sub-2m viral cuts, 16:9 export; episode grid for one-click reruns. Editors ship clips same day, not after a manual scrub. Run the URL bar and thumbnail grid in the dashboard.
View Project βTechnologies Used
Quotes from thousands of hours shouldnβt be unsearchable. RAG over My First Million: semantic search, query expansion, suggested prompts, YouTube deep links, bridge to clip generator. Pull the exact riff, then jump to video or clips in one flow. Try the search bar, chips, and Viral Clip entry in the hero.
View Project βArmaan Agrawal Β· CS @ Northeastern Β· Boston, MA Β· ζ₯ζ¬δΊΊ π―π΅ Β· 2026