Staff Software Engineer, Platform Infrastructure

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Zūm" then "Who You Are", "What You'll Do", "What You Bring To Zūm", "Bonus Points", compensation, benefits, location, schedule. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We need to decide which sections to include based on content. We have: - About Zūm (company description) maybe not needed as a section? Could be "About the role"? Actually "About the role" is typical heading for description of role. The posting includes "Who You Are", "What You'll Do", "What You Bring To Zūm", "Bonus Points". Also compensation and benefits. We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can combine: - About the role: maybe a brief summary of role (own architecture etc). Could use "What You'll Do" as Responsibilities. - Responsibilities: list of duties from "What You'll Do". - Requirements: maybe "What You Bring To Zūm" (core requirements) plus "Bonus Points" as optional? Could treat Bonus Points as Skills? Or separate Skills section. - Qualifications: maybe education and experience. - Skills: technical skills list. - Benefits: benefits listed. - Pay: salary range. - Schedule: onsite 3x/week Monday, Tuesday, Thursday; based in Bay Area. We must not create sections with placeholder text. Must include only if real content. We need to preserve all substantive information, not invent or summarize away detail. Must not repeat job title. We must remove boilerplate: EEO, AI tools, etc. Also remove navigation, cookie, legal, duplicated lines. We need to output only HTML fragment, no /, no markdown fences. Let's extract substantive content: Company description: About Zūm (first paragraph). Might be considered "About the role"? Not exactly but could be included as part of About the role? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not limited to those? Probably we should stick to those headings. So we need to map content to those headings. We could have:

About the role

Own the architecture and roadmap for Zūm's product platform, and build it - our product engineering team uses TypeScript/Node.js, Kubernetes, PostgreSQL, OpenSearch, Redis, Kafka, and gRPC. Stay hands-on with the product: build and review features, so foundational layers stay grounded in how they're actually used. Work with product teams to decide what stays in the monolith and what becomes its own service, and make that extraction process routine and low-risk when it happens. Make security and compliance part of the platform by design: build shared primitives for authentication and access rules to sensitive data, so product teams build on secure, policy-aligned foundations. Watch how the platform behaves under real production load and evolve it ahead of need: spot emerging bottlenecks (event-loop stalls, slow queries, locking, index design, partition skew, consumer lag, RPC latency, retry storms, etc.), trace them to the architectural cause, and turn recurring problems into platform improvements. Build the rules, automated checks, and tooling improvements that steer AI coding agents toward writing code that already fits platform patterns and conventions. Jump in on live platform issues, lead incident and correction-of-error reviews, and own the systemic fixes that follow. Act as the escalation point and thought partner for engineering leadership on platform investment and tradeoffs.

That's responsibilities essentially. But we also need a Responsibilities section; maybe we can combine About the role and Responsibilities? But we need to avoid duplication. Could make About the role a brief summary, and Responsibilities a list. Let's parse: About Zūm (company) maybe not needed. Could be omitted? The instruction says we should include sections only when posting has real, specific content for it. The posting does have "About Zūm" describing company. But allowed headings don't include "About the company". However we could put that under About the role? Might be okay. But we need to preserve ALL substantive information. If we omit company description, we lose info. So we need to include it somewhere. Perhaps we can include a brief paragraph under About the role that includes company description plus role overview. That would preserve. Alternatively we could create a section "About the role" that includes both company description and role overview. That seems acceptable. Now Responsibilities: we could list bullet points from "What You'll Do". Use

