Software Engineer, Staff (Applied AI)

We need to output HTML fragment only, with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading only if there is real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate. We need to parse the posting. Content: - About Lightfield (company description) - maybe not needed as a heading? The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The "About Lightfield" is company overview; not one of those headings. Should we include it? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples, but we should include sections only when posting has real specific content for it. The posting includes "About Lightfield" and "About The Role". "About The Role" is essentially a summary of role. Could map to "About the role". We'll include that. Then "What you'll do" -> Responsibilities. Then "Who you are" -> Requirements/Qualifications/Skills. We need to split appropriately. The posting lists experience, tech stack, degree, AI/ML concepts, passion, etc. Could be Requirements (experience, degree) and Skills (tech stack, LLM experience). Qualifications maybe overlapping. We'll decide: Use Requirements for experience and education; Skills for technical stack and LLM familiarity; Qualifications maybe for AI/ML concepts and ability to drive projects etc. But we must not create thin sections. Better to combine into a few substantive sections: Responsibilities, Requirements (including experience, education, skills), Benefits & Perks, Pay (Compensation Range). Schedule maybe not mentioned except "Wednesdays work from home" which is schedule info. So we can include Schedule heading with that detail. We must not include headings with filler like "commensurate with experience". Not present. We must not include boilerplate like EEO etc. Not present. We need to preserve all substantive information: company description, role description, responsibilities list, who you are list, benefits list, compensation range, schedule note. We must not repeat job title (not given). No Job ID. We must output only HTML fragment. Let's extract content. Company description: "About Lightfield Lightfield is reimagining CRM as a world model of a business. By learning from emails, meetings, and customer conversations, we’re building a living understanding of how a company works—so AI can help teams anticipate what comes next, make better decisions, and take action. More than 5,000 companies have used the product since its November launch. We’ve raised more than $70M from Andreessen Horowitz, Coatue, Maverick Ventures, and Greylock to attack the biggest software category in the world. We previously built Tome, which reached more than 25 million users, and our team brings experience from Llama, Instagram, Google, and Salesforce." We could put this as a

maybe under a heading? Not required headings. Could just include as a

before sections. The instruction says use headings for sections like About the role etc. It doesn't forbid other

outside headings. So we can include a

for company overview. Then About the role: "About The Role We’re looking for a driven, creative engineer who is excited about the challenge of leveraging LLMs to build exceptionally innovative product experiences. You’ll join us at the frontier of AI product development, developing industry-leading approaches to solve important customer problems. Engineers at Lightfield own and drive projects from inception to impact, working with teammates of all functions along the way. You’ll also push our company’s overall product and technical vision as we learn from each project and continue to scale." We'll put that under

About the role

and then a

with that text. Responsibilities: "What you'll do Collaborate with product leaders to identify customer problems, scope requirements, and implement LLM-powered solutions. Apply LLMs as reasoning engines to build domain-specific AI assistants. Create and enhance prompts, applying techniques like few-shot learning and chain-of-thought. Develop and optimize end-to-end RAG pipelines and agent architectures to leverage public and proprietary data. Improve end-to-end AI agent quality (e.g. relevance, fidelity, latency) via empirical evaluation and iteration. Build and enhance systems and tools that enable high-velocity experimentation (e.g. LLM-powered automated evaluation) and customized product experiences. Stay at the forefront of AI research and incorporate state-of-the-art techniques. Shape technical direction and best practices for AI application development at Lightfield. Help build a world-class engineering team by recruiting and mentoring teammates." We'll put under

Responsibilities

and a

