Member of Technical Staff, Admin Experiences
Envoy · San Francisco, CA · 1 mo ago
On-siteEngineering$205k–$225k/yrFull-time
We need to produce HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. No Job ID etc. Remove boilerplate. Must preserve all substantive info.
We need to parse the posting.
Let's extract sections:
- About The Role: description about fullstack engineering, etc. We'll put under
About the role
with paragraphs. - Responsibilities: bullet list of duties: Build and ship high-quality..., Partner closely..., Design and evolve backend..., Build performant..., Contribute to architecture..., Design and optimize relational data models..., Participate in code reviews..., Own features end-to-end..., Build intuitive administrator experiences... - Requirements: maybe "You have" list: BS/MS, 7+ years, strong frontend fundamentals, backend experience, experience designing relational schemas, familiarity with Git/GitHub and CI/CD, product mindset, experience collaborating cross-functionally, comfort in ambiguous spaces, experience building or integrating identity and authentication systems. - Qualifications: maybe overlapping with requirements; but we can treat "You have" as qualifications. Could also have "Your values" as separate section? Might be "Skills" or "Values". The instruction says use headings like Skills, Benefits, Pay, Schedule. We'll include Skills for technical skills list. Benefits: "Competitive compensation, benefits, and growth opportunities" maybe too vague; but we have compensation range given: $205K - $225K. That's Pay. Benefits: maybe not detailed; but we have "Competitive compensation, benefits, and growth opportunities" which is vague; we should not create Benefits section unless posting actually states them. It mentions benefits but not specifics. The rule: never create Benefits section unless posting actually states them. It does state "Competitive compensation, benefits, and growth opportunities" which is a mention of benefits but not specific. Might be considered stating benefits generically; but we need to decide. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It states benefits generically, so we could include a Benefits section with that sentence. However we also have Pay: compensation range given, so include Pay section. Schedule: "This is an on-site position that requires 4 days a week (Monday through Thursday) in our San Francisco HQ office." That's schedule info. So include Schedule section. Now we need to avoid filler like "commensurate with experience". Not present. We need to output only HTML fragment, no html/body tags. We'll structure:About the role
... paragraphs ...
Responsibilities
- ... ...
Requirements
- ... ...
Skills
- ... ...
Pay
Compensation range: $205K - $225K
Schedule
On‑site, 4 days per week (Monday through Thursday) at the San Francisco HQ office.
We might also include Benefits: "Competitive compensation, benefits, and growth opportunities" but we already have Pay; Benefits could be generic but we have mention. Let's include Benefits section with that sentence. But we must avoid duplication: Pay already mentions compensation range; Benefits can mention "benefits and growth opportunities". We'll include. Now we need to ensure we preserve all substantive information from the posting. Let's extract all substantive sentences. Original text: Envoy protects the places the world relies on most by unifying people, spaces, and communications in one secure, integrated workplace management platform and ecosystem. More than 16,000 workplaces around the world trust Envoy to run secure, compliant, and connected operations across every location. From manufacturing sites and data centers to life sciences labs, healthcare facilities, and corporate headquarters, Envoy unifies visitor management, risk assessment, mailroom management, digital signage software, resource booking, and emergency management into one integrated platform. With deep integrations across access control, identity, compliance screening, and collaboration tools—including LenelS2, Brivo, Genetec, Honeywell, Cisco Meraki, Okta, Microsoft Azure, Microsoft Teams, Slack, ServiceNow, DocuSign, Avigilon Alta, and Descartes Visual Compliance—Envoy helps organizations reduce risk, stay audit-ready, and operate with clarity at scale. Learn more at envoy.com This is an L3 opportunity. Successful candidates often come from senior engineering roles and are experienced in leading complex projects, mentoring peers, and making architectural contributions across teams. About The Role Fullstack engineering at Envoy sits at the intersection of product, systems, and real-world experience. The features you build touch everything — from the interfaces millions of people use to interact with their workplace, to the administrator experiences that help organizations manage users, access, permissions, and workplace settings at scale. As a Fullstack Engineer, you'll own meaningful product areas end-to-end, partnering closely with Product, Design, and Engineering to translate complex problems into simple, high-quality solutions. Your work spans the full stack — from scalable backend systems and APIs to performant, accessible frontend experiences. We value engineers who move fluidly across the stack and take pride in the quality of everything they ship. We hire for strong full stack fundamentals and a product mindset first. The balance between frontend and backend depth is flexible - some engineers skew heavier toward the frontend, others toward the backend. What matters most is end-to-end ownership and high-quality execution across the stack. Role Lean: Fullstack (50/50) This role requires equal depth across frontend and backend. UI craftsmanship and backend systems carry the same weight — you'll move fluidly across the stack, and neither side is secondary. Full end-to-end ownership is the expectation. This is an on-site position that requires 4 days a week (Monday through Thursday) in our San Francisco HQ office. You will Build and ship high-quality, scalable features across the full stack — frontend UI, backend services, and APIsPartner closely with Product, Design, and Engineering to deliver thoughtful, user-centered solutionsDesign and evolve backend systems: APIs, data models, and services consumed by web and mobile clientsBuild performant, accessible, and maintainable frontend experiences using React and modern web technologiesContribute to architecture decisions, shared components, and engineering standards across the stackDesign and optimize relational data models (Postgres) and improve system performance and observabilityParticipate in code reviews, technical discussions, and continuous improvement of engineering qualityOwn features end-to-end, from discovery and design through launch and iterationBuild intuitive administrator experiences for managing users, access, permissions, identity, and authentication across complex organizations You have A BS or MS in Computer Science or a related technical field7+ years of experience building production software, with meaningful fullstack or cross-stack contributionsStrong frontend fundamentals, including React and JavaScript/TypeScript, with a solid foundation in HTML and CSSBackend experience building and consuming APIs (RESTful and/or GraphQL), with production exposure to TypeScript, Java/Kotlin, and/or Ruby on RailsExperience designing relational schemas and working with PostgresFamiliarity with Git/GitHub and CI/CD workflowsA product mindset — you care deeply about usability, performance, and measurable impactExperience collaborating cross-functionally with Product, Design, and Engineering partnersComfort working in ambiguous problem spaces and taking ownership to drive outcomesExperience building or integrating identity and authentication systems, including SCIM, SSO, OAuth, and SAML Your values You are product-minded and user-focused, with a strong sense of quality and craftsmanship across the full stackYou take ownership for outcomes, driving work forward end-to-end and following through on impact, not just implementationYou hold a high bar for everything you build — how it looks, how it performs, and how it scalesYou communicate clearly and value collaboration and constructive feedbackYou balance technical excellence with delivery, adapting as priorities evolveYou are curious and motivated to continuously learn and improveYou thrive in a team environment and take pride in shared success You'll get The opportunity to work across the full stack on meaningful product areas, including customer-facing surfaces, platform systems, and internal toolsA collaborative, cross-functional environment with a strong Product and Design partnershipOwnership and autonomy over impactful work spanning frontend and backendA thoughtful team-matching process designed to align your strengths and interests with the right product teamCompetitive compensation, benefits, and growth opportunities By applying for this position, you acknowledge that you have fully read and understand the job requirements and received the Envoy Privacy Notice for applicants, which is linked here. Completing this application requires you to provide personal data, such as your name and contact information, which is mandatory for Envoy to process your application. Envoy is an EEO Employer and does not discriminate on the basis of any characteristic protected by local, state or federal law. Compensation Range: $205K - $225K We need to remove boilerplate: EEO, privacy notice, application instructions, Learn more at envoy.com, etc. We need to keep substantive info: company description maybe not needed? It's about Envoy but not directly role specifics. Might be considered background but could be included in About the role? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The company description is substantive about Envoy. Should we include? It's not a section heading but could be part of About the role paragraph. The About the role currently includes description of fullstack engineering. We could prepend a brief paragraph about Envoy from the first few sentences. That is substantive. Let's include it in About the role. Thus About the role paragraph(s) will include: Envoy protects the places the world relies on most by unifying people, spaces, and communications in one secure, integrated workplace management platform and ecosystem. More than 16,000 workplaces around the world trust Envoy to run secure, compliant, and connected operations across every location. From manufacturing sites and data centers to life sciences labs, healthcare facilities, and corporate headquarters, Envoy unifies visitor management, risk assessment, mailroom management, digital signage software, resource booking, and emergency management into one integrated platform. With deep integrations across access control, identity, compliance screening, and collaboration tools—including LenelS2, Brivo, Genetec, Honeywell, Cisco Meraki, Okta, Microsoft Azure, Microsoft Teams, Slack, ServiceNow, DocuSign, Avigilon Alta, and Descartes Visual Compliance—Envoy helps organizations reduce risk, stay audit-ready, and operate with clarity at scale. Then continue with the role description. We must not include "Learn more at envoy.com". Also remove "This is an L3 opportunity. Successful candidates often come from senior engineering roles and are experienced in leading complex projects, mentoring peers, and making architectural contributions across teams." That's also substantive about seniority; could be included in About the role or maybe as a separate section? Could be part of About the role. We'll include it. Now Responsibilities: we have list after "You will". Need to split into bullet points. Let's extract each bullet: - Build and ship high-quality, scalable features across the full stack — frontend UI, backend services, and APIs - Partner closely with Product, Design, and Engineering to deliver thoughtful, user-centered solutions - Design and evolve backend systems: APIs, data models, and services consumed by web and mobile clients - Build performant, accessible, and maintainable frontend experiences using React and modern web technologies - Contribute to architecture decisions, shared components, and engineering standards across the stack - Design and optimize relational data models (Postgres) and improve system performance and observability - Participate in code reviews, technical discussions, and continuous improvement of engineering quality