Aperture vs Comet Browser

“Running a startup means I'm buried in applications every time I post a job. Having an AI conduct initial behavioral screens means I only see candidates who've already demonstrated they can articulate relevant experience. The comparative ranking is more useful than individual scores — it tells me who's best among the pool, not just who cleared a threshold.”

“AI-conducted hiring interviews carry real legal risk — EEOC guidance on automated employment decisions is evolving rapidly, and several states already require human review for consequential hiring choices. The rubric design problem is also unsolved: if the rubric encodes biased assumptions about what 'good' answers look like, the AI will systematically discriminate at scale. I'd want an independent audit before using this for anything above entry-level roles.”

“The category here is AI browser agent, and the direct competitors are Arc with Browse, Chrome's built-in Gemini integration, and every Playwright-wrapper startup that launched in 2024. The specific scenario where Comet breaks: any website with a CAPTCHA, a bot-detection layer, or a dynamic login flow — which is most of the websites people actually need agents to navigate. My 12-month kill prediction: Google ships Gemini-native agentic browsing into Chrome for free and Comet's entire distribution thesis evaporates. To earn a ship, Comet needs to demonstrate a reliable task completion rate above 80% on a published, third-party benchmark — not a cherry-picked demo on a frictionless checkout flow.”

“The hiring funnel is one of the last major business processes that still runs primarily on gut instinct and keyword matching. Aperture points toward a world where assessment of actual competency replaces credential signaling — which is a genuinely more meritocratic outcome if the rubrics are well-designed. The regulatory questions are real, but the direction is right.”

“The thesis Comet is betting on: within 3 years, the browser's primary interface is intent-driven rather than URL-driven, and the agent layer sits below the UI rather than on top of it as an extension. That's a falsifiable, specific bet — and it's one I think is roughly on time, not early. The second-order effect that matters here isn't faster form-filling; it's that Perplexity captures the session-level data that Google currently owns through Chrome, which fundamentally shifts who can build the best personal web model. The dependency that has to hold: agent reliability needs to hit a threshold where users trust it with consequential tasks, not just toy demos, and that threshold is further out than Perplexity's beta launch implies.”

“As someone who hires freelancers frequently, the promise of getting past 'looks great on paper' to actual capability assessment without scheduling 20 intro calls is compelling. Even if I ultimately talk to everyone, having AI pre-screen with behavioral questions means I'm having better conversations with more prepared candidates.”

“The buyer here is unclear in a way that matters: is this a consumer product funded by attention and ads, or a prosumer tool with a subscription model? 'Free beta with pricing TBD' is not a business model, it's a deferral, and for a company that's already raised at a multi-billion valuation, that deferral is a red flag. The moat problem is real — Perplexity's agent layer is only as defensible as its model quality and browser telemetry, and Google can replicate both with Chrome's existing install base. What would need to change: a clear pricing architecture that shows users pay for task completion or saved time, not for a browser they'll abandon the moment Chrome ships the same capability.”

“The job-to-be-done is clean and singular: complete a web task I would otherwise have to do manually. That's a real job, and most tools in this space make users context-switch between a chat interface and a browser, which is exactly the friction Comet eliminates by collapsing them into one surface. The onboarding question I'd need answered before moving this to a strong ship: does a user reach a completed task in their first 2 minutes, or do they spend that time granting permissions and configuring agent scope? The opinion the product needs to have — and may not yet have — is which tasks it's opinionated about doing well versus which it declines, because an agent that attempts everything and fails unpredictably is worse than one that does three things reliably.”