Jobswire

Jobswire was a multi-service hiring product prototype. It was developed with a team but never released to customers. I was responsible for coding across the project.

The codebase spans a Node/Express API, a GraphQL messaging service, a frontend application, and Docker-based local/deploy configuration. Public mirrors of the work live under my GitHub account.

I owned implementation while working with a team. I was responsible for coding the product systems we were building.

Team project with coding ownership — not a solo founder product and not a production customer deployment. Scope covers backend services, messaging foundations, frontend application work, and deployment configuration.

Hiring workflows need coordinated services: accounts and domain APIs, realtime messaging, a client application, and a reproducible deploy path.

• Implemented and maintained the Express/MongoDB backend (auth-related work, validation, API structure, Sentry).
• Established the GraphQL messaging service with Apollo Server and WebSocket subscription plumbing.
• Contributed the frontend application codebase.
• Configured Docker Compose orchestration for the service set.

• Service-oriented split (backend, message, frontend, deploy) for independent iteration.
• MongoDB/Mongoose for API persistence.
• GraphQL + graphql-ws for messaging foundations.
• Docker Compose for local multi-service runtime.

• Coordinating multiple repositories and service boundaries early.
• Messaging service remained early-stage relative to the richer backend API.
• Shipping rigor for an unreleased product without live customer feedback.

• A multi-service codebase demonstrating backend, messaging, frontend, and deploy ownership.
• The product was never released and has no customers — included as evidence of full-stack coding responsibility, not production traction.

• JavaScript
• TypeScript
• Node.js
• Express
• MongoDB
• Mongoose
• GraphQL
• Apollo Server
• WebSockets
• Docker
• Sentry

• Backend↗
• Message service↗
• Deploy↗
• Frontend↗