Platform Developer - AI
Listed on 2026-07-18
-
Software Development
Backend Developer, DevOps, Software Engineer, AI Engineer (Applied/Software)
General information
Remote? No
Ally and Your CareerAlly Financial only succeeds when its people do - and that’s more than some cliché people put on job postings. We live this stuff! We see our people as, well, people - with interests, families, friends, dreams, and causes that are all important to them. Our focus is on the health and safety of our teammates as well as work-life balance and diversity and inclusion.
From generous benefits to a variety of employee resource groups, we strive to build paths that encourage employees to stretch themselves professionally. We want to help you grow, develop, and learn new things. You’re constantly evolving, so shouldn’t your opportunities be, too?
At Ally, you get a startup feel, but experience the benefits of a company that has worked out the kinks and is fulfilling its purpose. We are always evolving and see that as a good thing. From owning our work to seeing its impact in the real world, our team is relentless in finding new ways technology can help make experiences better and help people.
We are problem solvers, we value diverse thinking, we support one another, and we challenge ourselves to think bigger in the journey to deliver customer-obsessed tech solutions. To read more about what our tech team does, be sure to visit our tech blog h
You will be the engineer who makes the agent ecosystem stable, reusable, and scalable. Where Senior Developers build agents and features, you build the platform those agents run on — the shared tooling, the deployment patterns, the REST API infrastructure, the script libraries, and the automation that reduces friction across every team in the Lightspeed and Logos programs.
You sit at the intersection of AI and platform engineering. You care about what happens after the demo:
How does this agent get deployed? How does the script that hits the Confluence API get maintained when the auth pattern changes? How do we run 20 Python automation scripts without them diverging? You answer those questions by building the right foundations, not by writing the same fix 20 times.
At this time, Ally will not sponsor a new applicant for employment authorization for this position.
The Work ItselfAgent runtime and tooling infrastructure
- Own the shared Python script library that underpins Confluence, Jira, and Dynatrace integrations — auth patterns, SSL context management, REST helpers, error handling conventions
- Build and maintain the scaffolding that new agent types are generated from (session startup, context loading, tool access patterns, output schemas)
- Standardize how agents write, read, and manage files in C:/Temp/ and persistent storage — naming conventions, JSON schemas, lifecycle management
Deployment and CI/CD for AI workloads
- Build the CI pipeline integrations that execute agent-driven gates (coverage, vulnerability, SRE readiness) as blocking checks before merge
- Implement the exit-code conventions and JSON report schemas that gate scripts emit, so CI can act on them reliably
- Own the environment and dependency management for the Python agent scripts: pinned versions, packaging, distribution to developer machines and CI runners
API and integration platform
- Maintain and evolve the REST API patterns for Confluence Cloud (Basic auth, Cloud HTML sanitization rules, version conflict handling) and on-prem Jira (Bearer PAT, CA cert, pagination)
- Build reusable integration modules that any agent or script can import rather than re-implement
- Extend MCP server configurations as new tool needs are identified; manage settings and permission profiles across the Claude Code harness
Developer experience
- Reduce the friction for teams onboarding to the Lightspeed framework — templates, init scripts, documentation, and the CLAUDE.md / knowledge core content that makes new agents immediately productive
- Build the tooling that validates agent behavior against the manifest and behavioral rules before a new agent type ships
- Own the C:/Temp/ workspace conventions, script naming standards, and output file lifecycle so the pipeline components stay composable
Minimum Requirements:
- 3+ years of relevant experience
- Bachelor’s Degree in…
(If this job is in fact in your jurisdiction, then you may be using a Proxy or VPN to access this site, and to progress further, you should change your connectivity to another mobile device or PC).