Verdict
Submitted 5/15/2026, 12:20:50 AM · Completed 5/15/2026, 12:21:48 AM
Spent the last few months building a free job search engine that aggregates 2.6M+ listings from 100+ ATS sources — no signups, no paywalls
Show original source text →
Strengths
- • Unique value proposition with a free, account-free experience and direct employer links
- • Technical edge with a daily sync pipeline using MotherDuck/DuckDB that normalizes over 100 ATS formats
- • Strong product-market fit, solving a real pain point for job seekers
- • Fast, normalized data layer with sub-second filters
- • Growing job corpus and brand-level trust built around a frictionless experience
Weaknesses
- • Lack of explicit data licensing agreements with ATS platforms poses an existential risk
- • Undefined revenue model, with no clear path to scalable monetization
- • Dependence on scraping/syncing data from ATS platforms without explicit permission
- • Potential for competitors to replicate the data pipeline and API
- • Risk of churn if job seekers find stale listings or if the platform cannot differentiate itself from emerging competitors
Best angle
Aurat.AI Jobs should pivot to focus on employer-facing solutions, such as analytics and boosted listings, to create a scalable revenue model while mitigating platform risk by establishing partnerships with ATS platforms.
Panel verdicts
Viability
meta/llama-4-maverick-17b-128e-instruct
“The key challenge in building Aurat.AI Jobs is normalizing job data across multiple ATS formats.”
Building a job listing aggregator like Aurat.AI Jobs is technically feasible for a solo or 2-person team within 4-12 weeks, but it depends on the scope and complexity of the initial version. The data pipeline, frontend, and database setup are all achievable tasks. However, normalizing job data across 100+ different ATS formats is a significant challenge that requires substantial development time. The use of MotherDuck (DuckDB cloud hosting) simplifies the database deployment, and Next.js + React with Tailwind CSS is a well-established frontend stack. The main complexity lies in handling the diverse data formats from various ATS platforms and maintaining a robust data pipeline. If the initial version (v1) focuses on a subset of ATS platforms and basic search functionality, it's achievable within the given timeframe. However, aiming to support 100+ ATS formats and advanced filtering might be too ambitious for a solo or 2-person team in 4-12 weeks.
Risk
nvidia/llama-3.3-nemotron-super-49b-v1
“Lack of explicit data licensing agreements with ATS platforms poses an existential risk.”
Aurat.AI Jobs faces significant threats from platform risk and regulation, primarily due to its reliance on scraping/syncing data from 100+ ATS platforms without explicit permission. Many ATS platforms have terms of service that prohibit such activities, leading to potential takedown notices or lawsuits. Additionally, the free API endpoint (/data.json) could be exploited by competitors or recruiters, undermining the platform's unique value proposition and potentially leading to legal issues if used in violation of the original ATS terms. Churn is less immediate but could rise if job seekers find stale listings despite daily syncs, or if the platform cannot differentiate itself from emerging competitors. No-budget customers are not a direct issue since the platform is free, but monetization strategies (if pursued) could face challenges.
Market
qwen/qwen3-next-80b-a3b-instruct
“Job seekers crave direct access to listings, but the real money lies in empowering employers to find and track candidates at scale — a gap Aurat.AI is uniquely positioned to fill.”
Aurat.AI Jobs solves a real, painful, and widespread problem: job seekers are frustrated by opaque, recruiter-mediated, account-locked job boards. The target audience is large — millions of active job seekers globally, especially tech-savvy professionals in software, data, and product roles who value transparency and direct access. The product’s technical execution is impressive: syncing 2.6M+ listings from 100+ ATS platforms with clean deduplication and real-time updates is non-trivial and creates a unique moat. The free, no-account model is a strong differentiator against LinkedIn, Indeed, and Glassdoor. The API adds developer appeal and potential for ecosystem growth. However, monetization is unaddressed — without a clear path to revenue (e.g., premium filters, employer analytics, sponsored listings, or recruiter lead gen), this remains a public good, not a scalable business. Also, while the user base is broad, the most willing-to-pay segment — employers and recruiters — aren’t being targeted directly. The product is loved by job seekers but lacks a clear B2B revenue engine. If monetization is added (e.g., employer dashboards showing application volume or candidate sourcing insights), this could easily become a $10M+ ARR business. As-is, it’s a 9/10 product but only an 8/10 business because demand exists, but the business model is underdeveloped.
Competition
nvidia/nemotron-3-nano-omni-30b-a3b-reasoning
“The real defensible advantage is a free, account‑free experience that delivers direct employer links while maintaining a fast, normalized aggregation of millions of listings from many ATS platforms.”
Aurat.AI Jobs differentiates itself by eliminating account requirements, removing recruiter middlemen, and linking directly to employer career pages — a clear user‑experience win that incumbents like Indeed, LinkedIn, and Glassdoor do not provide. Its technical edge — a daily sync pipeline using MotherDuck/DuckDB that normalizes over 100 ATS formats and serves 2.6M+ listings with sub‑second filters — creates a performance moat that is non‑trivial to replicate, though not impossible for larger players with comparable engineering resources. Competitors such as Indeed (massive index but requires login and paywalls for some listings), LinkedIn (social network with apply‑through‑profile), Glassdoor (reviews plus jobs but also account‑heavy), and niche aggregators like Jopwell or RemoteOK lack the combination of free, direct‑apply access and a fast, normalized data layer. While the data‑pipeline and API are replicable, the network effect of a growing job corpus and the brand‑level trust built around a frictionless experience give the venture a durable, though not unassailable, differentiation. The main risk is that a big job board could launch a similar ‘no‑account, direct‑link’ feature, eroding the moat, but until then the combination of UX simplicity and technical speed offers a defensible niche.
Monetization
mistralai/mistral-medium-3.5-128b
“Strong product-market fit but needs a concrete, scalable revenue model beyond 'free for all'.”
The idea addresses a clear pain point—fragmented job listings with middlemen—and solves it with a clean, direct-to-employer search. The technical execution (DuckDB, delta syncs, 2.6M+ listings) is solid, and the free, no-account model lowers friction. However, the revenue model is undefined. Monetization paths could include: (1) **Freemium API**: Charge for high-volume access to `/data.json` (e.g., $0.10 per 1K requests, tiered pricing). (2) **Employer upsells**: Offer 'boosted' listings or analytics (e.g., $200/month for visibility metrics). (3) **Recruiter tools**: Sell bulk exports or advanced filters (e.g., $50/month for Boolean search). Gross margins would be high (90%+) for API/software, but cost-to-serve scales with data volume. The lack of a paywall or ads keeps UX clean but risks under-monetization. Unit economics hinge on conversion: if 1% of 100K monthly users pay $20/month for API access, that’s $20K MRR. The biggest gap is proving employers/recruiters will pay for direct access or data.
Synthesized by meta/llama-3.3-70b-instruct · 23.8s