> Markdown version of [/jobs/ext/1494565-technical-program-manager](https://www.wearedevelopers.com/jobs/ext/1494565-technical-program-manager). 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). --- # Technical Program Manager - **Company:** Nexus - **Location:** Atlanta, GA, United States - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** RAID, Issue Tracking Systems - **Published:** July 30, 2026 - **Apply:** https://www.indeed.com/viewjob?jk=bbcfe10352d8fc1b ## About the Role * 5-8 years in a customer-facing solution delivery, consulting, or forward-deployed role: Forward Deployed Engineer, Engagement Manager (consulting or product), Solutions Architect with delivery scope, strategic-level Technical Account Manager, Customer Engineering Lead, Implementation Lead, or equivalent * Operationally rigorous. Strong track record of delivering against customer needs - not activity-shaped ("I ran the program") but outcome-shaped ("the customer got X and here's specifically how I made it land"), * A collaborative team culture built on curiosity and respect * Challenging work where your contributions clearly matter * A leadership team that invests in learning and development * The opportunity to work at the intersection of cloud, data, and AI innovation, If this role sounds like a great fit - or even close to one - we'd love to hear from you. We know that no candidate checks every single box, and we're excited to meet people who bring curiosity, talent, and a desire to build meaningful work together. ## Description This is the person who, from the moment a customer signs, owns whether NX1 delivers for them. Not a project manager who tracks tickets. Not a CSM who runs QBRs. This is the delivery and technical operations owner at a portfolio of NX1's strategic accounts. Solution delivery is the operative phrase. The work is: understand the customer's actual business problem, translate it into the requirements the NX1 platform and engineering team will solve for, design the engagement around that solution, and drive it to ground until the customer is winning. Everything else - program mechanics, executive presence, margin, documentation - is in service of that solution landing. You are the buck-stops-here owner for whether NX1 delivers: the rollout program, the solution architecture and roadmap commitments, the documentation surface, the customer health signal at the engineering level, the margin against the engagement, and the loop back into engineering when the platform needs to evolve. What You'll Own Account Ownership, Delivery, and Gross Margin (the headline) * A portfolio of 2-4 strategic NX1 accounts, $5-10M each in delivery / managed services revenue * Gross margin management for the portfolio. You own the unit economics: cost-to-serve per account, scope discipline, hero-engineer-attrition risk, custom work that doesn't generalize. Margin is not finance's job to track - it's yours to manage, with finance providing the books * The P&L for those accounts - drive against deliverables AND against gross margin; surface risk on both before it's a number on the dashboard * The customer-side executive relationship: their VP of Data / CDO / CTO knows you by name and treats you as a peer, not a vendor * Renewal and expansion strategy, in partnership with the CRO - you don't carry quota, but you shape the conditions under which the customer grows Program & Delivery Operations * Stand up the delivery program on day 1 of a new engagement: roadmap, milestones, dependencies, governance, communication cadence * Run the weekly operating rhythm - internal stand-ups, customer syncs, exec readouts, escalation reviews - and build the artifacts that keep them grounded in reality, not theater * Own the documentation surface for each engagement: program plan, decision log, RAID register, exec status, runbooks, the customer-facing roadmap view * Linear and Notion are your primary instruments; you will design how they're used for your portfolio, not inherit a template someone else built Technical Quarterbacking & Requirements Translation * Own the bidirectional translation between the customer's business problem and NX1's engineering reality - surface the right requirements into the org, surface engineering trade-offs back to the customer, without distorting either side * This is the craft of the role: customers don't hand you a requirements doc that's correct. You build it together, in conversation, by knowing what to ask and what to push back on * Pull in Solution Architects when the work needs architecture depth; pull in FDEs / engineers when the work needs to be built * Hold the line on technical commitments: what's in scope, what's a roadmap ask, what's a one-off custom build the engagement can't absorb * Be the person who reads the architecture doc, asks the sharp question, and writes the one-page summary the customer's CTO actually reads - and the one-page brief the engineering team uses to scope the work Customer Health & Outcomes * Define what "winning" looks like for each customer in writing within the first 60 days of an engagement - and instrument it * Build the customer-health signal that catches problems 60 days before they become escalations: usage trajectory, executive sentiment, milestone slippage, support ticket pattern, roadmap dependency drift * Run quarterly business reviews that the customer's exec team treats as the most useful meeting of the quarter * Convert customer pain back into product roadmap input - and close the loop when it lands ## Related Videos - [Recruiting in 2025: Will AI Help or Take Over?](https://www.wearedevelopers.com/videos/1301-recruiting-in-2025-will-ai-help-or-take-over) - [The user in the eye of the Cargo1492 storm](https://www.wearedevelopers.com/videos/96-the-user-in-the-eye-of-the-cargo1492-storm) - [7 tips for releasing on a Friday afternoon: YouTrack to the rescue](https://www.wearedevelopers.com/videos/204-7-tips-for-releasing-on-a-friday-afternoon-youtrack-to-the-rescue) - [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) - [Empowering Thousands of Developers: Our Journey to an Internal Developer Platform](https://www.wearedevelopers.com/videos/1519-empowering-thousands-of-developers-our-journey-to-an-internal-developer-platform) - [Startup Presentation: Dealing with the bug Mafia](https://www.wearedevelopers.com/videos/1175-startup-presentation-dealing-with-the-bug-mafia) ## Related Articles - [Should Tech Managers Be Developers First? Pros and Cons](https://www.wearedevelopers.com/magazine/327-should-tech-managers-be-developers-first-pros-and-cons) - [From developer to manager – what does it take to become an engineering manager?](https://www.wearedevelopers.com/magazine/42-from-developer-to-manager-what-does-it-take-to-become-an-engineering-manager) - [Navigating the AI Shift](https://www.wearedevelopers.com/magazine/629-navigating-the-ai-shift) - [What Makes WeAreDevelopers World Congress Different From Every Other Tech Event?](https://www.wearedevelopers.com/magazine/701-what-makes-wearedevelopers-world-congress-different-from-every-other-tech-event) - [Best US AI Conferences for CTOs in 2026: Build vs. Buy, Vendor Evaluation, and Peer Intelligence](https://www.wearedevelopers.com/magazine/736-best-us-ai-conferences-for-ctos-in-2026-build-vs-buy-vendor-evaluation-and-peer-intelligence) - [What Are The Top Skills Required For Azure Developers?](https://www.wearedevelopers.com/magazine/77-what-are-the-top-skills-required-for-azure-developers)