Gautam Patil

Backend work across permissions, search and batch data movement on a DynamoDB-backed platform.

• Fine-grained access control — permission checks enforced at the API layer, so every request resolves only the records the caller is entitled to.
• Real-time search — DynamoDB Streams feed an indexing pipeline that keeps OpenSearch in step with writes, making new data searchable without a reindex.
• Fault-tolerant pipelines — Step Functions orchestrate multi-step data jobs with retries and explicit failure states, so one bad record fails a single execution rather than the whole batch.

• NestJS
• Go
• DynamoDB
• OpenSearch
• Step Functions

Backend services behind the platform's billing workflows, reporting and third-party automation.

• Invoice & expense APIs — the REST services covering the core record-keeping workflow customers use day to day.
• Scheduled reporting — Go workers generate reports on a schedule, keeping long-running aggregation off the request path.
• Zapier integrations — custom triggers and actions so customers can wire the platform into their own automation flows without bespoke work.

• Node.js
• Go
• MongoDB
• Zapier

Verification backend built for correctness under repeat submissions and bursty load.

• Verification logic in Go — the service that runs submitted documents through the verification flow and returns a decision.
• Redis caching — de-duplicates in-flight and recently seen work, so the same document is never processed twice.
• Rate limiting — API-level limits keep latency and throughput predictable when submissions spike.

• Go
• Redis
• AWS Storage/Search

Read-heavy microservices with a schema and delivery pipeline built to match.

• Service boundaries — Node.js microservices split along inventory and order-processing lines so each can be changed and deployed on its own.
• PostgreSQL tuning — schemas and indexes shaped around the hot query paths for high read throughput.
• Automated delivery — GitHub Actions running the test suites on every push, so regressions surface before merge.

• Node.js
• PostgreSQL
• GitHub Actions