Software Platform Integration Lead

About the role

VADD Construction Services delivers mission-critical data center and infrastructure projects as an EPC contractor, owner's representative, engineer, estimator and scheduler. Over the past year we built about fifteen custom software tools using AI-assisted development. About half are in production use on live projects. The rest are field-tested, in alpha, or in the requirements stage. Your job is to turn these prototypes into one production platform that people across VADD use.

About 95% of your code will be written with AI agents such as Claude Code. You need to read, debug and correct what the agents produce, and know when to write the code yourself. The other half of the job is people. Nobody at VADD will be ordered to use your tools, so you will earn adoption one user at a time, on job sites and in offices.

What you will do

• Own production: Take over the existing tools and keep them running. Manage hosting, including cloud VMs, on-site single-board computers, domains, TLS, zero-trust access, backups and monitoring. Set up users, roles, permissions and AI API key controls. Close out pre-release items and keep a status log of every tool.
• Integrate: Build shared services for users, badges, projects and jobs so the tools work behind one login. Remove duplicate stacks. Connect tools where it saves people work, such as schedule to estimate or field capture to reports.
• Build with AI agents: Turn short requirements outlines from engineers into working alphas. Ship each one with a white paper, a user guide, a license review and a feedback channel. Use only packages whose licenses allow free commercial use.
• Drive adoption: Meet with group leaders and entry-level staff on site to learn what they need. Run a weekly feedback review, turn the feedback into releases, and follow up until the tools replace the spreadsheets.
• Report: Meet regularly with the CEO, COO and VPs on goals and progress.

The current stack

Most tools run on a lightweight Python server with a JSON document store, a browser front end, and a commercial LLM API. Others include a low-code module, Android apps, and embedded devices such as scanners, tablets, cameras and per-job servers. Tools span field operations, engineering and design, project controls and finance, reporting, and launchers. We also have an AI-first construction management platform in the requirements phase. You will coordinate device provisioning with our embedded-systems group.

First-year goals: one login and user directory, shared project and job records, connected schedule, estimate and drawing tools, a feedback channel in every tool, and a CM platform built from these pieces. You may build a team or work as an individual contributor.

Requirements

Technical

• S. in Computer Science or a closely related degree with a CS core
• Working knowledge of networking (routing, VLANs, VPNs, DNS, TLS), security (access control, secrets, hardening), relational and document databases, and software integration (REST APIs, auth, webhooks)
• Writes code in at least one mainstream language (Python preferred) and reads several
• Has built real software with AI coding agents
• Comfortable administering Linux servers and VMs
  
  

Hands-on background (one required)

Raised on a farm; construction site work in any role; mechanic or trade work; serious home-improvement experience; or exposure to estimating, scheduling, job costing, bookkeeping, lending or finance.

People (one required)

Sales experience, competitive high school or college sports, or raised on a farm.

Preferred

• Customer-service work (server, bartender, retail, call center)
• Android (Kotlin) or embedded experience (ESP32, Raspberry Pi, Arduino)
• Low-code platforms (Xano, Adalo) and migrating off them
• MS Project, Primavera P6, estimating, or Procore
• Cloudflare, Azure or similar cloud administration
• Has shipped software people outside the team used

Travel

About 50% for the first six months, then about 25%. You will travel for job site visits, in-person sessions with group leaders, and a few days each month with the CEO in Steamboat Springs, CO.

First six months

• Days 1 to 30: Learn every tool's code and documentation, set up dev environments, visit two job sites, and hold your first CEO session.
• Days 31 to 90: Take over production hosting and access, close pre-release items, publish the product map, and meet with every group leader.
• Days 91 to 180: Ship shared login and project services and the first integrations, run the weekly feedback review on a steady cadence, and show adoption by named users on named projects.