Founding Engineer | AI + Creative | San Francisco | USD $250K to $275K + Founding Equity

We need to output HTML fragment with sections using

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Also must not include sections with filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. Let's parse the posting. It starts with a quote about Yoda, then narrative about Empire vs small crew, mission, etc. Then "What you will actually build" describing tasks: interface (React, Next.js), backend (Node...), generation layer (Python...), agents (LLM powered agents...), infrastructure (long running jobs...). That's responsibilities. Then "Who this is for": bullet list of qualifications/experience. Then "Who this is not for": more qualifications. Then "The deal": USD $250,000 to $275,000 base, founding equity, lunch and dinner daily, five days a week in SF office, US work authorisation required, no visa sponsorship, multiple hires. Then "Boarding": instructions to send CV etc - that's application instructions, which we must remove. Also contact email etc - remove. We need to extract sections. Potential sections: - About the role: maybe the narrative about mission and what they are building. Could be considered "About the role". We'll include that. - Responsibilities: "What you will actually build" details. - Requirements/Qualifications/Skills: The "Who this is for" and "Who this is not for" could be combined into Requirements/Qualifications/Skills. We need to decide which headings to use. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can include multiple of those if content exists. We should not create thin sections. Perhaps combine into Requirements and Skills. We have specific qualifications: "Zero to three years as a full stack engineer", Python and JavaScript both genuinely yours, React and Next.js specifically, shipped production web applications end to end, founder/founding engineer/employee number small at startup where job description changed monthly, spent time somewhere that takes creative tools or generative AI seriously, built LLM powered things that real people used, can defend technical decision under pressure, tell founder they are wrong, make things outside of work (design, film, music, art, weird side projects). Selective programs like Contrary, Neo Scholars or KP Fellows are a strong signal, not a requirement. Also "Who this is not for": If entire career is straight line through biggest tech companies with no startup chapter, nothing built yourself, this will not work. Coming from giant fine, having only ever been inside one is problem. Big tech plus a company you started, plus something you shipped alone that people actually used, is strong profile. We can put these under Requirements (or Qualifications). Skills could be specific tech: Python, JavaScript, React, Next.js, Node, LLMs, etc. But we already have those in qualifications. We have Pay: USD $250,000 to $275,000 base, founding equity, lunch and dinner daily. That's pay and benefits. Benefits: lunch and dinner daily. Also maybe "Five days a week in the San Francisco office. In the room, with the founders, every day." That's schedule? It's location and schedule (5 days a week in office). So we can have Pay section with salary and equity. Benefits section with lunch/dinner daily. Schedule section with "Five days a week in the San Francisco office. In the room, with the founders, every day." Also US work authorisation required, no visa sponsorship - that's a requirement maybe under Requirements. We must not include sections with filler like "commensurate with experience". We have concrete numbers. Thus we will output:

About the role

... narrative about mission and building ...

Responsibilities

• ... each bullet from "What you will actually build"

Requirements

• ... qualifications from Who this is for and Who this is not for and US work authorisation

Skills

• ... specific tech: Python, JavaScript, React, Next.js, Node, LLMs, etc.

Pay

• Base salary: USD $250,000 to $275,000
• Founding equity (materially larger the earlier you join)

Benefits

• Lunch and dinner provided daily

Schedule

• Five days a week in the San Francisco office; work in‑person with the founders each day

