Startup Jobs San Francisco: A Practical Bay Area Guide

Finding startup jobs in San Francisco means sorting out more than company names. A promising role might be in the city, across the Peninsula, or tied to an office schedule you cannot sustain. This guide gives you verified companies to investigate, local places to search, and the commute and compensation checks to make before applying.

The pay-transparency discussion is general information, not legal advice. Check the official sources linked below or consult a California employment attorney.

Why San Francisco's startup job search centers on AI

The funding concentration is real. Joint Venture Silicon Valley's 2026 Silicon Valley Index reports that AI companies captured about 83% of venture dollars in Silicon Valley and San Francisco in its 2025 estimate, based on data through October. That is regional evidence for the prior year, not a San Francisco city-only funding total for the current year.

For your search, the useful distinction is between building AI models and building businesses around them. The verified companies below include developer tools, customer-service agents, enterprise search, healthcare documentation, and security compliance. You can target the customer problem you understand rather than treating “AI startup” as a single industry.

The city also has a concentrated office footprint. The San Francisco Standard's January 2026 analysis of JLL lease data identifies clusters in Yerba Buena, SoMa, South Beach, and the Financial District, extending into Mission Bay and nearby neighborhoods. That matters if you want to attend events after work or meet a team without making a separate regional trip.

Do not confuse funding with easy entry. The same local reporting cautions that AI hiring has not offset broader tech job losses. Build a focused application around a team's actual work, not the idea that every funded company needs more people.

For an early-career search, inspect the department before the brand. Look for a defined manager, onboarding expectations, and work you can demonstrate. A recognizable company with an unsuitable role is still an unsuitable target.

San Francisco versus the Peninsula and South Bay

Treat Bay Area startup jobs as several geographic searches. Start with San Francisco itself, then search Peninsula cities separately, and finally the South Bay. A regional location label is not enough to choose housing or promise office attendance.

As of November 2026, Replit's headquarters is in Foster City, Glean lists its corporate address in Palo Alto, and Luma AI's careers page identifies Redwood City as its headquarters. Applied Intuition now identifies Sunnyvale as its headquarters. These are different commute decisions from a downtown San Francisco role.

Use the Caltrain timetable to check Peninsula and South Bay rail connections. Use the BART system map when comparing cross-bay routes. Neither a station name nor a train's running time tells you the full commute: add the trip to the station, waiting, transfers, and the office's last-mile connection.

Suggested commute test: choose a realistic arrival time, then map the complete route on a normal office day. Check the return trip at the time you expect to leave. Repeat the calculation for the specific address, not just the city.

Ask whether the company has a shuttle, commuter benefits, or secure bike storage. Do not count any of these until the team confirms them. A lower advertised rent can be a poor trade if the route adds transfers and makes your working day harder to sustain.

Ten startups and scaleups with verified Bay Area offices

This is a research shortlist, not a ranking or a promise that a suitable opening exists. Office information was checked as of November 2026; the source column links location evidence and financing or company-status evidence. Funding labels identify the announced round in the linked reporting, not a guarantee of runway.

Start by checking the relevant department on each company's own careers site. Search your function and adjacent titles, then read responsibilities before deciding whether the title fits. A customer-facing technical role and a research role can demand very different evidence from an applicant.

This shortlist skews toward funded scaleups. If you want a smaller team, add earlier-stage companies from the boards below. Compare the scope, support, and risk using the startup versus big-tech guide, rather than assuming every private company offers the same experience.

Where to find local startup jobs before applying

As of November 2026, these verified sources provide different ways to discover companies and roles:

• Built In San Francisco: a regional technology-job search. Check company size and the actual office requirement; a regional board is not a startup-only filter.
• Y Combinator's San Francisco jobs page: a place to explore roles at YC companies. Check stage, location, and function rather than assuming every listing is an early-stage city-office job.
• Wellfound's San Francisco page: startup discovery with company and job profiles. Confirm the location and compensation details against the employer's posting.
• Pear VC's portfolio job board: portfolio-company opportunities, with a Department filter that groups openings by company. Inspect the listed location; the portfolio is not limited to San Francisco.

Use boards to discover, then the company page to verify and apply. Save the employer's application link rather than depending on an aggregator's copy. If the posting and company page disagree, ask which is current before spending time on a tailored application.

Keep a simple tracker with company, function, office address, work arrangement, posting link, date checked, and next action. For a fuller sourcing routine, use how to find startup jobs.

Unicorn Hunter can support that routine with a daily email digest of US and Canadian startup jobs matched to your skills and interests by AI. Use the digest as a discovery layer, then make the same employer-page checks.

