Suyank's Profound AI Rep
Suyank Saraswat
Edges
Owning Full-Stack Product Delivery
Suyank operates as a complete product engineer: he takes a feature or product from brief to shipped without handing off between layers. Frontend, backend, data model, deployment, and mobile are all within his scope. This pattern has shown up across every founding role he has held. At HeyHey, he built an NFT marketplace end-to-end, learning smart contract development and shipping the full stack in under two months. At Segwise, he shipped a working analytics product in a single month as the founding engineer. His approach is to start with what is needed to prove the bet, ship it, and then invest in the architecture once the product has earned the investment. He makes stack and data model decisions without waiting for sign-off, and he moves between React, React Native, Node, and cloud infrastructure as the work requires. For an early-stage team, this means one engineer who can cover the full surface area of the product.
Spotted in 3 Stories
Building Engineering Standards From Scratch
Suyank has a consistent pattern of arriving in codebases without standards and building the infrastructure that lets teams move together. He does not just fix the immediate problem; he puts in place the systems that prevent the problem from recurring. At CodeRabbit, he was brought in specifically because the engineering team had grown without shared standards. He designed and built an internal NPM package covering components, utilities, theming, and access controls, then handed it off with documentation and an automated deployment pipeline. At HeyHey, he took over a React Native codebase from a third party and rebuilt the component architecture using atomic design principles, centralizing styling tokens and eliminating the inline CSS that had made the codebase brittle. The mechanism is the same in both cases: identify the shared layer that is causing divergence, extract it into a controlled artifact, and give the team a clear process for evolving it. The result is a codebase where new engineers can contribute without breaking what already works. This is the kind of work that compounds: the team that inherits a Suyank-structured codebase moves faster than the one that does not.
Spotted in 2 Stories
Shipping Fast Under Startup Constraints
Suyank has a clear and consistent approach to early-stage tradeoffs: ship the version that proves the bet, then invest in quality once the bet is proven. He applies this deliberately, not by default. At Segwise, the team had one month to ship a working product for a fundraise. Suyank had planned to build a proper design system, but the team collectively decided to use existing templates and move. The product shipped on time, the fundraise succeeded, and he led the revamp afterward. At HeyHey, he shipped an NFT marketplace in under two months by learning and building simultaneously, prioritizing a working product over a polished architecture. The pattern is not about cutting corners; it is about knowing which corners to cut and which to protect. Suyank makes the tradeoff explicitly, communicates it to the team, and plans the cleanup before the debt accumulates. For a founding engineer role, this is the judgment that separates engineers who ship from engineers who plan.
Spotted in 2 Stories
Learning and Shipping New Technical Domains
Suyank has a demonstrated ability to enter genuinely unfamiliar technical territory, learn what is needed, and ship something real in a short window. This is not about picking up a new framework; it is about owning a new domain end-to-end under time pressure. The clearest example is the HeyHey NFT marketplace. When the company decided to move into NFTs, smart contract development was new enough that there were few references available online. Suyank learned Solidity, token minting, wallet interactions, and Web3 integration from scratch, and shipped a full marketplace in under two months. The launch generated meaningful revenue for the company. His approach is to identify what he needs to learn, learn it in the context of building, and ship rather than study. He treats unfamiliar domains as a constraint to work around, not a reason to slow down. For an early-stage team moving into new product territory, this is a meaningful capability.
Spotted in 1 Story