C# / .NET Developer — API Identity authentication and authorization services
C# / .NET Developer — API Identity authentication and authorization services
Posted yesterday
SENIORITY
Senior
About the role
- Cross-service features — API services using SQL (PostgreSQL or SQL Server) and Redis, across the broader platform
- Redis-backed data access — Reading and serving cached data snapshots with low latency; session and user-state management across data servers
- API platform patterns — Building on our internal REST server framework: dual-port public/private hosting, Swagger documentation, compression, CORS, and standardized error handling
- Design, implement, and maintain REST API endpoints in C# / ASP.NET Core (.NET 8+)
- Experience with authorization and authentication best practices including OAuth 2.0, API keys, JWT tokens, MFA, key rotation, etc.
- Integrate with Redis for caching, snapshots, and pub/sub patterns using Stack Exchange. Redis and related libraries
- Write and optimize SQL queries and stored procedures against PostgreSQL or SQL Server as needed
- Add Swagger/OpenAPI documentation and follow established API conventions
- Tune performance for high-throughput, low-latency scenarios (thread pool configuration, connection pooling, async patterns)
- Participate in code reviews, troubleshooting production issues, and iterative feature delivery
- 3–5 years of professional experience with C# and .NET (ASP.NET Core)
- Solid understanding of REST API design, HTTP semantics, and API versioning practices
- Comfort with async/await, dependency injection, and standard .NET service patterns
- Experience with Redis — caching, key design, connection management, and basic pub/sub
- Experience with relational databases — writing queries, understanding indexes, and working with PostgreSQL or SQL Server
- Familiarity with Git, CI/CD pipelines, and deploying services to production
- Experience with Polly or similar resilience libraries (retries, circuit breakers)
- Experience with performance logging, observability, and production debugging under load
Before you apply
Applying takes about a minute. These four things decide how fast it moves after that.
Your profile is current
It's what we read first. Occupations, seniority and locations matter more than a long history.
Two examples you can talk through
Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.
A number in mind
What you're on now and what would make you move. We negotiate better when we know both.
Your notice period
Employers plan around it, and it's the question that stalls offers most often.
Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.
More like this
