> Markdown version of [/jobs/ext/2388783-senior-platform-engineer](https://www.wearedevelopers.com/jobs/ext/2388783-senior-platform-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Senior Platform Engineer - **Company:** COLLECTORS L.L.C. - **Location:** Jersey City, NJ, United States (Remote available) - **Experience:** Expert - **Salary:** $140,000.0 - $200,000.0 - **Contract:** Permanent contract - **Skills:** Artificial Intelligence, Amazon Web Services, Cloud Computing, Continuous Integration, Software Design Documents, Python (Programming Language), Runbook, Software Systems, TypeScript, Delivery Pipeline, Large Language Models, Backend, Kubernetes, Code Migration - **Published:** August 7, 2026 - **Apply:** https://www.indeed.com/viewjob?jk=e307a74e62360a6c ## About the Role * An experienced engineer with 5+ years building, shipping, and operating production software, ideally with meaningful time spent in platform, infrastructure, developer experience, or similarly leverage-oriented roles. * A strong software generalist with systems knowledge. You're comfortable moving across backend services, automation pipelines, infrastructure, and internal tools, and you know when to go deep. * Fluent in at least one modern language commonly used for platform work (such as Python or TypeScript) and experienced with cloud infrastructure (AWS preferred), containers and Kubernetes, infrastructure-as-code, and modern CI/CD systems. * A hands-on builder with AI. You've integrated LLMs or agent-based automation into real engineering workflows - shipping working tools, not just experiments - and you stay current on where the technology is heading. * Energized by ambiguity. You can take a fuzzy problem statement, break it down, propose a plan, and execute - course-correcting quickly as you learn. * Product-minded about internal customers. You treat fellow engineers as users, care about the usability of what you ship, and measure success by adoption and outcomes rather than output. * An excellent communicator. Your design docs, runbooks, and postmortems are clear, and you build trust with partner teams through consistent, low-drama delivery. * Pragmatic about operations. You take ownership from design through deployment and on-call, and you leave systems better documented and more reliable than you found them. Nice to Have: * Experience with developer portals, service catalogs, or fleet/dependency management systems. * Experience running large-scale code migration or modernization efforts. * Familiarity with evaluation and observability practices for AI-powered systems ## Description We're looking for a Senior Platform Engineer to join our Platform Engineering team and help make every engineer at Collectors more productive. This is a builder's role for a strong software generalist with systems depth: you'll design and ship the internal platforms, paved paths, and custom tooling that product teams rely on to develop, deploy, and operate software quickly and safely. The problems you'll take on are often ambiguous and cross-cutting; we'll count on you to scope them, propose a direction, and drive them to completion. Remote or hybrid candidates will also be considered. We believe that there is significant value in in-person collaboration. If you live within a 1 hour commuting distance to one of our offices, you will be required to be onsite most of the time. This will be discussed further as part of the recruiting process. What You'll Do: * Build the paved path. Design, build, and operate the internal platforms that engineers use every day - CI/CD pipelines, developer environments, deployment workflows, and shared services - and continuously reduce the friction between "code written" and "value shipped." * Create custom tooling that multiplies the team. Identify repetitive, error-prone, or slow engineering workflows and replace them with automation and self-service tools that generalize beyond a single use case. * Bring AI into the engineering workflow. Prototype and productionize AI-assisted capabilities - from LLM-powered code modification and migration automation to agentic workflows for operational tasks - treating them as real software systems with evaluation, observability, and guardrails, not just prompts. * Own problems end-to-end in ambiguous spaces. Take loosely defined, high-priority platform challenges from discovery through design, implementation, rollout, and adoption, making pragmatic build-vs-buy and speed-vs-durability tradeoffs along the way. * Strengthen core infrastructure. Contribute to our cloud and container foundations (Kubernetes, infrastructure-as-code, networking, observability), improving the reliability, scalability, and cost-efficiency of the systems other teams build on. * Drive adoption with data. Instrument the platforms you build, define success metrics, and use telemetry and direct partnership with product teams to guide what gets built next. * Communicate and collaborate. Write clear design documents and tradeoff analyses, embed with partner teams to understand their pain points, and influence engineering practices across the organization without relying on formal authority., U.S. residents: for disclosures relating to personal information we collect during the employment application and recruitment process, please see our Privacy Notice for U.S. Applicants. ## Related Videos - [Shipping Faster with Less: Render on Cloud Hosting, AI Workloads, and the Future of DevOps](https://www.wearedevelopers.com/videos/1894-shipping-faster-with-less-render-on-cloud-hosting-ai-workloads-and-the-future-of-devops) - [Do TypeScript without TypeScript](https://www.wearedevelopers.com/videos/327-do-typescript-without-typescript) - [Developing the Backend with Stefan Lingler, CTO at Shpock](https://www.wearedevelopers.com/videos/100360-developing-the-backend-with-stefan-lingler-cto-at-shpock) - [Technical Documentation - How Can I Write Them Better and Why Should I Care?](https://www.wearedevelopers.com/videos/681-technical-documentation-how-can-i-write-them-better-and-why-should-i-care) - [Nest.js - TypeScript in the backend can also be clean](https://www.wearedevelopers.com/videos/1033-nest-js-typescript-in-the-backend-can-also-be-clean) - [Meet Your New BFF: Backend to Frontend without the Duct Tape](https://www.wearedevelopers.com/videos/682-meet-your-new-bff-backend-to-frontend-without-the-duct-tape) ## Related Articles - [How to Become an AI Engineer](https://www.wearedevelopers.com/magazine/331-how-to-become-an-ai-engineer) - [How We Built a Worry-Free System That Runs for 10+ Years – And What We’d Do Again](https://www.wearedevelopers.com/magazine/751-how-we-built-a-worry-free-system-that-runs-for-10-years-and-what-we-d-do-again) - [Dev Digest 121 - AI goes offline](https://www.wearedevelopers.com/magazine/456-dev-digest-121-ai-goes-offline) - [Navigating the AI Shift](https://www.wearedevelopers.com/magazine/629-navigating-the-ai-shift) - [From Prototype to Production: Build AI Agents with This Free 4-Course Learning Path](https://www.wearedevelopers.com/magazine/655-from-prototype-to-production-build-ai-agents-with-this-free-4-course-learning-path) - [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers)