Integration Developer

We've got around 20 Java / Spring Boot / Apache Camel services that basically connect everything at PopSockets that needs to talk to something else. NAV and Business Central on the ERP side, a 3PL that ships every B2B and B2C order, Salesforce Commerce Cloud, EDI with the big retailers (Target, Amazon, Best Buy, etc), a fulfillment partner in China, our PLM, and a data platform that wants a copy of all of it. It all runs on Azure Kubernetes.

We're looking for a senior dev who can own a chunk of that. Honestly, adding bodies doesn't add much shipping capacity unless the dev is legitimately good. Building up all the context and requirements somebody needs to do the job well takes real time, so we're being picky. The person we want is the one who can pick up "orders stopped showing up at the warehouse this morning," run it to ground across three systems, fix it properly, and write down what happened so the next person doesn't have to.

The team is split between India and Colorado and you'd be working day to day with devs and ops folks on both sides. There's real overlap required, more on that below.

We build with AI. A lot.

Read this part twice. AI coding agents aren't a side tool here, they're how the work actually gets done. We use them to write code, review PRs, dig through logs, draft runbooks and work production issues. Every repo has agent instructions checked in and an AI review runs on every PR before a human looks at it. We expect you to work this way from day one and get better at it every month.

That does not mean "let the model write it and ship it." It means you know how to drive an agent, check its work, spot when it's confidently wrong, and set it up so it's actually useful on our codebase instead of generic. If you're skeptical of the whole thing, or you've only ever used autocomplete, this probably isn't the right fit. If you've already rebuilt your workflow around agents and you're a little annoyed at teams that haven't, let's talk.

What you'd actually be doing

• Build and maintain Camel routes and Spring Boot services. New integrations, changes to existing ones, the occasional "why is this taking 40 seconds" rabbit hole.
• Own prod. When an order doesn't reach the warehouse or a shipping confirmation doesn't come back, you're one of the people who figures out why and fixes it. Some of that is code, a lot of it is reading logs and data and asking the right person the right question.
• EDI. 850 / 940 / 945 / 856 / 810 with SPS Commerce and direct retailer connections. If you haven't done EDI before you can learn it, but you have to actually want to.
• Work with the ERP and ops teams. Half the bugs in an integration platform are really data or process problems upstream. The good engineers here are the ones who can tell the difference and say so without being a jerk about it.