I work like a forward-deployed engineer and think like a GTM engineer: find the operational bottleneck, build the production system, activate the workflow, and turn field learning into compounding growth.
Each role moved me one layer closer to the real problem—from interface, to backend, to operations, to the systems that connect product and growth.
Full-stack Intern · LetzStepIn
Responsive React interfaces for a VR learning platform taught me the first field lesson: a system only matters when people can understand and use it.
Full-stack Engineer · Ironhawks
I built APIs, reusable service adapters, authentication, and production React experiences—learning to connect performance, security, and delivery speed.
Backend Engineer · Sajre Edutech
Multi-tenant SaaS, payments, certificates, WhatsApp, referrals, CI/CD, and uptime pulled engineering directly into the daily reality of schools and event teams.
Forward-Deployed × GTM Engineer
My focus is the space between customer need and company growth: discover the bottleneck, ship the system, activate the workflow, and feed what the field teaches back into product.
Production work, personal systems, and one representative GTM architecture—each labeled clearly so the evidence stays as strong as the presentation.
A schema-per-tenant backend for institution workflows with role boundaries, operational APIs, certificates, payments, and communication paths.
Multi-role workflows spanning enrollment, fees, artwork submission, validation, judging, voting, certificates, notifications, and referrals.
A MERN system for subscription state, attendance, billing, revenue analytics, and automated WhatsApp or email reminders before expiry.
A transparent automation pattern for collecting product, form, payment, and conversation signals; enriching the record; scoring intent; and routing the next action with an audit trail.
A modern field-and-growth engineer crosses commercial context, automation, product systems, and production reliability without pretending every tool has already been mastered.
Discovery, workflow mapping, stakeholder translation, adoption, and outcome definition.
APIs and event-driven workflows that connect communication, payments, product, and operations.
Multi-role SaaS foundations, interfaces, permission models, analytics, and data boundaries.
The operating layer that keeps a useful prototype from becoming a fragile production burden.
These are developing capabilities—not disguised client claims. The goal is to combine my production engineering base with the current GTM systems stack.
Contributing across frontend and backend delivery while continuing to move closer to customer workflows and full-cycle ownership.
Built multi-tenant SaaS systems, APIs, RBAC, payments, certificates, WhatsApp workflows, CI/CD, and production operations for education products.
Shipped secure APIs and React applications, tuned MongoDB queries, documented integrations, and improved frontend performance.
Built responsive interfaces for a VR learning platform and improved reuse, accessibility, cross-browser quality, and review workflows.
Tell me where the handoff breaks, what your team repeats, and what a valuable outcome looks like. I will bring the system questions.