Supabase lists two full-time remote engineering roles on its AI Tooling team, both requiring at least five years of relevant experience. One focuses on developer-facing AI tools. The other builds and operates the production services behind them. Both are marked Remote, Global on the employer’s official hiring board.

These are existing vacancies checked on November 12, 2026. The AI Tooling role was published on November 10 and the infrastructure role on October 31, according to the employer’s hiring feed. Neither is being presented here as a new announcement from the last 24 hours. No salary range or application deadline is disclosed in the retrieved listings.

Two roles with different responsibilities

The distinction matters when choosing where to apply. An engineer who builds useful interfaces and evaluation frameworks may be a stronger fit for AI Tooling. Someone who has operated backend services, handled incidents and designed authorization systems should examine AI Tooling Infrastructure.

The listings state that Supabase hires globally. That makes them relevant to India-based applicants, rather than roles explicitly restricted to the United States or Europe. Country-specific contracting, work authorization and payroll arrangements should still be confirmed during recruitment. Remote, Global is not a promise of visa sponsorship or an offer in every jurisdiction.

AI Tooling: build tools that prove their value

The Software Engineer, AI Tooling listing covers agents, the MCP server, agent skills and the dashboard assistant. It asks engineers to make Supabase products usable by agents and to evaluate whether those tools actually improve outcomes.

A central requirement is evidence. The description calls for evaluation frameworks, instrumentation and feedback loops, including comparison against a baseline without tools. This is a useful signal for applicants: a polished demonstration alone may not show the judgment the team is seeking. A candidate should be ready to explain how they measured quality, reliability, cost and task success.

Skills the employer names

The role requires strong TypeScript, familiarity with the JavaScript ecosystem, practical knowledge of AI tools and agent patterns, and experience building tools or interfaces used by other engineers. It also asks for Postgres knowledge, testing discipline and clear written communication across engineering, product and documentation teams.

Experience with vector databases, embeddings, pgvector, evaluation platforms and open-source contributions appears among the preferred qualifications. Those additions should not distract from the required experience. A short project that uses a model API is not automatically equivalent to five years of professional software engineering.

Infrastructure: own the systems behind the tools

The AI Tooling Infrastructure vacancy focuses on services running in production. Responsibilities include deployment, scaling, configuration, authorization, monitoring and incident response. The team carries its own on-call rotation and handles a support queue.

The employer explains that agent traffic can create rapid repeated calls and retries. That changes the engineering problem. A service needs to remain understandable and controlled when a client sends many requests or an upstream dependency fails. Applicants should be able to discuss concrete production decisions rather than only the architecture they would like to build.

Experience that fits this opening

Required areas include operating APIs, OAuth, OIDC, JWT, PostgreSQL, containerized deployments and infrastructure as code. The description also asks for debugging across services using metrics, traces and logs. It expects depth in at least one area such as authorization, operations or gateways and distributed systems.

For an application, choose one incident or migration you genuinely owned. Explain the original problem, the trade-off you made and the result you could observe. Remove customer secrets and internal credentials from any examples. This is editorial application advice, not an extra employer requirement or a promised interview question.

Benefits are listed, but salary is not

Both descriptions advertise remote work, equity participation, technology and education allowances, health benefits and an annual company gathering. They also describe asynchronous work. Exact allowance amounts and local implementation are not supplied in the retrieved descriptions, so applicants should ask how each benefit applies to their location.

Do not use an overseas salary estimate as the expected India offer. No verified pay band is available in these postings. Compensation, currency, employment entity and any location adjustments need to be discussed directly. A global remote label describes the working arrangement, not a uniform worldwide salary.

How to choose and prepare

Start with the official Supabase careers page, then open the exact role. Confirm it remains listed before submitting. Save the job title and official URL so you can distinguish the two applications later. The infrastructure requisition is fb0b563a-e541-43fd-8555-9eb6473aaa11. The product tooling requisition is 0055f731-cffa-4c74-9c00-8abfa579873d.

For AI Tooling, highlight developer-facing work and how you evaluated it. A useful portfolio explanation can describe the baseline, test cases, failures and changes made after observing users. For Infrastructure, highlight production ownership, incident work, API compatibility and authorization. State your actual contribution when describing a team project.

A resume should make the required five-year experience threshold easy to assess. Use dates, responsibilities and specific outcomes. Listing many libraries without showing what you shipped gives the reviewer less useful evidence. If your background overlaps both roles, tailor each application to its responsibilities rather than sending an identical generic statement.

Questions worth asking before accepting

Clarify expected collaboration hours from India and how on-call coverage is organized. Ask how incidents are escalated, how production ownership is shared and what a successful first few months would involve. For the tooling role, ask how quality gates are maintained as models and product features change.

Also confirm the employment arrangement, compensation currency, equipment support and local benefits in writing. No deadline, vacancy count or guaranteed hiring timeline is disclosed. These are application opportunities, not evidence that a specific number of candidates will be hired immediately.

For readers comparing project-based work with employment, BoringDude’s Telugu maps-rating guide covers a separate freelance opportunity. Its limited rounds are very different from these full-time engineering roles. Apply based on your experience and preferred work, not the remote label alone.

Frequently asked questions

About Post Author

Boring Dude

boringdude.in@gmail.com

Happy

0 0 %

Sad

0 0 %

Excited

0 0 %

Sleepy

0 0 %

Angry

0 0 %

Surprise

0 0 %

Please leave this field empty

Receive updates directly to your email

We don’t spam! Read our privacy policy for more info.

Check your inbox or spam folder to confirm your subscription.