Sr Software Engineer - Full Stack

We need to output HTML fragment with sections: headings

for sections present: About the role? The posting includes "Job Summary" which is like about the role. Also "Responsibilities", "Requirements And Preferred Experience", "Why OpenGov?" which includes subsections: A Mission That Matters, Opportunity to Innovate, A Team of Passionate, Driven People, A Place to Make Your Mark, Benefits That Work For You. We need to decide which sections to include based on real specific content. The instructions: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we can include sections for About the role (Job Summary), Responsibilities, Requirements, Benefits (since they list benefits). Also maybe "Why OpenGov?" could be considered as "About the company" but not required heading list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list "Why OpenGov?" as a standard heading, but we could incorporate its content under Benefits or maybe as separate sections like "About the company"? Not in allowed headings. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, but we should prefer those headings. Probably we should stick to those headings. So we will have sections: About the role (Job Summary), Responsibilities, Requirements, Benefits. Possibly also Qualifications? The posting includes Education requirement under Requirements. Could treat that as Qualifications. But we already have Requirements covering qualifications. Might not need separate Qualifications. Skills maybe covered under Requirements. We'll include About the role, Responsibilities, Requirements, Benefits. We must not repeat job title as heading. No Job ID. Remove boilerplate etc. We need to preserve all substantive information. So we need to include the content from Job Summary, Responsibilities list, Requirements list, Benefits list. We must format lists with

• . Use

  for prose. Let's extract content. Job Summary paragraph: "At OpenGov, bold ideas ship daily and rapid iteration turns directly into measurable customer impact. We stay relentlessly aligned with customer outcomes while pushing the frontier of AI-driven software development, using cutting-edge AI tools and techniques to build systems that scale. As a Sr. Software Engineer, you will develop top-tier SaaS solutions that enhance efficiency, transparency, and accountability in government agencies. We are looking for a fearless, hands-on technical leader who thrives on tackling the most challenging architectural problems. As a crucial member of our team, you will lead and deliver new full stack features in a fast-paced environment, utilizing modern technologies such as ReactJS, TypeScript, NodeJS, PostgreSQL, and S3. You aren't just an individual contributor; you are a technical navigator who can quickly master new codebases, lead cross-team collaborations, and serve as the technical voice for the team." That's the About the role. Responsibilities list: bullet points each starting with bold heading? The text: Technical Leadership: Act as the team’s "Tech Lead" by overseeing the design, development, testing, and deployment of multi-tenant cloud-native solutions. Fearless Problem Solving: Troubleshoot, debug, and resolve the most complex technical issues and architectural bottlenecks with a proactive, "can-do" attitude. AI Transformation Leadership: Lead the team’s transition toward AI-native development, championing the adoption of AI-driven tools and methodologies to fundamentally improve engineering productivity and software quality. Rapid Contribution: Quickly pick up and master new or existing codebases to provide immediate value and high-quality code contributions. Cross-Functional Collaboration: Lead collaboration across the organization to translate business priorities into shipped features that deliver customer success. Team Representation: Speak up and represent the team’s technical interests in stakeholder meetings and cross-suite engineering forums. Engineering Excellence: Generate clean, efficient, and well-documented software following industry best practices and driving continuous improvement of development processes. Mentorship: Mentor and guide junior software engineers, fostering a culture of continuous learning, innovation, and quality. Customer Empathy: Cultivate deep customer empathy to ensure that procurement and contract solutions exceed the expectations of the government agencies we serve. We'll put each as

