GHX
Software Engineer III – Developer Platform & AI Enablement
Office Location or Remote - USA (Remote)$102k–$136kmidAdded today
About this role
GHX is hiring a Software Engineer III to build developer platforms and AI capabilities that enable healthcare engineering teams. You'll own end-to-end platform features—from agent SDKs to MCP servers to infrastructure-as-code—while working embedded with product teams to prove patterns before scaling them organization-wide.
What you'll do
- Design, develop, and maintain platform capabilities end-to-end, including technical documentation and architectural reviews
- Build and operate MCP servers with stdio and HTTP transports, managing schema design and authentication
- Develop reusable GitHub Actions, Terraform modules, and IaC artifacts consumed across the organization
- Extend the internal agent platform SDK and APIs, including local model routing logic
- Co-facilitate weekly AI in Automation Office Hours and deliver live technical sessions both remote and in-person
- Instrument developer-facing tools to measure adoption and contribute to delivery metrics infrastructure
What they're looking for
- GitHub Actions and CI/CD pipeline development
- Infrastructure-as-Code (Terraform or equivalent)
- AI-powered development tools (Claude Code, Copilot, Cursor)
- MCP server architecture and implementation
- Python and AWS deployment/debugging
- Technical writing (design docs, ADRs, runbooks)
- Java and Maven for reading unfamiliar codebases
- System measurement and benchmarking methodologies
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
GHX
GHX builds healthcare supply chain technology solutions and platforms. The company is hiring Software Engineers at multiple levels to develop full-stack applications using Angular, Java, and AWS cloud services.
- Website
- ghx.com
Likely interview questions
- Walk us through a time you built internal tooling for engineers—how did you measure whether it was actually adopted, and what would you do differently?
- Describe your experience authoring reusable GitHub Actions or CI workflows. How do you ensure they're maintainable and documented for other teams?