RN/Software Engineer
00:00:00
>esc
↑↓ move↵ open[ ] prev / next pageT modeP palette

Selected projects

Things I've
built

4 client engagements, described without client names, and 7 things I build in public.

GitHub · @rahul-narayanasamy

Eaten
0/—
Contributions
—
Best
0

Loading contribution data…

Autopilot · hunting the nearest commit

Client work

Problem · approach · outcome

  1. A real-time transaction and case-management application whose workflows are configurable: new business processes are onboarded as JSON Schema rather than hand-built screens.

    Role Feature owner · rollout · production support

    JSON SchemaUI SchemaRJSF renderer (owned)Rule validators (owned)Transaction API Part I owned
    Problem
    Every new business process needed its own transaction screens, validations and rollout, and the rules changed often.
    Approach
    • Schema-based workflows rendered with RJSF.
    • Configurable transaction screens and custom widgets with typed contracts.
    • Business-rule validation kept in the configuration layer, not in components.
    Outcome
    New flows move from requirement analysis to production through configuration. I also lead UAT, incident resolution and client-specific tickets for them.
    • React
    • TypeScript
    • RJSF
    • JSON Schema

  2. Reusable React components integrated into Adobe Experience Manager, moving two separate CMS platforms onto one.

    Role UI component engineer

    AEM authoringContent modelReact component (owned)Rendered page Part I owned
    Problem
    Two CMS platforms with their own markup and behaviour had to land on AEM without breaking pages for readers on any device.
    Approach
    • Reusable React components mapped to AEM authoring.
    • Integration with the AEM framework alongside backend developers.
    • Responsive, cross-browser behaviour verified per component.
    Outcome
    Components rendered consistently across devices and browsers, and integration bugs were fixed inside the components rather than patched page by page.
    • React
    • AEM
    • JavaScript
    • CSS

  3. Reusable UI for tariff code search, trade lane comparison and a product catalog, built against API contracts agreed with BFF and backend teams before the screens existed.

    Role Frontend engineer

    UI components (owned)API contract (owned)BFFTrade services Part I owned
    Problem
    A complex trade domain, several teams, and a quality bar measured by coverage, Sonar and Sigrid scores.
    Approach
    • Shared component set for search, comparison and catalog screens, with real-time validation.
    • API contracts defined with BFF and backend teams up front.
    • Unit tests shipped with every feature.
    Outcome
    Coverage held at 85% or higher, fewer Sonar code smells, and a better Sigrid maintainability score.
    • React
    • TypeScript
    • BFF
    • Unit testing
    • SonarQube

  4. The DataGrid, DataManager and Pager web components in a commercial UI library used by developers building data-heavy applications.

    Role Senior software engineer

    Data sourceDataManager (owned)Grid (owned)Pager (owned) Part I owned
    Problem
    A grid used by thousands of external developers in combinations no one can predict, where every release has to stay stable.
    Approach
    • DataManager for querying local and remote data sources.
    • Grid rendering kept separate from the data layer.
    • Pager built as an independent, composable component.
    Outcome
    Customer-requested features shipped release after release, with customer bugs triaged and fixed through support.
    • JavaScript
    • TypeScript
    • Web components

Side projects

[ GitHub · @rahul-narayanasamy ↗ ]
  1. Project 01

    Project 01 — Motion design · 2026

    Apogee

    A scroll-driven GSAP landing built for the CodeTV × Webflow Cloud hackathon. Atmosphere, pacing, and type as the product.

    • GSAP
    • ScrollTrigger
    • Webflow Cloud
    • TypeScript
    Source ↗
  2. Project 02

    Project 02 — Full-stack app · 2026

    Vault

    Full-stack expense tracker with auth, transactions, analytics, and budgets — Next.js, Clerk, Prisma, and Supabase.

    • Next.js
    • Prisma
    • Clerk
    • Supabase
    Source ↗
  3. Project 03

    Project 03 — Terminal UI · 2026

    Terminal Portfolio

    Interactive terminal-style portfolio — explore projects, skills, and contact through typed commands and shell output.

    • Next.js
    • TypeScript
    • Terminal UI
    • Tailwind CSS
    Source ↗
  4. Project 04

    Project 04 — Developer tool · 2026

    Markdown Editor

    Browser-based markdown editor with live preview, autosave, and export — CodeMirror 6, GFM rendering, local persistence.

    • React
    • CodeMirror
    • Vite
    • TypeScript
    Source ↗
  5. Project 05

    Project 05 — AI pipeline · 2026

    Signal

    Local-first pipeline that turns Hacker News and RSS into high-signal developer posts — Groq, Gemini, or Ollama.

    • Python
    • LLMs
    • Streamlit
    • RSS
    Source ↗
  6. Project 06

    Project 06 — Frontend app · 2025

    Atmosphere

    Next.js weather surface focused on hierarchy and calm — forecast as typography, not a widget dump.

    • Next.js
    • Weather API
    • Tailwind CSS
    Source ↗
  7. Project 07

    Project 07 — Enterprise UI · 2018–22

    Grid Systems

    Years of grid, template, and editing work at Syncfusion — UI that has to be correct for millions of cells.

    • Blazor
    • EJ2
    • C#
    • Data grids
    Source ↗
>