Software Engineer (Product)
Centralize · New York, NY · Today
HybridEngineering$190k–$260k/yrFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes sections: About Centralize (company description), The Role, What You Will Do, What Success Looks Like, What We Are Looking For, This Role Is Not For You If, Preferred Qualifications, The Team You'll Join, Compensation And Logistics, Benefits.
We need to use for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But we must only include sections when posting has real, specific content. We need to map content to appropriate headings. The instructions: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning examples, not exhaustive. So we can use other headings as needed.
Thus we can include headings: About the role, Responsibilities, What Success Looks Like, What We Are Looking For, This Role Is Not For You If, Preferred Qualifications, The Team You'll Join, Compensation And Logistics, Benefits.
We must not include empty sections.
Now we need to extract content precisely.
Let's parse the posting.
Company description:
"About Centralize Enterprise sales runs on relationships, and every tool built to manage them is a database from 2005. Reps lose seven-figure deals because they can't see who actually matters inside an account. We're building the system of intelligence that replaces the CRM. Centralize is the relationship intelligence platform for enterprise revenue teams. Companies like Webflow, Intercom, Brex, Cognition, LangChain, and Cresta use us to close their largest deals. We've grown 5x since last year, and customers are pulling us forward faster than we can ship. We just raised a Series A led by NEA, bringing our total funding to $17M+ alongside Salesforce Ventures, Y Combinator, and operators including Cal Henderson (Co-Founder, Slack), Noah Weiss (former CPO, Slack), and sales leaders from Figma, Box, Dropbox, Anthropic, and Notion. Centralize was founded by Rachit Kataria, a founding engineer on Facebook Shops who helped scale it to 250M MAUs, and Will Wang, who led the launch of Slack Huddles, the fastest-growing product in Slack's history. Our Bar We stay small on purpose. No passengers, no politics, no waiting for permission or for someone else to fix what's broken. We own the unglamorous work alongside the exciting work. The 9pm customer request, the integration buried three layers deep, the bug nobody wants to touch. You go after it because it needs to get done, and because the next thing you build is better for it. You won't have the answers handed to you. The roadmap, the architecture, the right call on a customer request, you'll be the one figuring it out. We hire people who are energized by ambiguity, not slowed down by it. Your work shapes what Centralize becomes."
That's a lot. We'll keep it as a paragraph.
Now "The Role" heading: "We are hiring a product engineer. You will own entire product lines end to end: identifying what to build through direct customer conversations, scoping with the founders, shipping production code across the stack, measuring outcomes, and iterating. This role is well-suited to engineers who have built products from zero to one, led significant initiatives at growth-stage companies, or are looking to grow from senior to staff+ level scope at an early-stage company."
We could incorporate that into About the role or Responsibilities. But we have a separate "What You Will Do" section.
Let's extract "What You Will Do":
"Own a full product line, including roadmap definition, technical architecture, implementation, and measurement of outcomes.
Work directly with customers through sales calls, customer Slack channels, and discovery conversations to identify and prioritize what to build.
Build across the full stack: React and Next.js on the frontend, scalable backend systems, durable third-party integrations, and LLM pipelines tuned to near-perfect accuracy.
Work directly with Rachit and Will on weekly product and architecture decisions.
Set the bar for engineering quality and shipping velocity as one of the first ten hires."
Now "What Success Looks Like":
"Week 1: First PR shipped to production.
Day 15: Owning your first feature end to end, including the customer conversations that scoped it.
Day 60: Leading a product line, with customers using what you built daily."
Now "What We Are Looking For":
"Demonstrated experience building a product from zero to one, or leading a high-impact technical initiative at a growth-stage or larger company.
Strong product instincts. You can sit in a customer call and know what to build next without being told.
Excellent written and verbal English communication. You can write a Loom that moves a deal forward and a PR description another engineer can review in two minutes.
Demonstrated ability to operate independently. We give you the goal, not the steps.
Expertise across complex frontend and backend systems, including React, Next.js, background job infrastructure, and database architecture."
Now "This Role Is Not For You If":
"You want detailed specs handed to you and a clear queue of tickets to work through.
You prefer to specialize narrowly. Product engineers at Centralize work across the full stack and across product surfaces.
You want a slower pace. We work hard and move quickly.
Please only apply if that excites you."
Now "Preferred Qualifications":
"Experience shipping LLM-powered products to production with rigorous evaluation practices.
Direct exposure to enterprise sales cycles, whether participating in or observing customer calls.
Prior experience as a founder, founding engineer, or early engineer at a top-tier early-stage company."
Now "The Team You'll Join":
"You'll work directly with Rachit and Will, alongside former founders and engineers from Coinbase, Gusto, Modern Treasury, and C3 AI."
Now "Compensation And Logistics":
"Location: This role is open to remote candidates in the US, with a strong preference for candidates based in or willing to relocate to San Francisco or New York City. Most of the team works in person, and remote hires should expect regular travel to one of the two hubs.
Work Authorization: We are unable to sponsor visas. Candidates must have existing US work authorization.
Compensation: $190,000 to $260,000 base salary depending on level, plus 0.20% to 0.40% equity. Final offer calibrated to seniority and experience."
Now "Benefits":
"Fully covered medical, dental, and vision insurance
401(k)
Parental leave
Unlimited PTO plus company holidays
Quarterly offsite
Equipment stipend"
We need to format benefits as
for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But we must only include sections when posting has real, specific content. We need to map content to appropriate headings. The instructions: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings? Probably we can use similar headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we need to map content accordingly.
We have content: About Centralize (company overview) could be "About the role"? Actually "About the role" is about the role description. But we have "About Centralize" which is company description. Could treat as "About the role"? Might be better to use "About the role" for role description, and maybe "About the company" not in list. However instructions say use those headings as examples, not strict list. Probably we should use headings that match content: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections we have.
We have:
- About Centralize (company description) maybe fits under "About the role"? Not exactly. Could be "About the role" includes role description and company context. We'll put company overview under "About the role".
- Responsibilities: "What You Will Do" bullet list.
- Requirements: "What We Are Looking For" bullet list.
- Qualifications: "Preferred Qualifications" maybe.
- Skills: maybe "Expertise across complex frontend and backend systems" etc. Could be part of Requirements.
- Benefits: list of benefits.
- Pay: compensation range.
- Schedule: location, remote, work auth, travel expectations.
We must not include sections with filler like "commensurate with experience". We have concrete pay and benefits.
We must not repeat job title as heading. Not include Job ID.
We must remove boilerplate: cookie/navigation/legal/EEO etc. Not present.
We must preserve all substantive information.
We need to output only HTML fragment, no /, no markdown fences.
We'll produce something like:
About the role
About the role
Centralize is the relationship intelligence platform for enterprise revenue teams... (company description)
Responsibilities
- Own a full product line, including roadmap definition, technical architecture, implementation, and measurement of outcomes.
- Work directly with customers through sales calls, customer Slack channels, and discovery conversations to identify and prioritize what to build.
- Build across the full stack: React and Next.js on the frontend, scalable backend systems, durable third-party integrations, and LLM pipelines tuned to near-perfect accuracy.
- Work directly with Rachit and Will on weekly product and architecture decisions.
- Set the bar for engineering quality and shipping velocity as one of the first ten hires.
What Success Looks Like
maybe not in list but could be under Responsibilities? But we have a section "What Success Looks Like". Could be its own heading maybe "What Success Looks Like". But instructions only gave examples; we can add other headings if they have content. Probably okay. But to follow instruction, we could map "What Success Looks Like" to maybe "Responsibilities"? But better to keep as its own heading. We need to decide which headings to use. The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning examples, not exhaustive. So we can use other headings as needed.
Thus we can include headings: About the role, Responsibilities, What Success Looks Like, What We Are Looking For, This Role Is Not For You If, Preferred Qualifications, The Team You'll Join, Compensation And Logistics, Benefits.
We must not include empty sections.
Now we need to extract content precisely.
Let's parse the posting.
Company description:
"About Centralize Enterprise sales runs on relationships, and every tool built to manage them is a database from 2005. Reps lose seven-figure deals because they can't see who actually matters inside an account. We're building the system of intelligence that replaces the CRM. Centralize is the relationship intelligence platform for enterprise revenue teams. Companies like Webflow, Intercom, Brex, Cognition, LangChain, and Cresta use us to close their largest deals. We've grown 5x since last year, and customers are pulling us forward faster than we can ship. We just raised a Series A led by NEA, bringing our total funding to $17M+ alongside Salesforce Ventures, Y Combinator, and operators including Cal Henderson (Co-Founder, Slack), Noah Weiss (former CPO, Slack), and sales leaders from Figma, Box, Dropbox, Anthropic, and Notion. Centralize was founded by Rachit Kataria, a founding engineer on Facebook Shops who helped scale it to 250M MAUs, and Will Wang, who led the launch of Slack Huddles, the fastest-growing product in Slack's history. Our Bar We stay small on purpose. No passengers, no politics, no waiting for permission or for someone else to fix what's broken. We own the unglamorous work alongside the exciting work. The 9pm customer request, the integration buried three layers deep, the bug nobody wants to touch. You go after it because it needs to get done, and because the next thing you build is better for it. You won't have the answers handed to you. The roadmap, the architecture, the right call on a customer request, you'll be the one figuring it out. We hire people who are energized by ambiguity, not slowed down by it. Your work shapes what Centralize becomes."
That's a lot. We'll keep it as a paragraph.
Now "The Role" heading: "We are hiring a product engineer. You will own entire product lines end to end: identifying what to build through direct customer conversations, scoping with the founders, shipping production code across the stack, measuring outcomes, and iterating. This role is well-suited to engineers who have built products from zero to one, led significant initiatives at growth-stage companies, or are looking to grow from senior to staff+ level scope at an early-stage company."
We could incorporate that into About the role or Responsibilities. But we have a separate "What You Will Do" section.
Let's extract "What You Will Do":
"Own a full product line, including roadmap definition, technical architecture, implementation, and measurement of outcomes.
Work directly with customers through sales calls, customer Slack channels, and discovery conversations to identify and prioritize what to build.
Build across the full stack: React and Next.js on the frontend, scalable backend systems, durable third-party integrations, and LLM pipelines tuned to near-perfect accuracy.
Work directly with Rachit and Will on weekly product and architecture decisions.
Set the bar for engineering quality and shipping velocity as one of the first ten hires."
Now "What Success Looks Like":
"Week 1: First PR shipped to production.
Day 15: Owning your first feature end to end, including the customer conversations that scoped it.
Day 60: Leading a product line, with customers using what you built daily."
Now "What We Are Looking For":
"Demonstrated experience building a product from zero to one, or leading a high-impact technical initiative at a growth-stage or larger company.
Strong product instincts. You can sit in a customer call and know what to build next without being told.
Excellent written and verbal English communication. You can write a Loom that moves a deal forward and a PR description another engineer can review in two minutes.
Demonstrated ability to operate independently. We give you the goal, not the steps.
Expertise across complex frontend and backend systems, including React, Next.js, background job infrastructure, and database architecture."
Now "This Role Is Not For You If":
"You want detailed specs handed to you and a clear queue of tickets to work through.
You prefer to specialize narrowly. Product engineers at Centralize work across the full stack and across product surfaces.
You want a slower pace. We work hard and move quickly.
Please only apply if that excites you."
Now "Preferred Qualifications":
"Experience shipping LLM-powered products to production with rigorous evaluation practices.
Direct exposure to enterprise sales cycles, whether participating in or observing customer calls.
Prior experience as a founder, founding engineer, or early engineer at a top-tier early-stage company."
Now "The Team You'll Join":
"You'll work directly with Rachit and Will, alongside former founders and engineers from Coinbase, Gusto, Modern Treasury, and C3 AI."
Now "Compensation And Logistics":
"Location: This role is open to remote candidates in the US, with a strong preference for candidates based in or willing to relocate to San Francisco or New York City. Most of the team works in person, and remote hires should expect regular travel to one of the two hubs.
Work Authorization: We are unable to sponsor visas. Candidates must have existing US work authorization.
Compensation: $190,000 to $260,000 base salary depending on level, plus 0.20% to 0.40% equity. Final offer calibrated to seniority and experience."
Now "Benefits":
"Fully covered medical, dental, and vision insurance
401(k)
Parental leave
Unlimited PTO plus company holidays
Quarterly offsite
Equipment stipend"
We need to format benefits as - .
Now we need to ensure we don't include any boilerplate like "Please only apply if that excites you." That's part of "This Role Is Not For You If". We'll keep it.
Now we need to output HTML fragment.
We'll wrap each section in
heading and then content.
For paragraphs, use
. For lists,
- .
We must not repeat job title as heading. Not needed.
Now produce final HTML.
Let's craft.
First section: About the role (maybe include company description and The Role summary). We'll combine company description and The Role summary into a paragraph or two.
We'll do:
About the role
Centralize is the relationship intelligence platform for enterprise revenue teams. Companies like Webflow, Intercom, Brex, Cognition, LangChain, and Cresta use us to close their largest deals. We've grown 5x since last year, and customers are pulling us forward faster than we can ship. We just raised a Series A led by NEA, bringing our total funding to $17M+ alongside Salesforce Ventures, Y Combinator, and operators including Cal Henderson (Co‑Founder, Slack), Noah Weiss (former CPO, Slack), and sales leaders from Figma, Box, Dropbox, Anthropic, and Notion. Centralize was founded by Rachit Kataria, a founding engineer on Facebook Shops who helped scale it to 250M MAUs, and Will Wang, who led the launch of Slack Huddles, the fastest‑growing product in Slack's history. We stay small on purpose — no passengers, no politics, no waiting for permission. We own the unglamorous work alongside the exciting work, from the 9 pm customer request to deep‑layer integrations and bugs nobody wants to touch. You figure out the roadmap, architecture, and customer‑request trade‑offs; your work shapes what Centralize becomes.
We are hiring a
heading and then content. For paragraphs, use
. For lists,
- .
We must not repeat job title as heading. Not needed.
Now produce final HTML.
Let's craft.
First section: About the role (maybe include company description and The Role summary). We'll combine company description and The Role summary into a paragraph or two.
We'll do:
About the role
Centralize is the relationship intelligence platform for enterprise revenue teams. Companies like Webflow, Intercom, Brex, Cognition, LangChain, and Cresta use us to close their largest deals. We've grown 5x since last year, and customers are pulling us forward faster than we can ship. We just raised a Series A led by NEA, bringing our total funding to $17M+ alongside Salesforce Ventures, Y Combinator, and operators including Cal Henderson (Co‑Founder, Slack), Noah Weiss (former CPO, Slack), and sales leaders from Figma, Box, Dropbox, Anthropic, and Notion. Centralize was founded by Rachit Kataria, a founding engineer on Facebook Shops who helped scale it to 250M MAUs, and Will Wang, who led the launch of Slack Huddles, the fastest‑growing product in Slack's history. We stay small on purpose — no passengers, no politics, no waiting for permission. We own the unglamorous work alongside the exciting work, from the 9 pm customer request to deep‑layer integrations and bugs nobody wants to touch. You figure out the roadmap, architecture, and customer‑request trade‑offs; your work shapes what Centralize becomes.
We are hiring a