• for each bullet. The text is sentences; we can split by sentences. Each bullet corresponds to each sentence? Let's list: - Collaborate with product leaders to identify customer problems, scope requirements, and implement LLM-powered solutions. - Apply LLMs as reasoning engines to build domain-specific AI assistants. - Create and enhance prompts, applying techniques like few-shot learning and chain-of-thought. - Develop and optimize end-to-end RAG pipelines and agent architectures to leverage public and proprietary data. - Improve end-to-end AI agent quality (e.g. relevance, fidelity, latency) via empirical evaluation and iteration. - Build and enhance systems and tools that enable high-velocity experimentation (e.g. LLM-powered automated evaluation) and customized product experiences. - Stay at the forefront of AI research and incorporate state-of-the-art techniques. - Shape technical direction and best practices for AI application development at Lightfield. - Help build a world-class engineering team by recruiting and mentoring teammates. We'll output each as
• . Now Who you are: list of qualifications. "You have 7+ years experience and the ability to ramp up quickly on a tech stack that features TypeScript, React, Next.js, Node.js, Apollo GraphQL, and Aurora PostgreSQL. You have explored working with LLMs, either through professional projects or personal experimentation. You have a degree in Computer Science or a related field, with a strong foundation in software engineering principles. You are familiar with AI and ML concepts (e.g. training, evaluation techniques). You are passionate about keeping up with and exploring the latest advancements in LLMs and LLMOps (including open source solutions). You are excited to develop new best practices in an emerging domain. You can drive a project with an ambiguous problem independently. You enjoy strategically balancing ambitious vision with frequent delivery of user value. You are able to clearly communicate your reasoning and decisions to your teammates (technical and nontechnical) at an appropriate altitude of detail. You are energized by building software experiences customers will use directly and depend on to do their jobs successfully." We need to split into sections: Requirements, Qualifications, Skills. Let's decide: - Requirements: 7+ years experience, degree in CS or related field, ability to ramp up quickly on tech stack? Actually tech stack is skill. Could put experience and degree under Requirements. - Skills: tech stack (TypeScript, React, Next.js, Node.js, Apollo GraphQL, Aurora PostgreSQL), LLM exploration, familiarity with AI/ML concepts, passion for LLMs/LLMOps, excited to develop new best practices, ability to drive ambiguous project independently, enjoy balancing vision with delivery, clear communication, energized by building user-facing software. - Qualifications: maybe overlapping. But we can combine Skills and Qualifications into one section? The instruction says prefer a few substantive sections over many thin ones. So we could have Requirements (experience + degree) and Skills (everything else). Or we could have Requirements (experience, degree, ability to ramp up), Skills (tech stack, LLM, AI/ML concepts), Qualifications (soft skills like communication, driving ambiguous project, etc.). That would be three sections, each substantive. Let's extract: Requirements: - 7+ years experience - Degree in Computer Science or related field, with strong foundation in software engineering principles. Skills: - Tech stack: TypeScript, React, Next.js, Node.js, Apollo GraphQL, Aurora PostgreSQL - Experience working with LLMs (professional or personal) - Familiar with AI and ML concepts (training, evaluation techniques) - Passionate about keeping up with and exploring latest advancements in LLMs and LLMOps (including open source) - Excited to develop new best practices in an emerging domain Qualifications: - Ability to drive a project with an ambiguous problem independently - Enjoy strategically balancing ambitious vision with frequent delivery of user value - Able to clearly communicate reasoning and decisions to teammates (technical and nontechnical) at appropriate altitude of detail - Energized by building software experiences customers will use directly and depend on to do their jobs successfully We could also include "ability to ramp up quickly on a tech stack" maybe under Skills. Now Benefits & Perks: list: "Competitive salary Meaningful early equity Health insurance (medical, dental, vision) 3 weeks of PTO 11 paid company holidays + we enjoy a winter holiday break 3 months of paid family leave Wednesdays work from home Regular team dinners, events, offsites, and retreats 401k plan Other perks include: commuter and lunch stipend" We need Benefits section only if posting has real specific content. It does. We'll put under

  Benefits

  and a
  • each. Pay: "Compensation Range: $220K - $300K". We'll put under

    Pay

    and a

    with that. Schedule: "Wednesdays work from home" is schedule info. We'll put under

    Schedule

    and a

    with that. We must not include headings with filler. All have content. Now we need to output HTML fragment only, no /, no markdown fences. We'll start with company overview

    . Then sections. Let's craft. Company overview: maybe wrap in

    about Lightfield. Then

    About the role

    ...

    Then

    Responsibilities

    ...
    Then

    Requirements

    ...
    Then

    Skills

    ...
    Then

    Qualifications

    ...
    Then

    Benefits

    ...
    Then

    Pay

    Compensation Range: $220K - $300K

    Then

    Schedule

    Wednesdays work from home

    Check that we haven't missed any substantive info: company overview included; about the role included; responsibilities included; requirements (experience, degree) included; skills (tech stack, LLM experience, AI/ML concepts, passion for LLMs/LLMOps, excitement to develop best practices) included; qualifications (drive ambiguous project, balance vision/delivery, communication, energized by building user-facing software) included; benefits list included; pay included; schedule included. We omitted "ability to ramp up quickly on a tech stack" - we could include that under Skills as a bullet. Let's add. Also "You have explored working with LLMs, either through professional projects or personal experimentation." covered. Also "You are familiar with AI and ML concepts (e.g. training, evaluation techniques)." covered. Also "You are passionate about keeping up with and exploring the latest advancements in LLMs and LLMOps (including open source solutions)." covered. Also "You are excited to develop new best practices in an emerging domain." covered. Also "You can drive a project with an ambiguous problem independently." covered under Qualifications. Also