A practical education
The first useful thing that happened to Alex Yurkowski's startup career was that several startups declined to give him one. Fresh from studying computer science at Notre Dame, he applied to young companies and small businesses. Their answer was discouraging and, he later conceded, probably correct: he did not yet have the experience to be one of the first two or four engineers in the room. Such engineers do not merely receive a ticket. They receive the whole untidy problem, followed immediately by another.
So Yurkowski went to IBM. It was not the romantic version of the plan. It was the useful version. The large company offered colleagues, systems and accumulated knowledge. He learned enough to understand why those startups had hesitated, and enough to become the kind of engineer they had needed. The apparent detour supplied the map.
This was a natural destination for a child who grew up in New Jersey playing Warcraft and StarCraft, assembling Lego and K'Nex, and gravitating toward mathematics, science and computers. In an interview years later, Yurkowski sounded almost apologetic about having known his direction early. He liked computers. He liked building things. Computer science followed without a grand conversion scene.
The side project with better manners
After IBM, Yurkowski joined Zeb Evans in Los Angeles. They were working on another product, but their working life had become scattered across project-management systems, messaging products and documents. The tools were meant to improve productivity. The daily experience felt more like administrating the tools.
The team built its own system, originally for itself. This is the charmingly impolite part of ClickUp's origin: the internal utility interrupted the business it was supposed to assist. It proved more compelling than the original project. By 2017, ClickUp was the company.
Investors and observers offered familiar advice. Choose a market. Pick a vertical. Do one thing for one kind of customer. Yurkowski and Evans had arrived at the opposite conviction. They disliked software that insisted upon one correct workflow. They wanted a platform broad enough for the user to decide how the work should look, with features that could be switched on or off rather than endured.
The first paying customer made the case more neatly than a strategy memo could: a jiu-jitsu gym. It used the product to schedule tasks and team work. The same system could serve engineers, marketers, a large company or two people organizing chores. Breadth creates its own dangers, of course. An everything app can become a junk drawer with authentication. Yurkowski's answer was not to deny complexity, but to make it optional and configurable.
December 2020
October 2021
the Series C
Architecture without theatre
Yurkowski's public engineering conversations are notable for how little ceremony he brings to them. Early ClickUp used a Node.js backend, PostgreSQL, an Angular frontend and AWS. The codebase began as a monolith because a monolith was faster to build. Services separated when imports, notifications and heavier integrations created a reason for them to separate. The architecture changed when reality presented the invoice.
The team stayed with Angular even when moving to React became the fashionable migration. They had a conversation about it, Yurkowski said, but it did not really matter. They wanted to keep moving forward. ClickUp also managed its own PostgreSQL instances on AWS to retain the control required for bidirectional replication across regions. It added Elasticsearch for search and Redis for caching, but kept the original spine recognizable.
That pragmatism should not be confused with carelessness. Yurkowski has been blunt that compliance is not a synonym for security. A SOC 2 process may require controls, documentation and evidence, but a certificate does not remove the need for code reviews, penetration testing and automated checks. He describes security as work embedded in the pipeline, not a framed document waiting in reception.
Speed, in this system, comes from reducing distance. ClickUp's engineering team used small actionable work items, sprint planning and communication across product, quality assurance, marketing and support. Dashboards surfaced capacity and bottlenecks. The aim was a weekly release rhythm, but the more interesting mechanism was emotional: Yurkowski wanted developers to see praise as well as bug reports. Engineers easily receive every defect and none of the delight. Customer value becomes abstract if the good news never travels back.
The CTO who puts his phone in its place
The founder of a productivity platform has an occupational obligation to possess at least one useful quirk. Yurkowski's is notification control. He has described checking notifications in batches on his computer. Calls are generally scheduled. An Apple Watch can alert him when one arrives, but the phone does not enjoy an unrestricted right to his attention.
This small habit is consistent with the larger product argument. A tool should accommodate the person using it. The person should not become unpaid staff for the tool. He made the point more broadly in 2021: work is not a license for bad user experience. It is possible to dislike your project-management software and go elsewhere.
Even his personal use of ClickUp was ordinary rather than evangelical. He described a dashboard that gathered the day's work beside private errands, including the stubborn little obligations such as renewing a license. He did not claim to run every domestic conversation through a task database. The distinction is sensible. Productivity software is useful when it remembers what a person would otherwise carry around in the head; it becomes comedy when the system requires more tending than the obligation itself.
The same practical eye shaped ClickUp's early hiring. Yurkowski looked for work ethic and an understanding of what the team was building and why. Some early developers had worked with Evans before; others joined while the founders were still pursuing their original product. A few remained through the pivot. Culture, Yurkowski said, was not invented in a meeting. The first five or six people worked together for years, then examined which habits were succeeding and wrote those down as values.
A public trail of practical problems
Before the funding headlines, Yurkowski was asking and answering the sorts of questions that fill an engineer's afternoon: Node.js process failures, AWS email behavior, Jenkins branch names, GitHub mergeability and Google Calendar edge cases. His Stack Overflow posts reached hundreds of thousands of readers. The archive is less polished than a founder biography and more revealing.
The weekly half hour that closes the loop
ClickUp eventually acquired the large numbers that attach themselves to software companies. In December 2020 it raised a $100 million Series B. Ten months later, a $400 million Series C valued the company at $4 billion and brought disclosed funding to $535 million. The product expanded from tasks into documents, whiteboards, chat and, by ClickUp 4.0, a redesigned workspace connecting work and AI.
Yet Yurkowski's more recent work brings the story back to where it began: students who know they want to build and need practice converting that appetite into a product. At Notre Dame's Innovation Sprint Lab, he has served as a technical mentor to entrepreneurial student teams. The arrangement is modest and specific: thirty minutes each week with the co-founder and CTO.
In a public note after the 2025 semester, Yurkowski singled out Joshua Tighe for handling difficult team dynamics, contributing frontend work and helping colleagues ramp up. He praised Khang Le as the person teammates trusted with complex problems, and as a sprint lead who kept work moving while holding people accountable. The compliments reveal his scorecard. Technical ability matters. So do communication, momentum and making the rest of the team better.
Notre Dame's student entrepreneurship program later recognized Yurkowski and Justin Hintz with a 2026 Program Builder Award for creating hands-on opportunities that pair computer science students with real feature development. ClickUp returned to the lab for fall 2026. The engineer who once needed experience before a startup would hire him is now helping students obtain precisely that kind of experience.
There is no need to force a grand symmetry onto it. The symmetry is already doing fine. A boy builds with plastic bricks. A student learns computer science. A graduate receives an inconvenient no, then an education at IBM. A founder makes a tool because the available tools do not behave. Years later, he gives student builders half an hour each week so their own detours may be shorter, or at least more useful. Yurkowski kept moving forward. The road, obligingly, became a product.