Showcase Your NestJS Skills with a GitHub README Badge

Use this markdown in your README:

![NestJS](https://img.shields.io/badge/NestJS-E0234E?style=for-the-badge&logo=nestjs&logoColor=white)

The #E0234E is NestJS's official red — a distinctive crimson that mirrors the NestJS cat logo and matches their brand guidelines. The nestjs logo identifier renders NestJS's cat logo from Simple Icons. This red badge is immediately recognizable to TypeScript backend engineers and stands out distinctly from Express's minimalist gray profile.

NestJS's architecture mirrors Angular closely — list the concepts you use in production:

• Modules: Application modularization, feature modules, dynamic modules
• Controllers and Services: Request handling separation, service layer with business logic
• Dependency injection: Provider scopes (singleton, request, transient), custom providers
• Guards and Interceptors: Authentication guards (JWT, roles), request/response transformation
• Pipes: Validation with class-validator and class-transformer DTOs
• Microservices: Transport layers (TCP, Redis, RabbitMQ, Kafka), hybrid applications
• Database integration: TypeORM, Prisma, or Mongoose with NestJS
• Testing: Jest unit tests, supertest E2E tests with NestJS test utilities

Mentioning DTOs (Data Transfer Objects) with class-validator decorators signals that you build APIs with proper input validation and type safety throughout the request lifecycle.

NestJS appears in TypeScript-heavy backend stacks:

• TypeScript API stack: NestJS + TypeScript + PostgreSQL + TypeORM + Redis
• Microservices: NestJS + Kafka/RabbitMQ + Docker + Kubernetes
• GraphQL API: NestJS + GraphQL (code-first) + PostgreSQL + Prisma
• Full-stack TypeScript: NestJS + Next.js + PostgreSQL + Prisma (shared types)

NestJS and Express are complementary — NestJS is built on Express (or Fastify) and adds architectural structure on top. Engineers who understand when to use NestJS's opinionated structure (team projects, microservices, complex APIs) versus bare Express (simple APIs, prototypes, performance-critical services) demonstrate framework selection judgment.

NestJS applications are TypeScript — your language stats will correctly show TypeScript as the primary language. NestJS's decorator-heavy style produces more TypeScript boilerplate than Express, but this structure pays dividends in maintainability at scale.

For pinned repositories, a NestJS project with well-organized module structure, complete DTO validation, authentication implemented with Guards, and comprehensive test coverage (unit + E2E) is an outstanding backend engineering showcase. Adding OpenAPI documentation (NestJS has built-in Swagger integration via @nestjs/swagger) that auto-generates from your DTOs and controllers demonstrates a production-quality API development approach that hiring managers specifically look for in TypeScript backend roles.