Checkly

"E2E tests are too slow." "The test pyramid says minimize them." "They're flaky by default." Most of these haven't been true for yearsn but they still drive architecture decisions. Stefan Judis is running through the most persistent Playwright myths at the top of the hour. You still have time to register last minute here: https://lnkd.in/ev-rGs7C

4.25 out of 5. That's the average score candidates gave Checkly's hiring process in 2025, including people who didn't get the job. One person wrote: "I am glad that even though I was not selected to continue the process, I got interviewed anyway. The application form was unique and my time was respected. Thank you." To say that we’re proud of this is quite the understatement. We survey every candidate. We read every response. We try to make the process feel human, even when the answer is no. https://lnkd.in/dz3ivfPX

Thank you so much Rootly, Russel CLIMACO-ESTARDO and all the partners present at #KubeCon Unwind with Checkly! We had a blast last week!

Daniel Paulus asked Claude to add an assertion to a DNS monitor. Claude read the Checkly docs, wrote the code, and deployed it. Then the check failed. Rocky AI analyzed the trace route and explained the root cause. That's the full loop: coding agent builds the monitor, AI debugs the failure. All from the terminal. Link in comments

I don't usually geek out over CLI launches. But today is different. What we shipped today at Checkly genuinely excites me, not just as a product, but as a signal of where we're headed. The short version: AI agents can now use Checkly the same way your engineers do. Create tests, monitor your apps, manage incidents - all autonomously, with guardrails built in. We've always believed Checkly plays a critical role in keeping software running. Now we get to play that role in a world where AI is writing, deploying, and fixing that software too. The software factory is coming. And I think we're going to be right at the center of it. So proud of the team for this one! Links in the comments, would love to hear how your team is thinking about agentic workflows.

Median time from application to offer at Checkly in 2025: 22.5 days. Fastest? 4 days. Here's how each stage broke down (median days, including weekends): 📋 Application review: 1 day 📞 Recruiter screen: 5 days 🧑💼 Hiring manager interview: 6 days ⚒️ Challenge: 9 days 👥 Team interview: 7 days 👔 Executive interview: 6 days 📄 Offer: 3 days The challenge stage only applies to Engineering, Design, Support, and CS roles. GTM and Product moved faster as there was no take-home assignment involved. For People folks: what kept us on pace was a strong internal SLA culture and a hiring team that stayed committed. Candidates' time isn't infinite. We try to act like it. More details 👇 https://lnkd.in/dz3ivfPX

Your agent can now manage your monitoring. npx checkly skills install One command. Your AI agent discovers Checkly, sets up checks, investigates failures, opens incidents, resolves them. All from the terminal. Or Claude. Or Codex. Or Cursor. Or anywhere you are building applications with AI. Write commands implement a confirmation protocol so your agent never takes a public action without your approval. Full details → https://lnkd.in/ehWQRkFb

On March 31, Stefan is running a live session to tackle Playwright and E2E testing myths head-on. Direct answers, rapid-fire, with code. Link in the comments.

Congrats to Tomasz Jaciubek, winner of our booth raffle. Thanks to everyone who entered. We had hundreds of conversations about synthetic monitoring, Monitoring-as-Code, and how AI is changing the way teams set up and manage their monitors: from generating checks with AI agents to root cause analysis with Rocky, our AI-powered debugging assistant. Congrats Tomek!  #KubeCon #CloudNativeCon