• . Requirements And Preferred Experience: list: Full-Stack Expertise: 7+ years of experience in developing highly scalable cloud-native applications, working across the stack (frontend + backend) to ship features end-to-end. Technical Stack: Proficiency in JavaScript/TypeScript, ReactJS, NodeJS, PostgreSQL, and S3 is a MUST. Modern Architecture: Proficiency with event-driven architecture and API integration is a MUST. Cloud & DevOps: Experience building applications on AWS using the latest CI/CD and DevOps best practices. Observability: Experience leveraging modern tools like Grafana for observability and performance monitoring. AI Integration: Experience building with AI-driven UX, agents, and workflow automation (direct ML experience not required). Adaptability: Thrives in a fast-paced, high-growth, and sometimes ambiguous environment. Communication: Exceptional communication skills with the ability to represent the team’s technical vision to both technical and non-technical stakeholders. Education: BA/BS in a computer science-related field or equivalent experience required. We'll put each as
• . Benefits: list from "Benefits That Work For You": Comprehensive healthcare options for individuals and families Flexible vacation policy and paid company holidays 401(k) with company match Paid parental leave, wellness stipends, and HSA contributions Professional development and growth opportunities A collaborative office environment with weekly catered lunches. We'll put each as
• . We should not include Pay or Schedule sections because not specified. We should not include "Why OpenGov?" sections because they are not in the allowed headings list; but we could incorporate some of that content into About the role? However the instruction: "Prefer a few substantive sections over many thin ones." It might be okay to omit the "Why OpenGov?" content? But we must preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include that content somewhere. If we don't have a heading for it, we could incorporate it into About the role as prose? But that would be mixing company description with role summary. The instructions say we can use headings for sections like About the role, Responsibilities, etc. It didn't forbid adding other headings, but gave examples. It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not an exhaustive list. So we could add other headings like "Why OpenGov?" if we want. However they also say "Prefer a few substantive sections over many thin ones." So maybe we should combine the "Why OpenGov?" content into a section like "About the company" or maybe incorporate into About the role? But the About the role already has role summary; adding company mission might be okay as part of About the role? However the instruction says "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." It doesn't forbid other headings. Given we need to preserve all substantive information, I think we should include a section for "Why OpenGov?" maybe as

  Why OpenGov?

  and then include its subpoints as

  or

  . But the subpoints are themselves headings like "A Mission That Matters", etc. Those could be

  paragraphs. But to keep sections few, we could merge all "Why OpenGov?" content into a single

  paragraph under a heading "About OpenGov". However the instruction's examples include "About the role". Not "About the company". But we could still use "About OpenGov". Might be okay. Alternatively, we could treat the "Why OpenGov?" content as part of Benefits? No. Better to add a section "About OpenGov" with the content. But the instruction says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but they gave examples. I'd stick to those examples to be safe. However then we would drop the "Why OpenGov?" content, violating "Preserve ALL substantive information". So we need to include it somewhere else. Perhaps we can incorporate it into the "Benefits" section? No. We could add a

  after the Benefits section that includes the OpenGov mission etc. That would preserve info without a heading. That seems acceptable: we can have a

  paragraph that contains the OpenGov mission etc. The instruction says use

  for prose. So we can have a prose paragraph after Benefits that includes the "Why OpenGov?" content. That would preserve all info without extra headings. Thus final HTML:

  About the role

  Job Summary paragraph...

  Responsibilities

  ...
  • ...
  ...

  Requirements

  ...
  • ...
  ...

  Benefits

  ...
  • ...
  ...

  Why OpenGov? content...

  We need to ensure we don't include any boilerplate like "Learn about OpenGov’s mission...". That's part of Why OpenGov? content; we should include it. Let's extract the Why OpenGov? content exactly: "Why OpenGov? A Mission That Matters. At OpenGov, public service is personal. We are passionate about our mission to power more effective and accountable government. Government that operates efficiently, adapts to change, and strengthens public trust. Some people say this is boring. We think it’s the core of our democracy. Opportunity to Innovate The next great wave of innovation is unfolding with AI, and it will impact everything—from the way we work to the way governments interact with their residents. Join a trusted team with the passion, technology, and expertise to drive innovation and bring AI to local government. We’ve touched 2,000 communities so far, and we’re just getting started. A Team of Passionate, Driven People This isn’t your typical 9-to-5 job; we operate in a fast-paced, results-driven environment where impact matters more than simply clocking in and out. Our global team of 800+ employees is united in our commitment to challenge the status quo. OpenGov is headquartered in San Francisco and has offices in Atlanta, Boston, Chicago, Dubuque, Dallas, and Pune. A Place to Make Your Mark We pride ourselves on our performance-based culture, where every employee is encouraged to jump in head-first and take action to help us improve. If you have a great idea, we want to hear it. Excellent performance is recognized and rewarded, and we love to promote from within. Benefits That Work For You Enjoy an award-winning workplace with the benefits to match, including: Comprehensive healthcare options for individuals and familiesFlexible vacation policy and paid company holidays401(k) with company matchPaid parental leave, wellness stipends, and HSA contributionsProfessional development and growth opportunitiesA collaborative office environment with weekly catered lunches." Note that the Benefits That Work For You part repeats the benefits list we already captured; we should avoid duplication. The Benefits That Work For You section is essentially the same as the benefits list we already have. To avoid duplication, we should not repeat that list again. The Why OpenGov? section includes a sentence "Benefits That Work For You Enjoy an award-winning workplace with the benefits to match, including:" then the list. Since we already have a Benefits section with that list, we should not duplicate it. We can either omit the benefits sentence from