The Opportunity

At Drumkit, we are building the AI platform for the logistics industry. We help the largest freight brokers in the US save time by automating quote responses, scheduling, and tracking. Our secret sauce is our ability to intelligently read data from an inbox and write it directly into our customer's Transportation Management Systems (TMS).

Here is the reality: Our product is only as good as our integrations. If we can't reliably read from and write to a customer's legacy TMS, the AI can't do its job.

We are looking for an Integration Engineer to join our team and help build and maintain the connectivity layer of our platform. You will be responsible for shipping reliable TMS and third-party integrations quickly, without sacrificing stability. You'll work alongside a small, tight-knit engineering team where everyone presents their work daily and collaborates closely.

How We Work (The AI Balance)

We believe in using modern tools to move fast. We want you to use AI coding assistants (like Cursor) to accelerate boilerplate and implementation.

However, we need you to be paranoid. AI makes mistakes. In the logistics industry, a bad API call can result in a truck showing up at the wrong warehouse or a broker losing thousands of dollars. We need an engineer who uses AI to speed up, but uses their experience to vigorously test, debug, and verify every line of code before it hits production.

Roles and Responsibilities

• Build & Maintain Integrations: Design and implement robust integrations with various TMS platforms (e.g., McLeod, Aljex, Turvo, Tai, Revenova) and third-party logistics tools. You will work primarily in Go.
• Reverse Engineering & Creative Problem-Solving: Sometimes there are no public docs. You must be comfortable inspecting network traffic in the browser, identifying internal API calls, and building scrapers to get the job done when standard APIs fail. We value engineers who think beyond official documentation and find creative paths to make integrations work.
• End-to-End Verification: A "200 OK" status is not the definition of success. Success is when the data actually appears in the customer's TMS exactly as they expect it. You will build testing patterns that verify the visual final state of the data in the target system, not just the successful transmission of the request.
• Communicate Clearly and Often: This is just as important as writing good code. You will present your progress and blockers every day during our Daily Standup. You will write clear updates in Linear tickets and Slack. When you're stuck — whether it's broken credentials, a weird API endpoint timing out, or complicated TMS logic you need to replicate to pass validation — we expect you to flag it clearly and quickly so the team can help.
• Collaborate Across the Team: You'll work closely with other engineers on shared codebases, review PRs, and contribute to architectural discussions. We're a small team, so everyone's input matters.
• Customer-Facing Communication (Bonus): Ideally, you're someone who can hop on a call with a customer or integration partner and explain how we're building an integration, what we need from their side, and think outside the box to support their use case.

Qualifications

• 3-5+ years of software engineering experience, with a strong focus on backend systems and API integrations.
• Strong proficiency in Go. (We are a Go shop. If you are a master of Python/Java and can learn Go quickly, let's talk, but Go experience is strongly preferred).
• Scraping & Browser Automation: Experience with tools like Selenium, Playwright, or AI-driven browser tools like Stagehand. You know how to handle dynamic content and complex DOMs.
• Excellent Communication Skills: This is non-negotiable. You need to be able to:
  • Write clear daily standup updates summarizing what you're working on, your priorities, and where you need help.
  • Write detailed, well-structured Linear tickets and Slack messages.
  • Articulate technical blockers clearly — e.g., "This integration isn't working because the API endpoint returns a 403 after their session token expires every 15 minutes."
  • Collaborate effectively with other engineers, including giving and receiving code review feedback.
• Experience with AI Coding Tools: You are comfortable using tools like Cursor to write code faster, but you have the discipline to verify the output rigorously.