P. Goutham

Architected and built a property-tech platform from scratch as sole solution architect — three Next.js frontends (user search, agent portal, admin) over a shared Fastify/TypeScript/MongoDB backend, live on Vercel in about 10 months.

• Each of the three backend apps (user, agent, admin) can run standalone or as a single unified server, sharing core logic through a common module layer designed to split into separate services later if scale requires it.
• Set up Vercel deployment pipelines with GitHub Actions preview environments across all three frontends, plus Sentry error monitoring and SEO/GTM automation for internal tooling.

A chat-based concierge on AWS that finds, filters, and recommends property listings conversationally — replacing traditional filter-driven search with a natural-language interface.

• Understands free-text preferences (budget, location, room type) and maps them onto the platform's structured property filters to return relevant matches.
• Built as a discrete AWS-hosted service so it can evolve independently of the core booking/listings API.

A full payments system built on Razorpay, with a serverless webhook listener on AWS Lambda (via the Serverless Framework) that processes payment events asynchronously instead of blocking the main API on webhook delivery.

• Decouples payment-event handling from the request/response cycle of the core API, so a slow or retried webhook can't back up regular traffic.
• Deployed and scaled independently of the main Fastify backend, using AWS Lambda's pay-per-invocation model for a workload that's bursty by nature.

Real-time chat between matched flatmates/roommates, built on Ably rather than a hand-rolled WebSocket layer, so presence and delivery guarantees came for free instead of being reinvented.

• Presence detection, typing indicators, and message reactions on top of Ably Chat's React SDK, wired into the platform's flatmate-matching and connection-request flow.
• Paired with face-detection screening (face-api.js) on profile image uploads to keep the matching pool free of low-quality or inappropriate photos.

Pass a JSON schema, get a fully functional form — built on React Hook Form for battle-tested form state with zero re-render overhead. Proposed at MassMutual and maintained as a customized fork tailored to internal practices, compressing roughly 2 months of sprint-planned form work into about 2 weeks and earning team recognition.

• 18 field types out of the box — text, select, file, slider, rating, repeatable field arrays, grouped fieldsets, and multi-field rows — plus async/dependent options via getOptions, apiEndpoint, and dependsOn.
• Conditional show/hide/require/disable logic with AND/OR groups and 6 operators, a built-in multi-step wizard with per-step validation, and a formRef escape hatch exposing the full React Hook Form API.
• Tree-shakable via a custom fieldRegistry (ship only the field types you use), and accessible by default — proper ARIA attributes and WCAG AA contrast on every field.

Built on driver.js for the spotlight/overlay/popover engine, with a React-first layer of typed tour config on top. Proposed at MassMutual and maintained as a customized fork powering guided tours across both the Portal and UMA applications in production.

• Cross-route tours via beforeNext/afterNext/waitForTarget hooks, action-driven steps (advanceOn, canAdvance, autoAdvanceAfter), and mobileOverrides for responsive step content.
• Persistence and scheduling — resume progress, cap show count, re-show on a version bump, or delay by time/visits/idle — plus a global tour registry and useTourSequence for chaining multiple tours.
• Built-in analytics adapters for PostHog, Segment, Mixpanel, and Amplitude, and testing utilities for mocking TourControls cleanly in Vitest/Jest.

Played a pivotal role standing up UMA as a greenfield application from scratch — React front end, Express/Node backend, Sequelize ORM. Now in production alongside the MMSD Portal, with guided product tours powered by a ReactDriver fork.

• Sequelize ORM over an RDS Postgres cluster in hosted environments and SQLite for local development, with migrations run automatically before boot in every non-local environment.
• A local-override workflow for the shared DSP component library lets changes there be tested against UMA without cutting a new library version first.
• Ships as a single Express server that serves the built React app statically in production, with database credentials pulled from AWS Secrets Manager rather than checked-in config.

Introduced a Hierarchy Tool giving MassMutual home-office users a clear view into agent hierarchy and product info for QA purposes. Quickly became a heavily used internal feature and is being rolled out to production for an initial group of home-office users, with plans to expand to a wider audience.

• Look up a firm by business-partner ID (bpId) and render its structure as a D3-powered hierarchy tree, or run two bpIds side by side in compare mode.
• A companion data viewer surfaces line-of-business, role, and relation badges per firm so QA can inspect product/role enablement without querying backend systems directly.

An org-wide Node.js/Express/Octokit service that listens for Snyk vulnerability webhooks — instead of scanning on every PR commit — and automatically raises a GitHub PR with the fix. Moving off per-commit scanning to a webhook-driven model cut scanning costs drastically while keeping remediation just as fast.

• Verifies each webhook's HMAC signature, batches issues per repo over a configurable window so a burst of events becomes one PR, and skips duplicates and Snyk-ignored issues.
• Direct dependencies get a normal npm install --save bump; transitive ones get an overrides/resolutions entry instead — with a preflight check for peer/engine conflicts before anything is dispatched.
• Three risk tiers (safe, major-bump, out-of-range) route straight to a normal PR or a draft PR labeled snyk-needs-review; the tool itself never merges or installs — a GitHub Actions workflow in the target repo does that and posts the PR number back via a signed callback.
• Auto-closes PRs for issues Snyk later marks resolved, cleans up stale PRs past a configurable age, and posts to Slack — with per-project policy (severity threshold, allow/deny list, major-version policy) defined in a central registry.

A macOS tool that runs `snyk test` across a configured list of local repos concurrently and only surfaces a modal alert when high/critical issues turn up — no more manually re-running Snyk on every repo each morning. A companion VS Code extension (vscode-snyk-check) wraps the same script's `--json` mode in a sidebar panel, so findings show up right in the editor without a terminal.

• Scheduling uses launchd's StartCalendarInterval rather than cron (deprecated on macOS for GUI-facing jobs) — missed runs during sleep coalesce into a single catch-up alert as soon as the Mac wakes, unlike a plain interval timer which would just drop them.
• An optional unlock-watcher — a persistent JXA process wired to the undocumented com.apple.screenIsUnlocked notification — triggers an immediate scan the moment the screen unlocks, independent of the schedule.
• Alerts use an AppleEvents modal dialog instead of a Notification Center banner, sidestepping per-app notification permissions that silently default to off for scripts and cron-style jobs.
• One shared results parser feeds both the macOS dialog and the VS Code extension's JSON consumer, so there's a single source of truth for issue data (package, current/fix version, advisory link, dependency chain).

A Chrome extension that auto-fills and submits login forms across multiple accounts, browser profiles, and environments — cutting out the repetitive re-login flows that come with juggling dev/staging/prod and test accounts day to day.

• Profiles activate automatically by URL pattern; a searchable, keyboard-navigable picker (Cmd/Ctrl+Shift+L) lists accounts by role, with per-user password overrides on top of a shared profile password.
• Bulk-load accounts via CSV/TSV or JSON with auto-detected delimiters, and back up or restore every profile as a single JSON export.

Designed and proposed as MassMutual's next-generation, multi-framework design system to remove external vendor dependencies and give the org its own design library — a token layer, a base React component set, theme adapters for Ant Design and MUI, and a codegen'd icon pipeline, run as a pnpm monorepo with Storybook and visual regression tests.

• Presented to the existing Blueprint maintainers and leads; the outcome favored bringing similar standards into the existing Blueprint repos over adopting an entirely new system, with strong appreciation for the initiative and intent.
• Built independently from the ground up as a working proof of concept — tokens, base components, and two framework-specific theme layers — rather than a slide-deck pitch.