Pylon is one of those companies that makes you pay attention. Founded in 2022 by three engineers who came out of Airbnb, Samsara, and Caltech, the company has built a B2B customer support platform that is quietly becoming the de facto replacement for Zendesk, Intercom, and Salesforce Service Cloud among fast-growing startups. Over 750 companies — including Together AI, Cognition, Temporal, and AssemblyAI — now run their support on Pylon.
With $51M in funding from Andreessen Horowitz, Bain Capital Ventures, General Catalyst, and Y Combinator, and 5x year-over-year revenue growth for two consecutive years, Pylon is at a stage where the product-market fit is undeniable. But with only ~70 employees, it’s still small enough that every hire reshapes the company. That makes the culture question especially high-stakes: who should join, and what are they walking into?
We pulled data from Pylon's company profile, employee reviews, and the founders’ own public statements to give you an honest picture. Here’s what you need to know.
Pylon at a Glance
| Founded | 2022 |
| Headquarters | San Francisco, CA |
| Founders | Marty Kausas, Advith Chelikani & Robert Eng |
| Company Size | ~70 employees |
| Total Funding | $51M (Series B, Aug 2025) |
| Glassdoor Rating | 4.3 / 5.0 |
| Work-Life Balance | 4.0 / 5.0 |
| Recommend to Friend | 100% |
| Key Investors | a16z, Bain Capital Ventures, General Catalyst, YC |
| Culture Values | Ship Fast, Many Hats, Product Impact, Flat Hierarchy |
The Founding Story
Pylon’s origin story starts at Caltech, where co-founders Advith Chelikani and Robert Eng met as students. The two later crossed paths with Marty Kausas during the Kleiner Perkins Fellowship — an engineering fellowship that has historically connected ambitious builders before they start companies. All three went on to work as software engineers at prominent tech companies: Marty at Airbnb, Advith at Samsara, and Robert at Affinity.
The insight that became Pylon came from a frustration they kept seeing across B2B companies: customer support conversations were fragmenting across Slack shared channels, Microsoft Teams, email, community forums, and in-app chat — and legacy tools like Zendesk were built for a consumer support model that didn’t fit. B2B support is fundamentally collaborative. The customer isn’t filing a ticket and waiting — they’re pinging a shared Slack channel and expecting a response in minutes.
They went through Y Combinator in winter 2023, raised a $17M Series A from Andreessen Horowitz in August 2024, and closed a $31M Series B co-led by a16z and Bain Capital Ventures in August 2025. In under three years, Pylon grew from a YC demo day pitch to the support platform behind 750+ of the fastest-growing companies in tech.
What Makes Pylon’s Culture Different
Pylon’s CEO Marty Kausas made headlines in September 2025 when he posted “HARDCORE STARTUP CULTURE IS BACK” alongside a Wall Street Journal feature on Pylon’s work culture. It wasn’t an exaggeration. This is a company that is explicit about being intense, demanding, and built for people who want to work hard on something that’s working.
What makes Pylon’s intensity different from, say, the grind culture at a pre-PMF startup is that the intensity sits on top of genuinely strong product-market fit. The company has 5x revenue growth for two consecutive years, 150+ migrations from legacy platforms, and a customer list that reads like a who’s who of fast-growing AI and infrastructure companies. You’re not grinding because the business might work — you’re sprinting because it is working and the window to capture the market is right now.
The second defining characteristic is the founder-engineer identity. All three co-founders are engineers. All three still write code. This creates a culture where engineering isn’t a department — it’s the company. Decisions are made by the people building the product, not by layers of product management or strategy consultants. When employees describe working at Pylon, the recurring theme is direct impact: you build something, ship it, and see customers using it within days.
At ~70 people, Pylon is at the stage where everyone knows everyone. The flat hierarchy isn’t aspirational — it’s structural. There are no layers between an IC engineer and a founder. You Slack Marty directly. You push to production the same week you start. The many-hats culture means you might be fixing a customer’s integration issue in the morning and shipping a new feature in the afternoon.
Employee Sentiment
Pylon’s Glassdoor rating of 4.3 out of 5.0 with 100% of employees recommending the company is notable. The review sample is small — as you’d expect from a 70-person company barely three years old — but the signal is consistently positive. Work-Life Balance rates 4.0 out of 5.0, which is surprisingly strong given the explicit “hardcore” culture positioning.
That 4.0 WLB score deserves interpretation. It doesn’t mean Pylon is a 40-hour-week company — it almost certainly isn’t. What it likely reflects is that people who join Pylon are self-selected for intensity, and they calibrate “balance” differently. When you’re excited about the product, the pace feels energizing rather than draining. But that’s a selection effect, not a culture guarantee. If you’re coming from a more structured environment and expect clear boundaries, the 4.0 may overstate how balanced you’ll find it.
What employees love
What could be better
The cons are refreshingly predictable for a company at this stage: immature processes and high intensity. These are growing pains, not structural problems. The question is whether they bother you now — because by the time they’re fixed, Pylon will be a very different (and likely much larger) company, and the window for outsized individual impact will have closed.
The Product & Why It Matters for Culture
Pylon’s product directly shapes the culture in a way that’s worth understanding. The platform unifies B2B customer support across every channel a modern company uses: shared Slack channels, Microsoft Teams, email, in-app chat, ticket forms, and community. It’s built as the modern alternative to legacy tools that were designed for consumer support, not the collaborative, channel-fragmented reality of B2B.
Why does this matter for culture? Because Pylon’s customers are exactly the kind of companies that everyone in tech wants to work at: fast-growing AI and infrastructure startups. Together AI, Cognition, Temporal, AssemblyAI — these are the companies building the next generation of developer tools and AI infrastructure. When you work at Pylon, you’re building the support platform these companies depend on, and your customers are often founders and engineers themselves.
That creates an unusually tight product-feedback loop. Customers don’t just submit tickets — they ping the Pylon team in shared Slack channels (using Pylon, naturally) and describe exactly what they need. Engineers can ship a feature and watch a named customer start using it the same week. That direct product impact is one of the strongest parts of Pylon’s culture.
Engineering at Pylon
With all three founders being engineers, Pylon’s engineering culture is about as engineering-driven as it gets. There’s no separate product org making roadmap decisions while engineers execute. The founders are in the codebase daily, reviewing PRs and shipping features alongside the team. For engineers who want to build rather than attend meetings about building, this is a meaningful signal.
How engineering works
- Ship weekly, not quarterly. Pylon’s shipping cadence is genuinely fast. Features go from idea to production in days, not months. The small team size means there are no multi-week approval processes or cross-functional sign-offs. If the founders agree it’s worth building, you build it.
- Own the full surface. At 70 employees, there are no specialists. You own a customer-facing surface end-to-end: the frontend, the backend, the integrations, the performance. This many-hats approach means rapid skill development but requires comfort with ambiguity.
- Customer proximity. Engineers interact with customers directly. The Slack-native nature of the product means the line between the team using Pylon and customers using Pylon is blurry — intentionally. You see exactly how your work lands.
- Founder code review. PRs get reviewed by the founders. This is a genuine part of the culture, not a bottleneck. At this stage, the founders’ product intuition shapes the codebase in ways that documentation alone can’t replicate.
Who Thrives at Pylon
Pylon is a 70-person Series B startup with a “hardcore” culture label attached. That’s not for everyone, and it’s not trying to be. Based on the culture signals, founder positioning, and employee feedback, here’s who fits:
- Early-career engineers who want career acceleration. The scope of ownership at Pylon is extraordinary for the company size. You will learn more in a year at a 70-person company with strong PMF than in three years at a 5,000-person company. If you want the compressed career trajectory that early startup employees get, Pylon is one of the clearest bets in the market right now.
- Generalists who like to ship fast. If you hate the idea of only touching one part of the stack, Pylon is a great fit. Engineers here work across the full product surface. If you like going from a Slack integration bug in the morning to a new feature deploy in the afternoon, this is your place.
- People energized by winning. Pylon has genuine product-market fit with 5x YoY growth and 150+ migrations from legacy platforms. If you want to join a company where the product is clearly winning and the mission is to capture the market while the window is open, the intensity feels purposeful rather than exhausting.
- B2B builders. If you’re interested in enterprise SaaS, developer tools, or B2B infrastructure, Pylon’s customer base (Together AI, Cognition, Temporal) puts you in direct contact with the most interesting companies in the space. You learn about the B2B ecosystem by serving it daily.
Pylon is not ideal for people who need structure, clear processes, and well-defined career ladders. It’s not for people who want remote-first flexibility — this is a San Francisco office-centric company. And it’s not for people who are looking for a balanced 40-hour week, despite the 4.0 WLB score. The pace is fast and the expectations are high. If you want a startup with more structure, consider Linear (4.4 WLB) or PostHog (4.0 WLB, remote-first). If you want the intense startup energy but at a slightly later stage, Decagon offers a comparable culture at larger scale.
Open Positions at Pylon
Pylon currently has 31 open positions on our platform across engineering, product, and go-to-market roles, primarily in San Francisco. For a 70-person company, hiring 31 roles means the team could grow by nearly 50% — which underscores the growth moment. If the culture and product described here resonate with you, now is an unusually good time to join.
For full details on Pylon’s open roles, culture values, and side-by-side comparisons, visit the Pylon culture profile page or browse all Pylon jobs.
Frequently Asked Questions About Working at Pylon
Explore Pylon & similar startups
See Pylon’s 31 open roles alongside jobs from companies like Decagon, Linear, Granola, and more — all with culture context.
View Pylon Profile → Pylon Jobs →