Role Overview
- 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)
Tech Stack
- Azure
- Distributed Systems
- Docker
- GraphQL
- Kafka
- Kubernetes
- NoSQL
- SQL
- .NET
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.