Webflow Career Growth & Development

How does this culture positively impact the work your team produces?

These capabilities help engineers spend less time managing complexity and more time building high-impact solutions. They give our team real leverage, and the impact is clear.

In the last 90 days, Cursor usage is up 80 percent, cycle time is down 21 percent, deployment rates have risen 11 percent, off an already high baseline, and change failure rate remains below 2 percent.

We are now using remote agents in combination with tools like Cursor and Augment Code. This setup enables parallelism for our engineers, making it possible for them to work on many PRs concurrently as they manage a team of remote agents. We see this integrated approach as a promising and exciting development that opens the door to entirely new ways of working and amplifies what our engineers can accomplish.

Testing is another area where AI makes a measurable difference. We use AI code generation tools to generate unit, smoke and functional tests based on recent code changes. These tests are automatically inserted into our continuous integration pipelines and reviewed for coverage and quality. This gives our engineers confidence in every deployment without slowing down release velocity.

What advice would you give to other engineers or engineering leaders interested in creating a culture of learning on their own team?

Start by making learning part of the way your team builds. Give engineers tools that are embedded into their daily workflows and integrate with how they write, review and ship code. The best learning happens through repetition, feedback and visible progress, not in a separate course or doc.

Pair AI with human judgment. Every change should be reviewed by an engineer, whether it was written by a person or generated by a model. Treat code review as a core practice and hold all contributions to the same standard. This keeps quality high and helps engineers sharpen their own ability to evaluate code over time.

Surface context wherever decisions are made. When engineers can ask a question like, “What was decided about the new Designer API?” and immediately find the answer, they stay unblocked and informed. This reduces cognitive overhead and makes it easier for teams to move forward with clarity.

Finally, create space for experimentation while holding a high bar for excellence. AI will not replace engineers, but it will multiply what they are capable of every day, especially when the systems around them are designed to help them learn by building.