Engineering Manager

We need to output 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. Must not include Job ID etc. Remove boilerplate. We need to parse the posting. Content: - Intro about Gigs: description of company. Could be "About the role"? Actually "About Gigs" is company description. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. We have: - About Gigs (company description) maybe fits "About the role"? But "About the role" is about the role, not company. However we can still use "About the role" heading for description of role? The posting includes "The Role Engineering Managers at Gigs are responsible..." That's about the role. So we can put that under "About the role". Also there is "What You'll Do" which is responsibilities. - Responsibilities: list of duties under "What You'll Do". - Requirements: maybe "What We're Looking For" includes requirements. - Qualifications: maybe overlapping with requirements; but we can separate: Requirements could be experience, technical background; Qualifications could be specific skills? But we need to avoid duplication. The instruction: Prefer a few substantive sections over many thin ones. So we might combine. We need to include sections only if posting has real specific content. We have content for: - About the role: description of role (Engineering Managers at Gigs are responsible... building modern connectivity platform...). That's substantive. - Responsibilities: bullet list under "What You'll Do": Lead, support, grow team; Partner with Product and Design; Drive technical excellence; Create team environment; Ensure sustainable culture; Contribute to hiring; Step into technical discussions. - Requirements/Qualifications/Skills: "What We're Looking For" includes: 4+ years experience leading engineering teams; Strong technical background; thoughtful approach to people management; comfort navigating ambiguity; clear communicator; bias for impact; Experience with modern product development practices (Go, Ruby, TypeScript, PostgreSQL, GCP), including continuous delivery, observability, infrastructure as code; Ideally experience managing remote/distributed teams; Experience building API forward products (nice to have). That's a mix of requirements and skills. We could make a single section "Requirements" with bullet list. - Benefits: "What We Offer" includes: competitive compensation and stock options; stipends for home office or work setup; budget for learning and development; free phone and international data plan. Also mention offices designed like home-inspired workspaces, plants, tools, small teams. Also mention flexibility, regular time in hubs, occasional travel. That's benefits and maybe schedule. - Pay: Not explicitly stated; only "competitive compensation". That's vague; we should not create Pay section unless posting actually states them. It says "competitive compensation and stock options". That's not a specific number; but it's still mention of compensation. The rule: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. "competitive compensation" is somewhat vague but it's still stating they offer compensation. However it's not a specific number; but it's still stating they offer compensation. The rule about filler text includes "commensurate with experience". "competitive compensation" is similar but not exactly filler? Might be considered vague but still a statement. Safer to include Benefits section and maybe not Pay. Since they didn't give specific salary, we might omit Pay. - Schedule: They mention "We value in-person collaboration... You should expect regular time in one of our hubs, as well as occasional travel for team workshops, customer meetings, and Gigs Republic". That's schedule expectations. Could be considered Schedule section. The rule: only create Schedule if posting actually states them. It does state expectations about time in hubs and occasional travel. So we can include Schedule. Thus sections: About the role, Responsibilities, Requirements, Benefits, Schedule. We need to use

