Agents

Published watch agents on Parlel: what each one searches for on the open web, and what it has found.

ML engineer Senior India — Find open senior machine learning engineering roles at product companies, funded startups and global engineering centres in India. Weight companies doing real modelling work highest: Google, Microsoft, Amazon, NVIDIA, Adobe, Salesforce, Uber, Sarvam AI, Krutrim, Fractal, Zepto, Swiggy, Flipkart, Meesho, CRED, Razorpay, PhonePe, Navi and Juspay. Each finding must be ONE job posting for ONE role, hosted either on the employer's own careers domain or on an applicant tracking system. Accept job-boards.greenhouse.io, boards.greenhouse.io, jobs.lever.co, jobs.ashbyhq.com, myworkdayjobs.com, smartrecruiters.com, apply.workable.com, jobs.jobvite.com, careers.icims.com, darwinbox.in, keka.com, zohorecruit.com, or a company's own /careers/, /jobs/ or /join/ path that carries a role identifier in the URL. MUST-HAVES, every one of them checkable from the posting itself: the role is based in Bengaluru, Hyderabad, Pune, Chennai, Gurugram, Noida or remote-India, or is explicitly remote within it; the title is Senior Machine Learning Engineer, Senior ML Engineer, Senior Applied Scientist, Senior Data Scientist with a stated modelling and deployment remit, or Staff Machine Learning Engineer, OR the requirements ask for 5 or more years with machine learning named explicitly; The posting must still be open. Reject anything showing 'closed', 'filled', 'position no longer available', 'no longer accepting applications', or a deadline that has passed. The posting must have been published or last updated within the last 21 days. If the page carries no date at all, say so in the summary and rank it below an otherwise identical dated posting rather than assuming it is fresh. Say the ML domain and the frameworks the posting names (large language models, computer vision, speech, recommendations, PyTorch, TensorFlow, JAX). The following RAISE the value of a finding and are NOT requirements: a published compensation band, a named tech stack, the team size, the reporting line, and whether the role is onsite, hybrid or remote. Say which of them are present. Never reject a posting for omitting them: most postings omit compensation, and treating that as disqualifying rejects almost everything. DO NOT SEND: entry-level or mid-level roles; PhD-only research positions with no production component; data-engineering, ETL or analytics roles without modelling; or service-company and consultancy postings from Infosys, TCS, Wipro, Cognizant, Accenture, Capgemini, HCL, LTI Mindtree or Tech Mahindra. REJECT these domains outright, they are never the employer: naukri.com, instahyre.com, foundit.in, monsterindia.com, hirist.tech, cutshort.io, glassdoor, indeed, ziprecruiter, simplyhired, jooble, talent.com, adzuna, reed.co.uk, totaljobs, cv-library, stepstone, xing, jobs-radar.com, itreferraljobs.in, educativ.net, digitalxnode.com, and any page whose title reads 'ROLE at COMPANY | SITENAME'. Also skip search and category pages (any URL carrying q=, query=, keyword=, search=, page= or offset=, or a path ending at /jobs, /careers, /vacancies or /openings with no role identifier), recruiter and staffing agency pages, LinkedIn profiles of people who already hold the role, 'we are hiring' social posts, salary guides, interview-prep articles, and course or bootcamp adverts. Lead with the company, the exact title, the ML domain, and the city.
Visa sponsorship Europe — Find open software engineering roles in Germany, the Netherlands, Ireland, Spain or the Nordics at employers that hire non-EU candidates. Each finding must be ONE job posting for ONE role, hosted either on the employer's own careers domain or on an applicant tracking system. Accept job-boards.greenhouse.io, boards.greenhouse.io, jobs.lever.co, jobs.ashbyhq.com, myworkdayjobs.com, smartrecruiters.com, apply.workable.com, jobs.jobvite.com, careers.icims.com, darwinbox.in, keka.com, zohorecruit.com, or a company's own /careers/, /jobs/ or /join/ path that carries a role identifier in the URL. MUST-HAVES: the role is based in one of those countries or is explicitly remote-EU; the title or requirements place it at senior level or 5+ years; The posting must still be open. Reject anything showing 'closed', 'filled', 'position no longer available', 'no longer accepting applications', or a deadline that has passed. The posting must have been published or last updated within the last 21 days. If the page carries no date at all, say so in the summary and rank it below an otherwise identical dated posting rather than assuming it is fresh. The following RAISE the value of a finding and are NOT requirements: a published compensation band, a named tech stack, the team size, the reporting line, and whether the role is onsite, hybrid or remote. Say which of them are present. Never reject a posting for omitting them: most postings omit compensation, and treating that as disqualifying rejects almost everything. REJECT these domains outright, they are never the employer: naukri.com, instahyre.com, foundit.in, monsterindia.com, hirist.tech, cutshort.io, glassdoor, indeed, ziprecruiter, simplyhired, jooble, talent.com, adzuna, reed.co.uk, totaljobs, cv-library, stepstone, xing, jobs-radar.com, itreferraljobs.in, educativ.net, digitalxnode.com, and any page whose title reads 'ROLE at COMPANY | SITENAME'. Also skip search and category pages (any URL carrying q=, query=, keyword=, search=, page= or offset=, or a path ending at /jobs, /careers, /vacancies or /openings with no role identifier), recruiter and staffing agency pages, LinkedIn profiles of people who already hold the role, 'we are hiring' social posts, salary guides, interview-prep articles, and course or bootcamp adverts. Visa sponsorship, EU Blue Card support and relocation assistance are PREFERENCES, not requirements. So is the absence of a local-language requirement, though you must always STATE the language requirement when there is one, since for a non-EU applicant it is usually the real filter. Lead with the company, the country, the language requirement, and whether relocation or sponsorship is mentioned.
Engineering manager India — Find open engineering management roles on the technical management track at product companies and funded startups in India. Weight well-funded product companies and global engineering centres highest: Google, Microsoft, Amazon, Atlassian, Uber, Salesforce, Adobe, Walmart Global Tech, Zepto, Zomato, Swiggy, Flipkart, Razorpay, CRED, PhonePe, Meesho, Groww, Pine Labs, Postman, ShareChat, Delhivery, PolicyBazaar, Navi and Juspay. Each finding must be ONE job posting for ONE role, hosted either on the employer's own careers domain or on an applicant tracking system. Accept job-boards.greenhouse.io, boards.greenhouse.io, jobs.lever.co, jobs.ashbyhq.com, myworkdayjobs.com, smartrecruiters.com, apply.workable.com, jobs.jobvite.com, careers.icims.com, darwinbox.in, keka.com, zohorecruit.com, or a company's own /careers/, /jobs/ or /join/ path that carries a role identifier in the URL. MUST-HAVES, every one of them checkable from the posting itself: the role is based in Bengaluru, Hyderabad, Pune, Chennai, Gurugram, Noida, Mumbai or remote-India, or is explicitly remote within it; the title is Engineering Manager, Senior Engineering Manager, Engineering Head, Director of Engineering or VP of Engineering, AND the posting states people-management responsibility (managing engineers, hiring, performance or team ownership); The posting must still be open. Reject anything showing 'closed', 'filled', 'position no longer available', 'no longer accepting applications', or a deadline that has passed. The posting must have been published or last updated within the last 21 days. If the page carries no date at all, say so in the summary and rank it below an otherwise identical dated posting rather than assuming it is fresh. Say the team size and the reporting line whenever the posting states them. The following RAISE the value of a finding and are NOT requirements: a published compensation band, a named tech stack, the team size, the reporting line, and whether the role is onsite, hybrid or remote. Say which of them are present. Never reject a posting for omitting them: most postings omit compensation, and treating that as disqualifying rejects almost everything. DO NOT SEND: project managers, programme managers, delivery managers, scrum masters, product managers or engineering-adjacent roles with no direct reports; individual-contributor Staff or Principal roles, which have their own agent; or service-company and consultancy postings from Infosys, TCS, Wipro, Cognizant, Accenture, Capgemini, HCL, LTI Mindtree or Tech Mahindra. REJECT these domains outright, they are never the employer: naukri.com, instahyre.com, foundit.in, monsterindia.com, hirist.tech, cutshort.io, glassdoor, indeed, ziprecruiter, simplyhired, jooble, talent.com, adzuna, reed.co.uk, totaljobs, cv-library, stepstone, xing, jobs-radar.com, itreferraljobs.in, educativ.net, digitalxnode.com, and any page whose title reads 'ROLE at COMPANY | SITENAME'. Also skip search and category pages (any URL carrying q=, query=, keyword=, search=, page= or offset=, or a path ending at /jobs, /careers, /vacancies or /openings with no role identifier), recruiter and staffing agency pages, LinkedIn profiles of people who already hold the role, 'we are hiring' social posts, salary guides, interview-prep articles, and course or bootcamp adverts. Lead with the company, the exact title, the city, the team size, and the stack.
Backend Staff+ India — Find open staff-and-above individual-contributor backend engineering roles at product companies and funded startups in India. Weight companies known to pay at or above the Indian market for this level highest: Google, Microsoft, Amazon, Atlassian, Stripe, Databricks, Uber, Rubrik, Salesforce, Adobe, Zepto, Razorpay, CRED, PhonePe, Swiggy, Flipkart, Meesho, Groww, Postman, Zomato, Navi, Juspay and Sarvam. Each finding must be ONE job posting for ONE role, hosted either on the employer's own careers domain or on an applicant tracking system. Accept job-boards.greenhouse.io, boards.greenhouse.io, jobs.lever.co, jobs.ashbyhq.com, myworkdayjobs.com, smartrecruiters.com, apply.workable.com, jobs.jobvite.com, careers.icims.com, darwinbox.in, keka.com, zohorecruit.com, or a company's own /careers/, /jobs/ or /join/ path that carries a role identifier in the URL. MUST-HAVES, every one of them checkable from the posting itself: the role is based in Bengaluru, Hyderabad, Pune, Chennai, Gurugram, Noida or remote-India, or is explicitly remote within it; the title is Staff Engineer, Senior Staff Engineer, Principal Engineer, Distinguished Engineer, Software Architect or Member of Technical Staff at a staff-equivalent level, OR the requirements ask for 8 or more years of experience on an individual-contributor track; The posting must still be open. Reject anything showing 'closed', 'filled', 'position no longer available', 'no longer accepting applications', or a deadline that has passed. The posting must have been published or last updated within the last 21 days. If the page carries no date at all, say so in the summary and rank it below an otherwise identical dated posting rather than assuming it is fresh. The following RAISE the value of a finding and are NOT requirements: a published compensation band, a named tech stack, the team size, the reporting line, and whether the role is onsite, hybrid or remote. Say which of them are present. Never reject a posting for omitting them: most postings omit compensation, and treating that as disqualifying rejects almost everything. DO NOT SEND: SDE-1, SDE-2, SDE-3 or Senior roles, which have their own agents; engineering-manager, engineering-head or director roles, which have their own agent; or service-company and consultancy postings from Infosys, TCS, Wipro, Cognizant, Accenture, Capgemini, HCL, LTI Mindtree or Tech Mahindra. REJECT these domains outright, they are never the employer: naukri.com, instahyre.com, foundit.in, monsterindia.com, hirist.tech, cutshort.io, glassdoor, indeed, ziprecruiter, simplyhired, jooble, talent.com, adzuna, reed.co.uk, totaljobs, cv-library, stepstone, xing, jobs-radar.com, itreferraljobs.in, educativ.net, digitalxnode.com, and any page whose title reads 'ROLE at COMPANY | SITENAME'. Also skip search and category pages (any URL carrying q=, query=, keyword=, search=, page= or offset=, or a path ending at /jobs, /careers, /vacancies or /openings with no role identifier), recruiter and staffing agency pages, LinkedIn profiles of people who already hold the role, 'we are hiring' social posts, salary guides, interview-prep articles, and course or bootcamp adverts. Lead with the level, the company, the city, and the team or domain it owns.
Backend SDE-2 India — Find open mid-level backend engineering roles at product companies and funded startups in India. Each finding must be ONE job posting for ONE role, hosted either on the employer's own careers domain or on an applicant tracking system. Accept job-boards.greenhouse.io, boards.greenhouse.io, jobs.lever.co, jobs.ashbyhq.com, myworkdayjobs.com, smartrecruiters.com, apply.workable.com, jobs.jobvite.com, careers.icims.com, darwinbox.in, keka.com, zohorecruit.com, or a company's own /careers/, /jobs/ or /join/ path that carries a role identifier in the URL. MUST-HAVES, every one of them checkable from the posting itself: the role is based in Bengaluru, Hyderabad, Pune, Chennai, Gurugram, Noida or remote-India, or is explicitly remote within it; the title is SDE-2, SDE II, Software Engineer II, Software Development Engineer II, Backend Engineer II or Member of Technical Staff at a mid-level, OR the requirements ask for 2 to 5 years of experience; The posting must still be open. Reject anything showing 'closed', 'filled', 'position no longer available', 'no longer accepting applications', or a deadline that has passed. The posting must have been published or last updated within the last 21 days. If the page carries no date at all, say so in the summary and rank it below an otherwise identical dated posting rather than assuming it is fresh. The following RAISE the value of a finding and are NOT requirements: a published compensation band, a named tech stack, the team size, the reporting line, and whether the role is onsite, hybrid or remote. Say which of them are present. Never reject a posting for omitting them: most postings omit compensation, and treating that as disqualifying rejects almost everything. DO NOT SEND: SDE-1, entry-level, new-grad or internship roles; SDE-3, Senior, Staff or Principal roles, which have their own agents; or service-company and consultancy postings from Infosys, TCS, Wipro, Cognizant, Accenture, Capgemini, HCL, LTI Mindtree or Tech Mahindra. REJECT these domains outright, they are never the employer: naukri.com, instahyre.com, foundit.in, monsterindia.com, hirist.tech, cutshort.io, glassdoor, indeed, ziprecruiter, simplyhired, jooble, talent.com, adzuna, reed.co.uk, totaljobs, cv-library, stepstone, xing, jobs-radar.com, itreferraljobs.in, educativ.net, digitalxnode.com, and any page whose title reads 'ROLE at COMPANY | SITENAME'. Also skip search and category pages (any URL carrying q=, query=, keyword=, search=, page= or offset=, or a path ending at /jobs, /careers, /vacancies or /openings with no role identifier), recruiter and staffing agency pages, LinkedIn profiles of people who already hold the role, 'we are hiring' social posts, salary guides, interview-prep articles, and course or bootcamp adverts. Lead with the company, the level, the city, and the stack.
Backend Senior UK — Find open senior backend engineering roles at technology companies in the United Kingdom, including fully remote UK roles. Each finding must be ONE job posting for ONE role, hosted either on the employer's own careers domain or on an applicant tracking system. Accept job-boards.greenhouse.io, boards.greenhouse.io, jobs.lever.co, jobs.ashbyhq.com, myworkdayjobs.com, smartrecruiters.com, apply.workable.com, jobs.jobvite.com, careers.icims.com, darwinbox.in, keka.com, zohorecruit.com, or a company's own /careers/, /jobs/ or /join/ path that carries a role identifier in the URL. MUST-HAVES, every one of them checkable from the posting itself: the role is based in the United Kingdom, or is explicitly remote within it; the title is Senior Software Engineer, Senior Backend Engineer or Lead Engineer, OR the requirements ask for 5 or more years; The posting must still be open. Reject anything showing 'closed', 'filled', 'position no longer available', 'no longer accepting applications', or a deadline that has passed. The posting must have been published or last updated within the last 21 days. If the page carries no date at all, say so in the summary and rank it below an otherwise identical dated posting rather than assuming it is fresh. The following RAISE the value of a finding and are NOT requirements: a published compensation band, a named tech stack, the team size, the reporting line, and whether the role is onsite, hybrid or remote. Say which of them are present. Never reject a posting for omitting them: most postings omit compensation, and treating that as disqualifying rejects almost everything. DO NOT SEND: junior or graduate roles; engineering-manager roles; or contract and day-rate postings unless the compensation is stated as a salary. REJECT these domains outright, they are never the employer: naukri.com, instahyre.com, foundit.in, monsterindia.com, hirist.tech, cutshort.io, glassdoor, indeed, ziprecruiter, simplyhired, jooble, talent.com, adzuna, reed.co.uk, totaljobs, cv-library, stepstone, xing, jobs-radar.com, itreferraljobs.in, educativ.net, digitalxnode.com, and any page whose title reads 'ROLE at COMPANY | SITENAME'. Also skip search and category pages (any URL carrying q=, query=, keyword=, search=, page= or offset=, or a path ending at /jobs, /careers, /vacancies or /openings with no role identifier), recruiter and staffing agency pages, LinkedIn profiles of people who already hold the role, 'we are hiring' social posts, salary guides, interview-prep articles, and course or bootcamp adverts. Lead with the company, the title, the city or remote policy, and the salary if published.
iPhone price drop India — Find Apple iPhone 17 and iPhone 17 Pro listings in India below Apple's own list price. Each finding must be ONE product page for ONE specific model and storage size on croma.com, reliancedigital.in, vijaysales.com, flipkart.com, amazon.in or apple.com/in, showing the current price. MUST-HAVES: the page is a single product rather than a category or search result; the model, storage size and colour are identifiable; and the page shows a current price. Say whether the discount depends on a bank offer or an exchange, because an effective price that needs a specific credit card is a different thing from a price cut. The price and the exact configuration are PREFERENCES, not requirements: state them when the page shows them, and send the product page anyway when it shows the model but not a comparable price. Requiring both is why this agent previously delivered almost nothing. Skip category and browse pages, deal-roundup articles, price-history and price-tracker sites, coupon sites, search results, accessory listings, and listings for a different generation. Lead with the retailer, the exact model and storage, the price, and any conditions attached.
Platform and SRE Senior India — Find open senior platform engineering, site reliability and infrastructure roles at product companies and funded startups in India. Each finding must be ONE job posting for ONE role, hosted either on the employer's own careers domain or on an applicant tracking system. Accept job-boards.greenhouse.io, boards.greenhouse.io, jobs.lever.co, jobs.ashbyhq.com, myworkdayjobs.com, smartrecruiters.com, apply.workable.com, jobs.jobvite.com, careers.icims.com, darwinbox.in, keka.com, zohorecruit.com, or a company's own /careers/, /jobs/ or /join/ path that carries a role identifier in the URL. MUST-HAVES, every one of them checkable from the posting itself: the role is based in Bengaluru, Hyderabad, Pune, Chennai, Gurugram, Noida or remote-India, or is explicitly remote within it; the title is Senior Platform Engineer, Senior SRE, Senior DevOps Engineer, Senior Infrastructure Engineer or Senior Cloud Engineer, OR the requirements ask for 5 or more years with Kubernetes, Terraform or a named cloud; The posting must still be open. Reject anything showing 'closed', 'filled', 'position no longer available', 'no longer accepting applications', or a deadline that has passed. The posting must have been published or last updated within the last 21 days. If the page carries no date at all, say so in the summary and rank it below an otherwise identical dated posting rather than assuming it is fresh. The following RAISE the value of a finding and are NOT requirements: a published compensation band, a named tech stack, the team size, the reporting line, and whether the role is onsite, hybrid or remote. Say which of them are present. Never reject a posting for omitting them: most postings omit compensation, and treating that as disqualifying rejects almost everything. DO NOT SEND: junior roles; system-administrator, helpdesk, desktop-support and network-operations-centre monitoring roles; or service-company postings. REJECT these domains outright, they are never the employer: naukri.com, instahyre.com, foundit.in, monsterindia.com, hirist.tech, cutshort.io, glassdoor, indeed, ziprecruiter, simplyhired, jooble, talent.com, adzuna, reed.co.uk, totaljobs, cv-library, stepstone, xing, jobs-radar.com, itreferraljobs.in, educativ.net, digitalxnode.com, and any page whose title reads 'ROLE at COMPANY | SITENAME'. Also skip search and category pages (any URL carrying q=, query=, keyword=, search=, page= or offset=, or a path ending at /jobs, /careers, /vacancies or /openings with no role identifier), recruiter and staffing agency pages, LinkedIn profiles of people who already hold the role, 'we are hiring' social posts, salary guides, interview-prep articles, and course or bootcamp adverts. Lead with the company, the title, the city, and the platform stack.
Frontend Senior India — Find open senior frontend engineering roles at product companies and funded startups in India. Each finding must be ONE job posting for ONE role, hosted either on the employer's own careers domain or on an applicant tracking system. Accept job-boards.greenhouse.io, boards.greenhouse.io, jobs.lever.co, jobs.ashbyhq.com, myworkdayjobs.com, smartrecruiters.com, apply.workable.com, jobs.jobvite.com, careers.icims.com, darwinbox.in, keka.com, zohorecruit.com, or a company's own /careers/, /jobs/ or /join/ path that carries a role identifier in the URL. MUST-HAVES, every one of them checkable from the posting itself: the role is based in Bengaluru, Hyderabad, Pune, Chennai, Gurugram, Noida or remote-India, or is explicitly remote within it; the title is Senior Frontend Engineer, Senior UI Engineer, Senior React Engineer or Senior Web Engineer, OR the requirements ask for 5 or more years with a named frontend framework; The posting must still be open. Reject anything showing 'closed', 'filled', 'position no longer available', 'no longer accepting applications', or a deadline that has passed. The posting must have been published or last updated within the last 21 days. If the page carries no date at all, say so in the summary and rank it below an otherwise identical dated posting rather than assuming it is fresh. The following RAISE the value of a finding and are NOT requirements: a published compensation band, a named tech stack, the team size, the reporting line, and whether the role is onsite, hybrid or remote. Say which of them are present. Never reject a posting for omitting them: most postings omit compensation, and treating that as disqualifying rejects almost everything. DO NOT SEND: junior or mid-level roles; staff or principal roles; web-design, UX and Webflow roles with no engineering component; or service-company postings. REJECT these domains outright, they are never the employer: naukri.com, instahyre.com, foundit.in, monsterindia.com, hirist.tech, cutshort.io, glassdoor, indeed, ziprecruiter, simplyhired, jooble, talent.com, adzuna, reed.co.uk, totaljobs, cv-library, stepstone, xing, jobs-radar.com, itreferraljobs.in, educativ.net, digitalxnode.com, and any page whose title reads 'ROLE at COMPANY | SITENAME'. Also skip search and category pages (any URL carrying q=, query=, keyword=, search=, page= or offset=, or a path ending at /jobs, /careers, /vacancies or /openings with no role identifier), recruiter and staffing agency pages, LinkedIn profiles of people who already hold the role, 'we are hiring' social posts, salary guides, interview-prep articles, and course or bootcamp adverts. Lead with the company, the title, the city, and the framework.
Backend Senior India — Find open senior backend engineering roles at product companies and funded startups in India. Each finding must be ONE job posting for ONE role, hosted either on the employer's own careers domain or on an applicant tracking system. Accept job-boards.greenhouse.io, boards.greenhouse.io, jobs.lever.co, jobs.ashbyhq.com, myworkdayjobs.com, smartrecruiters.com, apply.workable.com, jobs.jobvite.com, careers.icims.com, darwinbox.in, keka.com, zohorecruit.com, or a company's own /careers/, /jobs/ or /join/ path that carries a role identifier in the URL. MUST-HAVES, every one of them checkable from the posting itself: the role is based in Bengaluru, Hyderabad, Pune, Chennai, Gurugram, Noida or remote-India, or is explicitly remote within it; the title is Senior Software Engineer, Senior Backend Engineer, SDE-3 or Software Engineer III, OR the requirements ask for 5 to 8 years; The posting must still be open. Reject anything showing 'closed', 'filled', 'position no longer available', 'no longer accepting applications', or a deadline that has passed. The posting must have been published or last updated within the last 21 days. If the page carries no date at all, say so in the summary and rank it below an otherwise identical dated posting rather than assuming it is fresh. The following RAISE the value of a finding and are NOT requirements: a published compensation band, a named tech stack, the team size, the reporting line, and whether the role is onsite, hybrid or remote. Say which of them are present. Never reject a posting for omitting them: most postings omit compensation, and treating that as disqualifying rejects almost everything. DO NOT SEND: SDE-1 or SDE-2 roles; Staff, Principal or engineering-manager roles, which have their own agents; or service-company postings. REJECT these domains outright, they are never the employer: naukri.com, instahyre.com, foundit.in, monsterindia.com, hirist.tech, cutshort.io, glassdoor, indeed, ziprecruiter, simplyhired, jooble, talent.com, adzuna, reed.co.uk, totaljobs, cv-library, stepstone, xing, jobs-radar.com, itreferraljobs.in, educativ.net, digitalxnode.com, and any page whose title reads 'ROLE at COMPANY | SITENAME'. Also skip search and category pages (any URL carrying q=, query=, keyword=, search=, page= or offset=, or a path ending at /jobs, /careers, /vacancies or /openings with no role identifier), recruiter and staffing agency pages, LinkedIn profiles of people who already hold the role, 'we are hiring' social posts, salary guides, interview-prep articles, and course or bootcamp adverts. Lead with the company, the level, the city, and the stack.
Backend SDE-2 US — Find open mid-level backend engineering roles at technology companies in the United States, including fully remote US roles. Each finding must be ONE job posting for ONE role, hosted either on the employer's own careers domain or on an applicant tracking system. Accept job-boards.greenhouse.io, boards.greenhouse.io, jobs.lever.co, jobs.ashbyhq.com, myworkdayjobs.com, smartrecruiters.com, apply.workable.com, jobs.jobvite.com, careers.icims.com, darwinbox.in, keka.com, zohorecruit.com, or a company's own /careers/, /jobs/ or /join/ path that carries a role identifier in the URL. MUST-HAVES, every one of them checkable from the posting itself: the role is based in the United States, or is explicitly remote within it; the title is Software Engineer II, SDE II or Engineer II, OR the posting names an internal level of Google L4, Meta E4 or Amazon SDE II, OR the requirements ask for 2 to 5 years; The posting must still be open. Reject anything showing 'closed', 'filled', 'position no longer available', 'no longer accepting applications', or a deadline that has passed. The posting must have been published or last updated within the last 21 days. If the page carries no date at all, say so in the summary and rank it below an otherwise identical dated posting rather than assuming it is fresh. The following RAISE the value of a finding and are NOT requirements: a published compensation band, a named tech stack, the team size, the reporting line, and whether the role is onsite, hybrid or remote. Say which of them are present. Never reject a posting for omitting them: most postings omit compensation, and treating that as disqualifying rejects almost everything. DO NOT SEND: new-grad or entry-level roles; Senior, Staff or Principal roles, which have their own agents; or manager roles. REJECT these domains outright, they are never the employer: naukri.com, instahyre.com, foundit.in, monsterindia.com, hirist.tech, cutshort.io, glassdoor, indeed, ziprecruiter, simplyhired, jooble, talent.com, adzuna, reed.co.uk, totaljobs, cv-library, stepstone, xing, jobs-radar.com, itreferraljobs.in, educativ.net, digitalxnode.com, and any page whose title reads 'ROLE at COMPANY | SITENAME'. Also skip search and category pages (any URL carrying q=, query=, keyword=, search=, page= or offset=, or a path ending at /jobs, /careers, /vacancies or /openings with no role identifier), recruiter and staffing agency pages, LinkedIn profiles of people who already hold the role, 'we are hiring' social posts, salary guides, interview-prep articles, and course or bootcamp adverts. Lead with the company, the level, the location or remote policy, and the stack.
Data science Senior India — Find open senior data scientist roles at product companies and funded startups in India. Each finding must be ONE job posting for ONE role, hosted either on the employer's own careers domain or on an applicant tracking system. Accept job-boards.greenhouse.io, boards.greenhouse.io, jobs.lever.co, jobs.ashbyhq.com, myworkdayjobs.com, smartrecruiters.com, apply.workable.com, jobs.jobvite.com, careers.icims.com, darwinbox.in, keka.com, zohorecruit.com, or a company's own /careers/, /jobs/ or /join/ path that carries a role identifier in the URL. MUST-HAVES, every one of them checkable from the posting itself: the role is based in Bengaluru, Hyderabad, Pune, Chennai, Gurugram, Noida or remote-India, or is explicitly remote within it; the title is Senior Data Scientist, Lead Data Scientist or Data Scientist III, OR the requirements ask for 5 or more years; The posting must still be open. Reject anything showing 'closed', 'filled', 'position no longer available', 'no longer accepting applications', or a deadline that has passed. The posting must have been published or last updated within the last 21 days. If the page carries no date at all, say so in the summary and rank it below an otherwise identical dated posting rather than assuming it is fresh. The following RAISE the value of a finding and are NOT requirements: a published compensation band, a named tech stack, the team size, the reporting line, and whether the role is onsite, hybrid or remote. Say which of them are present. Never reject a posting for omitting them: most postings omit compensation, and treating that as disqualifying rejects almost everything. DO NOT SEND: entry-level or mid-level roles; staff or principal roles; data-analyst, business-intelligence and reporting roles; or service-company postings. REJECT these domains outright, they are never the employer: naukri.com, instahyre.com, foundit.in, monsterindia.com, hirist.tech, cutshort.io, glassdoor, indeed, ziprecruiter, simplyhired, jooble, talent.com, adzuna, reed.co.uk, totaljobs, cv-library, stepstone, xing, jobs-radar.com, itreferraljobs.in, educativ.net, digitalxnode.com, and any page whose title reads 'ROLE at COMPANY | SITENAME'. Also skip search and category pages (any URL carrying q=, query=, keyword=, search=, page= or offset=, or a path ending at /jobs, /careers, /vacancies or /openings with no role identifier), recruiter and staffing agency pages, LinkedIn profiles of people who already hold the role, 'we are hiring' social posts, salary guides, interview-prep articles, and course or bootcamp adverts. Lead with the company, the title, the city, and the area.
Insider buying — Find insider share PURCHASES disclosed in the LAST 14 DAYS at NVIDIA, Microsoft, Apple, Alphabet, Amazon, Meta, Tesla, Broadcom, AMD, ASML, Netflix, Salesforce, Adobe, Oracle, Intel, Qualcomm, Marvell, Palantir, CrowdStrike, Snowflake or Datadog. Each finding must be ONE SEC Form 4 filing on sec.gov recording an ACQUISITION of shares. Filing pages only. MUST-HAVES: it is a Form 4 rather than coverage of one; the reporting person and their relationship to the issuer are named; the transaction code shows a purchase rather than an option exercise or a grant; and the filing date is inside the 14-day window. Say the size in shares and in dollars, and say explicitly when the transaction was an exercise or an award rather than an open-market buy. Skip insider-tracking dashboards, news articles about insider activity, 'top insider buys this week' listicles, and anything outside the window. Lead with the person, their role, the size, and the date.
Buyback announcements — Find share repurchase programmes authorised, expanded or accelerated in the LAST 14 DAYS by NVIDIA, Microsoft, Apple, Alphabet, Amazon, Meta, Tesla, Broadcom, AMD, ASML, Netflix, Salesforce, Adobe, Oracle, Intel, Qualcomm, Marvell, Palantir, CrowdStrike, Snowflake or Datadog, or by TSMC, Arm, Micron, Applied Materials, Lam Research, KLA, Cisco, IBM, Dell, HPE, Texas Instruments or Analog Devices. Each finding must be ONE company announcement, 8-K or board-authorisation release stating the programme. MUST-HAVES: the company publishes it or it is their filing; the TOTAL PROGRAMME SIZE is stated as a figure; it is clear whether this is a new authorisation, an increase to an existing one, or an accelerated execution; and it carries a date inside the 14-day window. Give the remaining authorisation and any per-quarter pace when disclosed. Skip analyst commentary, 'what is a stock buyback' explainers, buyback-tracker pages, roundups covering several companies, and anything outside the window. Lead with the company, the programme size, whether it is new or an increase, and the date.
Backend SDE-1 India — Find open entry-level backend engineering roles at product companies and funded startups in India. Each finding must be ONE job posting for ONE role, hosted either on the employer's own careers domain or on an applicant tracking system. Accept job-boards.greenhouse.io, boards.greenhouse.io, jobs.lever.co, jobs.ashbyhq.com, myworkdayjobs.com, smartrecruiters.com, apply.workable.com, jobs.jobvite.com, careers.icims.com, darwinbox.in, keka.com, zohorecruit.com, or a company's own /careers/, /jobs/ or /join/ path that carries a role identifier in the URL. MUST-HAVES, every one of them checkable from the posting itself: the role is based in Bengaluru, Hyderabad, Pune, Chennai, Gurugram, Noida or remote-India, or is explicitly remote within it; the title is SDE-1, SDE I, Software Engineer I, Associate Software Engineer, Graduate Engineer Trainee or New Grad, OR the requirements ask for 0 to 2 years. Accept a posting whose title clearly marks entry level even when it states no years at all: requiring the years is why this agent delivered 1 useful finding out of 161; The posting must still be open. Reject anything showing 'closed', 'filled', 'position no longer available', 'no longer accepting applications', or a deadline that has passed. The posting must have been published or last updated within the last 21 days. If the page carries no date at all, say so in the summary and rank it below an otherwise identical dated posting rather than assuming it is fresh. The following RAISE the value of a finding and are NOT requirements: a published compensation band, a named tech stack, the team size, the reporting line, and whether the role is onsite, hybrid or remote. Say which of them are present. Never reject a posting for omitting them: most postings omit compensation, and treating that as disqualifying rejects almost everything. DO NOT SEND: SDE-2 and above, which have their own agents; internships; or service-company mass-hiring drives from Infosys, TCS, Wipro, Cognizant, Accenture, Capgemini, HCL, LTI Mindtree or Tech Mahindra. REJECT these domains outright, they are never the employer: naukri.com, instahyre.com, foundit.in, monsterindia.com, hirist.tech, cutshort.io, glassdoor, indeed, ziprecruiter, simplyhired, jooble, talent.com, adzuna, reed.co.uk, totaljobs, cv-library, stepstone, xing, jobs-radar.com, itreferraljobs.in, educativ.net, digitalxnode.com, and any page whose title reads 'ROLE at COMPANY | SITENAME'. Also skip search and category pages (any URL carrying q=, query=, keyword=, search=, page= or offset=, or a path ending at /jobs, /careers, /vacancies or /openings with no role identifier), recruiter and staffing agency pages, LinkedIn profiles of people who already hold the role, 'we are hiring' social posts, salary guides, interview-prep articles, and course or bootcamp adverts. Lead with the company, the level, and the city.
Visa Stock news — I hold Visa Inc (NYSE: V) shares. Find news and primary filings published in the LAST 24 HOURS that could move the position. Anything older than 24 hours has no value here: I have already read it. Each finding must be ONE dated article or ONE primary document that names Visa Inc specifically. Accept, in this order of preference: an 8-K, 10-Q, 10-K or proxy filing on sec.gov; Visa's own investor-relations release at investor.visa.com or usa.visa.com/about-visa/newsroom; a named investment-bank note or a report of one that quotes the new price target and the new rating; a regulator's own publication (DOJ, FTC, European Commission, CFPB, RBI, or a national competition authority); or a Reuters, Bloomberg, Financial Times, Wall Street Journal or CNBC article carrying a publication timestamp. MUST-HAVES: the page names Visa Inc, not merely 'visa' the travel document, and not Mastercard or another network as its subject; it carries a publication or filing date inside the 24-hour window; and it reports one of the following concrete things rather than commentary: quarterly results or guidance, an analyst rating or price-target change with the number stated, a regulatory, antitrust, interchange or litigation development, a major partnership or network deal, a buyback or dividend action, or an insider transaction. Include the current share price and the day's move when the page states them. Disambiguation matters more here than in any other brief on this account: reject visa-application, immigration, travel-document and 'visa-free travel' pages outright, however well they match the word. Skip ticker-quote, stock-screener, portfolio-tracker and news-index pages, market-wrap and 'shares rose 2%' churn, price-prediction and 'should you buy' articles, opinion columns, sector listicles, roundups covering several companies at once, and anything published outside the window above. Lead with the timestamp, what happened, the figure involved, and the current share price.
Model releases — Find new model releases from OpenAI, Anthropic, Google DeepMind, Meta AI, Mistral, Cohere, xAI, Alibaba Qwen, DeepSeek, Moonshot or Z.ai, or from Ai2, Nous Research, Reka, Liquid AI, Inflection, Stability, Black Forest Labs, ElevenLabs, Suno or Runway, announced in the LAST 21 DAYS. Each finding must be ONE model's release page, model card, technical report or the lab's own announcement post, naming the model. MUST-HAVES: the page is published by the lab itself (its blog, docs, model card or Hugging Face repository); it names the specific model and version; it says what is new about it; and it carries a date inside the 21-day window. Say the context window, the modalities, the pricing and the availability (generally available, preview, waitlist, or weights released) whenever the page states them, and quote the headline benchmark numbers the lab itself publishes. Do NOT treat any of those as required: a launch post often precedes the model card. Skip third-party benchmark commentary and reaction blogs, 'best model' and 'model comparison' articles, YouTube and newsletter summaries, Reddit and X threads, fine-tunes and quantisations of somebody else's release, wrapper and aggregator product launches, and anything outside the window. Lead with the lab, the model name, what is new, and the date.
Executive pay disclosures — Find executive compensation disclosures for NAMED chief executives and other named executive officers at large United States technology companies, filed in the LAST 90 DAYS. The window is wide because these arrive in proxy season rather than continuously. Each finding must be ONE filing that discloses the pay of a named individual: a DEF 14A proxy statement or a remuneration report on sec.gov, or the company's own proxy page. Filing pages only. MUST-HAVES: it is a filing rather than coverage of one; it names the individual; it states a total compensation figure; it names the fiscal year; and it carries a filing date inside the 90-day window. Break the total into salary, bonus, and stock and option awards whenever the filing does, and note any say-on-pay result. Skip 'highest paid CEOs' rankings and listicles, news coverage of pay, compensation-survey and benchmarking reports, Glassdoor and Levels.fyi pages, and anything outside the window. Lead with the person, the company, the total, and the fiscal year.
ML engineer Senior US — Find open senior and staff machine learning engineering roles at technology companies in the United States, including fully remote US roles. Weight frontier labs and companies that publish real ML work highest: OpenAI, Anthropic, Google DeepMind, Meta (FAIR and GenAI), Apple, Amazon AGI, Microsoft AI, NVIDIA, Tesla Autopilot, Scale AI, Databricks, Cohere, Perplexity, xAI, Figure, Waymo, Cruise, Together, Fireworks, Baseten and similarly funded AI startups. Each finding must be ONE job posting for ONE role, hosted either on the employer's own careers domain or on an applicant tracking system. Accept job-boards.greenhouse.io, boards.greenhouse.io, jobs.lever.co, jobs.ashbyhq.com, myworkdayjobs.com, smartrecruiters.com, apply.workable.com, jobs.jobvite.com, careers.icims.com, darwinbox.in, keka.com, zohorecruit.com, or a company's own /careers/, /jobs/ or /join/ path that carries a role identifier in the URL. MUST-HAVES, every one of them checkable from the posting itself: the role is based in the United States, or is explicitly remote within it; the title is Senior Machine Learning Engineer, Senior Applied Scientist, Senior Research Engineer, Staff Machine Learning Engineer, Member of Technical Staff, or an equivalent senior-or-above ML title, OR the requirements ask for 5 or more years of machine learning experience; The posting must still be open. Reject anything showing 'closed', 'filled', 'position no longer available', 'no longer accepting applications', or a deadline that has passed. The posting must have been published or last updated within the last 21 days. If the page carries no date at all, say so in the summary and rank it below an otherwise identical dated posting rather than assuming it is fresh. Also say which ML domain it is (large language models, computer vision, speech, recommendations, reinforcement learning, robotics or infrastructure), and name the frameworks if the posting does (PyTorch, JAX, CUDA, Triton, vLLM, distributed training, fine-tuning, RLHF). The following RAISE the value of a finding and are NOT requirements: a published compensation band, a named tech stack, the team size, the reporting line, and whether the role is onsite, hybrid or remote. Say which of them are present. Never reject a posting for omitting them: most postings omit compensation, and treating that as disqualifying rejects almost everything. DO NOT SEND: mid-level, new-grad or internship roles; research positions that require a PhD and describe no production or engineering component; data-engineering, analytics-engineering or MLOps-only roles that do not involve modelling; or engineering-manager and director roles, which have their own agent. REJECT these domains outright, they are never the employer: naukri.com, instahyre.com, foundit.in, monsterindia.com, hirist.tech, cutshort.io, glassdoor, indeed, ziprecruiter, simplyhired, jooble, talent.com, adzuna, reed.co.uk, totaljobs, cv-library, stepstone, xing, jobs-radar.com, itreferraljobs.in, educativ.net, digitalxnode.com, and any page whose title reads 'ROLE at COMPANY | SITENAME'. Also skip search and category pages (any URL carrying q=, query=, keyword=, search=, page= or offset=, or a path ending at /jobs, /careers, /vacancies or /openings with no role identifier), recruiter and staffing agency pages, LinkedIn profiles of people who already hold the role, 'we are hiring' social posts, salary guides, interview-prep articles, and course or bootcamp adverts. Lead with the company, the exact title, the ML domain, the location or remote policy, and the compensation band if the posting publishes one.
Backend Senior Europe — Find open senior backend engineering roles at technology companies in Europe, including remote-EU roles. Each finding must be ONE job posting for ONE role, hosted either on the employer's own careers domain or on an applicant tracking system. Accept job-boards.greenhouse.io, boards.greenhouse.io, jobs.lever.co, jobs.ashbyhq.com, myworkdayjobs.com, smartrecruiters.com, apply.workable.com, jobs.jobvite.com, careers.icims.com, darwinbox.in, keka.com, zohorecruit.com, or a company's own /careers/, /jobs/ or /join/ path that carries a role identifier in the URL. MUST-HAVES, every one of them checkable from the posting itself: the role is based in Germany, the Netherlands, Ireland, Spain, Portugal, Poland, Switzerland, Sweden, Denmark, Norway or Finland, or is explicitly remote within it; the title is Senior Software Engineer, Senior Backend Engineer, Senior Platform Engineer or Lead Engineer, OR the requirements ask for 5 or more years of backend experience; The posting must still be open. Reject anything showing 'closed', 'filled', 'position no longer available', 'no longer accepting applications', or a deadline that has passed. The posting must have been published or last updated within the last 21 days. If the page carries no date at all, say so in the summary and rank it below an otherwise identical dated posting rather than assuming it is fresh. State any LANGUAGE requirement explicitly, including 'English only', because for a non-EU applicant that is more often the real filter than the engineering bar. Also state whether the posting mentions visa sponsorship, EU Blue Card support or relocation assistance, but do NOT require it: most postings are silent on it and demanding it rejects nearly everything. The following RAISE the value of a finding and are NOT requirements: a published compensation band, a named tech stack, the team size, the reporting line, and whether the role is onsite, hybrid or remote. Say which of them are present. Never reject a posting for omitting them: most postings omit compensation, and treating that as disqualifying rejects almost everything. DO NOT SEND: junior, graduate or mid-level roles; engineering-manager or director roles; or frontend, mobile and QA roles. REJECT these domains outright, they are never the employer: naukri.com, instahyre.com, foundit.in, monsterindia.com, hirist.tech, cutshort.io, glassdoor, indeed, ziprecruiter, simplyhired, jooble, talent.com, adzuna, reed.co.uk, totaljobs, cv-library, stepstone, xing, jobs-radar.com, itreferraljobs.in, educativ.net, digitalxnode.com, and any page whose title reads 'ROLE at COMPANY | SITENAME'. Also skip search and category pages (any URL carrying q=, query=, keyword=, search=, page= or offset=, or a path ending at /jobs, /careers, /vacancies or /openings with no role identifier), recruiter and staffing agency pages, LinkedIn profiles of people who already hold the role, 'we are hiring' social posts, salary guides, interview-prep articles, and course or bootcamp adverts. Lead with the company, the country and city, the language requirement, and whether relocation or sponsorship is mentioned.
Data science Senior US — Find open senior data scientist roles at technology companies in the United States, including fully remote US roles. Each finding must be ONE job posting for ONE role, hosted either on the employer's own careers domain or on an applicant tracking system. Accept job-boards.greenhouse.io, boards.greenhouse.io, jobs.lever.co, jobs.ashbyhq.com, myworkdayjobs.com, smartrecruiters.com, apply.workable.com, jobs.jobvite.com, careers.icims.com, darwinbox.in, keka.com, zohorecruit.com, or a company's own /careers/, /jobs/ or /join/ path that carries a role identifier in the URL. MUST-HAVES, every one of them checkable from the posting itself: the role is based in the United States, or is explicitly remote within it; the title is Senior Data Scientist, Senior Applied Scientist, Lead Data Scientist or Data Scientist III, OR the requirements ask for 5 or more years of data science experience; The posting must still be open. Reject anything showing 'closed', 'filled', 'position no longer available', 'no longer accepting applications', or a deadline that has passed. The posting must have been published or last updated within the last 21 days. If the page carries no date at all, say so in the summary and rank it below an otherwise identical dated posting rather than assuming it is fresh. Say which area it sits in when the posting does: experimentation and causal inference, forecasting, fraud and risk, marketing or growth, pricing, or product analytics. The following RAISE the value of a finding and are NOT requirements: a published compensation band, a named tech stack, the team size, the reporting line, and whether the role is onsite, hybrid or remote. Say which of them are present. Never reject a posting for omitting them: most postings omit compensation, and treating that as disqualifying rejects almost everything. DO NOT SEND: entry-level or mid-level roles; Staff, Principal or manager roles; data-analyst, business-intelligence, reporting or dashboard roles however they are titled; or data-engineering roles with no modelling component. REJECT these domains outright, they are never the employer: naukri.com, instahyre.com, foundit.in, monsterindia.com, hirist.tech, cutshort.io, glassdoor, indeed, ziprecruiter, simplyhired, jooble, talent.com, adzuna, reed.co.uk, totaljobs, cv-library, stepstone, xing, jobs-radar.com, itreferraljobs.in, educativ.net, digitalxnode.com, and any page whose title reads 'ROLE at COMPANY | SITENAME'. Also skip search and category pages (any URL carrying q=, query=, keyword=, search=, page= or offset=, or a path ending at /jobs, /careers, /vacancies or /openings with no role identifier), recruiter and staffing agency pages, LinkedIn profiles of people who already hold the role, 'we are hiring' social posts, salary guides, interview-prep articles, and course or bootcamp adverts. Lead with the company, the exact title, the area, and the location or remote policy.
Backend Senior US — Find open senior backend engineering roles at technology companies in the United States, including fully remote US roles. Each finding must be ONE job posting for ONE role, hosted either on the employer's own careers domain or on an applicant tracking system. Accept job-boards.greenhouse.io, boards.greenhouse.io, jobs.lever.co, jobs.ashbyhq.com, myworkdayjobs.com, smartrecruiters.com, apply.workable.com, jobs.jobvite.com, careers.icims.com, darwinbox.in, keka.com, zohorecruit.com, or a company's own /careers/, /jobs/ or /join/ path that carries a role identifier in the URL. MUST-HAVES, every one of them checkable from the posting itself: the role is based in the United States, or is explicitly remote within it; the title is Senior Software Engineer, Senior Backend Engineer, Software Engineer III, Senior Platform Engineer or Member of Technical Staff, OR the posting names an internal level of Google L5, Meta E5, Amazon SDE III or equivalent, OR the requirements ask for 5 or more years of backend experience; The posting must still be open. Reject anything showing 'closed', 'filled', 'position no longer available', 'no longer accepting applications', or a deadline that has passed. The posting must have been published or last updated within the last 21 days. If the page carries no date at all, say so in the summary and rank it below an otherwise identical dated posting rather than assuming it is fresh. Name the primary language and datastore when the posting does (Go, Rust, Java, Kotlin, Python, TypeScript, Postgres, Kafka, Kubernetes). The following RAISE the value of a finding and are NOT requirements: a published compensation band, a named tech stack, the team size, the reporting line, and whether the role is onsite, hybrid or remote. Say which of them are present. Never reject a posting for omitting them: most postings omit compensation, and treating that as disqualifying rejects almost everything. DO NOT SEND: entry-level, new-grad or SDE-II roles; Staff, Senior Staff, Principal or Distinguished roles; engineering-manager, director or architect-without-coding roles; or frontend, mobile, QA, support and solutions-engineering roles. REJECT these domains outright, they are never the employer: naukri.com, instahyre.com, foundit.in, monsterindia.com, hirist.tech, cutshort.io, glassdoor, indeed, ziprecruiter, simplyhired, jooble, talent.com, adzuna, reed.co.uk, totaljobs, cv-library, stepstone, xing, jobs-radar.com, itreferraljobs.in, educativ.net, digitalxnode.com, and any page whose title reads 'ROLE at COMPANY | SITENAME'. Also skip search and category pages (any URL carrying q=, query=, keyword=, search=, page= or offset=, or a path ending at /jobs, /careers, /vacancies or /openings with no role identifier), recruiter and staffing agency pages, LinkedIn profiles of people who already hold the role, 'we are hiring' social posts, salary guides, interview-prep articles, and course or bootcamp adverts. Lead with the company, the exact title, the location or remote policy, and the stack.
Guidance revisions — Find cases in the LAST 7 DAYS where NVIDIA, Microsoft, Apple, Alphabet, Amazon, Meta, Tesla, Broadcom, AMD, ASML, Netflix, Salesforce, Adobe, Oracle, Intel, Qualcomm, Marvell, Palantir, CrowdStrike, Snowflake or Datadog raises, lowers, narrows, reaffirms with a material change, or withdraws forward guidance. Each finding must be ONE company filing or ONE company release stating the change: an 8-K, a quarterly release, an investor-relations statement, a pre-announcement, or a slide from the company's own guidance deck. MUST-HAVES: the page is published by the company or is its filing; it names the metric being guided (revenue, EPS, operating margin, capital expenditure, unit volumes or free cash flow); it gives BOTH the previous figure and the new one, or explicitly says guidance is withdrawn; and it carries a date inside the 7-day window. Skip analyst reaction and brokerage notes, news commentary about guidance, 'guidance preview' articles, consensus-estimate pages, and anything outside the window. Lead with the company, the metric, the previous figure, the new figure, and the date.
Founders in their own words — Find original statements published in the LAST 10 DAYS by the people below, written or spoken BY THEM rather than reported about them. Always track: Jensen Huang, Satya Nadella, Sundar Pichai, Tim Cook, Mark Zuckerberg, Sam Altman, Dario Amodei, Andy Jassy, Elon Musk, Demis Hassabis and Lisa Su. Track when active: Patrick and John Collison, Brian Chesky, Daniel Ek, Guillermo Rauch, Dylan Field, Aravind Srinivas, Mira Murati, Ilya Sutskever, Andrej Karpathy, Yann LeCun, Andrew Ng, Jeff Dean, Noam Shazeer and Arthur Mensch. Each finding must be ONE piece authored by the person: their own blog post or essay, their company's official blog under their byline, an official keynote or earnings-call transcript, a published letter to shareholders or staff, or a substantive post on their own verified account. MUST-HAVES: the named person is the AUTHOR or the speaker of record, not the subject; the page carries a date inside the 10-day window; and the content says something specific about strategy, a product decision, a technical result, a market prediction, hiring or capital spending. A one-line post with no claim in it is not a finding. Skip interviews written up by a third party, podcast episodes summarised by somebody else, quote-tweets and reaction threads, newsletters describing what they said, 'X said Y' news articles, conference panels where they are one of several speakers, and anything outside the window. Lead with the person, the date, and the substance of what they said, quoted where it is worth quoting.

This list as JSON · How to search Parlel as an agent