The loudest artifact in technology is usually the launch. A quieter kind of evidence lives in the company that is still answering clients, assembling teams and filing the paperwork years later. Anjali Yadav's career sits in that quieter register. Public business profiles have attached two consequential titles to her work at InfoObjects Inc.: vice president of human resources and chief executive officer. Employer records also place her name beside the formal responsibility of representing the San Jose company in labor matters. These are not the glamorous pixels of the software business. They are its load-bearing ones.
Yadav is based in Santa Clara, close to InfoObjects' San Jose headquarters. Her public biography is compact. There is no sprawling archive of keynote talks, autobiographical essays or founder folklore. What emerges instead is an operator's outline: people, institutional process and executive responsibility inside a consulting firm whose technical vocabulary has repeatedly changed. InfoObjects began in 2005. Its work has stretched from enterprise applications, analytics and distributed data to cloud-native engineering, machine learning and, now, generative and agentic AI.
Two titles, one operating spine
Human resources and the chief executive's office can look like opposite ends of an org chart. In a services company they share a nervous system. Revenue depends on selling expertise that must then arrive in the form of actual people, with the right experience, in the right place, at the right time. A staffing mistake can become a delivery mistake. A vague capability plan can become a sales promise with nobody ready to keep it. The distance between workforce planning and corporate strategy is often one calendar invitation.
That makes Yadav's pair of recorded titles more revealing than a polished leadership slogan. Human-resources leadership offers a close view of how a business really behaves. It sees where teams are stretched, which skills are scarce, which managers can turn a difficult brief into calm work and where culture becomes either an advantage or an invoice. The CEO title widens the frame, but the underlying questions remain practical: What can the company credibly promise? Who can deliver it? What system lets them do it again?
In a consulting company, the talent system is part of the product.
There is also a revealing bureaucratic detail. Yadav has been listed as an authorized InfoObjects contact in the company's employment filings. Paperwork rarely appears in heroic business stories, perhaps because a correctly completed form has no pyrotechnics. Yet a global technical workforce does not materialize from an inspirational memo. It depends on compliance, timelines and decisions made far from the demo screen. The operator lives where ambition meets a checklist and learns to respect both.
A company keeps changing its nouns
InfoObjects' history mirrors a broader migration in enterprise technology. Data integration led to big data. Big data led to real-time analytics and machine learning. Cloud infrastructure became cloud-native engineering. The current language includes retrieval-augmented generation, model fine-tuning, reinforcement learning from human feedback, evaluation systems and agents. Each noun arrives with a small parade. The operating work begins after the parade has left.
The company's present pitch emphasizes production rather than spectacle: forward-deployed engineers, model-agnostic architecture, customer-owned intellectual property and evaluation loops. Its dedicated AI practice, Cogence, brings together agentic engineering, model-improvement work and data operations. The firm says it works across six time zones and four continents. InfoObjects' LinkedIn page places its headcount in the 201-to-500 range; the company website describes a bench of more than 500 AI and data experts. The exact counting frame differs, but the organizational problem is plain: distributed knowledge must behave like one team.
That problem is easy to underestimate. A model can be copied. A cloud account can be opened before lunch. A dependable delivery culture takes longer. Technical services compound through accumulated judgment: knowing when a prototype is ready, when a requirement is still fog, when a specialist needs room and when a client needs a direct answer. People operations is where much of that judgment is recruited, rewarded and retained. Executive operations is where it is turned into a repeatable commercial promise.
The unphotogenic work
InfoObjects' labor-certification history supplies an unusually concrete view of the machinery. Its filings have included systems analysts, software developers, project managers and data analysts. The annual totals are modest, not a mass-hiring spectacle, and that is precisely why the detail matters. Each filing represents a specific technical role entering the company's delivery capacity. In a consultancy, one good analyst can rescue a confused data project. One strong project manager can prevent an expensive misunderstanding from becoming a recurring meeting.
Yadav's name appears at that junction between organization and obligation. It is a useful corrective to the way executive work is often portrayed. Strategy is not only choosing a market. It is arranging the company so that the choice survives contact with a customer. The work includes documents, handoffs, hiring judgments and the occasional sentence rewritten until nobody can misunderstand it. Oscar Wilde might have found paperwork unforgivably earnest. He would still have wanted the hotel reservation to exist.
Leadership without the personal broadcast tower
Yadav has not made herself the main character of InfoObjects' public marketing. The company's current leadership page presents founder Rishi Yadav as founder and CEO, Sudhir Jangir as founder and CTO, Dave Eddings as president of sales and Utkarsh Panwar as president of engineering. Separate business and employer listings preserve Anjali Yadav's CEO designation. Taken together, the records show a title history with different snapshots rather than a simple present-tense org chart. Precision is more useful here than mythology.
Her professional network is therefore easiest to understand through the company. Rishi Yadav and Sudhir Jangir founded InfoObjects. The wider leadership team covers engineering, sales and technical delivery. Anjali Yadav's documented work touches the human infrastructure that connects those functions. This is a less cinematic form of connection than a famous mentor story. It is also how companies persist: several disciplines agreeing, often imperfectly, on who must do what by Friday.
Visibility can advertise responsibility. It does not create it.
A restrained public profile leaves no license to invent personality. It does, however, reveal a professional posture. Yadav's public identity is attached to the firm, not a stream of personal commentary. The available facts point toward institutional work rather than personal brand-building. That distinction matters in an industry currently enchanted by fluent machines. Enterprise clients still buy accountability. Someone must own the staffing plan, the delivery rhythm and the formal promises around the work.
The lesson hiding in plain sight
The most portable idea in Yadav's story is simple: every technical strategy has a people-shaped shadow. A company that announces an AI practice needs researchers, data engineers, evaluators, cloud specialists and client-facing operators. It needs a way to judge those people, deploy them and help them learn faster than the market changes. The quality of that system eventually appears in the quality of the product, even when the customer never sees the system itself.
InfoObjects now talks about shipping production systems, preserving customer ownership and avoiding model lock-in. Those principles are architectural, but they are also managerial. Portability requires documentation. Customer ownership requires disciplined boundaries. Production requires somebody willing to care about the last stubborn edge case after the demonstration has earned its applause. The technical and operational halves are not rivals. They are partners with different calendars.
Anjali Yadav's career does not arrive as a neat fable, and it is better for refusing the shape. It is a view through a side door into the company-building work that rarely makes a keynote slide. There is the HR title, then the recorded CEO title, then the formal employer responsibility. Around those facts stands a company that has spent two decades learning new technologies without abandoning the old requirement to deliver. The machinery is quiet because machinery, when it works, usually is.
There is a final, practical way to read the arc. The technology business prizes reinvention, but reinvention without continuity is just expensive amnesia. Someone must remember why a process exists before deciding whether to replace it. Someone must preserve the client relationship while a delivery team learns a new tool. Someone must make a new capability legible enough to hire for it. Yadav's recorded path through people leadership, executive responsibility and employer representation sits inside that continuity. It suggests a kind of institutional memory carried through decisions rather than speeches. The machines may change from clusters to clouds to agents. The management question stays stubbornly human: can a group of people make a difficult promise together, keep it, and become a little more capable in the keeping?