Software Engineer

• Design, build, and maintainGraphQL graph types, queries, mutations, and resolvers that expose Quantum ERPdata (work orders, purchase orders, GL/AP/AR, companies, inventory) accuratelyand safely.
• Extend the Entity FrameworkCore data layer and Oracle package wrappers and repositories, writing correct,performant queries against the Quantum Oracle schema.
• Optimize GraphQL execution: useDataLoader to avoid N+1 queries, apply sensible result limits, and keepresolver work efficient.
• Maintain JWT-basedauthentication and authorization and respect multi-tenant scoping on everyrequest and query.
• Translate business-layerprocess steps into API behavior that maintains parity with Quantum's businessrules.
• Write and maintain unit testsacross the API, business, and data layers, and use the benchmark projects tocatch performance regressions.
• Support the Angular clientwhere it consumes the GraphQL API, and keep the schema and client contract insync.
• Contribute to worker scheduledtasks where API and background work overlap.
• Document graph types, queries,and the Oracle-side dependencies each surface relies on.
• Participate in code review, theweekly integration sync, and discovery sessions, and coordinate early with theCorridor / Aviate parity teams so we do not build the same capability two ways.

Requirements

• 4+ years building productionAPIs in C# / .NET (ASP.NET Core or ASP.NET Web API).
• Strong object-oriented C# and asolid grasp of layered service architecture (data, business, API).
• Hands-on Entity Framework (EFCore or EF6) and strong SQL. Comfortable reading schemas, writing efficientqueries, and reasoning about ORM behavior and N+1 problems. Oracle experienceis a strong plus.
• Practical understanding of APIsecurity: JWT / bearer tokens, authentication and authorization, and inputvalidation.
• A track record of writing unittests and treating test coverage as part of the definition of done.
• Comfort working against realbusiness or ERP data models where correctness and auditability matter (finance,accounting, or inventory domains).
• Clear written communication andthe discipline to document schemas and open questions.

Originally posted on Himalayas