Suggested weekly plan: shortlist 12 companies, choose five strong-fit roles, and prepare one work sample for your highest-priority target. These are planning targets, not a claim about how many applications produce an interview. Expand the list only when you have exhausted genuinely suitable roles.

Use hackathons and demo nights to make useful connections

Attend an event because its builders or customer problems match your interests. A room full of founders is not automatically a recruiting event. Your objective is a substantive conversation and a relevant follow-up, not collecting contacts indiscriminately.

As of November 2026, Cerebral Valley lists the AIE Code Summit Hackathon for November 7 in San Francisco. The event conditions require in-person participation, application approval, and teams of no more than four people. Check availability before arranging travel or assuming you can walk in.

For product demos, Startup Grind lists its AI Demo Series: November Edition in Menlo Park on November 18, 2026, local time. The page offers attendee tickets and a separate application for presenters. It is an opportunity to see early-stage products and meet builders, not a promised route to a job.

For a hackathon, bring a small idea you can finish with a team. For a demo night, prepare a question about the product's user, deployment, or measurement. If you work in marketing, design, finance, or operations, ask about the business problem instead of pretending to be an ML researcher.

Illustrative follow-up after a real conversation:

Good meeting you at the demo night. Your explanation of the onboarding problem helped me understand where the team is spending time. I put together a short teardown of the setup flow and a proposed test. Would it be useful if I sent it? I'm looking for product work with a Bay Area team and can share my portfolio too.

Only send that message if the conversation happened and the work exists. Ask permission before sharing a long attachment. If someone offers an introduction, make it easy to forward a short description of your skills and target role.

Check hybrid expectations and housing before relocating

There is no single Bay Area startup office policy. As of November 2026, Sierra describes an in-person, in-office culture, while Replit says most of its team attends offices on Monday, Wednesday, and Friday. Glean says most teams work in the office four days a week, and Vanta describes its US setup as remote-first.

Those examples are company statements, not permission to choose your own arrangement. Ask about the specific team and employment location. An office in San Francisco does not mean every role is based there, and a remote-friendly company can still have location restrictions.

Before the interview process becomes expensive, ask:

Which office would this role use, and which days does this team attend? Are those expectations fixed? Are onboarding or customer visits different from the normal schedule? Could you confirm the arrangement before an offer?

Housing deserves its own check. In its October 27, 2026 update, Zumper reports a $4,560 monthly median across all bedroom counts and property types in its San Francisco listings. This is a rolling platform-listing measure, not the price of a typical one-bedroom apartment or a shared room.

Use that benchmark as a reason to price your actual housing plan, not as your personal budget. Compare a room, studio, and shared apartment near workable routes. Include utilities, transportation, health-plan costs, moving expenses, and any overlapping rent before accepting a relocation date.

Do not use a private equity grant to make an otherwise unaffordable monthly budget appear workable. Keep recurring expenses separate from uncertain future proceeds. Use the startup equity explainer to identify the grant details you need before comparing offers.

California salary ranges: what SB 1162 requires now

As of November 2026, California's job-posting pay-scale requirement remains in the current Labor Code section 432.3. The rule introduced through SB 1162 requires covered employers to include a pay scale in job postings; check its scope rather than assuming every startup is covered.

The Labor Commissioner's official FAQ specifies employers with 15 or more employees, with at least one employee currently located in California. The same guidance covers positions that may ever be filled in California, either in person or remotely. Do not treat the threshold as a California-only headcount; employee-counting conditions apply, including fact-dependent joint-employment questions.

Covered employers using a third party must supply the range, and the third party must include it in the posting, according to the same official guidance. Under the official FAQ, a link or QR code pointing elsewhere does not substitute for the scale in the posting itself.

The current definition reflects SB 642's amendment, effective January 1, 2026: a good-faith estimate of the salary or hourly range the employer reasonably expects to pay upon hire. Read the range for the position you would actually join, not as a promise of its highest number.

The official FAQ says additional compensation and benefits need not be included; commission or piece-rate ranges must be included when the position's salary or hourly wage is based on them. Ask separately about base pay, variable pay, and equity so you do not compare unlike packages.

If a range is missing, ask for it before discussing your expectations. If the range is broad, ask which level the team is recruiting and how that affects the offer. Once you have those answers, use the startup offer negotiation guide to prepare your request.

Next steps

1. Choose your geographic boundaries and test a door-to-door commute before committing to office attendance.
2. Build a shortlist from the verified companies and local boards, then confirm suitable roles on employer pages.
3. Ask about the team's office schedule and compensation structure before scheduling a long interview process.
4. Attend a relevant builder event and follow up with a useful question or work sample.
5. Price your actual housing plan and compare recurring cash costs before accepting an offer.