Principal Software Engineer

Zero-to-One Builder for an AI-First Venture StudioGreat zero-to-one builders are becoming more careful about where to spend their next years. AI is opening a rare company-creation window, with unusual room for new ventures to emerge fast. But that does not make great opportunities easier to find. And it definitely does not make great products easier to build. Once you've done real zero-to-one work, you know the risk is not just failure. It is spending your next years on something that was never real enough to deserve them. Gitwit was built to find problems worth solving. We are an AI-first venture studio built to win this moment through systematic exploration, ruthless validation, and fast cross-functional building. Over the last few years, we've launched products including an AI report-writing platform for psychologists, an AI troubleshooting platform for manufacturers, and AI-powered workflow tools for operators in complex industries. Over the next several years, we plan to launch more than a dozen new AI-native ventures. We do not ask you to make one blind bet on one company, one founder, or one codebase. We sweep broadly, test rigorously, and build the ventures that earn the right to exist. This role is for the kind of engineer who already knows the difference: someone who cares as much about what should be built as how to build it, and who wants the real version of ownership. Real product authorship, real technical direction, real proximity to users and venture decisions, and repeated chances to shape what gets built and how it gets to traction. And of course, real upside when the winners emerge, including meaningful equity participation across every venture the studio builds.What the Right Seat Actually Looks LikeThis role is designed for engineers who have already led major technical initiatives, shaped engineering strategy, and demonstrated exceptional judgment in ambiguous zero-to-one environments. This is not a role for someone who wants a clean lane, a polished backlog, and a roadmap handed down from somewhere else. It is for an engineer who wants to be close to the questions that matter earliest: What is the real problem? What is the sharpest way to solve it? What should be built now? What should wait? What should be killed before more time gets wasted? At Gitwit, principal engineers like this do not sit downstream from product decisions. They help shape them. You will work closely with designers, product strategists, researchers, and venture leaders to turn raw opportunity into real products people want. You will set technical direction, but also influence the bigger decisions that determine whether something becomes a feature, a product, or a company. You will think about user experience, business model, technical tradeoffs, speed, quality, and what the market is actually telling us. And because this is a venture studio, you will not spend your best years trapped inside one stale system or one narrow bet. You will get repeated chances to build from zero, learn fast, and apply that learning again. That is the seat.Why This Is a Rare Zero-to-One SeatMost early-stage engineering roles ask you to make one concentrated bet: one company, one market, one founder, one codebase, one trajectory. Sometimes that works. Sometimes it means spending your next years inside something that was never strong enough underneath. Gitwit is structured differently. Here, you get the intensity and zero-to-one challenge of early-stage building without tying all of your learning, upside, and career energy to a single fragile bet. This is not just a chance to join a company. It is a chance to build inside a company-creation system.