We must ensure we don't repeat job title. No markdown. Only HTML fragment. We need to preserve all substantive information; not invent or summarize away detail. Must not omit details like "The interface. React and Next.js. This is a creative product, so the interface is the product. Motion, latency, feel, the 4px that is wrong." etc. We'll capture those in responsibilities bullets. We need to be careful to not include application instructions like "Send your CV, your GitHub, and whatever you have made that you are quietly proud of. Keiran Hathorn, Big Wave Digital keiran@bigwavedigital.com.au". Remove that. Also remove the quotes from Yoda and Obi-Wan? Those are part of narrative but maybe considered boilerplate? They are part of the posting's flavor but not essential? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The quotes are not boilerplate; they are part of the posting's stylistic intro. Should we keep them? They are substantive? They are not job details but part of the "About" narrative. Probably we can keep them as part of About the role section. It's okay. We must not include duplicated lines. Ensure we don't repeat. Now craft the About the role paragraph: combine the initial narrative up to "What you will actually build". Let's extract: About "Do. Or do not. There is no try." Yoda, The Empire Strikes Back Every engineer eventually finds out which side of the galaxy they are on. One side is the Empire. Enormous. Gleaming. Impossible to steer. You get a badge, a bay, a ticket queue and a performance cycle. Somewhere above you, eleven levels of command decide what ships. Your code is excellent and almost nobody sees it. The catering is genuinely very good. The other side is a small crew in a fast ship, flying straight at something that everyone said could not be done. This is the small crew. The mission Imagine a machine that understands taste. Not in the vague marketing sense, in the working sense. A system that learns what a company looks like, sounds like and feels like, then produces world class creative work on its own, at a volume no human studio could match, without losing the thing that made it good in the first place. That is what this team is building. AI plus creative, pointed at one of the last genuinely human jobs anyone thought was safe. They already do it for customers you would recognise. The next chapter is turning that into a product anyone can pick up and use, and that is the part you are being hired for. The founders are the interesting bit. One trained as an artist before switching to computer science. The other has been writing code for more than a decade. They argue about frame timing and system design in the same conversation. Craft is not a tax on velocity here, it is the whole point. That seems like About the role. Now Responsibilities: "What you will actually build You are one of the first engineers in. There is no platform team to hand the hard half to, and no design system waiting for you. You build the thing, end to end. The interface. React and Next.js. This is a creative product, so the interface is the product. Motion, latency, feel, the 4px that is wrong. A CTO who came out of art school will notice, and will say so. The backend. Node, the app layer, workspaces, state, the API the whole self serve product runs on. The generation layer. Python. Model orchestration, prompt and scene construction, assembly, and the evaluation logic that catches a bad output before a customer ever sees it. The agents. LLM powered agents and agent architectures. The system has to plan the work, not just render it. Multi step reasoning, tool use, branching, retries, guardrails, and the unglamorous engineering that makes an autonomous pipeline survive contact with reality. The infrastructure. Long running jobs, queues, media processing, storage, delivery, and cost per run. Generation is slow, expensive and fails in creative ways. Someone owns the difference between a forty second wait and a four minute one. That someone is you. If human in the loop or preference learning is in your background, bring it up early. Teaching a system what good looks like is the core problem here, not a side quest." We'll break into bullet points. Now Requirements: combine Who this is for and Who this is not for plus US work authorisation. Who this is for bullet list: - Zero to three years as a full stack engineer (they mean it) - Python and JavaScript are both genuinely yours, React and Next.js specifically - You have shipped production web applications end to end, front, back and infrastructure - You have been a founder, a founding engineer, or employee number small at a startup where your job description changed monthly - You have spent time somewhere that takes creative tools or generative AI seriously, the design led product companies and the frontier labs alike - You have built LLM powered things that real people used, not demos - You can defend a technical decision under pressure, and tell a founder they are wrong when they are wrong - You make things outside of work. Design, film, music, art, weird side projects. It does not have to be professional. It counts more than you think - Selective programs like Contrary, Neo Scholars or KP Fellows are a strong signal, not a requirement. Who this is not for: - If your entire career is a straight line through the biggest companies in tech, with no startup chapter anywhere and nothing you built yourself, this will not work. - Not because that work is easy, but because this job has no scaffolding, no roadmap handed down and no one to escalate to at 11pm. - Coming from a giant is fine. Having only ever been inside one is the problem. - Big tech plus a company you started, plus something you shipped alone that people actually used, is a very strong profile here. US work authorisation required. No visa sponsorship of any kind, so US citizens and Green Card holders only. Multiple hires being made on this search - maybe not a requirement but note. We'll include these as bullet points under Requirements. Skills: maybe list specific technologies: Python, JavaScript, React, Next.js, Node.js, LLMs, agent architectures, orchestration, prompt engineering, media processing, queues, storage, delivery, cost optimization, etc. But we already covered many in responsibilities. Could still have a Skills section summarizing core tech: Python, JavaScript, React, Next.js, Node.js, LLM-powered agents, agent architectures, orchestration, evaluation logic, infrastructure (queues, media processing, storage, delivery). We'll keep it concise. Pay: base salary $250k-$275k, founding equity. Benefits: lunch and dinner daily. Schedule: five days a week in SF office, in-person with founders daily. We must not include sections with filler like "commensurate with experience". We