[US] Senior Full-Stack Engineer - Node.js, React & Flutter

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real content. No job title heading. No Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. Key sections: - About Benchmark Gensuite (company description) maybe "About the role"? Actually "About Benchmark Gensuite" is company description. Could be "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose appropriate headings based on content. We have: - Overview: "Benchmark Gensuite is seeking a Senior Full-Stack Engineer - Node.js, React & Flutter to join our engineering team. This role involves designing and developing software applications using our core technology stack of Node.js backend services with React web and Flutter mobile front-end clients. The ideal candidate will perform coding, debugging, testing, and troubleshooting throughout the application development process while actively collaborating with the team and taking initiative on technical solutions." That's about the role. - Position Level: Software Engineer III - Experience Level: 4-6+ years of related software development experience - Reporting Structure: Reports to Engineering Manager - Team Interaction: Active collaboration with cross-functional teams - Work Style: Works independently and sets technical direction, demonstrates initiative and resourcefulness These could be under "About the role" or "Qualifications"? Might be "Qualifications". But we also have "Required Technical Skills", "General Technical Requirements", "AI & Emerging Technology", "Required Qualifications" (Education, Professional Experience), "Key Responsibilities", "Desired Qualifications (Nice To Have)", "Success Metrics", "Growth Opportunities", "Work Environment". We need to decide sections: maybe "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits". Pay and Schedule not present, so omit. We must not create sections with filler. So include only those with substantive content. We need to preserve all substantive info: that includes company description, benefits, etc. Let's extract: Company description paragraphs: "Everyone wants to make the world a better place..." up to "Join us and help make the corporate world better for the planet and better for its employees." Then "Benchmark Gensuite jobs play a crucial role..." etc. Also "About Benchmark Gensuite…" paragraph. We can combine into an "About the company" maybe but heading options limited. Could use "About the role" for role description, and maybe "About Benchmark Gensuite" not in list but we could still use

About Benchmark Gensuite? 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 suggests those examples. Safer to stick to those. So we can put company description under "About the role"? Might be odd but acceptable. Or we could put under "Qualifications"? Not ideal. Maybe we can treat company description as part of "About the role" (the role at the company). We'll include that. Benefits: paragraph "Benchmark Gensuite Benefits At Benchmark Gensuite, your hard work is rewarded..." etc. Responsibilities: list under "Key Responsibilities" with sub-bullets: Development & Technical Design..., Collaboration & Leadership..., Project Contribution... We need to output

