Ricky Sahu and the education between build and deploy

Ricky Sahu has a useful answer to the person who would like to understand technology without getting too entangled in it: build something. Then deploy it. Somewhere between the promising first version and the working product, an education will occur. It may involve fewer inspirational quotations than expected and rather more debugging.

His own career offers several versions of that education. He worked on support automation at Google, built online marketing tools at Promediacorp, became the first employee at CareJourney, and co-founded 1upHealth in 2017. In 2023, he started again with GenHealth.ai. The companies and job titles changed. The recurring interest was in getting complicated work to happen with less friction.

There is a smaller, revealing trail alongside those appointments: a public coding profile, practical answers to programming questions, and a little web crawler offered for other people to copy. These are modest artifacts beside a founder’s biography. They also give the biography something a title cannot: evidence of how he approaches a problem when it is small enough to fit on a screen.

The education between build and deploy

Sahu studied at the University of Virginia from 2005 to 2009. His academic background combines systems engineering and economics. It is a useful pairing for someone who would spend his career dealing with software and the organizations expected to use it. One discipline asks how the parts interact; the other keeps asking what people have a reason to do.

At Google, he worked with Google Apps for Business. His work included automating customer support and forecasting demand so that hundreds of employees could be staffed around the world. A support queue is an unromantic place to begin a founder story, which is part of its appeal. Demand arrives on its own schedule. Someone must work out how to meet it.

The assignment brought software into contact with an operating problem. Forecasting mattered because people had to be available; automation mattered because customers needed help. Even an elegant program has to answer to the day’s work. That practical relationship between a system and the people around it would recur in Sahu’s later advice about products and management.

His next work at Promediacorp involved search engine optimization and online marketing tools. He used machine learning and crowdsourcing tools including Mechanical Turk on projects for companies such as Sony, Microsoft and Forever21. The range is a reminder that his technical career began before the current vocabulary of AI startups became standard business conversation.

A crawler, with permission to copy

In July 2014, Sahu contributed to a discussion about crawling web pages that use JavaScript. He pointed to a quick crawler he had built using Selenium and invited others to copy or modify it. It was a compact contribution: a concrete tool offered at the point where somebody else was stuck.

The repository, seleniumjscrawl, remains part of his public GitHub history. Its description is direct: crawl a page while executing JavaScript. There is no elaborate theory of disruption attached to it. The name is practically a packing list. For a developer looking for that particular capability, such plainness is a courtesy.

The contribution is interesting because it combines making and explaining. Building a tool solves one person’s problem. Leaving it where another programmer can find it makes the work reusable. Permission to modify it also acknowledges that somebody else’s problem will probably differ in a way its original author has not anticipated.

His GitHub profile links both companies he founded, alongside projects in JavaScript and Python. Taken together, the corporate work and the public repositories suggest a career with room for different scales of construction: a company, an application, a utility. A small tool does not need to pretend it is a company to justify being useful.

What forty-four answers leave behind

Sahu’s Stack Overflow profile supplies another view of this working life. At the time of review, it listed 44 answers, roughly 24,800 reputation points and an estimated six million people reached. The last figure is the platform’s own measure of reach. It offers a glimpse of how a practical contribution can keep circulating long after its author has moved to other work.

The subjects include Python, Node.js, JavaScript and Git. Among the questions associated with his contributions are encoding a query string, finding text with Selenium and reading a stream into a string. These are the ordinary connective tasks of programming. They have the distinction of remaining troublesome precisely when someone would prefer to be doing something more impressive.

A founder profile usually follows the things that acquired a company name. These answers record another kind of output: knowledge made available at the level of an individual task. Sahu’s career contains both. The public record of small technical contributions makes his later argument for learning to build feel less like advice issued from a safe distance.

Employee one, then founder

At CareJourney, Sahu was the first employee and led engineering. He worked with Aneesh Chopra, the former chief technology officer of the United States. That placed him inside a young organization with a technically experienced founder network, while giving him direct responsibility for turning an early business into working software.

He co-founded 1upHealth in 2017 and served as its CEO. By March 2022, he was publicly identified as its founder and CTO. Those titles mark different responsibilities within the business he helped create. They also complicate the tidy picture of a founder as someone whose principal occupation is always being chief executive.

In 2023 he co-founded GenHealth.ai, where he is CEO. Ethan Siegel is a fellow founder and the company’s chief product officer. Eric Marriott is also identified as a co-founder in public accounts. People from the earlier company were part of the new undertaking, carrying relationships as well as technical experience into it.

Investors had been watching across that stretch. Craft Ventures described meeting Sahu four years before backing GenHealth in 2023. Flare Capital dates its first meeting with him to 2017. The relationships behind a new funding announcement can have a much longer history than the company receiving the money. A launch date tells only part of the story.

The product is allowed to meet people

Sahu’s advice about product development favors early exposure to users. He has encouraged teams to put a beta version into the hands of a trusted customer, launch and iterate, while taking security concerns seriously. His closing instruction is short enough to survive the meeting: “Don’t wait for the product to be perfect.”

There is a social risk in that approach. An unfinished product gives someone else the opportunity to discover what its makers have missed. Keeping it inside the team protects the team from that encounter, but also postpones the useful information. His advice gives the customer a role before the developers have exhausted their own opinions.

On career development, he recommends “learning how to code and deploy a product.” His reason is practical: completing a project helps a person understand the effort involved and better assess a team’s work and opportunities. Deployment is doing considerable work in that sentence. It brings an idea into contact with conditions the idea itself cannot control.

“Don’t wait for the product to be perfect.”

Ricky Sahu, on testing with users, 2022

His management advice follows a similar route toward direct contact. He has described enjoying individual conversations with team members. Those exchanges, he argues, can help employees understand priorities and help leadership understand difficulties. It is a modest mechanism, with the advantage that neither side has to complete a presentation before a misunderstanding can become visible.

For recruiting, he has emphasized giving engineers interesting, technically demanding problems and access to current tools. The proposition is fairly specific: the work itself should help attract the people who will do it. A job description can promise a lively culture. A difficult problem offers a candidate something concrete to examine.

Another company, an old practical question

On September 8, 2026, Sahu announced a $16.5 million Series A for GenHealth.ai, led by Flare Capital. The company put its total funding at $30 million. Craft Ventures and Obvious Ventures returned as investors. Sahu also reported a team of more than 20 people and plans to expand engineering and other functions.

The announcement described a business increasingly focused on software agents that carry out work across existing systems. Within that ambition is a familiar operating question from his earlier career: where does work get stuck, and what would it take to keep it moving? The tools have changed substantially since Google Apps support automation. The question remains recognizable.

Sahu’s public advice brings the answer back to a manageable size. Build a project. Let somebody use it. Talk with the people doing the work. Offer an engineer a problem worth solving. Each step leaves room for an inconvenient response, which is often how a useful response first appears.

That is the thread connecting the executive appointments with the crawler and the coding answers. A product becomes more interesting when it leaves its maker’s hands. Someone else tries it, finds the awkward bit, asks a question, or changes the code. For a founder whose career keeps returning to automation, Sahu has left quite a few people in the loop.