Bonded by Love for Product
We’re building Webflow not only for our customers, but for ourselves, too.
In fact, the majority of our engineering team either started as Webflow users, or at the very least want to see it become the default tool for frontend development. We build a product that meets our own expectations and needs. You don’t have to be an experienced Webflow user in order to apply or join our team. However, we do look for engineers who share this fundamental belief: professionals will use visual tools to build production level web sites and apps.
All of us at Webflow share a vision of the future where designers are in charge of handling the look, feel, and UX of the final product, from inception through production. The web is an incredibly powerful medium to share knowledge, start businesses, and build communities, and everyone should have the power to leverage it. Webflow is democratizing access to the web, and empowering creative people to build websites and share their visions with the world.
We build products that developers didn’t think was possible. For example, our Visual CMS, which gives users a way to create a dynamic database, and bind it to the canvas is something that speeds up the development of CMS sites by several orders of magnitude.
We also innovate on the frontend. We pride ourselves by sticking to the HTML and CSS spec, providing a visual abstraction over the technology via our UI. Feel free to take it for a spin by trying out flexboxgame, and CSS Grid.
Creative + Innovative
We’re building a product that has never been built before.
We built the first ever visual CMS, we’re building the first visual Ecommerce (now here!), and we have so much more in our pipeline that will be the first of their kind. Software is eating the world, and we’re building the best possible way for professionals to build software visually. If AWS is making it easier for developers to scale their technology, Webflow makes it easier for developers to build frontends for their websites, apps, and businesses.
Imagine building a complex ecommerce website where you can have pixel perfect control of every part of the design experience, from browsing products to the checkout experience.
The idea for Webflow was born in 2012 when our co-founder and CTO Bryant was working at Vungle (a video advertising startup). His friends Sergie and Vlad (who are also brothers) were frustrated with the limitations that other tools like Wix or Squarespace had. Together, they imagined a better way to build websites, something as simple as the what-you-see-is-what-you-get (aka WYSIWG) CMS solutions, but as professional and fully-featured as Adobe's popular Dreamweaver.
Not only is Webflow great for first-time business owners and freelancers, but reputable organizations like NASA, Dell, and MTV also use our products.
We’re organized into squads that are pretty amorphous.
Engineers at Webflow are organized into two main teams: the frontend team works on the core designer product, and the backend team works on everything else, from hosting infra, our dashboard, and our APIs. People can quickly switch the products they work on and move freely from frontend to backend, or vice versa.
We revolve around "action teams,” which are multi-disciplinary teams made up of engineers, designers, and one PM. Teams orient around a specific feature or product, and work together collaboratively to see through the product. People rotate every few months, to as long as a year (if it's a big effort).
Even if you’ve only had a couple years of work experience, you’ll find opportunities to lead projects and take on tech lead roles. In fact, many of our current tech leads joined Webflow with only ~2 years of work experience. Our three founders Bryant, Vlad, and Sergie lead marketing, engineering, and design, respectively, and they work with nearly everyone in the company directly. We want to support our engineers' growth by being flexible with which teams they join. If you want to build customer facing products, you can. If you’re is infra-focused, we have plenty of opportunities for you as well.
We hope to maintain our flat structure even as we grow the company, allowing multiple people to get experience leading projects and their team members. One of our core principles is to lead by serving others, which means that each person should care personally about the people they work with, and put the success and needs of their team members ahead of their own.
As a distributed company, we want everyone to choose the schedule that works best for them.
The majority of our team members (~65%) are remote. We all try to be online at the same time for a few hours each day. This ends up being in the morning for our San Francisco engineers and in the evening for our European engineers (they end up having later dinners, but that works out given how late Europeans tend to eat!).
For the most part, our backend team is based in San Francisco and our frontend engineers are remote, living and working in Europe and South America. At our headquarters in SF, we have lots of fun activities and always make time to eat lunch together. Our lunches are catered Monday through Thursday, and on Friday, we go out together in SOMA.
We’ve prioritized work/life balance since the beginning, likely because we’ve always had parents on our leadership team. Regardless of where you’re based, we all stick to 40-hour work weeks, and never work weekends unless there is a fire to put out. In order to get to know one another better, we also have an annual treat where we fly everyone in the company to somewhere fun (Cabo in 2017 or Lisbon in 2018!). It’s an amazing time to get to know one another and the best way to re-orient around our company mission of empowering people to build software visually, together.
Ideal for Parents
Five Webflowers became new parents in 2018.
Actually, in the span of 12 months, eight of us became first-time parents including John our Content Strategist, Les a Software Engineer, Nate a Product Designer, and myself (Bryant)! The fact that our leadership team also includes parents, we’ve built a working culture that is not only mindful of parenthood, but also supportive to those in that stage of life. Parents are able to work around their kids’ schedules, even those who do work out of our San Francisco office.
We provide family leave (including adoption) to all parents: a 3-month paid leave for new moms and a paid 2-month leave for new dads. After leave, you can arrange for flexible hours, or even use some days from your leave after you return to work. We are a family-first company!
Below is a picture of Bryant, Webflow’s CTO, taking a break from code reviews by taking his 5-month old daughter on a hike.
Everyone at Webflow is encouraged to embody a founder mentality of ownership.
We try to have everyone in every function ask themselves the question, “What is best for Webflow?” whilst keeping in mind our three stakeholders: (1) customers, (2) employees, and (3) company. Our engineers work closely with design and product at the beginning of each project, and continue to get support and help along the way. We also assign a tech lead or engineering manager to every engineer so that everyone has access to technical assistance. Tech leads rotate on an as needed basis, and yes, everyone gets a chance to lead a project.
We’re organized into loose squads that scale up or down depending on needs and each engineer’s personal interests. Rarely do people work entirely on their own. Your code will always be reviewed by peers and you’ll always have opportunities to participate in other code reviews.
High Employee Retention
We haven’t had any voluntary churn from the engineers since we started Webflow in 2012.
We haven’t taken another dime of venture capital since raising a modest seed round in 2013. We’ve been profitable since then, and have been able to grow to 1M+ users due to positive word-of-mouth. We deliberately chose to take a slow-and-steady approach to growth and as a result, we’ve been able to prioritize the things that matter most: building a fantastic product for our customers to use and an incredible place for our employees to work.
Given our product, mission, and culture, there are plenty of reasons that make Webflow a great place to work as an engineer. Olena (based in London), shared the 10 reasons why she’s loved working here, and Amina (based in Atlanta) has also been known to do random tweets of appreciation. If you’re ever curious about what it’s really like to work somewhere, ask current team members.
We are a team of product-driven engineers.
Understanding the interplay between design, business, and technical challenges is something we highly value at Webflow. Engineers should never think about technical problems in isolation, we should also maintain sight of what what makes a strong product. We care deeply about the product we’re building and not just because we want to see it successfully used by our 30,000 customers, but because we also want to use the product for our own projects (there are a lot of fun/crazy projects by our Webflow team members!).