Manager, Engineering - Marine
for headings. Use - for lists. Use
for prose.
We need to preserve all substantive info, not invent. Remove boilerplate: EEO, scam warning, navigation, etc. Also remove duplicated lines like "About Us" repeated. Also remove "About Storable" repeated? The first paragraph about Storable is okay as part of About the role? Actually "About Storable" is company description; could be part of About the role or maybe we can include as a brief intro under About the role. The instruction: "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." So we can include a short paragraph about the company under About the role.
We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have content for About the role (company overview and role overview). Responsibilities: "What you'll do every day" bullet list. Also "How you'll lead with AI" could be part of responsibilities or skills. We'll treat as part of Responsibilities (maybe separate but we can include under Responsibilities). Requirements: "What you need to bring" includes education, experience, etc. Qualifications: maybe same as requirements? The posting lumps them together; we could treat "What you need to bring" as Requirements and Qualifications combined? But we need separate sections only if there is specific content. Could split: Requirements (education, experience) and Qualifications (specific technical skills). However the posting includes both in same list. To avoid thin sections, maybe combine into one section "Requirements" and omit Qualifications if no distinct content. But instruction: Prefer a few substantive sections over many thin ones. So we can have About the role, Responsibilities, Requirements, Benefits, Pay. Possibly Skills as part of Requirements. But we need to follow the allowed headings; we can omit sections that lack content. So we will output:
About the role
... company description and role overview ...
Responsibilities
- ...
...
Requirements
- ...
...
Benefits
- ...
...
Pay
Potential Pay Range: $125,000 USD - $175,000 USD
No Schedule.
We must ensure we preserve all substantive info: include details about leading team, tech stack, AI, etc. Also include bonus points? Those are optional; we can include them under Requirements as additional desirable experience. Should we include them? They are substantive but optional; we can include as part of Requirements (maybe as a separate list under "Preferred qualifications"). But we have only Requirements heading; we can include both required and preferred within same list, but maybe better to separate? However we don't have a "Preferred qualifications" heading. Could include them under Requirements as well, but note they are bonus points. We'll keep them as part of Requirements list.
We must remove boilerplate: EEO, scam warning, navigation, "About Us" duplicate, "Important Notice", "Pay Transparency" paragraph besides the pay range? The pay transparency paragraph is generic; we can keep only the pay range line. The instruction: "Prefer a few substantive sections over many thin ones." So we can keep the pay range line only.
We must not include "About Us" duplicate; we already have company description in About the role.
Now craft HTML.
Let's extract About the role content: First paragraph about Storable: "At Storable, we're redefining property management for specialty real estate. Tailored for the marine industry, Storable Marine empowers marinas, boat clubs and rental operations with the industry's most comprehensive technology platform. Our solutions span management software, service management, rental tools, websites, payments, and more to streamline operations, enhance customer experiences, and maximize revenue. Explore our platform solutions at storablemarine.com."
Then Overview: "Storable is seeking an experienced Engineering Manager to lead software development for our Marine Division (Storable Marine), building the software that powers the day-to-day operations of marinas, boatyards, yacht clubs, boat clubs, harbors, service yards, and other waterfront businesses. Our platform supports the workflows operators rely on to manage slips, docks, moorings, and dry storage; reservations and online bookings; boater and guest management; point of sale; payments and billing; customer and vessel records; digital waivers; service management; and other industry-specific needs."
Then description of role: "As the Engineering Manager for our Marine platform, you will lead a team of around 10 engineers building and modernizing cloud-native SaaS applications used by marina operators and their boaters around the world. Your team works across the stack primarily in Node.js, React, and TypeScript, with PHP powering our rentals product and some legacy .NET in our core marina management system (MMS), all supported by AI-assisted engineering workflows."
Then "Above all, this is a hands-on technical leadership role..." paragraph.
We can combine into About the role paragraph(s). Use for prose.
Now Responsibilities: list from "What you'll do every day" bullet points. Also "How you'll lead with AI" bullet points. We'll combine all bullet points under Responsibilities.
Let's extract responsibilities bullets:
- Lead a high-performing team of engineers building and modernizing cloud-native SaaS applications used by marinas, boatyards, and other waterfront businesses worldwide.
- Define and execute a product-aligned engineering strategy that advances Storable’s Marine platform and supports the broader business roadmap.
- Stay technically hands-on where it counts: pairing with engineers in the code, reviewing designs and pull requests, and weighing in on architecture to keep direction grounded in the realities of the codebase.
- Translate business priorities into actionable engineering roadmaps with clear KPIs, milestones, and success metrics for your team.
- Oversee the design, development, and scaling of mission-critical applications, ensuring stability, performance, security, and readiness for regulatory and compliance frameworks.
- Drive modernization initiatives that evolve legacy systems into distributed, service-oriented architectures, leveraging AI-assisted tooling to explore options, de-risk migrations, and move faster without compromising quality.
- Champion best-in-class engineering practices, including automated testing, code quality, observability, effective use of CI/CD pipelines, and thoughtful AI-assisted development workflows.
- Recruit, manage, coach, and grow a diverse team of engineers, fostering a culture of collaboration, innovation, continuous learning, and responsible AI adoption.
- Lead incident response for your team’s services in partnership with our dedicated DevOps team, continuously improving reliability, uptime, and cost-efficiency.
- Partner closely with Product, Operations, Client Success, and other stakeholders across the U.S. and Storable’s global hubs to align technology delivery with user and business needs, clearly explaining technical decisions and tradeoffs to both technical and non-technical audiences.
Then "How you'll lead with AI" bullets:
- Set clear standards and guardrails for AI-assisted development, including how AI-generated code is reviewed for correctness, security, maintainability, and fit within the broader system before anything ships.
- Coach engineers on effective use of tools such as GitHub Copilot, Cursor, ChatGPT, or similar platforms, helping them know when AI can safely accelerate the work and when careful human judgment is required.
- Identify and sponsor internal AI-enabled tools, automations, and workflows that reduce repetitive engineering work, improve developer experience, and free the team to focus on higher-leverage problems.
- Critically evaluate AI-generated designs, code, and documentation, ensuring your team improves and integrates outputs thoughtfully rather than accepting them blindly.
- Measure and communicate the impact of AI-assisted workflows on speed, quality, and delivery, using data to continuously refine how the team applies AI.
We'll include these as li under Responsibilities.
Now Requirements: "What you need to bring" list:
- Bachelor’s or Master’s degree in Computer Science, Software Engineering, or a related field, or equivalent professional experience.
- 7+ years of progressive software engineering experience, including direct experience managing and growing engineering teams.
- Proven track record delivering cloud-based SaaS products at scale in fast-paced, growth-oriented environments.
- Deep, hands-on engineering background building and shipping production web applications with Node.js and React (TypeScript/JavaScript), with the technical depth to review designs and code, reason through complex systems, mentor senior engineers, and guide transitions from legacy systems to cloud-native, service-oriented architectures.
- Demonstrated, day-to-day fluency with AI-assisted development tools (such as GitHub Copilot, Cursor, ChatGPT, or similar) and an AI-forward mindset for improving engineering workflows, code quality, and team performance.
- Strong communication and stakeholder management skills, with experience collaborating across functions and geographies and explaining technical decisions clearly to both technical and non-technical audiences, along with a working understanding of AWS, scalable infrastructure, application security, and Agile/Lean development practices.
Then Bonus points (preferred):
- Experience modernizing legacy systems or incrementally refactoring older codebases while maintaining reliability for production users.
- Experience working on SaaS products that power industry-specific operational workflows, such as point of sale, reservations and bookings, payments, customer management, service/work-order management, channel management, or marketplace-style systems.
- Experience in marine, marina, or waterfront hospitality software, or adjacent field-service and asset-management domains.
- Experience building internal AI-enabled tools, automations, or workflows for engineering teams, and mentoring engineers on effective prompting, AI-assisted code review, and AI-driven development practices.
- Experience defining and tracking engineering performance indicators (for example, velocity, uptime, release quality, and cost efficiency) and using those insights to improve team outcomes.
- All applicants must be currently authorized to work in the United States on a full-time basis.
- Storable is a fully distributed company, but is currently only registered for employment in certain states. To be eligible for employment, you must reside in the following states: AL, AZ, CA, CO, CT, FL, GA, ID, IL, IN, IA, KS, LA, MD, MA, MI, MN, MO, MS, NC, NE, NJ, NV, NY, OH, OK, OR, PA, SC, TN, TX, UT, VA, WA, WI, WY.
We should include those as part of Requirements (maybe as separate list). The instruction: preserve ALL substantive information. So include them.
We need to avoid repeating "All applicants must be currently authorized to work in the United States on a full-time basis." and the state list; they are substantive.
Now Benefits: list from "Benefits and Perks:" bullet points.
Let's extract:
- Generous health coverage for you and your family, including fully paid short- and long-term disability coverage and two-times base salary life insurance.
- 401(k) match after 60 days, 100% vested after 1 year.
- Employer contribution to your HSA, plus an HRA to help offset your deductible.
- Instant access to flexible vacation. We trust you, so we have a ‘take what you need’ vacation policy.
- Be More – company rewards and recognition that add up and can be redeemed for personalized gifts and experiences! Storriors have been able to enroll in SCUBA certification classes, travel overseas, and redo their back patio, among many other things
for prose. We need to preserve all substantive info, not invent. Remove boilerplate: EEO, scam warning, navigation, etc. Also remove duplicated lines like "About Us" repeated. Also remove "About Storable" repeated? The first paragraph about Storable is okay as part of About the role? Actually "About Storable" is company description; could be part of About the role or maybe we can include as a brief intro under About the role. The instruction: "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." So we can include a short paragraph about the company under About the role. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for About the role (company overview and role overview). Responsibilities: "What you'll do every day" bullet list. Also "How you'll lead with AI" could be part of responsibilities or skills. We'll treat as part of Responsibilities (maybe separate but we can include under Responsibilities). Requirements: "What you need to bring" includes education, experience, etc. Qualifications: maybe same as requirements? The posting lumps them together; we could treat "What you need to bring" as Requirements and Qualifications combined? But we need separate sections only if there is specific content. Could split: Requirements (education, experience) and Qualifications (specific technical skills). However the posting includes both in same list. To avoid thin sections, maybe combine into one section "Requirements" and omit Qualifications if no distinct content. But instruction: Prefer a few substantive sections over many thin ones. So we can have About the role, Responsibilities, Requirements, Benefits, Pay. Possibly Skills as part of Requirements. But we need to follow the allowed headings; we can omit sections that lack content. So we will output:
About the role
... company description and role overview ...
Responsibilities
- ... ...
Requirements
- ... ...
Benefits
- ... ...
Pay
Potential Pay Range: $125,000 USD - $175,000 USD
No Schedule. We must ensure we preserve all substantive info: include details about leading team, tech stack, AI, etc. Also include bonus points? Those are optional; we can include them under Requirements as additional desirable experience. Should we include them? They are substantive but optional; we can include as part of Requirements (maybe as a separate list under "Preferred qualifications"). But we have only Requirements heading; we can include both required and preferred within same list, but maybe better to separate? However we don't have a "Preferred qualifications" heading. Could include them under Requirements as well, but note they are bonus points. We'll keep them as part of Requirements list. We must remove boilerplate: EEO, scam warning, navigation, "About Us" duplicate, "Important Notice", "Pay Transparency" paragraph besides the pay range? The pay transparency paragraph is generic; we can keep only the pay range line. The instruction: "Prefer a few substantive sections over many thin ones." So we can keep the pay range line only. We must not include "About Us" duplicate; we already have company description in About the role. Now craft HTML. Let's extract About the role content: First paragraph about Storable: "At Storable, we're redefining property management for specialty real estate. Tailored for the marine industry, Storable Marine empowers marinas, boat clubs and rental operations with the industry's most comprehensive technology platform. Our solutions span management software, service management, rental tools, websites, payments, and more to streamline operations, enhance customer experiences, and maximize revenue. Explore our platform solutions at storablemarine.com." Then Overview: "Storable is seeking an experienced Engineering Manager to lead software development for our Marine Division (Storable Marine), building the software that powers the day-to-day operations of marinas, boatyards, yacht clubs, boat clubs, harbors, service yards, and other waterfront businesses. Our platform supports the workflows operators rely on to manage slips, docks, moorings, and dry storage; reservations and online bookings; boater and guest management; point of sale; payments and billing; customer and vessel records; digital waivers; service management; and other industry-specific needs." Then description of role: "As the Engineering Manager for our Marine platform, you will lead a team of around 10 engineers building and modernizing cloud-native SaaS applications used by marina operators and their boaters around the world. Your team works across the stack primarily in Node.js, React, and TypeScript, with PHP powering our rentals product and some legacy .NET in our core marina management system (MMS), all supported by AI-assisted engineering workflows." Then "Above all, this is a hands-on technical leadership role..." paragraph. We can combine into About the role paragraph(s). Usefor prose. Now Responsibilities: list from "What you'll do every day" bullet points. Also "How you'll lead with AI" bullet points. We'll combine all bullet points under Responsibilities. Let's extract responsibilities bullets: - Lead a high-performing team of engineers building and modernizing cloud-native SaaS applications used by marinas, boatyards, and other waterfront businesses worldwide. - Define and execute a product-aligned engineering strategy that advances Storable’s Marine platform and supports the broader business roadmap. - Stay technically hands-on where it counts: pairing with engineers in the code, reviewing designs and pull requests, and weighing in on architecture to keep direction grounded in the realities of the codebase. - Translate business priorities into actionable engineering roadmaps with clear KPIs, milestones, and success metrics for your team. - Oversee the design, development, and scaling of mission-critical applications, ensuring stability, performance, security, and readiness for regulatory and compliance frameworks. - Drive modernization initiatives that evolve legacy systems into distributed, service-oriented architectures, leveraging AI-assisted tooling to explore options, de-risk migrations, and move faster without compromising quality. - Champion best-in-class engineering practices, including automated testing, code quality, observability, effective use of CI/CD pipelines, and thoughtful AI-assisted development workflows. - Recruit, manage, coach, and grow a diverse team of engineers, fostering a culture of collaboration, innovation, continuous learning, and responsible AI adoption. - Lead incident response for your team’s services in partnership with our dedicated DevOps team, continuously improving reliability, uptime, and cost-efficiency. - Partner closely with Product, Operations, Client Success, and other stakeholders across the U.S. and Storable’s global hubs to align technology delivery with user and business needs, clearly explaining technical decisions and tradeoffs to both technical and non-technical audiences. Then "How you'll lead with AI" bullets: - Set clear standards and guardrails for AI-assisted development, including how AI-generated code is reviewed for correctness, security, maintainability, and fit within the broader system before anything ships. - Coach engineers on effective use of tools such as GitHub Copilot, Cursor, ChatGPT, or similar platforms, helping them know when AI can safely accelerate the work and when careful human judgment is required. - Identify and sponsor internal AI-enabled tools, automations, and workflows that reduce repetitive engineering work, improve developer experience, and free the team to focus on higher-leverage problems. - Critically evaluate AI-generated designs, code, and documentation, ensuring your team improves and integrates outputs thoughtfully rather than accepting them blindly. - Measure and communicate the impact of AI-assisted workflows on speed, quality, and delivery, using data to continuously refine how the team applies AI. We'll include these as li under Responsibilities. Now Requirements: "What you need to bring" list: - Bachelor’s or Master’s degree in Computer Science, Software Engineering, or a related field, or equivalent professional experience. - 7+ years of progressive software engineering experience, including direct experience managing and growing engineering teams. - Proven track record delivering cloud-based SaaS products at scale in fast-paced, growth-oriented environments. - Deep, hands-on engineering background building and shipping production web applications with Node.js and React (TypeScript/JavaScript), with the technical depth to review designs and code, reason through complex systems, mentor senior engineers, and guide transitions from legacy systems to cloud-native, service-oriented architectures. - Demonstrated, day-to-day fluency with AI-assisted development tools (such as GitHub Copilot, Cursor, ChatGPT, or similar) and an AI-forward mindset for improving engineering workflows, code quality, and team performance. - Strong communication and stakeholder management skills, with experience collaborating across functions and geographies and explaining technical decisions clearly to both technical and non-technical audiences, along with a working understanding of AWS, scalable infrastructure, application security, and Agile/Lean development practices. Then Bonus points (preferred): - Experience modernizing legacy systems or incrementally refactoring older codebases while maintaining reliability for production users. - Experience working on SaaS products that power industry-specific operational workflows, such as point of sale, reservations and bookings, payments, customer management, service/work-order management, channel management, or marketplace-style systems. - Experience in marine, marina, or waterfront hospitality software, or adjacent field-service and asset-management domains. - Experience building internal AI-enabled tools, automations, or workflows for engineering teams, and mentoring engineers on effective prompting, AI-assisted code review, and AI-driven development practices. - Experience defining and tracking engineering performance indicators (for example, velocity, uptime, release quality, and cost efficiency) and using those insights to improve team outcomes. - All applicants must be currently authorized to work in the United States on a full-time basis. - Storable is a fully distributed company, but is currently only registered for employment in certain states. To be eligible for employment, you must reside in the following states: AL, AZ, CA, CO, CT, FL, GA, ID, IL, IN, IA, KS, LA, MD, MA, MI, MN, MO, MS, NC, NE, NJ, NV, NY, OH, OK, OR, PA, SC, TN, TX, UT, VA, WA, WI, WY. We should include those as part of Requirements (maybe as separate list). The instruction: preserve ALL substantive information. So include them. We need to avoid repeating "All applicants must be currently authorized to work in the United States on a full-time basis." and the state list; they are substantive. Now Benefits: list from "Benefits and Perks:" bullet points. Let's extract: - Generous health coverage for you and your family, including fully paid short- and long-term disability coverage and two-times base salary life insurance. - 401(k) match after 60 days, 100% vested after 1 year. - Employer contribution to your HSA, plus an HRA to help offset your deductible. - Instant access to flexible vacation. We trust you, so we have a ‘take what you need’ vacation policy. - Be More – company rewards and recognition that add up and can be redeemed for personalized gifts and experiences! Storriors have been able to enroll in SCUBA certification classes, travel overseas, and redo their back patio, among many other things