Breaking Jyoti Bansal is betting the new software bottleneck begins after code Harness puts 16 product startups under one roof Seven years waiting, then straight to the workbench

Founder profile / Software's second shift

Jyoti Bansal Is Building the Factory After the Code

He waited seven years for permission to start. Then he sold AppDynamics on the eve of its IPO, discovered retirement was a poor fit, and returned to the workbench. Now Harness is his attempt to organize everything that happens after code.

Before Jyoti Bansal built software for the world's large companies, he sold something more physical: irrigation machinery. His father ran a small business in Rajasthan, and the boy helped after school. There were customers to understand, transactions to watch and machines whose usefulness could not be rescued by a clever slogan. Years later, Bansal would call this his only real exposure to business before becoming a founder. He never went to business school. The shop did the work more efficiently.

The other classroom belonged to his grandfather, whose library held thousands of books. Bansal read widely, from technical curiosities to Plato's Republic. A computer arrived in his world around ninth grade, followed by BASIC at school. Curiosity came first; the equipment caught up.

That combination, commerce beside curiosity, explains a surprising amount of what followed. Bansal became an engineer who could sell, a founder who liked to inspect the machinery and an investor who preferred getting involved to watching from a safe upholstered chair.

The useful education of a mediocre transcript

Bansal placed among the top JEE candidates and chose IIT Delhi, partly for the large-city life. He studied computer science, but formal academics did not hold him for long. He skipped classes, taught himself C and Java, and graduated with grades that kept the more coveted campus jobs out of easy reach. This inconvenience turned out to be educational.

At Tryst, IIT Delhi's technical festival, he handled sponsorship sales and raised multiples of the previous year's total. For extra income, he evaluated entrance-exam papers at a coaching center. Then he found his first job outside the most polished campus pipeline, joining Applion Networks and writing software for a real-time television system. Six months around production code taught him more programming, he later said, than four years of college.

“My style is to read, learn fast and do things.”Jyoti Bansal on why startups suited him

In 2000, he arrived in the United States on Independence Day, carrying an H-1B visa and an entrepreneurial ambition that the visa made difficult to exercise. He could work for an employer. Leaving to form his own company was another matter. So he spent roughly seven years inside startups, including Wily Technologies, absorbing how enterprise software behaved in production while his permanent-residency process advanced at bureaucratic speed.

The delay deserves precision. It was neither a spiritual retreat nor a clever incubation program. Bansal wanted to leave earlier and could not. Yet by the time he received employment authorization in 2007, he had a close view of application-performance software, a network in Silicon Valley and several years of unrealized founder energy. AppDynamics followed in 2008, just as the financial crisis made optimism look faintly irresponsible.

7years waiting for authorization to start
$3.7BCisco's announced AppDynamics price
16product startups inside Harness

A product makes the argument

AppDynamics monitored the behavior of complex applications, helping companies spot slowdowns and failures before customers did. The technical proposition was hard to demonstrate because the product itself had to add very little overhead. Buyers were being asked to install monitoring software in systems where small performance penalties mattered. Trust was the first product problem.

Bansal's team answered with AppDynamics Lite, a free edition designed to be downloaded, installed and producing useful data within minutes. Engineers could inspect the evidence without waiting through a procurement courtship. The free product had to be unusually self-sufficient because no salesperson would stand beside every user. Its usefulness carried the pitch.

That pattern appears throughout Bansal's advice. Sell what exists today, he tells founders, rather than the features living comfortably on a roadmap. Product-market fit means strangers buying at the price you intend to charge. A good enterprise product needs a “binary differentiator,” a capability the buyer can identify without interpretive dance. His preferred hires show a bias for action. Motion is not a substitute for judgment, but judgment improves rapidly after contact with a customer.

Level 01Find the painful problem
Level 02Prove strangers will pay
Level 03Build repeatable distribution
Level 04Keep evolving the operator

He compares these phases to a video game. Every level is confusing until it is cleared; from the next level, the old difficulty looks almost quaint. At AppDynamics, the founder's role expanded from engineering to product, sales, people and operational efficiency. Bansal eventually moved from CEO to executive chairman and chief strategist as the company prepared for public markets.

A finish line moves overnight

In January 2017, AppDynamics was days from an initial public offering. Then Cisco offered approximately $3.7 billion in cash and assumed equity awards. The board faced two valid futures: become a public company as planned or accept an unusually concrete outcome immediately.

