Sponsorship verdict
Sponsorship possible
One solid signal, not two. Worth applying, and worth asking about sponsorship early.
-
✓
Employer is on a government sponsor recordThe US Department of Labor certified 3 H-1B/E-3 labor condition applications for this employer between Oct 2025 and Jun 2026 (latest Apr 2026) — the step every H-1B hire needs first.
-
?
The posting doesn’t mention sponsorshipSilence isn’t a refusal — ask the recruiter before investing much time.
-
?
No salary bar for this routeH-1B has no fixed salary bar: the employer must pay at least the prevailing wage for the role and area.
-
✓
Confirmed live todayWhen a source last listed this job as open.
Details and sources
- Employer is on a government sponsor record
- The US Department of Labor certified 3 H-1B/E-3 labor condition applications for this employer between Oct 2025 and Jun 2026 (latest Apr 2026) — the step every H-1B hire needs first. Source: LCA disclosure data (US Department of Labor (OFLC)).
- No salary bar for this route
- H-1B has no fixed salary bar: the employer must pay at least the prevailing wage for the role and area. Cap-subject employers enter a lottery weighted by wage level. Source: https://www.federalregister.gov/documents/2025/12/29/2025-23853/weighted-selection-process-for-registrants-and-petitioners-seeking-to-file-cap-subject-h-1b, rules effective 2026-02-27.
US H-1B: cap-subject employers enter a lottery weighted by wage level — Level I gets 1 entry, Level IV gets 4 (DHS projected selection odds ≈15% at Level I to ≈61% at Level IV). Universities and non-profit research employers are cap-exempt. The $100,000 fee for new petitions from abroad is currently blocked by a court order (appeal pending).
A verdict summarises public evidence. It is not legal advice and never a guarantee: the employer and the immigration authority decide. Sign in to factor in where you can already work.
About the role
About Starburst
Starburst delivers enterprise intelligence at scale by giving organizations secure, governed access to all their data, wherever it lives. Built for distributed data environments, Starburst helps enterprises power AI and analytics without the cost and complexity of traditional data consolidation. With open standards including Trino and Apache Iceberg, Starburst enables trusted access to complete enterprise context while helping organizations avoid vendor lock-in. Leading global enterprises trust Starburst to fuel AI, analytics, and enterprise intelligence. Learn more at starburst.ai .
About the role
Starburst query engine workloads focus on two things: making federated queries fast across every source, and being the best place to run Apache Iceberg. Connectors and catalogs sit under both. They decide the breadth of connectors and use cases supported, how metadata is read, and how well Iceberg tables behave in practice.
AI agents reason across the whole data estate and generate queries as they go, so performance has to come from the engine and connectors working well on queries nobody planned in advance.
We are seeking a Product Manager to own the existing connector portfolio and catalog strategy, keeping both reliable, current, and prioritized by customer demand. You will also contribute to performance work on federation, including automated and dynamic approaches that engineering is building across data sources.
You will partner closely with other PMs to ramp up. We are looking for strong foundations and curiosity, not a perfect match on every item.
As Product Manager, Connectors and Federation at Starburst you will:
• Own the roadmap and health of existing connectors, including database connectors and lake connectors such as Iceberg
• Build new connectors where customer impact justifies it
• Own the strategy for the flagship Starburst Metastore offering, along with ownership of other catalogs (HMS, Glue, REST catalogs such as Polaris, Unity Catalog, and others), with a focus on optionality rather than betting on one
• Make federated queries faster by tracing slow queries to the responsible layer (engine, connector, or source) and turning findings into prioritized product work
• Make Starburst the best place to run Iceberg by shaping read and write paths, table metadata handling, and catalog interoperability
• Plan and prioritize performance enhancements for each connector based on customer demand, such as pushdown, type mapping, parallel reads, partition pruning, statistics, and metadata handling
• Keep up to date with Trino spec changes and their impact on connectors and catalogs
• Contribute to the automated, dynamic performance work across data sources, in partnership with engineering
• Define what agents need from a federation layer beyond access, such as signaling partial visibility instead of returning a confident but incomplete answer
• Prioritize connectors using customer demand evidence, revenue and churn context, and build and upkeep cost
• Track the competitive field and community signals to inform prioritization
Some of the things we look for:
• 3+ years as a Product Manager, with ownership of a technical infrastructure or data platform product
• Hands on experience with a query engine: you have shipped or owned features on one, or built closely against one
• Performance intuition: you ask for the plan before forming an opinion, and you can place a slowdown in the engine, the connector, or the source
• Willingness to learn how connectors differ from one another, and to direct engineering toward the specific features that matter most for each
• Working knowledge of object storage and the lakehouse, with a focus on Apache Iceberg
• Working understanding of what a catalog does and
Apply on employer site ↗