• for any list of duties/requirements/benefits. We also have "Required Technical Skills" etc. Those are requirements/skills. Could be under "Requirements" or "Skills". We'll separate: "Requirements" for required qualifications (education, experience) and "Skills" for technical skills. We have "Required Qualifications" (Education, Professional Experience). Also "Position Level", "Experience Level", "Reporting Structure", "Team Interaction", "Work Style". Those could be under "About the role" or "Qualifications". Might be better to put under "Qualifications". We'll include education and experience there. We have "Desired Qualifications (Nice To Have)" - could be under "Skills" as nice-to-have. We have "Success Metrics" - could be under "Responsibilities"? Might be its own section but not in list. Could omit if not fitting headings. But we need to preserve all substantive info; we could include under "Responsibilities" as part of performance expectations. Or we could create a custom heading like "Success Metrics" but instruction says prefer few substantive sections over many thin ones. Might be okay to include under "Responsibilities". Similarly "Growth Opportunities" and "Work Environment" could be under "About the role" or maybe under "Benefits"? Not exactly. Could be under "About the role". We'll incorporate. We must not repeat job title as heading. We must not include Job ID etc. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting ends with "Questions about the position? Please contact our HR Team, at jobs@benchmarkdigital.com." That's application instruction; remove. Now craft HTML. We'll have sections:

  About the role

  ... company description + role overview ...

  Responsibilities

  • Development & Technical Design: design and develop software applications using Node.js, React, and Flutter; write clean, maintainable, and well-documented code; perform thorough testing and quality assurance; troubleshoot and debug issues across the full technology stack; participate in code reviews; evaluate and integrate AI tooling into development workflow.
  • Collaboration & Leadership: actively collaborate with team members on technical solutions; mentor junior and mid-level engineers; contribute to architectural decisions; set technical direction and drive best practices.
  • Project Contribution: contribute to moderately complex aspects of projects; take initiative in problem-solving; work independently while maintaining team collaboration; support project planning and estimation.

  Requirements

  Position Level: Software Engineer III; Experience Level: 4-6+ years of related software development experience; Reports to Engineering Manager; Active collaboration with cross-functional teams; Works independently and sets technical direction, demonstrates initiative and resourcefulness.

  Education: Bachelor's degree in Computer Science, Software Engineering, or related technical field (equivalent professional experience may be considered).

  Professional Experience: 4-6+ years of professional software development experience; experience working in collaborative development environments; demonstrated ability to work on projects with moderate complexity.

  Skills

  Required Technical Skills

  but we cannot use h4? Not prohibited but we should stick to

  for section headings only. Could embed as or just list. We'll just list under Skills with

  . We'll separate required and nice-to-have maybe. But we need to preserve all details: Required Technical Skills includes backend, frontend, general technical, AI & emerging tech. We'll create two lists: Required Skills and Nice-to-have Skills. Under Skills section:

  Skills

  Required Technical Skills:

  • Backend Development: Node.js proficiency (4+ years hands-on); experience building RESTful APIs and/or GraphQL endpoints; working knowledge of SQL and/or NoSQL databases; understanding of server architecture, middleware, backend frameworks (Express.js, Fastify, etc.).
  • Frontend Development: React experience (3+ years) including component lifecycle, state management, React Hooks, modern React patterns, state management libraries (Redux, Context API, etc.); Flutter development experience: Dart programming language proficiency, cross-platform mobile app development, understanding of Flutter widgets and state management.
  • General Technical Requirements: Proficient with Git and collaborative development workflows; experience with unit testing, integration testing, and testing frameworks; strong debugging and troubleshooting skills across the full stack; familiarity with modern development tools, IDEs, and build processes.
  • AI & Emerging Technology: Proficient with AI coding assistants (e.g., GitHub Copilot, Claude Code, Cursor); experience integrating LLM APIs via AWS Bedrock into production applications; working knowledge of prompt engineering fundamentals; familiarity with AI agent frameworks, vector databases, or retrieval-augmented generation patterns (nice to have).

  Desired Qualifications (Nice To Have):

  • Experience with AWS Cloud
  • Knowledge of containerization via Docker
  • Familiarity with CI/CD pipelines and DevOps practices
  • Experience with microservices architecture
  • Understanding of mobile app deployment processes (App Store, Google Play)
  • Previous experience mentoring junior developers
  • Experience working in Agile/Scrum development environments
  • Open source contribution experience
  • Technical writing and documentation skills

  Benefits

  Benchmark Gensuite offers annual bonus programs, regular team-building events, and off-cycle reviews to promptly recognize and reward excellent performers. Engaging team activities including happy hours and exciting virtual events encourage teams to connect and build a strong, supportive, and fun rapport. Benchmark Gensuite Team Member Networks, like the Respect for Diversity Group and the Sustainability Group, provide a safe and supportive space for team members who share a common identity to voice ideas and initiate action.

  We also have success metrics and growth opportunities and work environment. Could incorporate into "About the role" or separate sections. Since we already have many sections, maybe add a section "Growth & Work Environment". But heading not in list; but we could still use

  Growth Opportunities and Work Environment. However instruction says prefer few substantive sections over many thin ones. We have many sections already; adding more may be thin. Could incorporate those details into existing sections. Success Metrics: could be under Responsibilities as performance expectations. Growth Opportunities and Work Environment could be under About the role or Benefits. Let's add a paragraph under About the role after company description covering growth opportunities and work environment. We'll need to ensure we don't miss any substantive info: we have covered: - Company description (first paragraphs) - Role overview - Benefits - Responsibilities (key responsibilities) - Requirements (position level, experience, reporting, work style, education, professional experience) - Skills (required technical, desired nice-to-have) - Benefits (done) - Success metrics (not yet) - Growth opportunities (not yet) - Work environment (not yet) We can add a paragraph under About the role after role overview: "This role provides excellent opportunities for professional growth including exposure to full-stack development across multiple platforms, opportunity to work on complex technical challenges, potential mentorship opportunities with junior team members, path toward Software Architect (Level IV) role, cross-training opportunities in different areas of the technology stack. Work environment: collaborative team environment with experienced engineers, opportunity to work on diverse projects with varying complexity, access to modern development tools and technologies, professional development and learning opportunities." Success metrics: "Success Metrics: Technical Performance – delivers high-quality code with minimal bugs in production, meets project deadlines and technical requirements, demonstrates continuous learning and adaptation to new technologies, shows initiative in identifying and solving technical challenges. Team Collaboration – provides valuable input in team discussions and technical reviews, effectively collaborates with cross-functional teams, shares knowledge and supports team members, communicates technical concepts clearly to both technical and non-technical stakeholders." We could add this as a subsection under Responsibilities or as a separate section "Performance Expectations". Since we have many sections, maybe add under Responsibilities as an extra bullet. Let's add a bullet under Responsibilities: "Success Metrics: deliver high-quality code with minimal bugs, meet deadlines, demonstrate continuous learning, show initiative; collaborate effectively, share knowledge,