GraphQL Engineer, .NET, Azure
Posted 1hrs ago
Employment Information
Report this job
Job expired or something wrong with this job?
Job Description
Backend Engineer responsible for owning and scaling GraphQL APIs using C# .NET. Working remotely with a focus on cloud-based infrastructures and distributed systems.
Responsibilities:
- Design, develop, and evolve **GraphQL APIs for performance and scalability**
- Define schemas, resolvers, and data models across distributed systems
- Own key decisions:
- Schema design and governance
- Backwards compatibility
- API evolution strategies
- Integrate multiple backend systems into a unified GraphQL layer
- Collaborate closely with frontend/client teams consuming the API
- Build scalable backend services using C# .NET
- Apply clean architecture and best practices
- Ensure maintainability and performance
- Deploy and operate distributed systems in Microsoft Azure
- Ensure reliability, observability, and scalability
- Troubleshoot and optimize production systems
- Support event-driven workflows when needed
- Kafka is a plus, not a requirement
Requirements:
- **Must-Have (Non-Negotiable)**
- 5+ years in backend or API engineering
- Strong experience with **C# .NET**
- Proven experience **owning APIs in production**
- Solid understanding of:
- Distributed systems
- API performance and scalability
- Data modeling (SQL/NoSQL)
- Experience with Microsoft Azure
- **GraphQL (Flexible Entry Point)**
- We are open to candidates with either:
- **Option A (Ideal):**
- Strong experience designing and owning GraphQL APIs in production
- **Option B (High Potential):**
- Hands-on exposure to GraphQL **OR**
- Strong REST/API design experience with understanding of:
- Over-fetching / under-fetching challenges
- Client-driven data needs
- API abstraction layers
- 👉 *Candidates in this category must demonstrate the ability to quickly transition into GraphQL ownership.*
- **What We Are Specifically Looking For (Refined Signal)**
- Strong candidates typically have:
- Owned APIs end-to-end in production
- Made architectural or design decisions
- Worked with multiple consumers (frontend, mobile, external clients)
- Experience integrating multiple data sources into a unified API
- **Less Suitable Candidates**
- Only implemented APIs without ownership
- No experience with performance or scalability challenges
- Limited exposure to multi-team environments
- No understanding of API design trade-offs
- **Nice to Have**
- GraphQL in production environments
- Kafka / event-driven systems
- Docker / Kubernetes
- Observability tools (Azure Monitor, App Insights)
Benefits:
- 🚀 Integration into global brands and disruptive startups.
- 🏡 Remote work / Home office.
- 📍 If a hybrid or on-site modality is required, you will be informed from the first interview.
- ⏳ Schedule aligned with the assigned project or work cell.
- 📅 Monday to Friday work schedule.
- 🎉 Day off on your birthday.
- 🏥 Major medical expenses insurance (applicable in Mexico).
- 🛡️ Life insurance (applicable in Mexico).
- 🌎 Multicultural work teams.
- 🎓 Access to courses and certifications.
- 📢 Meetups with special guests from the IT industry.
- 📡 Virtual team-building events and interest groups.
- 📢 English classes.
- 🏆 Opportunities across our different business lines.
- 🏅 Proudly certified as a Great Place to Work.
