• . Requirements: maybe "What You Bring To Zūm" (core requirements). Use
  • . Qualifications: maybe education and experience (Bachelor's degree or higher, 8+ years). Could be part of Requirements though. But we can separate. Skills: technical skills list (Node.js/TypeScript, Kubernetes, Kafka, gRPC, Redis, OpenSearch, etc.) plus authentication/authorization, etc. Benefits: list of benefits. Pay: salary range. Schedule: onsite 3x/week Monday, Tuesday, Thursday; based in Bay Area. We must not create sections with placeholder text like "commensurate with experience". We have actual content. Now we need to ensure we don't repeat job title as heading. No job title given explicitly; we can ignore. We must not include Job ID/requisition numbers. We must remove boilerplate: EEO, AI tools, etc. Now let's extract details: Company description (About Zūm): "Zūm is revolutionizing mass mobility with its Connected Mobility Experience ( Zūm CMX ™) system that connects and coordinates people, vehicles, and operations in real time. In the $50 billion student mobility market – the largest segment of the mass mobility industry – Zūm CMX is transforming a daily source of anxiety and disruption into a reliable, transparent, and efficient mobility experience for students and families. Today, more than 6,500 schools rely on Zūm CMX . Recognized globally for its innovative approach and operational execution, Zūm has been named to Fast Company’s World’s Most Innovative Companies, CNBC Disruptor 50 and Changemakers, the World Economic Forum, and the Financial Times’ Fastest Growing Companies lists. Zūm is backed by leading investors including Sequoia Capital, GIC, TPG, and Softbank." That's substantive. Location: "This role is based at the Company’s headquarters in Redwood Shores, CA and requires you to be onsite 3x/week (Monday, Tuesday, and Thursday). We will only consider candidates already based in the Bay Area." Now "Who You Are": a paragraph describing mindset. Could be part of About the role or Qualifications? Might be considered "What You Bring To Zūm"? Actually "Who You Are" is more about mindset/attributes. Could be part of Qualifications or Skills? Might be better to include under "What You Bring To Zūm" as part of requirements? But we have separate "What You Bring To Zūm" which lists qualifications and experience. The "Who You Are" is more about attitude. Could be included under "Qualifications" as soft skills? Or we could create a section "Skills" for soft skills? But allowed headings include Skills. We could put soft skills there. But we need to preserve all info. Let's capture "Who You Are" text: "You care as much about how software gets built as what it does, and you measure a platform by the features it enables.You want to build scalable infrastructure and technologies that enable Zūm products to grow and adapt at the pace today's AI makes possible.You lead through execution and influence through adoption of the platforms you build.When someone asks for "the best" solution, you map out the tradeoffs, present real options, and commit to a recommendation.You start simple, add complexity only when the data proves you need it, and lean on experience when measuring isn't worth the cost.Products created on your platform are easy to maintain and a joy to build on." Now "What You'll Do": we already captured. Now "What You Bring To Zūm": list: - Bachelor's degree or higher in Computer Science or equivalent experience. - 8+ years of industry experience as a Software Engineer, with significant time spent building platforms, shared services, or core backend systems that other engineering teams build on. - Deep expertise in Node.js/TypeScript (or a comparable backend language) and strong command of relational database design, including schema modeling, indexing, and query performance. - Hands-on experience with the building blocks of a modern service-oriented backend: Kubernetes, Kafka or equivalent messaging systems, gRPC or similar RPC frameworks, Redis, and search/indexing systems like OpenSearch. - Experience designing and building authentication/authorization systems, including SSO protocols (SAML, OIDC) and authorization models (RBAC/ABAC). - Track record of extracting services from a monolith deliberately and safely, with clear judgment about what should and shouldn't be split out. - Comfort diagnosing performance issues at the architectural level: query plans, locking, partitioning, consumer lag, RPC latency, and similar failure modes. - Proven ability to set technical direction and drive adoption through good defaults, not mandate. - Excellent communication skills, comfortable holding a technical line respectfully in design reviews. - Comfort operating with a high degree of ownership and autonomy in a fast-moving startup environment. - Good sense of humor with a great ability to work with others. Now "Bonus Points": - Passionate about working for a mission-driven company. - Experience embedding engineering standards into AI coding agents or developer tooling (linting/agent rules, code generation harnesses, automated review checks). - Experience building platforms in a regulated or compliance-sensitive space (e.g., education, healthcare, fintech) where access control and data handling are first-class concerns. - Experience working in transportation, logistics, or another operationally complex industry. Now compensation: "The targeted base salary range for this role is listed in the compensation section below. Actual salary may be above or below this range based on factors such as location, skills, and relevant experience. In addition, this position may include additional compensation in the form of equity or commissions. If you are a full-time salaried or hourly worker, we offer the following benefits: Medical, Dental, Vision, 401(k), Holidays, Wellness, Vacation, and more. The targeted pay range for this role in CA, USA is: $240,000 - $280,000 plus stock options." We need Benefits: Medical, Dental, Vision, 401(k), Holidays, Wellness, Vacation, and more. Pay: $240,000 - $280,000 plus stock options. Now schedule: onsite 3x/week (Monday, Tuesday, Thursday). Location: Redwood Shores, CA; must be based in Bay Area. Now we need to output HTML with headings

    and content. We must not include any markdown fences. Let's decide sections: - About the role: include company description + maybe brief role overview? Could also include "Who You Are"? But we might put "Who You Are" under Skills? Actually "Who You Are" is about mindset/attributes, could be part of Skills (soft skills). But we have a Skills heading for technical skills; we could also include soft skills there. However we have also a Qualifications heading for education/experience. Let's allocate: About the role: company description + role purpose (maybe a short sentence). Could also include "Who You Are"? Might be too much. Responsibilities: list from "What You'll Do". Requirements: maybe "What You Bring To Zūm" (core requirements). Could be a list. Qualifications: education and experience (Bachelor's degree, 8+ years