1

Rest Api Graphql Jobs (NOW HIRING)

NJ · On-site

What You''ll Do Architecture and platform strategy Define the enterprise API architecture model across REST, GraphQL, event-driven APIs, and service-to-service integration Own the technical strategy ...

Web Designer

Washington, DC · On-site

$100 - $125/hr

Integration & API Development * Build and maintain integrations with third‑party systems (REST, API, GraphQL, SSO, CRM, payment gateways, etc.). * Work with cloud hosting environments (Acquia ...

Required : • Strong hands-on experience in GraphQL (GQL) API development. • Proficient in Java, with experience building REST and/or GraphQL APIs. • Solid understanding of API design principles ...

You have Proven experience with GraphQL API development [preferable Apollo Graph QL] * Strong ... Strong understanding of REST API implementation, including Enterprise Authentication and ...

You have Proven experience with GraphQL API development [preferable Apollo Graph QL] * Strong ... Strong understanding of REST API implementation, including Enterprise Authentication and ...

$110K - $128K/yr

REST API * Git * CI/CD * Jest / React Testing Library * Azure * Docker / Kubernetes * GraphQL * Micro Frontends Education Bachelor's Degree in Computer Science, Software Engineering, Web Development ...

Responsibilities : • Design and implement high-quality, scalable RESTful, GraphQL, or event ... data formats (REST, SOAP, JSON, XML). • Hands-on experience with API gateways and management ...

Build and maintain integrations with third‑party systems (REST, API, GraphQL, SSO, CRM, payment gateways, etc.). Work with cloud hosting environments (Acquia, Pantheon, AWS, Azure) to deploy and ...

Sr. Java Developer - Seattle, WA

Seattle, WA · On-site

$65.25 - $83/hr

MongoDB or DynamoDB • REST API • Kafka and Event driven services • GraphQL • JWT and OAuth • Docker and Kubernetes • Developing on Mac OS • Cloud Experience Qualifications : Required ...

Hands-on experience with Message brokers (Kafka or equivalent), GraphQL or REST API development. * Expert-level coding experience in Java, Python, or Scala. * Expertise in Microservices architecture ...

Showing results 21-40

Rest Api Graphql information

See salary details

$10

$59

$77

How much do rest api graphql jobs pay per hour?

As of Sep 8, 2026, the average hourly pay for rest api graphql in the United States is $59.89, according to ZipRecruiter salary data. Most workers in this role earn between $54.57 and $67.31 per hour, depending on experience, location, and employer.

What are REST API and GraphQL?

REST API and GraphQL are two popular approaches for building APIs that allow different software applications to communicate with each other. REST (Representational State Transfer) is an architectural style that uses standard HTTP methods like GET, POST, PUT, and DELETE to access and manipulate resources. GraphQL, on the other hand, is a query language for APIs that enables clients to request exactly the data they need, making data fetching more flexible and efficient. Both have their advantages: REST is simple and widely adopted, while GraphQL offers more flexibility and reduces over-fetching of data.

What are the key skills and qualifications needed to thrive as a REST API and GraphQL developer?

To thrive as a REST API and GraphQL Developer, you need strong programming skills in languages like JavaScript, Python, or Java, and a solid understanding of API design principles and data modeling. Familiarity with frameworks such as Express.js, Apollo Server, and tools like Postman, as well as experience with API documentation and authentication protocols, are typically required. Excellent problem-solving abilities, attention to detail, and effective communication help developers collaborate with teams and address complex integration issues. These skills ensure robust, scalable, and user-friendly APIs that efficiently support diverse client applications.

How do REST API and GraphQL developers typically collaborate with frontend teams to optimize data fetching and performance?

REST API and GraphQL developers work closely with frontend teams to ensure that data delivery is efficient and meets the needs of user interfaces. For REST, this often involves designing endpoints that provide just the necessary data, while with GraphQL, developers create schemas and resolvers that enable clients to request specific fields, reducing over-fetching. Regular communication is key to understanding frontend requirements and iterating on the API structure to support new features or changes, leading to a more responsive and maintainable application.

What is the difference between Rest Api Graphql vs Backend Developer?

AspectRest Api GraphqlBackend Developer
Primary FocusDesigning and implementing APIs using REST or GraphQLBuilding server-side logic, databases, and application architecture
Skills & CertificationsAPI protocols, JavaScript, Node.js, GraphQL, RESTProgramming languages, database management, server frameworks
Work EnvironmentCollaborates with frontend teams, API design, cloud servicesServer-side development, database integration, system architecture
Industry UsageWeb services, SaaS, mobile appsWeb applications, enterprise systems, software solutions

While Rest Api Graphql specialists focus on designing and optimizing APIs using REST or GraphQL, Backend Developers build the overall server-side infrastructure and logic. Both roles often collaborate but differ in scope: API specialists concentrate on data exchange protocols, whereas Backend Developers handle broader system architecture and database management.

What other helpful pages are available for Rest Api Graphql?

Other pages related to Rest Api Graphql:

Infographic showing various Rest Api Graphql job openings in the United States as of July 2026, with employment types broken down into 91% Full Time, 3% Part Time, and 6% Contract. Highlights an 77% Physical, 4% Hybrid, and 19% Remote job distribution, with an average salary of $124,567 per year, or $59.9 per hour.

Principal API Architect, API Platform Engineering & Governance Enforcement

NJ • On-site

Intraedge
IT Services • 1 - 5K employees

Other

Re-posted 10 days ago


Key responsibilities

  • Translate API governance standards into machine-enforceable controls and ensure compliance through platform capabilities, CI/CD controls, contract validation, and runtime policy.

  • Lead the architecture and platform strategy for enterprise API delivery, including API patterns, gateway architecture, service mesh integration, and developer experience.

  • Review critical API designs, contribute to platform primitives, and mentor engineering teams to ensure secure, compliant, and reliable API implementations.


Job description

 

Principal API Architect, API Platform Engineering & Governance Enforcement

Long term contract

NJ (Hybrid-3 days onsite)

Immediate client interview

 

Job description:

Principal Architect reporting to engineering leadership. Partners closely with the API Governance Lead, Enterprise Architecture, Information Security, IAM, SRE and domain engineering teams.

 

The Role

You are the senior technical authority for enterprise API architecture and the enforcement of API governance standards. This role exists to close the gap between governance policy and engineering execution: governance defines the rules, you make them executable through platform capabilities, CI/CD controls, contract validation, and runtime policy.

This is a hands-on architecture and engineering leadership role. Your goal is to make the compliant delivery path the default path, so federated teams can move quickly without creating contract drift, security gaps, audit exposure, or inconsistent consumer experiences.

What You''ll Do

Architecture and platform strategy

Define the enterprise API architecture model across REST, GraphQL, event-driven APIs, and service-to-service integration

Own the technical strategy for gateway architecture, service mesh integration, developer experience, lifecycle tooling, observability, and runtime enforcement

Establish supported patterns and guardrails for enterprise-scale API delivery

 

Governance enforcement

Translate ratified standards into machine-enforceable controls: OpenAPI/AsyncAPI/Graphql validation, schema checks, linting, contract testing, backward-compatibility validation, CI/CD quality gates, and policy-as-code

Define what "compliant" means in code, pipelines, gateway policy, and production telemetry

Own the technical rules for API classification and layering: enterprise, domain, channel, data-access, and partner APIs

 

Traffic and migration architecture

Define where routing, authN/authZ, rate limiting, resiliency, and audit controls belong across ingress gateways, service mesh, and application services

Lead architecture across the gateway estate, including migration-safe patterns for policy parity, consumer cutover, and decommissioning without standards drift

 

Developer enablement

Build and maintain reference implementations and golden paths for common API patterns

Own the technical requirements for a complete, trustworthy enterprise API catalog: ownership metadata, classification, lifecycle status, consumer dependencies, and audit traceability

 

Security and reliability

Own implementation patterns for OAuth2, OIDC, JWT validation, mTLS, workload identity, token propagation, rate limiting, circuit breakers, SLOs, and end-to-end traceability

Partner with Security, IAM, SRE, and Compliance to ensure controls are enforceable and audit-ready

 

Technical leadership

Serve as senior reviewer for cross-domain, high-blast-radius, externally exposed, and regulated API designs

Review critical pull requests, contribute production code to platform primitives, and mentor senior engineers and domain architects

Lead through technical depth and credibility, not reporting lines

Your Authority

Establish mandatory technical controls for enterprise APIs

Approve or reject cross-domain and high-risk API designs

Require remediation before release when codified, non-negotiable standards are violated

Define compliance criteria for delivery pipelines and runtime enforcement

Recommend platform roadmap priorities for governance enforcement and developer experience

 

What You Bring

12+ years of software engineering experience in distributed systems, API platforms, or enterprise integration

Multi-year experience as a Principal, Staff or Lead Architect

Production ownership of enterprise-scale API platforms or high-volume API ecosystems

Deep expertise in REST, GraphQL, event-driven architecture, contract-first development and API lifecycle management

Strong knowledge of OAuth2, OIDC, JWT, mTLS, and enterprise identity integration

Experience building automated controls through CI/CD, policy-as-code, and deployment gates

Experience in one or more - APIC, KGateway, Datapower, IBM MQ, Kafka

Proven ability to influence engineering teams without direct reporting authority

Preferred

Banking, payments, insurance, healthcare, or other regulated environments

High-transaction-volume platforms and multi-gateway migrations or consolidations

Internal developer platforms, API catalogs, developer portals, or API product models

Audit-grade traceability and automated regulatory evidence


IntraEdge logo

About IntraEdge

Sourced by ZipRecruiter

At heart, we are a technology, products and services organization In our soul, it’s the people who make us what we are — the professionals we train and connect to next-level opportunities and the experts who create innovative solutions and value for our national and international partners. It’s true that innovative technology can provide a major boost to your business, but you also need the right talent pushing it forward. This critical combination is what we offer all of our partners: cutting edge tech solutions and the expertise to bring it to life.

Industry

It services

Company size

1,001 - 5,000 Employees

Headquarters location

Chandler, AZ, US

Year founded

2002

Social media