Lead Engineer

. We need to preserve ALL substantive information; do not invent or summarize away detail. We need to format lists appropriately. Let's extract content. Summary paragraph: "The Lead Engineer is responsible for the successful scaling of Vivian as a product and platform. This role bridges product strategy and technical execution, enabling JCA to continuously evolve the Vivian platform while maintaining the quality, stability, and performance our clients depend on. This is achieved by providing technical leadership to a small engineering team, completing hands-on engineering assignments, and demonstrating the operational discipline necessary to deliver a secure, reliable, and scalable SaaS platform that supports client growth and business objectives." That's prose. Responsibilities: multiple bullet-like sentences but not formatted as list. We need to convert to

• . The responsibilities section includes headings: Leadership, Management, and Accountability; Technical Strategy and Architecture; Engineering Operations; Software Delivery; Platform Operations. Each has multiple sentences. We could treat each bullet as a responsibility item. But we need to preserve all detail. Could create
  with each responsibility area as
  • containing the sentences (maybe multiple paragraphs inside). Simpler: treat each sentence as
  • . But that may lose grouping. However instruction: use
    • for any list of duties/requirements/benefits. The responsibilities are a list of duties. So we can make each duty as
    • . We'll split by the numbered? Not numbered. We'll split by the headings and sentences. Let's list duties: - Lead, manage, and develop software engineers, providing performance feedback, coaching, career development, and accountability for successful delivery. - Establish clear performance expectations and foster a culture of accountability, ownership, collaboration, and continuous improvement. - Effectively onboard engineers, promote consistent development practices, and reduce dependency on individual team members. - Partner with Vice President of Product and stakeholders to make sure the engineering team is delivering on business and client needs. - Own the definition and evolution of system and platform architecture, collaborating with the Vice President of Product and engineers to establish technical standards, design principles, and architectural roadmaps that promote consistency, scalability, and long-term health across the Vivian platform. - Own the product technical vision and architecture direction, ensuring engineering decisions support approved product strategy, business priorities, and growth objectives. - Evaluate and make architectural decisions for new initiatives that appropriately balance platform scalability, reliability, cost, performance, and long-term maintainability. - Define and enforce security architecture, standards, and risk management practices that protect data integrity, compliance, and platform reliability. - Balance long-term architectural improvements with near-term delivery needs to maintain execution velocity. - Ensure engineering work is coordinated with stakeholders, and dependencies are managed, so product commitments are delivered successfully. - Own engineering execution from requirements through delivery, including technical documentation, estimation, sprint planning, implementation, testing, debugging, and release support. - Implement automated testing, QA practices, third-party integrations, and continuous improvement of development standards for high-quality software. - Establish and drive engineering practices that reduce technical debt and improve the long-term maintainability, scalability, and reliability of the platform. - Lead secure software development by conducting security reviews, identifying and mitigating technical risks, and ensuring platform stability, performance, and client experience. - Produce clear, actionable engineering tasks by creating, refining, and maintaining development tickets with precise technical details and dependencies. - Create and maintain engineering documentation, standards, and knowledge-sharing practices. - Implement scalability and performance strategies to support growth in users, data, and platform complexity. - Implement and maintain continuous integration (CI) and continuous delivery (CD) pipelines, deployment processes, and engineering tooling that improve delivery speed and reliability. - Lead investigation and resolution of complex technical issues through root cause analysis, preventive design, and continuous improvement of architecture and engineering practices. - Strategy and management of cloud engineering and infrastructure management of resources for stable platform and cost management. That's many items. Skills: list of bullet points after "You are successful as the Lead Product Engineer because you:" then a series of clauses separated by semicolons. We need to convert to
      • . Each clause ends with semicolon, last ends with period. We'll split. Skills clauses: - lead technical teams, develop engineers and hold team members accountable for outcomes - analyze complex situations, manage competing priorities, and make data-driven decisions to optimize features and functionality - translate business requirements into clear, actionable technical requirements for engineers - develop, test, deploy, and support software solutions that deliver value to customers while maintaining quality, reliability, and performance - influence technical decisions and build alignment among engineers, product managers, and stakeholders - define architecture and operate distributed systems, including web application development, API design and integration patterns - design and implement scalable data engineering solutions, including complex data pipelines - identify technical, security, and operational risks and implement practical mitigation strategies - are a strong problem-solver and troubleshooter - quickly learn and apply industry, business, and client-specific knowledge to technical solutions Qualifications: similar list after "You are qualified for the position because you:" with semicolons. Clauses: - have a minimum of three years’ experience leading, coaching and developing engineering teams and establishing engineering standards - have a minimum of five years’ experience as a full stack software developer designing, deploying, and supporting cloud-based SaaS applications, including CI/CD pipelines, operational monitoring, troubleshooting, and production support - have a minimum of two years’ experience leading software delivery through estimation, planning, dependency management, and successful release of product features and enhancements using Agile and delivery software - have a minimum of three years’ experience with React, Python and SQL programming - have a minimum of two years’ experience developing scalable data solutions, including data pipelines, data modeling, and data processing workflows - have a minimum of five years’ experience implementing software solutions that comply with security, privacy, and compliance requirements, including secure SDLC practices - have a minimum of one year’s experience with observability and reliability practices, including monitoring, logging, tracing, SLO/SLA ownership, and incident response - have a minimum of three years’ experience with Microsoft Azure or other computing services Then "You Have An Advantage In The Position If You" list: also could be considered qualifications but it's separate advantage. Could include as part of Qualifications or separate section? Not in list of headings; we could add as part of Qualifications maybe as extra bullet. But instruction: include a section ONLY when posting has real, specific content for it. Advantage is specific content. Could create a section "Advantages" but not in allowed headings. Might be better to incorporate into Qualifications as extra bullets. We'll add them under Qualifications as additional
      • items. Advantage clauses: - have experience building machine learning models and data products - have experience using AI to deliver software solutions - have experience using the Atlassian suite with for product delivery (maybe typo: "with for") - have Microsoft Developer, AI, Data Engineer, DevOps Engineer or Solution Architect certification(s) - have experience working with the nonprofit Tessitura CRM - have experience working with or developing solutions for nonprofit organizations Requirements: list after "You may be required to:" with semicolons. Clauses: - work remotely from a home office or other remote space - work at least 40 hours per week, as this is a full-time position - maintain standard North American business hours with some flexibility - travel up to 10% of business days with easy access to airport - remain in a stationary position for the majority of an eight-hour workday Then "You Are Required To" list: - adhere to the company’s policies and procedures - embrace JCA’s core values We could combine both under Requirements. Benefits: list after "Benefits" line. Clauses: - Salary range of $100,750 to $111,400, commensurate with experience and performance - Paid holidays, vacation, personal, sick, and volunteer time - 401(k) retirement plan - Employee Stock Ownership Plan (ESOP) - Health, dental, and vision insurance - Life insurance and long-term disability insurance - Paid parental leave - Employee Assistance Program - Flexible Spending Account (FSA) - Dependent Care Account (DCA) But salary also could be separate Pay section. We'll keep salary in Benefits as per text. However we also need Pay section if we want. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. Salary is stated, so we could have Pay section with salary range. Benefits section then other benefits. Let's separate: Pay section with salary range. Benefits section with other benefits (excluding salary). Schedule: "Four-day Week". We'll put that. Thus sections: About the role (Summary) Responsibilities Requirements Skills Qualifications Benefits (excluding salary) Pay (salary range) Schedule (Four-day Week) We must not repeat job title as heading. Now produce HTML fragment. We'll wrap each section in

        heading then content. For lists:

        • ...

        For prose:

        ... We need to ensure we don't include extra blank lines? It's fine. Let's craft. About the