How do you design a GraphQL schema with proper types, queries, and mutations?

Question

"Design a GraphQL schema for a job application tracker."

Interview OS Community · Accepted Answer

```graphql
type Query {
  applications(filter: ApplicationFilter, page: Int, limit: Int): ApplicationConnection!
  application(id: ID!): Application
}

type Mutation {
  createApplication(input: CreateApplicationInput!): Application!
  updateApplication(id: ID!, input: UpdateApplicationInput!): Application!
  deleteApplication(id: ID!): Boolean!
}

type Application {
  id: ID!
  company: String!
  position: String!
  status: ApplicationStatus!
  interviews: [Interview!]!
  offer: Offer
  createdAt: DateTime!
}

enum ApplicationStatus { APPLIED INTERVIEW OFFER REJECTED WITHDRAWN }

type ApplicationConnection {
  edges: [ApplicationEdge!]!
  pageInfo: PageInfo!
  totalCount: Int!
}
```

| Principle | Why |
|-----------|-----|
| IDs for mutations | Clear, cacheable |
| Pagination with connections | Handle large lists |
| Enums for fixed values | Type safety |
| Separate input types | Validation |

Interview OS

How do you design a GraphQL schema with proper types, queries, and mutations?

Question Details

Suggested Solution

Discussion (0)