Supriya Dutta
Software Engineer
4+ years exp
3+ projects
Node JS
JavaScript
C++
TypeScript
Data Layer & Database: 5/10
API Design: 4/10
System Architecture: 4/10
Active 1 day ago
+7 (000) 293438
Invite to interview
Message
Download CVCV
Overview
Technical skills
Timeline
Roles
Overview
Software Engineer with 3+ years building scalable SaaS products end-to-end - from backend architecture to production UI. As one of two engineers owning the full product, cut API response times by 50% through database optimization, built a metered billing engine handling recurring revenue, and led development of a CRM-style estimate platform for roofing contractors. Strong foundation in Data Structures & Algorithms, OOP, REST API design, and system design, with a track record of turning ambiguous product requirements into reliable, measurable engineering outcomes.
Technical skills
Node JS• Middle
JavaScript• Senior • 4y+
C++• Middle • 4y+
TypeScript• Senior • 3y+ • 2 projects
Databases
MongoDB• 4y+
Frontend
Next.js
React.js
shadcn/ui
Gatsby
Zod
npm• 4y+ • 3 projects
Yarn• 4y+ • 2 projects
Tailwind CSS• 3y+ • 1 project
Mapbox GL JS• 3y+
react-map-gl• 3y+
react-leaflet• 3y+ • 1 project
Material UI• 3y+ • 1 project
tRPC• 3y+ • 2 projects
TanStack Table• 3y+
Zustand• 3y+
Three.JS
DevOps
Azure AKS• 3y+
Kubernetes• 3y+
Amazon EKS• 3y+
Google Cloud Run• 3y+
Design
Figma• 3y+
Timeline
Software Engineer
•
Middle
Granular
•
Contractor
- Reduced API response times by 50% by redesigning MongoDB indexes, optimizing aggregation pipelines, and selecting efficient data access patterns to minimize query complexity across large inspection datasets.
- Designed a modular billing architecture around Stripe metered usage, encapsulating subscription, usage-reporting, and billing workflows into reusable service components powering recurring revenue.
- Designed a vendor-agnostic architecture for the estimate management platform - supporting generic and vendor-specific catalogs, templates, pricing, materials, labor, and warranties - using reusable Zustand-based state management for complex multi-step flows; currently in final testing ahead of launch.
- Built an interactive geospatial measurement engine (Leaflet, Mapbox, Turf.js) performing polygon editing, coordinate transformations, and precise area calculations on satellite imagery.
- Designed reusable integration layers for external platforms including Canva, CompanyCam, and ABC, alongside an asynchronous PDF generation pipeline using cloud object storage and signed URLs - reducing duplication, improving reliability, and simplifying future integrations.
- Collaborated directly with product leadership (CTO, CEO) to translate ambiguous business requirements into scalable technical designs, while owning deployment across Docker, Kubernetes, and Azure CI/CD pipelines.
- Led technical interviews, mentored junior engineers, and established code review practices that improved maintainability and consistency across the team.
Middle Backend Developer
Confidence: Medium API Engineer
A pragmatic backend API engineer (Middle) focused on building well-structured single-repository SaaS features with a strength in practical Prisma-based data access and application-level access control. The strongest proven skill is implementing CRUD and sharing workflows with Prisma and tests, as shown in lib/services/documents.ts and tests/document.test.ts. There is limited evidence of advanced distributed-system design, production-grade scalability patterns, or large-scale infrastructure/CI engineering in the public human-authored code.
API Design
4/10
How well APIs are designed
API design is pragmatic and consistent for an application-level service: clear client-side helpers, server-side service layer and consistent error shaping exist, but there is no explicit versioning, idempotency keys, or advanced API contract/versioning strategy evident.
Data Layer & Database
5/10
Working with databases
Data layer shows practical, correct use of Prisma for queries, relations and includes; tests exercise migrations and seeding, but there is little evidence of explicit transaction usage, multi-statement consistency handling, or a migration history evolving across commits.
Evidence
SuperRiyaDev/Ajaija_Ai_Native_Assessment/lib/services/documents.ts - Prisma queries, includes and composite-unique lookups
SuperRiyaDev/Ajaija_Ai_Native_Assessment/tests/document.test.ts - test setup runs prisma migrate deploy and seeds a test DB
SuperRiyaDev/Ajaija_Ai_Native_Assessment/package.json - build/test scripts invoking prisma migrate/seed
Scalability & Performance
2/10
Handling load and speed
Limited scalability work is evident: standard server-side patterns are used but there are no caches, queues, rate limiters, or measured performance optimizations present in the human-authored code.
System Architecture
4/10
Overall system structure
Reasonable module separation and folder structure (lib/services, lib/api, client helpers, export utilities) show component boundaries and separation of concerns, but there is no multi-service decomposition or cross-service contract architecture to indicate a larger distributed design.
Security & Auth
4/10
Protecting data and access
Basic security practices appear: explicit access checks, centralized ApiError handling, and upload/export validation exist, but there is no evidence of a full auth lifecycle (refresh/revocation), secrets management, or hardened input-sanitization for all boundaries.
Reliability & Observability
3/10
Stability and monitoring
Some reliability practices are present (unit/integration style tests, test DB setup and graceful prisma disconnect in tests), but there is little evidence of retries with backoff, timeouts, structured tracing or metrics and no circuit breakers or advanced resiliency patterns.
Expertise
Node.js• Middle
Databases & Vector Storage• Middle
Microservices & API Architecture• Middle
Technologies
Node JS• Middle
Recommendations
- Develop REST/Next.js API endpoints and medium-complexity SaaS features that use Prisma for schema-driven data models and transactional operations.
- Build internal admin or CRM-style tools that require reliable access control, document sharing, and export features (PDF/Markdown) using the existing export utilities and tiptap converters.
- Expand test-driven schema evolution and migration workflows (add explicit migration history and transactional integration tests) before tackling cross-service or high-throughput systems.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Middle Frontend Developer
Confidence: High Fullstack
Fullstack Software Engineer (mid-level) focused on building Next.js/React apps with typed server-side data access and document workflows. The strongest proven skill is server-client integration and data modelling, demonstrated by the Prisma-backed server services in lib/services/documents.ts together with the typed client helpers in lib/api/client.ts. There is limited public evidence of large-scale system architecture, measured frontend performance work, advanced accessibility automation, or broad test coverage.
UI Component Architecture
3/10
How interface parts are built
Reasonable component and module boundaries for a small app; mostly utility modules and small components rather than a custom design system or advanced component composition patterns.
Responsive & Cross-browser
2/10
Works on all screens and browsers
Basic responsive layout and CSS variables used; no advanced responsive techniques (container queries, RTL scaffolding) or explicit cross-browser feature-detection shown.
Performance Optimization
2/10
Speed of the interface
Some pragmatic performance considerations (canvas scale for PDF export, ordering in DB queries) but no measured optimization artifacts, bundle analysis, or advanced runtime optimizations.
Accessibility & Semantics
3/10
Usable for everyone
Some accessibility and semantic attention in places (lang attribute, aria-hidden on export iframe), but no comprehensive a11y patterns or automated a11y checks evidenced.
State Management & Data Flow
4/10
Managing data in the app
Clear client-server data flow with typed client helpers, server-side services, and explicit error handling; good discipline on authorization checks but no complex state-machine or advanced optimistic update patterns.
UX & Visual Polish
3/10
Look and feel quality
Concrete UX features (PDF export, TipTap -> Markdown conversion, upload flow) and reasonable error messaging; lacks comprehensive loading/error UI coverage and undo/rollback flows in the UI code shown.
Expertise
React• Middle
Modern Web Frameworks• Middle
Industries
Commerce• Middle
Real Estate• Middle
Technologies
Next.js
React.js
Zod
Gatsby
shadcn/ui
Recommendations
- Implement and own small-to-medium SaaS features end-to-end (Next.js frontend, Prisma-backed APIs, billing integrations).
- Build rich document or editor UX features including export (PDF/Markdown) and upload pipelines, extending the existing TipTap integrations.
- Develop internal admin dashboards and CRM-style flows where typed server-client contracts and access checks are valuable.
- Work on feature-level performance improvements and automated a11y testing to strengthen cross-cutting engineering quality.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories: