Founding Engineer · Seed-stage startup
A fictional software startup needs a hands-on engineer to ship its product and customer integrations in San Francisco.
- Company stage
- Seed
- Role under discussion
- Founding Engineer
- Working model
- In person · San Francisco
The business problem
The founders need to turn customer requests into a product that can be shipped and supported. Integrations are interrupting core product work. The draft role combines product engineering, integration delivery, architecture and responsibility for managing a future engineering team.
The role hypothesis
Start with a senior, hands-on individual contributor who can own a product area and its integrations from definition through production. The founder retains people management and hiring-plan decisions. Revisit the leadership mandate when there is a team and a management problem to solve.
Where to look
Search the San Francisco market for engineers who have shipped full-stack products and external integrations in small teams. Confirm willingness to work in person early. Examine direct contribution, customer contact and production responsibility before filtering by an employer name.
A compensation assumption to test
USD 150,000–250,000 annual base + equity
An initial planning range for this fictional role, subject to the final scope, working model and equity terms. It is informed by the public advertisements below. These are advertised reference points, not a market-wide benchmark or a compensation commitment.
Public advertisements reviewed 17 October 2026. Advertisements can change.
- Paradigm · Founding Engineer · Y Combinator Jobs
San Francisco. The posting states a USD 150,000–250,000 base range and describes equity separately.
- Ploy · Founding Engineer · Y Combinator Jobs
San Francisco. The posting lists USD 150,000–250,000; its headline does not specify the base/equity split.
The links are public research references. They do not imply a client relationship or endorsement.
Evidence the role would require
- Direct responsibility for shipping and supporting a product or integration, with a clear account of the decisions and work done personally.
- An example of choosing a smaller technical solution under customer or business constraints, including what was deliberately left out.
- A production problem they investigated and resolved, explaining the symptoms, diagnosis, recovery and prevention.
- A way of working with founders or customers that turns incomplete requests into a usable technical plan.
Three questions we would start with
- Walk us through a product integration you shipped. Which decisions and implementation were yours, what context was missing and what happened after release?
- A customer integration is blocking launch while the core product is still changing. What would you investigate first, and how would you decide what to ship?
- In this company, which engineering responsibilities would you take on yourself and which would you need the founder to retain? What would you leave unbuilt for now?
Risks in the current brief
- The company is combining a people-management mandate with a full-time building role before defining the team the person would manage.
- An executive title may attract candidates expecting resources or authority the company cannot yet provide.
- Unclear integration priorities could turn the hire into a reactive delivery function and leave core product ownership unresolved.
Our recommendation in this exercise
Redefine the role before opening the search.
Prioritize a hands-on Senior IC mandate focused on product delivery and integrations. Clarify the founder’s responsibilities, the initial technical scope and the equity proposal. Assess the ability to grow into broader responsibility through evidence; keep a future management role separate from the work needed today.
This exercise demonstrates a way to reason about a role. It does not represent a live vacancy, a real candidate recommendation or a promise of introductions.