--- title: "Why We're Hiring — and What That Says About Where PE Operations Stand Right Now" description: "Five open roles. Here's the kind of work driving the growth, and the kind of people we're looking for to do it." lang: en json-ld: | [ { "@context": "https://schema.org", "@type": "Organization", "name": "Craft Digital", "url": "https://craft-digital-systems.lovable.app/", "logo": "https://craft-digital-systems.lovable.app/og-image.png", "description": "Custom software, AI, automation, and operational infrastructure for mid-market operators and their investors." }, { "@context": "https://schema.org", "@type": "WebSite", "name": "Craft Digital", "url": "https://craft-digital-systems.lovable.app/" }, { "@context": "https://schema.org", "@type": "Article", "headline": "Why We're Hiring — and What That Says About Where PE Operations Stand Right Now", "description": "Five open roles. Here's the kind of work driving the growth, and the kind of people we're looking for to do it.", "image": "https://ndgfftdthvrwtbdbbswj.supabase.co/storage/v1/object/public/blog-assets/covers/CRAFT HIRING.png", "datePublished": "2026-05-21T17:53:19.329+00:00", "author": { "@type": "Person", "name": "Craft Digital" }, "publisher": { "@type": "Organization", "name": "Craft Digital", "logo": { "@type": "ImageObject", "url": "https://craft-digital-systems.lovable.app/og-image.png" } }, "mainEntityOfPage": { "@type": "WebPage", "@id": "https://craft-digital-systems.lovable.app/blog/why-we-re-hiring-and-what-that-says-about-where-pe-operations-stand-right-now" } } ] --- [![Craft Digital](/__l5e/assets-v1/bc7a6fac-7a94-4caa-a751-a7e463885a50/craft-logo-full-color.svg) ](/) [Solutions](/solutions)[Custom Development](/custom-development)[Case Studies](/work)[About](/about) Book a Call Menu [Back to Insights](/blog) # Why We're Hiring — and What That Says About Where PE Operations Stand Right Now Craft Digital / May 21, 2026 / 7 min read ![Why We're Hiring — and What That Says About Where PE Operations Stand Right Now]() ## Why We're Hiring — and What That Says About Where PE Operations Stand Right Now _Five open roles. Here's the kind of work driving the growth, and the kind of people we're looking for to do it._ _~5 min read_ We just rebranded. New site, new identity, and — more importantly — a sharper definition of who we build for. After a few years of running production AI work across a mix of client types, we made the call to point Craft squarely at PE-backed portfolio companies. That's where the operational problems we solve are most acute, the timelines are tightest, and the math at exit works hardest in the client's favor. The decision to narrow cost us some breadth and earned us something more useful in return: the right kind of inbound, more of it, and faster than we expected. The pipeline that's followed has outgrown what our current team can absorb without compromising how we build. So we're hiring. Five roles, all open right now — three on the engineering side, two on client operations. The conclusion is one we've watched form across dozens of conversations with operating partners over the last eighteen months: AI initiatives that don't produce measurable EBITDA lift inside a hold period aren't worth the management attention they consume. That's not a controversial position anymore. MIT's 2025 _State of AI in Business_ found that 95% of generative AI pilots produce no measurable return, and that fewer than 5% reach production. McKinsey's most recent _State of AI_ puts the share of organizations attributing more than 5% of EBIT to AI at roughly 6%. The pattern is consistent: a lot of activity, very little that shows up in the P&L. What's changing is the response. A year ago, the question was whether to run pilots. Now the question is what to do instead. And the answer most sponsors are quietly converging on is that the AI work worth funding inside a portco looks nothing like the demos. It looks like operational plumbing. Speed-to-lead automation that doesn't depend on a rep remembering to follow up. CRM data that's actually trustworthy at QofE time. Sales processes that don't vary by who happens to be on the call. Acquisition integrations that don't take six quarters to clean up. That work is unglamorous on the surface. It also happens to be the work that moves the number that matters most. We've written before about why operational efficiency is the right entry point for AI work in a portco, but the short version is worth repeating: cost-side improvements are immediate, ops is universal across a portfolio in a way that sales improvements aren't, and the math at exit is unforgiving in favor of EBITDA. A $1M reduction in operational cost in a portco bought at 8x EBITDA is roughly $8M of equity value at exit. Not $1M. Sponsors who internalize that math tend to move quickly, because the urgency is no longer abstract. That urgency is what's putting us in the position of needing to hire. ## What we actually build We don't ship templates. We don't have a product. We don't have a productized "AI for portcos" package that gets dropped into a portco's environment with a few configuration changes and a kickoff slide. We've thought about whether to build one — periodically and seriously — and we keep arriving at the same conclusion: the work doesn't generalize the way a product would need it to. Every portco we walk into has its own ecosystem of inherited tooling, brittle handoffs, partial automations from previous initiatives, and a layer of operational debt that nobody has had time to chart. The execution gap isn't located in the same place from one company to the next. In one, it's a CRM full of incomplete contact data and a sales team that's developed elaborate workarounds to compensate. In another, it's a lead pipeline where the average first-touch time is fourteen hours and the marketing team has no idea. In a third, it's a recent acquisition whose data still lives in a different ERP and whose people are still running on the old playbook. A template can't fix any of that. A team that sits with the client, maps the actual system, and builds against the constraints they find can. That's the work we do, across all three of the layers we typically operate in — demand and customer capture, sales execution and accountability, and the operational infrastructure underneath both. ## The kind of people we're looking for The roles we have open reflect how the work actually gets done. On the engineering side, we're hiring a Lead Engineer, a Software Engineer, and a Junior Engineer. None of these are ticket-shop roles. The senior end of the bench is for engineers who can sit in a room with a client, see the full system, make the architecture calls, and own a build from kickoff through production — not implementers waiting for a spec. The mid-level role is for engineers who've been senior-adjacent for a while and want the autonomy and ownership that title implies but haven't been given the room to exercise it. The junior role is for someone early in their career who's shipped a few real things and is ready to apply what they know with senior guidance and unusually good tooling around them. The throughline across all three: we care about whether the system still runs in six months, not whether it shipped this sprint. That orientation tends to filter out a particular kind of engineer, which is the point. On the client operations side, we're hiring an Account Director and an Account Manager. These aren't account-management roles in the conventional sense — minding the inbox, taking notes, presenting a QBR deck once a quarter. The work is closer to embedded operational partnership. The job is to sit with the client, understand the real operational problem behind what they're asking for, translate that into something the engineering team can build against, and then keep the communication tight enough that the build doesn't drift from what the client actually needs. That requires a particular kind of person — calm under pressure, deeply organized, good with founders and with frustrated operators inside a portco, and able to hold the line on scope without becoming a friction point. The common thread across all five roles is the same trait we look for in everyone we work with: a preference for staying close to the problem, not the abstraction. Dedicated systems take more thought than configured templates, and the people who build them well tend to be the ones who'd be uncomfortable doing it any other way. ## What this means if you're on the other side of the table If you're a sponsor or operating partner reading this and wondering how to put the kind of capacity we're building toward your portfolio, the practical answer is that our calendar is opening up in a way it hasn't in the last two quarters. We're hiring specifically because we don't want to compromise the work — and because we'd rather grow the team than start turning down engagements that fit what we do well. If you're an engineer or a client operator who recognized yourself somewhere in the description above, the open roles are listed on our careers page and we read every application that comes in. The growth isn't a goal in itself. It's the byproduct of doing the work well in a market that's gotten quieter about AI hype and louder about AI results. We'd like to keep doing the work well. That's why we're hiring. Share this article Next step ## Ready to architect _your next system?_ [Schedule a Discovery Call](https://cal.com/craft-clinton/30-min-discovery-call-craft-digital?utm_source=craftdigital&utm_medium=website&utm_campaign=site-rebuild&utm_content=blog-post) [![Craft Digital](/__l5e/assets-v1/b959f9c9-7914-488d-b4ec-368b171a61e0/craft-logo-white.svg) ](/) We build AI software that replaces spreadsheets, disconnected systems, and manual work. [Start a conversation ](/contact) Solutions - [Self-Optimizing Website](/solutions#self-optimizing-website) - [SEO + AI Search](/solutions#seo-ai-search) - [Outreach System](/solutions#outreach-system) - [Intelligent Call System](/solutions#intelligent-call-system) - [Business Intelligence](/solutions#business-intelligence) - [Custom Development](/custom-development) Who We Serve - [Custom Development](/custom-development) - [Getting Started](/getting-started) - [Case Studies](/work) - [About](/about) - [Contact](/contact) Proof & Resources - [Case Studies](/work) - [Insights](/blog) Company - [About](/about) - [Contact](/contact) - Los Angeles California - Fort Collins Colorado [©](/msa) 2026 Craft Digital AI LLC [Privacy Policy](/privacy)[Terms of Service](/terms)[Cookie Policy](/cookies) [](https://www.linkedin.com/company/craftdigital-ai)[](https://www.instagram.com/craftdigital.ai/)