Senior Software Engineer
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should include sections only if content exists. The posting includes "About The Role" (description). That's about the role. So we can have About the role
with prose.
- Detailed Responsibilities: list of responsibilities with percentages. That's responsibilities. Should be a - list.
- Minimum Qualifications: list of qualifications. That's qualifications. Should be
- .
- What Can Help Your Application Stand Out: could be considered "Skills" or "Preferred qualifications". The instruction includes Skills section. We can treat that as Skills.
- Benefits, Pay, Schedule: not mentioned. So we should NOT include those sections.
- Also there is "About G2 - The Company" and "About G2 - Our People". Those are not requested sections; we should not include them as headings unless they map to one of the allowed headings. They are not in the list, so we should omit them. Also we should not repeat job title as heading.
- Also there is "Our Commitment to Inclusivity and Diversity", "For job applicants in California..." etc. Those are boilerplate; we should remove.
- Also "How We Use AI Technology In Our Hiring Process" etc. Remove.
Thus we need to output HTML fragment with sections: About the role, Responsibilities, Qualifications, Skills (maybe). Also maybe Requirements? The Minimum Qualifications could be considered Requirements. The instruction includes Requirements as a possible heading. We have both Qualifications and Requirements; we need to decide which to use. The posting has "Minimum Qualifications". That could be either Requirements or Qualifications. Since both headings are allowed, we could include either. To avoid duplication, we should pick one that best matches. The posting says "Minimum Qualifications". So we can use
Qualifications
. Or we could use Requirements. I'd choose Qualifications.
What about "What Can Help Your Application Stand Out" - could be Skills. We'll include Skills.
Thus sections: About the role, Responsibilities, Qualifications, Skills.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include the prose from About The Role, the responsibilities list (including percentages?), the qualifications list, and the "What Can Help Your Application Stand Out" list.
We must not add placeholder text like "commensurate with experience". Not present.
We need to format as About the role
then ... prose ...
. For responsibilities: Responsibilities
then - ... each bullet ...
. For qualifications: similar. For skills: similar.
We need to preserve the percentages? The responsibilities have percentages in brackets like [60%], [35%], [5%]. Should we keep them? They are substantive detail. Yes, we should keep them.
We need to ensure we don't include any boilerplate like "Minimum Qualifications We realize applying for jobs can feel daunting at times...". That's part of the qualifications section preamble. We should include that preamble as prose before the list? The instruction says use for prose. So we could include that preamble as a
then the list.
Similarly for "What Can Help Your Application Stand Out" we could include a preamble.
Let's extract the exact text.
About The Role:
"As a Senior Software Engineer, you will create new products and features end-to-end which directly contribute to G2’s key organizational goals. Your responsibilities will center around architecting the solution, delegating implementation to your agents across the full stack, and reviewing and validating what they produce with confidence in their performance. As a technologist, you will be a key voice in defining and refining product concepts and you’ll act as a hands-on, in-person technical partner to stakeholders and leadership. You will adopt industry-leading agentic engineering techniques and leverage “agent-first” ways of working to deliver products, reflecting the realities of today’s software development lifecycle."
That's the paragraph before "Detailed Responsibilities". We'll put that in
.
Then Detailed Responsibilities:
"Build AI and agent-first products and features [60%]: Contribute across the full software stack to deliver user journeys to production, owning implementation quality from architecture to releaseDesign and build agents that apply prompts, context, tools, and model reasoning to fulfill user journeys, generate content, and automate processesApply sound software engineering and system design principles to produce solutions that are observable, maintainable, scalable, and production readyValidate solutions against functional requirements using both traditional QA methods, model-based evals, and agent tracing to ensure quality is measurable and reproducibleIncorporate agentic software engineering techniques into the development workflow across the SDLC, from planning, design, implementation, testing, and maintenance Actively participate in product definition as a technologist [35%]: Drive product definition with designers and PMs: ideate, explore, and prototype with stakeholders, then cut down possible options to arrive at deliverable, but well-rounded solutionsWholly conceive and ship features & MVP iterations early in the product definition phase that directly advance high-visibility organizational goalsStrike the right balance between investment in UX quality and tending to practical business needs through the product development process.Partner with other engineering stakeholders to identify what technology makes possible, and what makes implementing a given product or feature hard. Bring that perspective into project scoping and prioritization Be a source of influence for other engineers on the team [5%]: Share knowledge, techniques, and agentic software engineering practices in async formats and dedicated venues, like technical discussions and team meetingsChampion the use of AI solutions for engineering and product tasks, accelerate product velocity and team’s execution"
We need to split into bullet points. The original text seems to have missing punctuation and line breaks. We need to parse into logical bullets.
We can break at each major section:
- Build AI and agent-first products and features [60%]:
- Contribute across the full software stack to deliver user journeys to production, owning implementation quality from architecture to release
- Design and build agents that apply prompts, context, tools, and model reasoning to fulfill user journeys, generate content, and automate processes
- Apply sound software engineering and system design principles to produce solutions that are observable, maintainable, scalable, and production ready
- Validate solutions against functional requirements using both traditional QA methods, model-based evals, and agent tracing to ensure quality is measurable and reproducible
- Incorporate agentic software engineering techniques into the development workflow across the SDLC, from planning, design, implementation, testing, and maintenance
- Actively participate in product definition as a technologist [35%]:
- Drive product definition with designers and PMs: ideate, explore, and prototype with stakeholders, then cut down possible options to arrive at deliverable, but well-rounded solutions
- Wholly conceive and ship features & MVP iterations early in the product definition phase that directly advance high-visibility organizational goals
- Strike the right balance between investment in UX quality and tending to practical business needs through the product development process.
- Partner with other engineering stakeholders to identify what technology makes possible, and what makes implementing a given product or feature hard. Bring that perspective into project scoping and prioritization
- Be a source of influence for other engineers on the team [5%]:
- Share knowledge, techniques, and agentic software engineering practices in async formats and dedicated venues, like technical discussions and team meetings
- Champion the use of AI solutions for engineering and product tasks, accelerate product velocity and team’s execution
We need to keep the content exactly as given, but we can reformat into list items. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we must not lose any detail. We can keep the substance but we can rephrase? It says do NOT invent or summarize away detail. Rephrasing might be considered summarizing? Safer to keep the exact sentences as they appear, but we need to split into list items. We can keep the sentences as they appear, maybe with minor punctuation adjustments for readability but not losing content.
We need to be careful not to omit any phrases. Let's copy the original text exactly and then split.
Original responsibilities paragraph:
"Build AI and agent-first products and features [60%]: Contribute across the full software stack to deliver user journeys to production, owning implementation quality from architecture to releaseDesign and build agents that apply prompts, context, tools, and model reasoning to fulfill user journeys, generate content, and automate processesApply sound software engineering and system design principles to produce solutions that are observable, maintainable, scalable, and production readyValidate solutions against functional requirements using both traditional QA methods, model-based evals, and agent tracing to ensure quality is measurable and reproducibleIncorporate agentic software engineering techniques into the development workflow across the SDLC, from planning, design, implementation, testing, and maintenance Actively participate in product definition as a technologist [35%]: Drive product definition with designers and PMs: ideate, explore, and prototype with stakeholders, then cut down possible options to arrive at deliverable, but well-rounded solutionsWholly conceive and ship features & MVP iterations early in the product definition phase that directly advance high-visibility organizational goalsStrike the right balance between investment in UX quality and tending to practical business needs through the product development process.Partner with other engineering stakeholders to identify what technology makes possible, and what makes implementing a given product or feature hard. Bring that perspective into project scoping and prioritization Be a source of influence for other engineers on the team [5%]: Share knowledge, techniques, and agentic software engineering practices in async formats and dedicated venues, like technical discussions and team meetingsChampion the use of AI solutions for engineering and product tasks, accelerate product velocity and team’s execution"
We need to insert spaces where missing. The original seems to have missing spaces after colons and periods. We can add spaces for readability but not change meaning. Probably acceptable.
We'll produce list items with the sentences.
Now Minimum Qualifications:
"We realize applying for jobs can feel daunting at times. Even if you don’t check all the boxes in the job description, we encourage you to apply anyway. 5-8 years of experience working as a Software Engineer, with proven experience building enterprise-scale applications.Solid working proficiency in Typescript/Javascript or Python, and familiarity with modern web application frameworks like React, Next.js, or Rails.Broad full-stack ownership; comfortable directing agents across both frontend and backend development.Strong understanding of data schemas, databases, APIs, and AWS infrastructure, including how to structure data so it holds up at high volume and returns quickly under load; hands-on experience with performance testing, logging, and monitoring. Golang preferred but not required.Hands-on experience building AI and agent-powered features and systems using frontier models from OpenAI, Anthropic, or Google.Comfort working AI-first: delegating implementation to AI agents (e.g., Claude Code, Codex, Opencode, Pi), reviewing outcomes, and guiding architecture as part of the daily development workflow.Understanding of the strengths and limitations of frontier models and open weight modelsExperience with continuous delivery through feature flagging and trunk-based development"
We need to split into bullet points. The preamble sentences: "We realize applying for jobs can feel daunting at times. Even if you don’t check all the boxes in the job description, we encourage you to apply anyway." That's prose. Then the list of qualifications.
We'll put preamble in
then
- each qualification.
We need to ensure we keep all details: "5-8 years of experience working as a Software Engineer, with proven experience building enterprise-scale applications." etc.
Now What Can Help Your Application Stand Out:
"Experience deploying or fine-tuning open-weight models for specific use casesHands-on experience with agent orchestration
- .
- What Can Help Your Application Stand Out: could be considered "Skills" or "Preferred qualifications". The instruction includes Skills section. We can treat that as Skills.
- Benefits, Pay, Schedule: not mentioned. So we should NOT include those sections.
- Also there is "About G2 - The Company" and "About G2 - Our People". Those are not requested sections; we should not include them as headings unless they map to one of the allowed headings. They are not in the list, so we should omit them. Also we should not repeat job title as heading.
- Also there is "Our Commitment to Inclusivity and Diversity", "For job applicants in California..." etc. Those are boilerplate; we should remove.
- Also "How We Use AI Technology In Our Hiring Process" etc. Remove.
Thus we need to output HTML fragment with sections: About the role, Responsibilities, Qualifications, Skills (maybe). Also maybe Requirements? The Minimum Qualifications could be considered Requirements. The instruction includes Requirements as a possible heading. We have both Qualifications and Requirements; we need to decide which to use. The posting has "Minimum Qualifications". That could be either Requirements or Qualifications. Since both headings are allowed, we could include either. To avoid duplication, we should pick one that best matches. The posting says "Minimum Qualifications". So we can use
Qualifications
. Or we could use Requirements. I'd choose Qualifications. What about "What Can Help Your Application Stand Out" - could be Skills. We'll include Skills. Thus sections: About the role, Responsibilities, Qualifications, Skills. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include the prose from About The Role, the responsibilities list (including percentages?), the qualifications list, and the "What Can Help Your Application Stand Out" list. We must not add placeholder text like "commensurate with experience". Not present. We need to format asAbout the role
then... prose ...
. For responsibilities:Responsibilities
then- ... each bullet ...
for prose. So we could include that preamble as a
then the list. Similarly for "What Can Help Your Application Stand Out" we could include a preamble. Let's extract the exact text. About The Role: "As a Senior Software Engineer, you will create new products and features end-to-end which directly contribute to G2’s key organizational goals. Your responsibilities will center around architecting the solution, delegating implementation to your agents across the full stack, and reviewing and validating what they produce with confidence in their performance. As a technologist, you will be a key voice in defining and refining product concepts and you’ll act as a hands-on, in-person technical partner to stakeholders and leadership. You will adopt industry-leading agentic engineering techniques and leverage “agent-first” ways of working to deliver products, reflecting the realities of today’s software development lifecycle." That's the paragraph before "Detailed Responsibilities". We'll put that in
. Then Detailed Responsibilities: "Build AI and agent-first products and features [60%]: Contribute across the full software stack to deliver user journeys to production, owning implementation quality from architecture to releaseDesign and build agents that apply prompts, context, tools, and model reasoning to fulfill user journeys, generate content, and automate processesApply sound software engineering and system design principles to produce solutions that are observable, maintainable, scalable, and production readyValidate solutions against functional requirements using both traditional QA methods, model-based evals, and agent tracing to ensure quality is measurable and reproducibleIncorporate agentic software engineering techniques into the development workflow across the SDLC, from planning, design, implementation, testing, and maintenance Actively participate in product definition as a technologist [35%]: Drive product definition with designers and PMs: ideate, explore, and prototype with stakeholders, then cut down possible options to arrive at deliverable, but well-rounded solutionsWholly conceive and ship features & MVP iterations early in the product definition phase that directly advance high-visibility organizational goalsStrike the right balance between investment in UX quality and tending to practical business needs through the product development process.Partner with other engineering stakeholders to identify what technology makes possible, and what makes implementing a given product or feature hard. Bring that perspective into project scoping and prioritization Be a source of influence for other engineers on the team [5%]: Share knowledge, techniques, and agentic software engineering practices in async formats and dedicated venues, like technical discussions and team meetingsChampion the use of AI solutions for engineering and product tasks, accelerate product velocity and team’s execution" We need to split into bullet points. The original text seems to have missing punctuation and line breaks. We need to parse into logical bullets. We can break at each major section: - Build AI and agent-first products and features [60%]: - Contribute across the full software stack to deliver user journeys to production, owning implementation quality from architecture to release - Design and build agents that apply prompts, context, tools, and model reasoning to fulfill user journeys, generate content, and automate processes - Apply sound software engineering and system design principles to produce solutions that are observable, maintainable, scalable, and production ready - Validate solutions against functional requirements using both traditional QA methods, model-based evals, and agent tracing to ensure quality is measurable and reproducible - Incorporate agentic software engineering techniques into the development workflow across the SDLC, from planning, design, implementation, testing, and maintenance - Actively participate in product definition as a technologist [35%]: - Drive product definition with designers and PMs: ideate, explore, and prototype with stakeholders, then cut down possible options to arrive at deliverable, but well-rounded solutions - Wholly conceive and ship features & MVP iterations early in the product definition phase that directly advance high-visibility organizational goals - Strike the right balance between investment in UX quality and tending to practical business needs through the product development process. - Partner with other engineering stakeholders to identify what technology makes possible, and what makes implementing a given product or feature hard. Bring that perspective into project scoping and prioritization - Be a source of influence for other engineers on the team [5%]: - Share knowledge, techniques, and agentic software engineering practices in async formats and dedicated venues, like technical discussions and team meetings - Champion the use of AI solutions for engineering and product tasks, accelerate product velocity and team’s execution We need to keep the content exactly as given, but we can reformat into list items. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we must not lose any detail. We can keep the substance but we can rephrase? It says do NOT invent or summarize away detail. Rephrasing might be considered summarizing? Safer to keep the exact sentences as they appear, but we need to split into list items. We can keep the sentences as they appear, maybe with minor punctuation adjustments for readability but not losing content. We need to be careful not to omit any phrases. Let's copy the original text exactly and then split. Original responsibilities paragraph: "Build AI and agent-first products and features [60%]: Contribute across the full software stack to deliver user journeys to production, owning implementation quality from architecture to releaseDesign and build agents that apply prompts, context, tools, and model reasoning to fulfill user journeys, generate content, and automate processesApply sound software engineering and system design principles to produce solutions that are observable, maintainable, scalable, and production readyValidate solutions against functional requirements using both traditional QA methods, model-based evals, and agent tracing to ensure quality is measurable and reproducibleIncorporate agentic software engineering techniques into the development workflow across the SDLC, from planning, design, implementation, testing, and maintenance Actively participate in product definition as a technologist [35%]: Drive product definition with designers and PMs: ideate, explore, and prototype with stakeholders, then cut down possible options to arrive at deliverable, but well-rounded solutionsWholly conceive and ship features & MVP iterations early in the product definition phase that directly advance high-visibility organizational goalsStrike the right balance between investment in UX quality and tending to practical business needs through the product development process.Partner with other engineering stakeholders to identify what technology makes possible, and what makes implementing a given product or feature hard. Bring that perspective into project scoping and prioritization Be a source of influence for other engineers on the team [5%]: Share knowledge, techniques, and agentic software engineering practices in async formats and dedicated venues, like technical discussions and team meetingsChampion the use of AI solutions for engineering and product tasks, accelerate product velocity and team’s execution" We need to insert spaces where missing. The original seems to have missing spaces after colons and periods. We can add spaces for readability but not change meaning. Probably acceptable. We'll produce list items with the sentences. Now Minimum Qualifications: "We realize applying for jobs can feel daunting at times. Even if you don’t check all the boxes in the job description, we encourage you to apply anyway. 5-8 years of experience working as a Software Engineer, with proven experience building enterprise-scale applications.Solid working proficiency in Typescript/Javascript or Python, and familiarity with modern web application frameworks like React, Next.js, or Rails.Broad full-stack ownership; comfortable directing agents across both frontend and backend development.Strong understanding of data schemas, databases, APIs, and AWS infrastructure, including how to structure data so it holds up at high volume and returns quickly under load; hands-on experience with performance testing, logging, and monitoring. Golang preferred but not required.Hands-on experience building AI and agent-powered features and systems using frontier models from OpenAI, Anthropic, or Google.Comfort working AI-first: delegating implementation to AI agents (e.g., Claude Code, Codex, Opencode, Pi), reviewing outcomes, and guiding architecture as part of the daily development workflow.Understanding of the strengths and limitations of frontier models and open weight modelsExperience with continuous delivery through feature flagging and trunk-based development" We need to split into bullet points. The preamble sentences: "We realize applying for jobs can feel daunting at times. Even if you don’t check all the boxes in the job description, we encourage you to apply anyway." That's prose. Then the list of qualifications. We'll put preamble in
then
- each qualification. We need to ensure we keep all details: "5-8 years of experience working as a Software Engineer, with proven experience building enterprise-scale applications." etc. Now What Can Help Your Application Stand Out: "Experience deploying or fine-tuning open-weight models for specific use casesHands-on experience with agent orchestration