for each heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not repeat job title. Not include metadata like Job ID. We must preserve all substantive information; do not invent or summarize away detail. We need to include all details from the posting that are relevant. Let's extract precise text. About the role: The paragraph: "Engineering Managers at Gigs are responsible for enabling a high-performing group of engineers to ship impactful work, grow their skills, and collaborate cross-functionally. This is a hands-on leadership role — you will guide technical execution while helping shape the team’s long-term direction We are building a modern connectivity platform that powers embedded telecom experiences and the challenges are real: scaling APIs, abstracting telco complexity, and designing systems that are global from day one." Note there is missing punctuation but we keep as is. Responsibilities: bullet list under "What You'll Do": each line starts with a verb. - Lead, support, and grow a team of software engineers working on core parts of our platform - Partner with Product and Design to define priorities, shape roadmaps, and deliver high-quality features - Drive technical excellence — from architecture to code reviews to reliability - Create a team environment that balances ambition, ownership, and continuous learning - Ensure a sustainable and inclusive engineering culture where people thrive - Contribute to hiring and onboarding processes to help scale the team thoughtfully - Step into technical discussions with clarity and pragmatism when needed We need to preserve exactly. Requirements: from "What We're Looking For": list items. - 4+ years of experience leading engineering teams in high-growth, product-driven environments - Strong technical background — you have shipped code at scale and can dive deep when needed - A thoughtful approach to people management and a track record of growing and developing engineers - Comfort navigating ambiguity and building clarity - A clear communicator who brings cross-functional stakeholders together - Bias for impact, balanced with high standards and good judgment - Experience with modern product development practices (we use Go, Ruby, TypeScript, PostgreSQL, GCP), including continuous delivery, observability, and infrastructure as code - Ideally experience managing and working with remote and distributed teams - Experience building API forward products (nice to have) We could group as requirements. Benefits: from "What We Offer": competitive compensation and stock options; stipends for your home office or work setup; a budget for learning and development to fuel your career; a free phone and international data plan. Also mention offices designed to feel like home-inspired workspaces, with plants, thoughtful tools, and small, tight-knit teams that make collaboration feel natural, energizing, and effective. Also mention flexibility where it makes sense, some focused work can be done remotely, not every role or week looks the same. Also mention regular time in hubs, occasional travel for team workshops, customer meetings, and Gigs Republic, our bi-annual company off-site. But some of that overlaps with schedule. We'll separate: Benefits: compensation, stipends, learning budget, free phone/data plan, office environment (plants, tools, small teams). Schedule: expectation of regular time in hubs, occasional travel, flexibility, remote work. We need to ensure we don't duplicate. Let's craft Benefits section: list items: - Competitive compensation and stock options - Stipends for home office or work setup - Budget for learning and development - Free phone and international data plan - Home‑inspired office workspaces with plants, thoughtful tools, and small tight‑knit teams Schedule section: list items: - Expectation of regular time in one of our hubs - Occasional travel for team workshops, customer meetings, and Gigs Republic (bi‑annual company off‑site) - Flexibility for focused remote work where it makes sense - Not every role or week looks the same (some flexibility) We need to preserve all substantive information; we should not lose any detail. Now produce HTML. Structure:

  About the role

  Engineering Managers at Gigs are responsible for enabling a high-performing group of engineers to ship impactful work, grow their skills, and collaborate cross-functionally. This is a hands-on leadership role — you will guide technical execution while helping shape the team’s long-term direction. We are building a modern connectivity platform that powers embedded telecom experiences and the challenges are real: scaling APIs, abstracting telco complexity, and designing systems that are global from day one.

  Responsibilities

  • Lead, support, and grow a team of software engineers working on core parts of our platform
  • Partner with Product and Design to define priorities, shape roadmaps, and deliver high-quality features
  • Drive technical excellence — from architecture to code reviews to reliability
  • Create a team environment that balances ambition, ownership, and continuous learning
  • Ensure a sustainable and inclusive engineering culture where people thrive
  • Contribute to hiring and onboarding processes to help scale the team thoughtfully
  • Step into technical discussions with clarity and pragmatism when needed

  Requirements

  • 4+ years of experience leading engineering teams in high-growth, product-driven environments
  • Strong technical background — you have shipped code at scale and can dive deep when needed
  • A thoughtful approach to people management and a track record of growing and developing engineers
  • Comfort navigating ambiguity and building clarity
  • A clear communicator who brings cross-functional stakeholders together
  • Bias for impact, balanced with high standards and good judgment
  • Experience with modern product development practices (we use Go, Ruby, TypeScript, PostgreSQL, GCP), including continuous delivery, observability, and infrastructure as code
  • Ideally experience managing and working with remote and distributed teams
  • Experience building API forward products (nice to have)

  Benefits

  • Competitive compensation and stock options
  • Stipends for home office or work setup
  • Budget for learning and development
  • Free phone and international data plan
  • Home‑inspired office workspaces with plants, thoughtful tools, and small tight‑knit teams

  Schedule

  • Expectation of regular time in one of our hubs
  • Occasional travel for team workshops, customer meetings, and Gigs Republic (bi‑annual company off‑site)
  • Flexibility for focused remote work where it makes sense
  • Not every role or week looks the same
  Check for any missing substantive info: The intro about Gigs company description: "About Gigs At Gigs, we're building the operating system for mobile services..." That is not included. Should we include that? It's substantive about company. The instruction: we should preserve ALL substantive information. The company description is substantive. Where to put? Could be part of About the role? But About the role is about the role, not company. However we could add a separate section like "About Gigs" but not in allowed headings list. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qual