Back-end engineer

Location:

In-office

San Francisco

Salary/equity:

$170k-210k

0.2%-0.35%

Role/industry:

Back-end

AI / Product team tools

Exp. floor:

3 years (hard)

Brief description

This is a back-end product engineering role building a platform for user research. Their product is a conversational AI that interviews users, prompts with followup questions, and summarizes the results into feedback for product teams.

This role touches on the AI portion, but is primarily a typical back-end product engineering role. You'll be:

  • Building internal and external APIs

  • Setting up infrastructure for their website, AI, and real-time data processing

  • Working with users to understand pain-points and with leadership to prioritize what to build next.

They have two internal "tracks". One works on core product features that are expected to be relatively stable (at least by startup standards). The other builds highly experimental features you might scrap after a week of work. You can choose to focus on either (though you may sometimes need to do the other).

This role is fully in-office in downtown San Francisco.

What they're looking for

[Required]

  • 3+ years of engineering experience. At least some of that experience should be with net-new, user-facing features (i.e. not just internals or optimizations).

  • Some experience with Python/Django

  • Experience at a startup between seed stage and series B. This is a preference for many company, but a hard requirement for them.

  • General independence. Expect a level of specification along the lines of "here's a ticket with one sentence about what this should do, figure it out".

[Nice to have]

  • Depth in SQL in particular, especially Postgres

  • Familiar with WebRTC or other streaming data tools

  • Background in ML or AI infrastructure

What they're offering

  • Salary: $170k-210k

  • Equity: 0.2% to 0.35%

  • A company on a good trajectory (10x revenue last year), plenty of runway, and big-name clients

  • You can focus more on core or speculative features (as mentioned in role description), at your preference.

Back-end engineer

In-office

San Francisco

$170k-210k

0.2%-0.35%

Back-end

AI / Product team tools

3 years (hard)

Brief description

This is a back-end product engineering role building a platform for user research. Their product is a conversational AI that interviews users, prompts with followup questions, and summarizes the results into feedback for product teams.

This role touches on the AI portion, but is primarily a typical back-end product engineering role. You'll be:

  • Building internal and external APIs

  • Setting up infrastructure for their website, AI, and real-time data processing

  • Working with users to understand pain-points and with leadership to prioritize what to build next.

They have two internal "tracks". One works on core product features that are expected to be relatively stable (at least by startup standards). The other builds highly experimental features you might scrap after a week of work. You can choose to focus on either (though you may sometimes need to do the other).

This role is fully in-office in downtown San Francisco.

What they're looking for

[Required]

  • 3+ years of engineering experience. At least some of that experience should be with net-new, user-facing features (i.e. not just internals or optimizations).

  • Some experience with Python/Django

  • Experience at a startup between seed stage and series B. This is a preference for many company, but a hard requirement for them.

  • General independence. Expect a level of specification along the lines of "here's a ticket with one sentence about what this should do, figure it out".

[Nice to have]

  • Depth in SQL in particular, especially Postgres

  • Familiar with WebRTC or other streaming data tools

  • Background in ML or AI infrastructure

What they're offering

  • Salary: $170k-210k

  • Equity: 0.2% to 0.35%

  • A company on a good trajectory (10x revenue last year), plenty of runway, and big-name clients

  • You can focus more on core or speculative features (as mentioned in role description), at your preference.