Nimsy Duddu

About

Backend engineer with insurance/claims domain experience who modernized legacy claims processing systems to support AI-assisted claim review. Emphasizes production-ready API design in Python/FastAPI (schemas, async, caching, graceful degradation), strong observability with Prometheus, and layered security including JWT auth plus database row-level security (Supabase/Postgres).

Experience

Education

Key Strengths

• Evolved a monolithic claims platform into service-oriented architecture to enable AI-driven insights
• Pragmatic architecture decisions balancing microservices benefits vs operational/team maturity constraints
• Designed APIs to degrade gracefully (partial/cached responses when dependencies fail)
• Led/implemented incremental backend refactors with parallel APIs, feature flags, and phased rollouts
• Strong focus on data integrity via old-vs-new response parity checks in production
• Proactive observability approach using Prometheus metrics and anomaly-based alerting
• Layered security implementation: JWT auth, RBAC/ABAC permissions, and database-enforced row-level security
• Identified and mitigated AI 'soft failure' edge cases (partial/low-confidence results) to prevent misleading outputs and UI issues

Reference Highlights

• Strong end-to-end ownership of backend systems
• Proactive about edge cases and integration risks
• Takes responsibility for production issues
• Prevents issues through early validation and fallback planning
• Sound architectural judgment
• Prefers simple, maintainable designs over unnecessary complexity
• Thinks about scalability before implementation
• Security-conscious; raises concerns early
• Practical and risk-aware decision-making
• Effective cross-functional collaborator with frontend engineers
• Aligns early on API behavior and UI data needs
• Clear communicator; open to feedback and quick to iterate
• Empathetic/product-aware approach (understands how screens are actually used)
• Delivers smoother releases with less rework
• Performs well in ambiguity and early-stage environments
• Keeps momentum by proposing practical starting points
• Adapts solutions as requirements evolve without major rework