Skip to content
MJSCRIPT®

About / The engineer

I build the systems behind the product.

Mrityunjay Deepak
Gurugram, India

I’m Mrityunjay Deepak, a full-stack software engineer working across product development, backend architecture, AI-powered automation, and production infrastructure.

I work best as a hands-on engineer who owns a product from architecture through production, in small teams where decisions are made close to the code.

01  /  Positioning

The roles I’m looking for.

Founding Engineer / Senior Full-Stack / AI Product Engineering

These are the roles I’m targeting. They describe what I’m looking for next, not job titles I’ve held. My actual titles are listed in the timeline below.

Open to founding engineer, senior full-stack, and remote product engineering opportunities.

02  /  Selected work

What I’ve shipped.

  1. 01

    Independently built a storefront and its integration layer

    Developed the TORA & TORY e-commerce storefront and a business operations system connecting separate applications and databases through REST APIs, webhooks, BullMQ, and Redis.

    TORA & TORY case study

  2. 02

    Shipped AI-agent workflows against a live advertising API

    Built a Google Ads automation application covering campaign creation, performance analysis, keyword discovery, and budget decisions, and led a team of four.

    Mind Matrics Media case study

  3. 03

    Worked on real-time systems under load

    Built React and D3.js trading dashboards and Node.js services, with a reported 30% reduction in data latency and streaming infrastructure for 10,000+ concurrent users.

    Copartner case study

03  /  Experience

Career timeline.

  1. June 2026 – Present

    TORA & TORY

    Head of Technology & Senior Full-Stack Developer

    Case study

    • Independently architected, developed, and deployed the e-commerce storefront.
    • Built a distributed business operations ecosystem integrating separate applications and databases.
    • Connected the applications with REST APIs, webhooks, BullMQ, and Redis.
    • Supported workflows covering inventory, orders, customer data, financial operations, and reporting.
    • Own technical architecture, integrations, and production engineering.
  2. December 2025 – May 2026

    Great Learning

    Senior Learning Consultant

    Non-engineering role

  3. March 2025 – December 2025

    Mind Matrics Media

    Senior Full-Stack Developer & Team Lead

    Case study

    • Built an AI-powered Google Ads campaign automation application.
    • Integrated the Google Ads API.
    • Developed agent-driven performance analysis and campaign decision workflows.
    • Implemented keyword discovery and market research integrations.
    • Led a development team of four.
  4. January 2025 – March 2025

    Freelance

    Full-Stack Developer

  5. January 2024 – January 2025

    Copartner.in

    Full-Stack Developer

    Case study

    • Developed real-time trading dashboards using React and D3.js.
    • Built Node.js services for trading and risk metrics.
    • Reported 30% reduction in data latency.
    • Supported streaming infrastructure for 10,000+ concurrent users.

Education

Lovely Professional University

Bachelor of Technology, Computer Science and Engineering

2019 – 2023
CGPA: 7.54/10

04  /  Technical strengths

What I work with.

Frontend
  • React
  • Next.js
  • TypeScript
  • JavaScript
  • Tailwind CSS
  • D3.js
Backend
  • Node.js
  • Express.js
  • REST APIs
  • Webhooks
Data & asynchronous systems
  • MongoDB
  • SQL
  • Redis
  • BullMQ
AI & automation
  • AI-agent workflows
  • LLM API integrations
  • Google Ads API
  • Campaign automation
Infrastructure
  • Linux
  • Docker
  • Deployment & server management

05  /  Approach

How I think about engineering.

  1. 01

    Own the outcome

    A feature is finished when it runs reliably in production and the people who depend on it can use it, not when the code merges.

  2. 02

    Keep the architecture practical

    Choose the simplest structure that meets today’s requirements and leaves room for tomorrow’s. Add a queue, a service boundary, or an abstraction when a real problem asks for it.

  3. 03

    Build, ship, learn

    Small releases expose real constraints sooner than long plans do. Shipping early is how the next decision gets better information.

  4. 04

    Write for the next maintainer

    Clear names, narrow interfaces, and explicit contracts between systems keep software changeable after the original context is gone.

  5. 05

    Start from the business problem

    Understanding what the business needs to do, and what it costs when it goes wrong, decides which technical details deserve attention.

  6. 06

    Name the trade-offs

    Every design gives something up: consistency, latency, simplicity, or cost. Stating the trade-off makes the decision reviewable.

Read the engineering notes

Contact

Let’s build something worth shipping.

Open to founding engineer, senior full-stack, and remote product engineering opportunities.