Software Engineer

This is a remote position.

· Design, build, and maintain GraphQL graph types, queries, mutations, and resolvers that expose Quantum ERP data (work orders, purchase orders, GL/AP/AR, companies, inventory) accurately and safely.

· Extend the Entity Framework Core data layer and Oracle package wrappers and repositories, writing correct, performant queries against the Quantum Oracle schema.

· Optimize GraphQL execution: use DataLoader to avoid N+1 queries, apply sensible result limits, and keep resolver work efficient.

· Maintain JWT-based authentication and authorization and respect multi-tenant scoping on every request and query.

· Translate business-layer process steps into API behavior that maintains parity with Quantum's business rules.

· Write and maintain unit tests across the API, business, and data layers, and use the benchmark projects to catch performance regressions.

· Support the Angular client where it consumes the GraphQL API, and keep the schema and client contract in sync.

· Contribute to worker scheduled tasks where API and background work overlap.

· Document graph types, queries, and the Oracle-side dependencies each surface relies on.

· Participate in code review, the weekly integration sync, and discovery sessions, and coordinate early with the Corridor / Aviate parity teams so we do not build the same capability two ways.

Requirements

· 4+ years building production APIs in C# / .NET (ASP.NET Core or ASP.NET Web API).

· Strong object-oriented C# and a solid grasp of layered service architecture (data, business, API).

· Hands-on Entity Framework (EF Core or EF6) and strong SQL. Comfortable reading schemas, writing efficient queries, and reasoning about ORM behavior and N+1 problems. Oracle experience is a strong plus.

· Practical understanding of API security: JWT / bearer tokens, authentication and authorization, and input validation.

· A track record of writing unit tests and treating test coverage as part of the definition of done.

· Comfort working against real business or ERP data models where correctness and auditability matter (finance, accounting, or inventory domains).

· Clear written communication and the discipline to document schemas and open questions.