Sign in to view Joseph’s full profile
or
New to LinkedIn? Join now
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
Sign in to view Joseph’s full profile
or
New to LinkedIn? Join now
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
Boulder, Colorado, United States
Sign in to view Joseph’s full profile
Joseph can introduce you to 10+ people at Actabl
or
New to LinkedIn? Join now
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
2K followers
500+ connections
Sign in to view Joseph’s full profile
or
New to LinkedIn? Join now
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
View mutual connections with Joseph
Joseph can introduce you to 10+ people at Actabl
or
New to LinkedIn? Join now
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
View mutual connections with Joseph
or
New to LinkedIn? Join now
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
Sign in to view Joseph’s full profile
or
New to LinkedIn? Join now
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
Activity
2K followers
-
Joseph Benjamin shared thisExcited to share that I’ve joined Actabl as Chief Technology Officer. Actabl is uniting four powerful hospitality platforms—ProfitSword, Hotel Effectiveness, ALICE, and Transcendent—into one solution to help hotels simplify complexity and unlock new value. The hospitality industry is going through big changes, and I’m looking forward to working with this talented team to drive innovation, integration, and impact for operators worldwide. https://lnkd.in/gkrBUAmaActabl Appoints Joseph Benjamin as Chief Technology OfficerActabl Appoints Joseph Benjamin as Chief Technology Officer
-
Joseph Benjamin shared thisAs we continue to innovate at iCIMS, we ask ourselves: How can we expand our GenAI capabilities? How can we bridge the gap between internal collaboration and communication among hiring managers? What are the ways we can enhance our data insights and reports to help our customers dive deeper into campaign performance and KPIs? All these questions and all the answers are in the iCIMS 2024 Fall release. We've listened to our customer feedback and delivered a product release packed with new innovations and capabilities to synchronize communications between internal TA teams, ensuring their candidate experience is best-in-class in today’s competitive landscape. I am excited to see how our technology and products will continue to transform our customers' talent acquisition processes and build winning teams. There’s a lot to unpack. Learn more in the full announcement here:iCIMS Expands GenAI and Internal Collaboration Capabilities to Bridge the Communication Gap between Hiring Teams and Candidates | iCIMS | The Leading Cloud Recruiting SoftwareiCIMS Expands GenAI and Internal Collaboration Capabilities to Bridge the Communication Gap between Hiring Teams and Candidates | iCIMS | The Leading Cloud Recruiting Software
-
Joseph Benjamin reposted thisJoseph Benjamin reposted thisHow can you build better candidate experiences? How are recruiters tapping into the power of AI? What are candidates preferred form of communication? What exactly do candidates want right now? 🤔 All these questions (plus more!) and all the answers: The iCIMS 2024 Talent Experience report, now live! This report examines the state of hiring and candidate expectations, how talent acquisition teams are building great experience and packed with best practices from leading brands and tips from industry leaders on how to become candidate experience builders 💪 Here are a few stats that took me by surprise: 📊64% of TA pros would like to see even more AI adopted in the recruiting and TA process 📊 51% of people would be less likely to be a consumer of a brand following a negative application or interview experience 📊69% of people expect the job application process from applying to receiving an offer letter, to take three weeks or less There’s data and findings from just about everyone in this report. iCIMS chief people officer, Laura Coccaro and global head of workforce and customer insights, Rhea Moss break down top highlights below 🔽 You can view the full report here: https://okt.to/PjYiIf
-
Joseph Benjamin reposted thisJoseph Benjamin reposted thisI want to recognize the many iCIMS team members who delivered our latest product release and are continuously bringing innovation to our customers around the world. We are hyper-focused on listening to feedback from our customer community to ensure they have the best experience and are achieving better business outcomes with iCIMS. I am proud to share that more than 20 enhancements were voted on by customers. A few of our new capabilities include: -Building stronger candidate engagement at scale with our award-winning Candidate Experience Management, iCIMS CXM -Enhancing internal hiring performance with a new analytics dashboard within iCIMS Opportunity Marketplace -Driving recruiting productivity with new bulk action items integrated within the iCIMS ATS Our customers help us shape the roadmap of our award-winning AI-powered products. Check out our latest enhancements: https://okt.to/XBrJg1
-
Joseph Benjamin reposted thisJoseph Benjamin reposted thisHow is the rise of AI in the workplace affecting job seekers’ desire to secure a tech job? Are candidates applying to AI-based jobs? Are people applying to tech jobs evenly across industries? These are just some of the questions answered in the iCIMS Workforce August Insights Report, which explores the state of hiring for tech jobs right now. We also surveyed 1,000 US adults to understand candidates’ appetite for AI jobs and whether they’re upping their digital skills to stay relevant in the 21st-century workplace. Each month, the iCIMS Insights Workforce Report provides the latest labor market insights that help employers make data-driven decisions to drive business forward. Are you tapping into the power of data to inform your strategy? Check out this month's report that explores: 🖥️ The number of people who applied to jobs that either involve building AI or in which AI plays a significant role. 💻 The number of workers who say that economic uncertainty and the rise of AI in the workplace would not affect their desire to secure a job in tech. 💻The number of applicants that applied for tech-based roles in July 💻 How EagleView Technologies went up against some of the biggest names in tech to recruit candidates with niche skills and saw a boost in applications after partnering with iCIMS Discover all top highlights, findings, and data in our full report here ➡️ https://lnkd.in/edh2Hnpp #workforce #AI #talent #labormarket #jobmarketactivity
-
Joseph Benjamin reposted thisJoseph Benjamin reposted thisI’m excited to share that the iCIMS 2024 Summer Release is here! In today’s competitive hiring landscape, the candidate experience is everything. That’s why we’re happy to deliver new innovations and capabilities that support global talent acquisition teams develop stronger candidate connections and more efficient recruiting processes. The company's latest product release empowers TA professionals to automate candidate engagement at scale with a next-gen CRM, accelerate high-volume hiring with new bulk actions and improved HR tech integrations, and strengthen internal recruiting with new reporting and analytics. These new enhancements help iCIMS customers deliver streamlined hiring that improves both the recruiter and candidate experience. I look forward to seeing how the enhancements in our Summer Release help our customer community build stronger connections with candidates and expand their global reach. Great job to the many cross-functional teams that brought this release across the finish line! Comment below what you’re most excited about and learn more here: https://lnkd.in/gSp8Cpte
-
Joseph Benjamin shared thisExcited to share that iCIMS Talent Cloud AI has been recognized in the 2024 AI Breakthrough Awards for “AI Solution of the Year.” 🏆 This year, the AI Breakthrough Awards program received over 5,000+ submissions and iCIMS was chosen alongside the most innovative companies, technologies, and products in the artificial intelligence industry. As AI continues to prove significant in the world of HR, choosing the right technology partner - that’s not only the best 😏 - but also is a trusted vendor in the space will help your organizations move forward in this competitive market. Since joining iCIMS a few months ago and working closely with our product and technology teams it’s clear that our commitment to delivering reliable and responsible AI-powered products is deep rooted in our strong product vision. Across the talent acquisition lifecycle, the iCIMS Talent Cloud AI is embedded in our platform (no integration required) helps our customers attract and nurture top talent with boosted efficiencies and productivity at scale. Go iCIMS! Thanks for recognizing iCIMS, AI Breakthrough Awards. Check it out here: https://lnkd.in/gTDEeyWU
-
Joseph Benjamin posted thisIt is with mixed emotions that I bid farewell to the incredible team at Behavox as I embark on my next adventure. I am honored and so proud of all that we accomplished together. What an amazing, talented and committed group of people! I am confident that I leave the team, the technology and our products in in great hands to build the next exciting chapter. It has been an amazing journey filled with invaluable learnings and experiences. Special thanks to Erkin Adylov for his vision, his unwavering confidence and leadership. I will be cheering you on from the sidelines, available to help, and will do my best to stay in touch. Thank You!
-
Joseph Benjamin liked thisJoseph Benjamin liked thisI’m excited to share that I’ve started my next chapter as VP of Engineering for the Process Manufacturing division at CAI Software, LLC! I’m looking forward to working with great people, driving innovation and scaling our engineering excellence in this space. I want to share a massive thank you to my team at iCIMS. It has been an incredible 10 years of learning, growth, and collaboration. There are far too many people to name individually, I am deeply grateful for my colleagues, leaders and mentors who made my decade there so rewarding.
-
Joseph Benjamin liked thisJoseph Benjamin liked thisThe guest experience is often determined by what happens after plans change. Dinner reservations move. A tour time shifts. Transportation runs late. Every hotel concierge knows the drill. Now someone is recreating an itinerary and trying to get it to the guest before they show up at the wrong place at the wrong time. Today, we’re launching Digital Itineraries in Alice Guest Services to fix that. Instead of static PDFs or printed packets, hotel teams now maintain one live itinerary per guest. Update it once in Alice, and the guest sees the latest version instantly through a secure link. No app download. No reprint. No chasing people down. Guests can tap into directions, phone numbers, and activity details directly from the itinerary. It actually becomes useful throughout the stay, rather than something they glance at once and leave on the nightstand. A few things to know about Digital Itineraries in Alice: • Custom-branded with your hotel or brand’s logo, colors, and fonts • Shared via email or SMS in seconds • Auto-expiration and guest authentication built in • Less paper waste This builds on Alice’s concierge solution, rated #1 by hoteliers in the 2026 HotelTechReport.com Hotel Tech Awards. We’re doubling down on the tools that help hotel teams spend less time managing logistics and more time delivering great service. Full details in the press release linked below. Tag someone in the comments who you think would enjoy using this!
-
Joseph Benjamin liked thisJoseph Benjamin liked thisStanding room only for this panel of world class IT leaders here at NoVacancy Hotel + Accommodation Industry Expo London. Enjoyed hearing about their career journeys and the skills required to be a tech leader in hospitality. Barry Thomas, CHTP Liz Dixon Andrew Evers Gavin A.
-
Joseph Benjamin liked thisJoseph Benjamin liked thisI like Steven Moore's Five Core Tenets of AI 1. People first: “AI needs to augment, not replace.” 2. Fits into an existing workflow: “Minimize forced process changes.” 3. Human-in-the-loop: “Make sure that humans still have the ability to have the final say.” 4. Iterative: “Don’t expect it to be an easy button that solves everything right away,” and 5. ROI-driven: “Make sure it is tied to a specific metric you are trying to drive, not just for novelty’s sake. Ignoring any one of these will likely lead to disappointing results.”How AI is affecting hotel management and operationsHow AI is affecting hotel management and operations
-
Joseph Benjamin liked thisJoseph Benjamin liked thisQ4 2025 delivered a reality check – that’s according to our latest https://hubs.li/Q043SWF60 report – out today! ➡️ ADR was down 0.9%. ➡️ RevPAR fell 9.6% quarter over quarter. ➡️ GOP% followed, dropping from 39.3% to 36.0%. For the full year, ADR declined 2.5% to $180.92. RevPAR fell 6.3% to $118.26. Yet GOP% improved 1.1 points to 38.3%. 📉 Revenue softened. Margin discipline improved. 📈 👉 Read the full Q4 2025 Profit Report for the complete breakdown of ADR, RevPAR, GOP%, TrevPAR, as well as chain scale and regional trends: https://hubs.li/Q043SVRK0 #HotelData #HotelRevPAR #TrevPAR #HotelProfit
-
Joseph Benjamin liked thisJoseph Benjamin liked thisEileen Gu set the record straight. 👏 At #MilanoCortina2026, the 22-year-old added two silver medals in freestyle skiing, bringing her total to five Olympic medals and becoming the most decorated female freeskier of all time. When a reporter asked whether she saw her results as “two silvers gained or two golds lost,” she answered with poise and the confidence of a true champion.
-
Joseph Benjamin liked thisJoseph Benjamin liked this𝗔𝗜-𝗣𝗼𝘄𝗲𝗿𝗲𝗱 𝗣𝗿𝗼𝗱𝘂𝗰𝘁 𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗺𝗲𝗻𝘁: 𝗠𝗮𝗸𝗶𝗻𝗴 𝗥𝗲𝗾𝘂𝗶𝗿𝗲𝗺𝗲𝗻𝘁𝘀 𝗖𝗿𝗶𝘀𝗽 𝗮𝗻𝗱 𝗘𝗹𝗶𝗺𝗶𝗻𝗮𝘁𝗶𝗻𝗴 𝗔𝗜 𝗦𝗹𝗼𝗽 A few days ago, I found myself debating what actually changed once AI became capable of writing production-level code. The answer was simple: requirements became the new bottleneck. Since then, the team I lead, 10 engineers, mostly senior, has switched to coding almost exclusively through AI. It was the fastest and most radical shift I have seen in my career! The trigger was a real example. One engineer implemented an epic-sized, cross-functional feature across ML, backend, and frontend to achieve functional completeness in a week, working alone. That was not luck. The difference was a carefully written design document and an implementation plan, stored alongside the code as Markdown files. The AI executed strictly against that plan. That discipline defined the success. We had seen this pattern before but never adopted it systematically. That changed when we discovered a structured approach to working with agentic AI: the GitHub Spec-Kit framework. It enforces a workflow that improves output quality by structuring thinking before implementation. https://lnkd.in/gRR8M6Vp The core idea is simple. 𝗔𝗜 𝗱𝗼𝗲𝘀 𝗻𝗼𝘁 𝘁𝗵𝗶𝗻𝗸. It amplifies existing human thinking. The framework itself is a set of agentic skills that force a structured flow. Each step is an explicit CLI command. That structure prevents AI slop. The flow is easy to scale: Define the foundation with /𝘴𝘱𝘦𝘤𝘬𝘪𝘵.𝘤𝘰𝘯𝘴𝘵𝘪𝘵𝘶𝘵𝘪𝘰𝘯. Write precise requirements with /𝘴𝘱𝘦𝘤𝘬𝘪𝘵.𝘴𝘱𝘦𝘤𝘪𝘧𝘺. Design the system with /𝘴𝘱𝘦𝘤𝘬𝘪𝘵.𝘱𝘭𝘢𝘯. Break it into concrete technical work with /𝘴𝘱𝘦𝘤𝘬𝘪𝘵.𝘵𝘢𝘴𝘬𝘴. Validate consistency with /𝘴𝘱𝘦𝘤𝘬𝘪𝘵.𝘢𝘯𝘢𝘭𝘺𝘻𝘦. Each step enforces clarity before execution. For details, refer to the documentation or simply try it. At the end, you will have extensive written artefacts living next to the code. Reading and polishing this is a tedious job for senior engineers and product managers; it is not easy. 𝗧𝗵𝗲 𝗺𝗼𝗿𝗲 𝗽𝗿𝗲𝗰𝗶𝘀𝗲𝗹𝘆 𝘁𝗵𝗲𝘀𝗲 𝗮𝗿𝘁𝗲𝗳𝗮𝗰𝘁𝘀 𝗰𝗮𝗽𝘁𝘂𝗿𝗲 𝗶𝗻𝘁𝗲𝗻𝘁, 𝗰𝗼𝗻𝘀𝘁𝗿𝗮𝗶𝗻𝘁𝘀, 𝗮𝗻𝗱 𝗲𝗱𝗴𝗲 𝗰𝗮𝘀𝗲𝘀, 𝘁𝗵𝗲 𝗯𝗲𝘁𝘁𝗲𝗿 𝘁𝗵𝗲 𝗼𝘂𝘁𝗽𝘂𝘁. AI-generated code quality is directly proportional to input quality. Once the groundwork is done, only one command remains. Execute the tasks with /𝘴𝘱𝘦𝘤𝘬𝘪𝘵.𝘪𝘮𝘱𝘭𝘦𝘮𝘦𝘯𝘵. That is where agentic AI truly shines. Unfortunately, the LinkedIn post size limit forces me to stop here. I will share key findings in the next post. Stay tuned! For now, I will just say this: the results are strong. The technical items we implemented using this approach exceeded expectations! Cheers! PS A huge kudos to Victoria Antonova, who introduced me to this framework in the first place. #ai #programming #softwareengineeringGitHub - github/spec-kit: 💫 Toolkit to help you get started with Spec-Driven DevelopmentGitHub - github/spec-kit: 💫 Toolkit to help you get started with Spec-Driven Development
-
Joseph Benjamin liked thisJoseph Benjamin liked thisFeb 11th 2001 - exactly 25 years ago - was the first day of a 3-day meeting at the Snowbird ski resort in Utah that gave birth to the Manifesto for Agile Software Development. Like all important documents, most folks who think they know what it says don't appear to have actually read it. There's no mention of "sprints", or "story points", or "user stories", or "build pipelines" or "Kanban boards" or any of the other details of specific Agile methodologies. The Manifesto isn't a "how-to" guide. It's a "why-to" guide. It lays out a set of values and principles for teams who wish to be more responsive to changing user and business needs, through continuous learning and adaptation in a highly people-centric - and especially customer-centric - process. On the front page of the manifesto's website, it states: "We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: - Individuals and interactions over processes and tools - Working software over comprehensive documentation - Customer collaboration over contract negotiation - Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more." The values and principles of Agile Software Development describe what it is like to *be* agile (with a small 'a'). We do not "do" agile. We do not "adopt" agile. We do not "implement" agile. We *become* agile. The manifesto itself is, of course, a laudable but compromised attempt to bring multiple iterative and "lightweight" development methodologies - different "brands" - under one banner. One of those brands came to dominate in the minds of software developers. Another came to dominate in the minds of managers and executives, and ultimately came to dominate economically. This was a mistake. "Agile Software Development" is doing software development in an agile way. It's not a management thing. Agile teams are self-organising, because putting decision-making power where (and more importantly, when) decisions need to be made - and therefore understood - is one of the keys to unlocking greater agility. A chain of command almost always becomes a serious bottleneck. The other key message that got lost in translation is the need for strong technical chops. Teams who can't deliver rapidly, reliably and sustainably get micromanaged, and that ends their experiment in agility. Without development teams with strong technical *discipline* who are empowered to make decisions, Agile Software Development becomes little more than Agility Theatre. And that's the reality for the majority of teams today - command-and-control waterfall development wearing an Agile Halloween costume. I recommend reading the manifesto again (or for the first time). Perhaps do it as a team. Maybe talk about how the values and principles could or are helping, and identify where your organisation might just be play-acting
Experience & Education
-
Actabl
***** ********** *******
-
**********
********* *******
-
******** * ********* ** *******
********* *******
-
********** ** ****** * ******* ******* ** ********
*** undefined undefined
-
-
** ** ********
** undefined
-
View Joseph’s full experience
See their title, tenure and more.
Welcome back
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
New to LinkedIn? Join now
or
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
Recommendations received
2 people have recommended Joseph
Join now to viewView Joseph’s full profile
-
See who you know in common
-
Get introduced
-
Contact Joseph directly
Other similar profiles
-
Jim Restivo
Jim Restivo
DXC Technology | Insurance | AI | Cloud | Platform
8K followersCharleston, SC -
Bashir Agboola DBA, MBA, CHCIO, CDH-E, FACHDM
Bashir Agboola DBA, MBA, CHCIO, CDH-E, FACHDM
Interdym
8K followersNew York City Metropolitan Area -
Jeff Shorts
Jeff Shorts
Strategic Management & Technology Services, LLC.
8K followersLand O' Lakes, FL -
Keith R. Worfolk - MBA, MCIS, CCIO, CISSP, CCISO, CCP
Keith R. Worfolk - MBA, MCIS, CCIO, CISSP, CCISO, CCP
Wavestone
8K followersEvergreen, CO
Explore more posts
-
Anila Augustine
Ascendion • 712 followers
Commerce & Revenue Optimization Today, recommendations are the default in commerce—guests expect relevant options, not generic offers. Onboard is no different. Ascendion helps cruise lines use AI-driven personalization to make it easy for guests to discover, explore, and buy—whether it’s dining, retail, or excursions. With predictive offers and tailored recommendations, every interaction has the potential to increase spend and satisfaction. When commerce feels natural and helpful, it becomes part of the experience, rather than a distraction. Learn more: https://lnkd.in/guDUnmNc #CruiseLine #Ascendion #FutureOfWork #EngineeringAI #DigitalCommerce
23
1 Comment -
Paul Chiusano
Unison Computing • 2K followers
I thought this was a good and very reasonable talk by Eleanor Millman on how to prioritize projects for a platform engineering team: https://lnkd.in/gaYtUHRH A few insights I took from it: - Unlike product features which can be more directly tied to revenue, platform engineering work is a couple steps removed. But that doesn't mean it's unimportant! Far from it, platform engineering projects can make everyone at the company more efficient, able to produce higher quality software, etc. - While "urgency" is always going to be a factor, you don't want to just be putting out fires, you want be able to prioritize work which is "high impact" ... even if that impact isn't felt immediately. - Good rule of thumb: prioritize "highest impact for lowest effort". - The talk has some ideas on what factors to choose for impact, and how to blend them. For instance "speed of development" is one factor, "cloud cost optimization" might be another. The weighting of different impact factors can change over time, depending on the needs of the business. I would say that a lot of companies don't have much methodology here but I can really see the value in codifying it. You can always change the methodology or the weighting if it's spitting out results that don't pass the smell test or you really feel it is leading the company astray. Clarity can give the org more freedom to put resources behind projects that would otherwise never be taken on. When things are unclear, prioritization still happens implicitly, but the decisions tend to be a lot more random and fear-based and the org is worse off as a result.
15
3 Comments -
Aspect Build
2K followers
Tired of long CI builds and rising compute costs? Coda was too. They trialed Aspect Workflows, saw a 10x improvement in build times and a 67% reduction in compute costs, and decided to roll it out more broadly. "We went from having significant limits in CI and tools to where the limits are now just due to our code." — Neal Norwitz, Software Engineer at Coda Read more about the challenges they faced and the results they saw: https://lnkd.in/eA_pwcDQ
5
-
Jellyfish
21K followers
💡 AI doesn’t just change how code is written – it changes expectations and outcomes. In the final section of Jellyfish’s AI Adoption Guide, we explore how expectations for engineering leaders are evolving as AI becomes embedded across the SDLC. Because the organizations pulling ahead are treating AI as a transformation, not a tooling upgrade. Inside, you’ll explore: - Why AI adoption is quickly becoming a leadership mandate, not an option - How to balance ambitious goals with realistic expectations - What cultural investments are required to sustain long-term gains - How data can be used to align executives and engineering teams The teams that win in the AI era won’t just have better tools – they’ll have leaders who know how to guide change. Download today: https://lnkd.in/dut_6WpQ
20
-
Anthropic
3M followers
Spotify's engineering team built a background coding agent with Claude Agent SDK that handles complex migrations across their massive codebase. Engineers describe what they need in plain text—via Slack, even—and the agent takes it from there, running tests and opening pull requests. They're now merging 650+ agent-generated PRs into production each month. Read more about how they built it, and what else Claude is enabling at Spotify: https://lnkd.in/gVhivXu6
4,365
164 Comments -
Mondesir Partners
4 followers
Growth without operational architecture is a liability. Most companies don’t fail because demand disappears. They fail because demand exposes structural weakness. Revenue rises. Complexity multiplies. Systems strain. Margins compress. Leadership burns out. Scale is not more sales. Scale is operational elasticity. At MONDESIR Partners, we design operating foundations that anticipate complexity before it arrives. Because growth should feel controlled — not chaotic. If your business feels heavier at 7 figures than it did at 6, your foundation isn’t built for altitude. Scale is engineered.
1
1 Comment -
Alexander Shulman
Tototheo Global • 2K followers
CPTO Revolution: Why SaaS Companies Are Merging Product and Tech Leadership I’ve lived the pain of siloed leadership and the inefficiencies it creates many times. And I’ve also seen how tightly integrated product and tech can transform not just delivery, but outcomes. Traditional org charts are no longer keeping up. The most competitive SaaS companies aren’t hiring separate CTOs and CPOs anymore - they’re bringing both roles under one roof with CPTOs. This isn’t about headcount optimization. It’s about reducing friction and moving faster in a world where complexity is climbing and customer expectations evolve by the week. Here’s the core issue: when product and engineering leadership are separate, you’re always playing a game of telephone. Product defines what’s needed. Engineering estimates and negotiates. Product pushes. Engineering pushes back. Handoffs everywhere. Every step is a delay. A CPTO owns the entire journey - from insight to shipped product. One person accountable. One vision. One continuous flow. And it works. Companies running this model are seeing up to 40% faster go-to-market. Less tech debt. Clearer priorities. Higher team velocity. What Actually Changes 1. Aligned Metrics You stop optimizing for isolated outcomes. Product isn’t chasing adoption while engineering shields uptime. Both roll into shared business goals. 2. AI Gets Strategic With unified leadership, AI isn’t a bolt-on. It becomes core to how you design, build, and validate products - through data, feedback loops, and automation. 3. Developer Experience Matters Platform engineering gets the attention it deserves. Internal tools align with product delivery, and suddenly teams aren’t waiting - they’re shipping. UX maturity, platform architecture, technical scalability - all of it becomes a single continuum. You’re not just improving “process”; you’re aligning every decision to what users need and what’s feasible to build. The CPTO Skillset This isn’t a hybrid role - it’s an integrated one. You need the technical depth to guide architecture and the product judgment to say no to overengineering. You talk to engineers about latency and reliability, and to the board about market traction and differentiation. As AI accelerates software development, what matters is orchestration—of systems, teams, and strategy. You need to see the whole board. Cloud infra spend is growing ~10% yearly, mostly due to AI. That spend needs direction. CPTOs are the ones who can match innovation speed with platform efficiency. Companies clinging to the old CTO/CPO split are playing a slower game. Integration is no longer optional - it’s a competitive advantage. So—what’s keeping your org from making the leap?
15
-
Srinivasan Venkatachary
6K followers
Right in time for the holiday reservation rush, we’ve expanded agentic restaurant booking in AI Mode to more people in the U.S. – no Labs opt-in required! This is a major shift from the standard way of planning. Typically, for something like booking dinner plans, we’re used to searching step-by-step: find the restaurants, check the hours, then cross-reference availability. But what if you could do it all with a single query? ⚡️ With agentic capabilities in Search, you can take the busywork off your plate. Here’s how it works 🔍: The orchestrator: When you ask AI Mode for something like “dinner in Little Havana for 5 people with live music and outdoor seating”, our model creates a plan that identifies every dependency. Specialized agents working in parallel: Instead of linearly searching the way we would, the orchestrating agent delegates tasks to specialized agents that use a hybrid approach of live web browsing and tool integrations to find real-time availability. The result: You get suitable options that match your specific needs, so all you have to do is book and enjoy your meal.
75
-
Software Co 🚀
18K followers
The enterprise software market is hitting $300B by 2026, but scaling remains the #1 failure point. The difference between a legacy system that bleeds money and a platform that drives revenue is its architecture. We're moving past "getting it live" to building systems that survive success. The new guide outlines the essential patterns for 2026: - The death of vertical scaling and the rise of Cloud-Native (Kubernetes). - Microservices and Event-Driven Architecture (EDA) for resilience. - Database Sharding and Polyglot Persistence. - Zero Trust & Circuit Breaker patterns for security and stability. Start building for infinite scale. 🔗 Read the full guide: https://lnkd.in/gi9bka8J #Scalability #CTO #CloudNative
7
-
Vivekaditya Sharma
Rintel Systems • 719 followers
Dashboards don’t create accountability. They create meetings. Charts get shared. Everyone nods. Action items get “noted”. Same problems. Next quarter. Accountability doesn’t come from visibility. It comes from systems — where ownership is clear and decisions can’t be ignored. I wrote a short note on why dashboards feel productive but rarely change behaviour — and what actually does. If your org has great dashboards but the same issues every review… this will sound familiar. Dashboards Don’t Create Accountability — Systems Do: https://lnkd.in/gCGpm-VU
7
1 Comment -
Marc Weitlauf
Corpay • 538 followers
Corpay Lodging's new mobile app has an upgraded design and smarter features to support crews and coordinators managing travel in the U.S. and Canada. As part of the Corpay brand, Corpay Lodging goes beyond workforce lodging. This app is built to simplify travel, control costs, and deliver powerful tools for field-based teams. Discover how Corpay’s technology is transforming business travel management and helping companies work smarter, every mile of the journey. #workforcetravel https://lnkd.in/dpEaV8Vb
1
-
Catherine Iger
2K followers
I've been sending around this HBR article (in the comments) on why transformation stalls at the "last mile". The article identifies seven structural frictions blocking AI transformation: productivity gaps, tribal knowledge, architectural complexity, and governance. What was underweighted for me in the list of frictions: change management and risk management. The article frames the identity problem as a knowledge capture challenge. How do you get what's in people's heads into the system? But there's a deeper issue. When you ask someone who has built their career around being the person who knows to hand that knowledge to a machine, you're asking them to redefine their professional identity. That requires trust, time, and intentional change management. The same is true for risk. The governance section is framed operationally: things like who can create agents and where accountability sits. But organizations scaling AI are also taking on new categories of risk: model bias, decision transparency, regulatory exposure, and reputational harm. Those deserve to be first-class considerations in any transformation. Great technology, poorly managed, creates great problems at scale. #AI #DigitalTransformation #ChangeManagement #Leadership #RiskManagement #Experient
36
2 Comments -
Tim Burnham
Burnham Consulting LLC • 1K followers
How I built a small business app for my wife's family Tl;dr, 1) Use Claude Artifacts to build basic functionality 2) Use cursor / claude code to build it out fully 3) Make mistakes and refactor to different technologies more than I probably should. Long version: 1) Use Claude artifacts to make a simple form 2) port it into GitHub using create react app, connect to vercel (super easy!) 3) get it working (can create and share receipt images, woohoo! In laws love it) 4) move to vite (apparently CRA is old and AI used it) 5) move to nextjs to have a semi backend 6) convert js to typescript (that took awhile) 6.1) Revert at least once due to urgently needed new features. 7) Add a database using Neon 8) Decide not use to Neon, use Prisma instead (because AI suggested that) 9) decide not to use Prisma, use railway instead 9.1) Also switch from Prisma ORM to postgres.js 10) fight with AI not to use "unsafe" 11) build different data views and UI for all database operations (add, edit, delete) 12) Add multiple tables and build out more advanced functionality (like expenses!) 13) learn how to backup and migrate databases 14) create a dev and prod instance in GitHub + railway, start pushing to dev for testing instead of prod 15) eventually try to make a pdf report, fail, build f# backend to make pdf 16) Learn type algebra to and build a super elegant user permission management system. 16) Start moving APIs to f#, make elegant schema system 16.1) Break UX, then fix it. Users slightly confused but they're my in-laws so they'll be ok. 17) Accidentally wipe my local database (it was my fault, not AI's), then restore it from a backup. You are here Next steps - build ability to dynamically build forms. - find another small client - teach AI to build with me Lessons : I find that AI doesn't create bad code, it just has generic assumptions. As I guide it to have better assumptions it gets me to something that I find elegant and easy to work with. Still it starts messy and I have to massage it to something clean. I also find that I move faster if I think first, but often I like to skip that and do first. This loses time (note to self).
5
-
LeadMachine
103 followers
This is the future of the 'Agentic Workflow.' Spotify is solving the technical debt problem with Claude; we’re using similar AI agent logic at LeadMachine to solve the 'Data Debt' problem in CRMs. When you treat your CRM like a codebase—where agents handle the tagging, routing, and updates—the entire organization moves faster. Love seeing this at scale! #CRM #AICRM #LeadGen
2
-
Bob Pisani
Addepar • 3K followers
There is a lot of AI doom-posting in the news right now with narratives focused on displacement and "doing more with less." At Addepar, we reject that premise. The investment industry doesn’t have a talent problem; it has a time problem. The global ecosystem is massive, fragmented, and increasingly complex. The "noise" of manual workflows and data silos shouldn't be the ceiling for what’s possible. Today, we are officially unveiling Addison. Addison is a native AI experience built to deliver actionable intelligence across investment workflows. We didn’t build it to replace the human element, we built it to accelerate it. In an industry built on trust and strategy, the human judgment remains irreplaceable. Our vision is simple: AI finds the patterns; you make the judgment calls. AI processes the "what"; you own the "why." We believe AI is the tool that finally allows investment professionals to get back to the high-value, high-impact work that actually moves the needle. The future of finance isn’t about automation for the sake of efficiency. It’s about empowerment for the sake of impact. Let’s go build the future. #Addepar #Addison #WealthTech #AI #Innovation #InvestmentManagement
101
3 Comments -
Rando Merhori
1771 Technologies • 2K followers
Your data is only as powerful as your data grid! Legacy grids? Sure, they sort of work, but you have to live with bloated bundle sizes, rigid APIs, and daily workarounds. Every update feels like Russian roulette; one tweak and something breaks. LyteNyte Grid changes all that. It's designed from the ground up for React, with a clean declarative API, a tiny bundle size, and enterprise-grade features, so you can code with confidence and ship faster. Unleash your potential and try it out now on GitHub https://lnkd.in/eu2Qew3D
2
-
Terry Moncada
Business Brokers Nation • 4K followers
Most breakthroughs don’t happen by adding features. They happen when someone notices a layer everyone else missed. When an entire industry optimizes the same downstream controls, real leverage quietly shifts upstream. Before the dashboards. Before the alerts. Before the market even has a language for it. Timing matters. Architecture matters. Restraint matters most. #RiskEngineering #SecurityArchitecture #UpstreamThinking #ThreatPrevention #SystemsDesign #Innovation #TheDarkKnightProject
1
-
NowSecure
20K followers
You don’t control how third-party mobile apps are built. You don’t control their SDK choices. You don’t control their update cadence. But you do own the risk. Learn how to evaluate and govern mobile apps with confidence: https://loom.ly/0_JvPY0 #ThirdPartyRisk #EnterpriseRisk #MobileRisk #MobileSecurity #AppSecurity
2
-
Aniket Shah
iManage • 1K followers
What separates people who get great results from Claude from those who don't? It's not what you think. I've spent hundreds of hours building production agents on Claude, Copilot Studio, Claude Code, raw API calls. Same model, wildly different results depending on how you interact with it. Three patterns changed everything for me. 1. Edit, don't reply When Claude gives you broken code, don't reply with "that didn't work." That keeps the failed attempt in context. Claude anchors on it and tries to patch its own mistake instead of rethinking. Edit your original prompt instead. Add a constraint like: Fix the root cause in [function_name] without adding wrapper functions. This removes the bad attempt entirely. Clean context, sharper constraint, better output. Fewer tokens burned. 2. Ban workarounds up front Claude's default instinct when code fails is to make it stop failing. Not the same as making it work correctly. It adds try/catch wrappers. Fallback values. Defensive layers that hide the real bug. In agent workflows, this is lethal. A silently failing tool call cascades through the entire chain. Put this in your system prompt: Do not add fallbacks to mask errors. If core logic fails, surface the error. Fix the underlying logic only. This one instruction changes Claude's behavior more than anything else I've tried. 3. Plan before you build In agentic coding tools, Claude can enter rapid edit-run-edit loops that compound mistakes. Each iteration adds context and moves further from intent. Require a plan first. Review it before approving changes. If the plan says "add a fallback," reject it. If it touches unrelated files, push back. Making Claude's reasoning legible before it acts is the single highest-leverage habit you can build. Bonus Pin your constraints at the top of the prompt. Instructions at the beginning and end of a long context window get more weight than those buried in the middle. "No fallback logic" on line 3 hits harder than the same rule on line 200. None of this is about clever prompt tricks. It's context engineering. You're controlling what's in the context window, constraining the model's solution space, and making its reasoning legible before it acts. The model isn't the bottleneck. The interaction pattern is. #LegalTech #AI #ContextEngineering #LLM #AgenticAI
10
1 Comment
Explore top content on LinkedIn
Find curated posts and insights for relevant topics all in one place.
View top content