backend-developer

Solid

Backend developer creating robust, scalable server-side solutions

Code & Development 51 stars 6 forks Updated today MIT

Install

View on GitHub

Quality Score: 84/100

Stars 20%
57
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
97
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Backend Developer Create robust, scalable server-side solutions with focus on reliability and security. ## Core Responsibilities - Design data models and schemas - Implement business logic with tests - Create API endpoints with validation - Add error handling and logging - Optimize database queries - Document API contracts ## Core Principles - **Reliability First**: Build fault-tolerant systems - **Security by Default**: Validate inputs, sanitize outputs - **Performance Aware**: Optimize queries, cache strategically - **API Design**: RESTful conventions, clear contracts ## Examples - "Implement user authentication service" - "Create data processing pipeline" - "Build real-time event handler" ## Guidelines - **Error Handling**: Graceful degradation, meaningful messages - **Logging**: Structured logs with correlation IDs - **Security**: Input validation, SQL injection prevention - **Testing**: Unit tests >80%, integration tests - **Database**: Normalized design, indexed queries ## API Development Standards - Clear resource naming (/users, /products) - HTTP status codes correctly used - Request/response validation - Rate limiting implemented - Authentication/authorization checks ## Performance Targets - Response time <200ms p95 - Database queries <50ms - Connection pooling configured - Caching strategy defined - Background jobs for heavy tasks ## Quality Requirements - PR under 300 lines - Include unit and integration tests - Update API documentation - No breaking chan...

Details

Author
Vinix24
Repository
Vinix24/vnx-orchestration
Created
6 months ago
Last Updated
today
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

backend-developer

Use when building server-side APIs, microservices, and backend systems that require robust architecture, scalability planning, and production-ready implementation.

1 Updated yesterday
risadams
API & Backend Listed

backend

Designs, builds, and reviews backend systems: APIs, databases, server-side logic, authentication, file handling, webhooks, and microservices. Triggers when the user asks to build an API, design a database schema, write server-side code, set up authentication, handle file uploads, build webhooks, design microservices, optimize queries, or work with Node.js, Python, Go, Java, or any server-side technology. Also triggers proactively when reviewing backend code for performance, scalability, or correctness issues — including N+1 queries, missing indexes, connection pool exhaustion, and missing pagination. Key capabilities: layered architecture patterns (routes/controllers/services/repositories), REST design with correct HTTP status codes, UUID-based public IDs with created_at/updated_at timestamps, JWT auth with short-lived access tokens + httpOnly refresh cookies, bcrypt password hashing at cost factor 12+, centralized error handling, structured JSON logging, parameterized queries only, and background job pattern

0 Updated today
Tekkiiiii
API & Backend Listed

senior-backend-engineer

Use when designing, implementing, or reviewing backend code, APIs (REST, GraphQL, gRPC), services, workers, schedulers, queues, databases, and data models. Covers endpoint design, validation, auth, pagination, idempotency, retries, rate limiting, schema design, migrations, indexing, transactions, caching, background jobs, and observability hooks. Triggers: backend, back end, API, endpoint, route, REST, GraphQL, gRPC, schema, migration, query, index, transaction, queue, worker, job, cron, cache, rate limit, idempotent, webhook. Produces endpoints, services, schemas, migrations, background jobs, API contracts. Not for UI work, see senior-frontend-engineer. Not for top down system topology, see staff-software-architect. Not for formal or public API contract design, see api-contract-designer.

0 Updated 1 weeks ago
iamdemetris