Product Engineer
for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate etc. No application instructions.
We need to output only HTML fragment, no /, no markdown fences.
Let's parse content.
Intro: "What We’re Building Denari is building the modern software stack for accounting firms: an AI-powered platform that unifies client collaboration, document management, workflow automation, and financial insights in one place. We’re a small, well-funded team with a built-in proving ground. Our sister company, Lucida Tax + Accounting, uses what we build every day, so we hear how a feature landed within hours of shipping it."
That's about the role/company. Could be "About the role". We'll put that as prose.
Next: "Your Impact Here Is Only Limited by Your Initiative We are genuinely open to change. If you have an idea and you’re willing to put in the effort, we will back you; whether that’s a new product direction, a better internal process, or rethinking how a whole workflow should work. AI has also changed what counts as "hard." Things that used to be too expensive or time-consuming to attempt are now on the table, and we use that to stay flexible in a way that empowers people. If something was off-limits before because it was "too difficult," that’s an invitation to question it."
That could be part of About the role or maybe separate? But we can incorporate into About the role.
Next: "The Tools You’ll Actually Get to Use We invest heavily in AI tooling and efficiency engineering, and our agents are harnessed directly into the software we work in, which compounds how fast we can move: AI development: Claude Code, Claude Cowork, Codex, and Conductor for running parallel agent workflowsModern stack: Next, oRPC, TanStack-everything, and other current-generation toolingConnected workflow: Linear for project management and Grain for meeting intelligence, both wired into our internal agentsDeveloper experience: 1Password integrated directly into development secrets injection, with seeding, tests, and more wired into Conductor (we care about our dx a lot). A lot of companies don’t get this luxury. We do, and we constantly try new things. If a better tool ships next month, we’ll probably be experimenting with it the week after."
That's a list of tools; could be Skills section.
Next: "How We Work Together This is a hybrid role based in Madison. You’ll spend three days a week in the office with the team, and the rest of the week you’ll work from wherever you do your best thinking. Day to day, the whole team (in-office and remote) shares a digital engineering office in Gather. Drop by someone’s desk to talk through a problem, or set focus time when you need to go heads down and everyone will see it at a glance."
That's about work arrangement; could be Schedule? But schedule is not explicit pay; but we have hybrid schedule details. The instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state hybrid schedule: three days in office, rest remote. That's schedule info. So we can include a Schedule section with that detail. However we must not include placeholder like "varies". This is specific. So we can include Schedule.
But also we have Benefits section later: "Benefits Health, dental, vision, life, and disability insurance401(k) with match20 days PTO plus paid holidays". That's benefits.
We also have "What You’ll Do Design, build, and ship features across multiple products and codebasesUse LLMs and AI agents throughout your workflow wherever they accelerate outputParticipate in architectural decisions and help define best practices for scalability, maintainability, and securityWork directly with founders and with real accounting firms using the productWear multiple hats; we’re a small startup and the most interesting work often sits between job descriptionsTalk directly with customers: you’ll join calls with the accounting firms using our products, hear problems firsthand, and ship features they care about". That's responsibilities.
We also have "We Love It When You disagree with us and say so, because you care about getting it rightYou take ownership of a problem end to end instead of waiting for permissionYou try a new tool or approach on a Friday and demo it on MondayYou ask “why is this hard?” and discover it doesn’t have to be anymoreYou help a teammate get unstuck even when it’s not your area". That's more like cultural expectations; could be part of Culture or maybe Qualifications? But we have Our Culture section later.
Our Culture: "We care that our co-workers care, even when we disagree. We’d rather hash out a real disagreement than watch someone quietly check out. We’re not AI-pilled, but we think AI is clearly a complete game-changer. We’re just another crew trying to figure it out, which means we stay open and experiment constantly. Assertiveness and accountability. Speak up, commit, follow through, and own the outcome either way. Collaboration and flexibility. Small team, multiple products, lots of context-switching. We support each other through it. Supportive by default. When someone’s stuck, struggling, or stretching into something new, the team shows up."
That's culture.
What We’re Looking For: "Strong software engineering fundamentals (how you think matters more to us than your years of experience)Genuine curiosity about AI tooling, with experience using LLMs or agents in your workflow a plusComfort with ambiguity and small-team dynamicsClear, honest, upfront communication". That's qualifications/requirements.
We need to decide sections: About the role (intro + impact), Responsibilities (What You’ll Do), Requirements/Qualifications (What We’re Looking For), Skills (Tools), Benefits, Schedule, Culture maybe? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It lists possible headings but says include a section ONLY when the posting has real, specific content for it. It doesn't forbid adding other headings like Culture, but the list includes examples; we could include Culture as a heading if we want, but it's not in the list. Safer to stick to those headings. Could we incorporate Culture into About the role or Requirements? Probably better to have a separate Culture section but not in list; risk of being considered extra. The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive. But to be safe, we could include Culture as a section heading; it's not prohibited. However they said "include a section ONLY when the posting has real, specific content for it". We have culture content. So we could include a Culture section.
But we must not repeat the job title as a heading. No job title given.
We must not put Job ID/requisition numbers as headings.
We need to output only HTML fragment.
Let's structure:
About the role
... (intro + impact)
Responsibilities
- Design, build, and ship features across multiple products and codebases
- Use LLMs and AI agents throughout your workflow wherever they accelerate output
- Participate in architectural decisions and help define best practices for scalability, maintainability, and security
- Work directly with founders and with real accounting firms using the product
- Wear multiple hats; we’re a small startup and the most interesting work often sits between job descriptions
- Talk directly with customers: you’ll join calls with the accounting firms using our products, hear problems firsthand, and ship features they care about
Requirements
- Strong software engineering fundamentals (how you think matters more to us than your years of experience)
- Genuine curiosity about AI tooling, with experience using LLMs or agents in your workflow a plus
- Comfort with ambiguity and small-team dynamics
- Clear, honest, upfront communication
Alternatively could split Requirements and Qualifications but we have only one list. Could combine as Requirements.
Skills
- AI development: Claude Code, Claude Cowork, Codex, and Conductor for running parallel agent workflows
- Modern stack: Next.js, oRPC, TanStack-everything, and other current-generation tooling
- Connected workflow: Linear for project management and Grain for meeting intelligence, both wired into internal agents
- Developer experience: 1Password integrated directly into development secrets injection, with seeding, tests, and more wired into Conductor
But we need to preserve the exact phrasing: "Modern stack: Next, oRPC, TanStack-everything, and other current-generation tooling". It says "Next" not "Next.js". We'll keep as given.
Also "AI development: Claude Code, Claude Cowork, Codex, and Conductor for running parallel agent workflows". Keep.
"Connected workflow: Linear for project management and Grain for meeting intelligence, both wired into our internal agents". Keep.
"Developer experience: 1Password integrated directly into development secrets injection, with seeding, tests, and more wired into Conductor (we care about our dx a lot)." Keep.
We could keep as prose but better as list items.
Benefits
- Health, dental, vision, life, and disability insurance
- 401(k) with match
- 20 days PTO plus paid holidays
Note the original had no commas between items: "Health, dental, vision, life, and disability insurance401(k) with match20 days PTO plus paid holidays". We need to split correctly. We'll separate as above.
Schedule
This is a hybrid role based in Madison. You’ll spend three days a week in the office with the team, and the rest of the week you’ll work from wherever you do your best thinking.
Optionally also mention Gather digital office but that's part of How We Work Together; could be included in Schedule or About the role. But we already captured schedule. Could add a separate How We Work Together but not needed.
We also have Culture content; we could add a Culture section.
Culture
We care that our co-workers care, even when we disagree. We’d rather hash out a real disagreement than watch someone quietly check out. We’re not AI-pilled, but we think AI is clearly a complete game-changer. We’re just another crew trying to figure it out, which means we stay open and experiment constantly. Assertiveness and accountability. Speak up, commit, follow through, and own the outcome either way. Collaboration and flexibility. Small team, multiple products, lots of context-switching. We support each other through it. Supportive by default. When someone’s stuck,
for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate etc. No application instructions. We need to output only HTML fragment, no /, no markdown fences. Let's parse content. Intro: "What We’re Building Denari is building the modern software stack for accounting firms: an AI-powered platform that unifies client collaboration, document management, workflow automation, and financial insights in one place. We’re a small, well-funded team with a built-in proving ground. Our sister company, Lucida Tax + Accounting, uses what we build every day, so we hear how a feature landed within hours of shipping it." That's about the role/company. Could be "About the role". We'll put that as prose. Next: "Your Impact Here Is Only Limited by Your Initiative We are genuinely open to change. If you have an idea and you’re willing to put in the effort, we will back you; whether that’s a new product direction, a better internal process, or rethinking how a whole workflow should work. AI has also changed what counts as "hard." Things that used to be too expensive or time-consuming to attempt are now on the table, and we use that to stay flexible in a way that empowers people. If something was off-limits before because it was "too difficult," that’s an invitation to question it." That could be part of About the role or maybe separate? But we can incorporate into About the role. Next: "The Tools You’ll Actually Get to Use We invest heavily in AI tooling and efficiency engineering, and our agents are harnessed directly into the software we work in, which compounds how fast we can move: AI development: Claude Code, Claude Cowork, Codex, and Conductor for running parallel agent workflowsModern stack: Next, oRPC, TanStack-everything, and other current-generation toolingConnected workflow: Linear for project management and Grain for meeting intelligence, both wired into our internal agentsDeveloper experience: 1Password integrated directly into development secrets injection, with seeding, tests, and more wired into Conductor (we care about our dx a lot). A lot of companies don’t get this luxury. We do, and we constantly try new things. If a better tool ships next month, we’ll probably be experimenting with it the week after." That's a list of tools; could be Skills section. Next: "How We Work Together This is a hybrid role based in Madison. You’ll spend three days a week in the office with the team, and the rest of the week you’ll work from wherever you do your best thinking. Day to day, the whole team (in-office and remote) shares a digital engineering office in Gather. Drop by someone’s desk to talk through a problem, or set focus time when you need to go heads down and everyone will see it at a glance." That's about work arrangement; could be Schedule? But schedule is not explicit pay; but we have hybrid schedule details. The instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state hybrid schedule: three days in office, rest remote. That's schedule info. So we can include a Schedule section with that detail. However we must not include placeholder like "varies". This is specific. So we can include Schedule. But also we have Benefits section later: "Benefits Health, dental, vision, life, and disability insurance401(k) with match20 days PTO plus paid holidays". That's benefits. We also have "What You’ll Do Design, build, and ship features across multiple products and codebasesUse LLMs and AI agents throughout your workflow wherever they accelerate outputParticipate in architectural decisions and help define best practices for scalability, maintainability, and securityWork directly with founders and with real accounting firms using the productWear multiple hats; we’re a small startup and the most interesting work often sits between job descriptionsTalk directly with customers: you’ll join calls with the accounting firms using our products, hear problems firsthand, and ship features they care about". That's responsibilities. We also have "We Love It When You disagree with us and say so, because you care about getting it rightYou take ownership of a problem end to end instead of waiting for permissionYou try a new tool or approach on a Friday and demo it on MondayYou ask “why is this hard?” and discover it doesn’t have to be anymoreYou help a teammate get unstuck even when it’s not your area". That's more like cultural expectations; could be part of Culture or maybe Qualifications? But we have Our Culture section later. Our Culture: "We care that our co-workers care, even when we disagree. We’d rather hash out a real disagreement than watch someone quietly check out. We’re not AI-pilled, but we think AI is clearly a complete game-changer. We’re just another crew trying to figure it out, which means we stay open and experiment constantly. Assertiveness and accountability. Speak up, commit, follow through, and own the outcome either way. Collaboration and flexibility. Small team, multiple products, lots of context-switching. We support each other through it. Supportive by default. When someone’s stuck, struggling, or stretching into something new, the team shows up." That's culture. What We’re Looking For: "Strong software engineering fundamentals (how you think matters more to us than your years of experience)Genuine curiosity about AI tooling, with experience using LLMs or agents in your workflow a plusComfort with ambiguity and small-team dynamicsClear, honest, upfront communication". That's qualifications/requirements. We need to decide sections: About the role (intro + impact), Responsibilities (What You’ll Do), Requirements/Qualifications (What We’re Looking For), Skills (Tools), Benefits, Schedule, Culture maybe? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It lists possible headings but says include a section ONLY when the posting has real, specific content for it. It doesn't forbid adding other headings like Culture, but the list includes examples; we could include Culture as a heading if we want, but it's not in the list. Safer to stick to those headings. Could we incorporate Culture into About the role or Requirements? Probably better to have a separate Culture section but not in list; risk of being considered extra. The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive. But to be safe, we could include Culture as a section heading; it's not prohibited. However they said "include a section ONLY when the posting has real, specific content for it". We have culture content. So we could include a Culture section.
But we must not repeat the job title as a heading. No job title given.
We must not put Job ID/requisition numbers as headings.
We need to output only HTML fragment.
Let's structure:
About the role
... (intro + impact)
Responsibilities
- Design, build, and ship features across multiple products and codebases
- Use LLMs and AI agents throughout your workflow wherever they accelerate output
- Participate in architectural decisions and help define best practices for scalability, maintainability, and security
- Work directly with founders and with real accounting firms using the product
- Wear multiple hats; we’re a small startup and the most interesting work often sits between job descriptions
- Talk directly with customers: you’ll join calls with the accounting firms using our products, hear problems firsthand, and ship features they care about
Requirements
- Strong software engineering fundamentals (how you think matters more to us than your years of experience)
- Genuine curiosity about AI tooling, with experience using LLMs or agents in your workflow a plus
- Comfort with ambiguity and small-team dynamics
- Clear, honest, upfront communication
Skills
- AI development: Claude Code, Claude Cowork, Codex, and Conductor for running parallel agent workflows
- Modern stack: Next.js, oRPC, TanStack-everything, and other current-generation tooling
- Connected workflow: Linear for project management and Grain for meeting intelligence, both wired into internal agents
- Developer experience: 1Password integrated directly into development secrets injection, with seeding, tests, and more wired into Conductor
Benefits
- Health, dental, vision, life, and disability insurance
- 401(k) with match
- 20 days PTO plus paid holidays
Schedule
This is a hybrid role based in Madison. You’ll spend three days a week in the office with the team, and the rest of the week you’ll work from wherever you do your best thinking.
Optionally also mention Gather digital office but that's part of How We Work Together; could be included in Schedule or About the role. But we already captured schedule. Could add a separate How We Work Together but not needed. We also have Culture content; we could add a Culture section.Culture
We care that our co-workers care, even when we disagree. We’d rather hash out a real disagreement than watch someone quietly check out. We’re not AI-pilled, but we think AI is clearly a complete game-changer. We’re just another crew trying to figure it out, which means we stay open and experiment constantly. Assertiveness and accountability. Speak up, commit, follow through, and own the outcome either way. Collaboration and flexibility. Small team, multiple products, lots of context-switching. We support each other through it. Supportive by default. When someone’s stuck,