Bansal has described the sale as emotionally difficult, even while defending it as the responsible choice for employees and shareholders. Every AppDynamics employee held equity. He later said more than 400 employees made over $1 million from the transaction. The number makes the decision vivid. A founder may supply the story's convenient face, but a company is an agreement among many people's years.

Afterward came the experiments expected of someone newly free from both a calendar and financial constraint: African safaris, ambitious travel, a week of Michelin-starred restaurants in Tokyo. Enjoyable, certainly. Sufficient, apparently not. Bansal asked what he would want to do every day and landed back on the activity he had just completed.

“I like to solve problems, build teams and compete.”Why retirement did not survive the itinerary

He calls building companies his craft. It is a revealing noun. A craft does not end after one fine object. It asks for another encounter with the raw material, another set of mistakes and the pleasure of having one's hands occupied. BIG Labs became his startup studio. Harness emerged from it in 2017, with former Apple DevOps architect Rishi Singh as co-founder. Traceable followed to work on API security. Bansal also co-founded Unusual Ventures with John Vrionis, pairing venture capital with practical operating support for early founders.

Jyoti Bansal speaking with WorkOS CEO Michael Grinich at HumanX 2026
AT HUMANX 2026, THE CONVERSATION MOVED DOWNSTREAM: AI CAN PRODUCE THE CODE; SOMEONE STILL HAS TO GET IT SAFELY INTO THE WORLD. VIDEO STILL: WORKOS.

The factory beyond the prompt

Harness began with continuous delivery, the unglamorous machinery that moves code from a developer's machine into production. Over time it added continuous integration, feature management, cloud-cost controls, developer portals, reliability tools and security. In February 2025, Harness and Traceable merged, bringing software delivery and application security into the same company.

The timing matters because generative AI is changing the volume of software. Bansal estimates that writing code accounts for roughly 30 percent of the work. The remaining 70 percent includes testing it, scanning it, approving it, deploying it, watching it, paying for its infrastructure and rolling it back when reality objects. Faster code generation increases the load on every downstream step.

At HumanX 2026, Bansal drew a distinction between adding an assistant to an existing tool and making the delivery system itself responsive. In his version, AI helps choose relevant tests, watches a canary release, detects unhealthy behavior, triggers a rollback and finds wasted cloud resources. The useful intelligence sits inside decisions, not merely inside a chat window.

Harness has grown by creating many product lines, which creates its own organizational puzzle. Bansal describes the company as 16 startups within a startup. Each product needs a focused team, a distinct customer problem and the urgency of a small business. The larger organization supplies shared infrastructure and a route into enterprise accounts. It is an attempt to obtain the reach of a platform without turning every product decision into committee upholstery.

The approach also carries a lesson from Bansal's second-company adjustment. Experience from AppDynamics sometimes tempted him to install mature sales machinery too early at Harness. A young company still needs improvisation before it earns a repeatable system. The veteran's advantage is pattern recognition; the veteran's hazard is applying a late-stage pattern to an early-stage mess.

The operator who keeps returning

In December 2025, Harness announced a $200 million primary Series E investment led by Goldman Sachs alongside a planned $40 million employee tender. The package valued the company at $5.5 billion post-money. Bansal said the business was on track to pass $250 million in annual recurring revenue for 2025. He has spoken openly about taking Harness public and working toward $1 billion in recurring revenue.

The financing is a milestone, but Bansal's more durable aspiration is visible in the architecture around him. BIG Labs creates companies. Unusual Ventures coaches and funds early founders. Harness tries to preserve mini-founders inside a larger enterprise. Across each structure sits the same question: how can a person keep the agency of the first day after the company acquires the obligations of year ten?

His answer seems to be constant rearrangement. Leaders must evolve with the stage. Products need a reason to win. Teams need clear ownership. Wrong decisions need repair before they become doctrine. He seeks advice from smart people and has said that if he cannot hold a convincing discussion with ten of them, the decision probably needs more work. Intellectual honesty, in this formulation, is less a virtue displayed on a wall than a maintenance schedule.

The child in the machinery shop would recognize the principle. A system earns trust by working under load. Bansal spent seven years waiting to build his first. Since then, he has kept finding new systems to test: observability, delivery, security, venture capital and the operating design of a multi-product company. AI has handed him the latest load. More code is coming. The factory after it had better be ready.