Engineering Manager — AI & Enterprise Platform
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we must only include sections when posting has real, specific content. We need to map content to these headings appropriately.
We have sections: About Skan.ai (company description) maybe "About the role"? Actually "About Skan.ai" is about company, not role. Could be "About the role" but we have "The Role". Could map to "About the role". The role description includes responsibilities (What You’ll Own). So we can have About the role
with paragraph summarizing role? But we must not repeat job title as heading. We can include a short paragraph about role.
Then responsibilities: "What You’ll Own" list of duties. Use - .
Requirements: "What You Bring" list of qualifications. Use
- .
Skills: maybe "Bonus Points" could be skills. Or we could treat "Bonus Points" as Skills.
Benefits: "Competitive base salary, meaningful equity, and comprehensive benefits." plus maybe "Compensation will be based on experience, location, and background." Also location details. We have compensation info: "Competitive base salary, meaningful equity, and comprehensive benefits." That's benefits. Also location: Menlo Park, California, USA. Also location later: San Francisco Bay Area, on-site. We need to include Pay and Schedule sections only if posting actually states them. Pay: they mention competitive base salary, meaningful equity, comprehensive benefits. That's compensation but not specific numbers. The rule says: 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. They do state compensation: "Competitive base salary, meaningful equity, and comprehensive benefits." That's not a specific number but it's still stating compensation exists. Is that considered filler? It's vague but it's stating they offer competitive base salary, equity, benefits. That's substantive enough? The instruction: "never emit a heading followed by filler/placeholder text (e.g., 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". "Competitive base salary, meaningful equity, and comprehensive benefits." is not exactly those placeholders; it's a statement of what they offer. So we can include a Benefits section (maybe also Pay). However they also have a separate "Compensation" heading in the posting. We could map that to Benefits and Pay? The instruction says use headings: Benefits, Pay, Schedule. So we could have a Benefits section describing equity, benefits. Pay maybe we could note "Competitive base salary" as pay. But we need to avoid filler. Could combine into Benefits? But we need separate headings if we have content. We have info about compensation: competitive base salary, meaningful equity, comprehensive benefits. That covers both pay and benefits. Could we put Pay: Competitive base salary. Benefits: meaningful equity, comprehensive benefits. That seems okay.
Location: we have location info: Menlo Park, California, USA. Also later: San Francisco Bay Area, on-site. We could include location in a short paragraph maybe under About the role? There's no heading for location in allowed list; we could fold minor metadata into a short
or drop it. So we can include a
with location details.
Schedule: not mentioned. So we should not create Schedule section.
We must remove boilerplate like EEO etc. Not present.
We need to output only HTML fragment, no /. Use
for headings, - for lists,
for prose.
We must preserve all substantive information; do not invent or summarize away detail. So we need to include all bullet points from What You’ll Own, What You Bring, Bonus Points, Why Join Skan Now, etc. Also include company description About Skan.ai.
We need to decide which headings to use: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map:
- About the role: include company description and role overview (The Role paragraph). Could also include location? Might be okay.
- Responsibilities: What You Own list.
- Requirements: What You Bring list (mandatory qualifications).
- Skills: Bonus Points list (desired skills/experience).
- Benefits: from Compensation: competitive base salary, meaningful equity, comprehensive benefits.
- Pay: maybe we could also include base salary? But we already used Benefits for equity and benefits. Pay could be "Competitive base salary". However that duplicates. Could we instead put Pay: Competitive base salary, and Benefits: meaningful equity, comprehensive benefits. That splits.
- Schedule: not present, omit.
We must not create a heading with filler. Ensure each heading has substantive content.
We need to ensure we don't repeat job title as heading. We are not.
Now we need to extract all bullet points.
Let's parse the posting.
Company description: "About Skan.ai Skan.ai is redefining how the world’s largest enterprises understand and optimize work. Our process intelligence platform uses AI and computer vision to observe how work actually happens across systems, teams, and workflows — creating a living operational model of enterprise execution. Fortune 500 enterprises across banking, insurance, healthcare, and BPO rely on Skan to uncover operational inefficiencies, accelerate transformation, and build the foundation for enterprise-scale AI adoption."
The Role paragraph: "We’re looking for an Engineering Manager to lead the development and delivery of critical platform and product capabilities across Skan’s AI-powered enterprise platform. You will combine strong technical leadership with people management, working closely with product, design, data science, and customer-facing teams to translate complex customer and business requirements into reliable, scalable software. This role is ideal for an engineering leader who enjoys operating at the intersection of software engineering, AI, ML, distributed systems, data platforms, and enterprise SaaS."
What You’ll Own (responsibilities) list:
- Lead, mentor, and grow a high-performing team of software engineers, fostering strong engineering practices and a culture of ownership and execution.
- Own engineering execution for key product and platform initiatives, from technical planning through production delivery.
- Partner closely with Product Management and Design to translate product requirements into scalable technical solutions.
- Drive architecture, system design, technical strategy, and engineering standards across the team.
- Build reliable and scalable backend and platform services supporting Skan’s enterprise AI and process intelligence products.
- Work closely with AI, ML and data engineering teams to integrate models, analytics, telemetry, and intelligence capabilities into production systems.
- Establish strong practices around code quality, testing, observability, deployment, reliability, and security.
- Identify technical risks, architectural bottlenecks, and opportunities to improve engineering velocity and system performance.
- Participate in hiring, onboarding, performance management, career development, and organizational planning.
- Collaborate with customer-facing teams when needed to understand enterprise requirements and resolve complex technical challenges.
- Help establish engineering roadmaps and ensure alignment between technical investments and business priorities.
- Provide clear technical communication to engineering leadership, product leadership, and executive stakeholders.
Compensation paragraph: "Competitive base salary, meaningful equity, and comprehensive benefits. Compensation will be based on experience, location, and background. Location: Menlo Park, California, USA."
What You Bring (requirements) list:
- 8+ years of software engineering experience, with demonstrated experience leading engineering teams.
- 2+ years of engineering management or people leadership experience in a product-focused software organization.
- Strong software engineering fundamentals and experience designing and building scalable production systems.
- Experience with backend systems, APIs, distributed systems, cloud infrastructure, or data-intensive applications.
- Strong understanding of modern software development practices, CI/CD, observability, testing, and production reliability.
- Experience working closely with Product, Design, Data Science, and other cross-functional teams.
- Ability to remain technically credible while operating effectively as a people and organizational leader.
- Proven ability to break down ambiguous technical problems, establish priorities, and drive projects to completion.
- Experience hiring, mentoring, developing, and retaining strong engineering talent.
- Strong communication skills with the ability to explain complex technical concepts to both technical and non-technical stakeholders.
- Comfortable operating in a fast-paced startup environment with evolving priorities and significant ownership.
Bonus Points list:
- Experience building AI, ML-powered enterprise products or platforms.
- Experience with LLMs, generative AI, machine learning infrastructure, or AI-enabled workflows.
- Background in process intelligence, observability, developer productivity, workflow automation, or enterprise SaaS.
- Experience with cloud platforms such as AWS, Azure, or GCP.
- Familiarity with technologies such as Python, Java, Go, TypeScript, Kubernetes, Docker, Kafka, PostgreSQL, Snowflake, Databricks, or similar modern technologies.
- Experience building data-intensive or telemetry-driven systems.
- Experience working with Fortune 500 customers or enterprise-scale software environments.
- Strong understanding of security, scalability, performance, and reliability requirements for enterprise applications.
- Technical background in Computer Science, Engineering, or a related field.
- Experience in a high-growth startup environment.
Why Join Skan Now list:
- Real Enterprise Scale: Skan.ai already powers operational intelligence initiatives inside Fortune 500 enterprises. You’ll build software that solves meaningful problems across complex enterprise environments.
- AI at the Core: Skan sits at the intersection of AI, computer vision, process intelligence, and enterprise software. You’ll work on technically challenging systems where AI creates measurable business impact.
- High Ownership, High Impact: This is not simply a team-management role. You’ll influence architecture, engineering strategy, product execution, hiring, and the technical direction of a growing enterprise AI platform.
- Build for the Enterprise: You’ll work on systems where scalability, reliability, security, and performance matter — and where engineering decisions directly impact large enterprise customers.
- Strong Cross-Functional Exposure: You’ll collaborate closely with Product, AI, ML, Data Science, Design, Customer Success, Solutions Engineering, and enterprise customers.
Location paragraph after Why Join: "Location San Francisco Bay Area, on-site. We expect regular in-office collaboration with engineering, product, and leadership teams. Occasional travel may be required for customer meetings and company events."
We need to include location info somewhere. Could add a short
under About the role or after.
We must not include application instructions etc. Not present.
Now construct HTML.
We'll start with
About the role
then containing company description and role overview and location? Maybe separate
for company description, then
for role overview, then
for location.
But we must not create extra headings. Use
for prose.
Let's do:
About the role
About Skan.ai: Skan.ai is redefining how the world’s largest enterprises understand and optimize work. Our process intelligence platform uses AI and computer vision to observe how work actually happens across systems, teams, and workflows — creating a living operational model of enterprise execution. Fortune 500 enterprises across banking, insurance, healthcare, and BPO rely on Skan to uncover operational inefficiencies, accelerate transformation, and build the foundation for enterprise-scale AI adoption.
The Role: We’re looking for an Engineering Manager to lead the development and delivery of critical platform and product capabilities across Skan’s AI-powered enterprise platform. You will combine strong technical leadership with people management, working closely with product, design, data science, and customer-facing teams to translate complex customer and business requirements into reliable, scalable software. This role is ideal for an engineering leader who enjoys operating at the intersection of software engineering, AI, ML, distributed systems, data platforms, and enterprise SaaS.
Location: Menlo Park
- .
Skills: maybe "Bonus Points" could be skills. Or we could treat "Bonus Points" as Skills.
Benefits: "Competitive base salary, meaningful equity, and comprehensive benefits." plus maybe "Compensation will be based on experience, location, and background." Also location details. We have compensation info: "Competitive base salary, meaningful equity, and comprehensive benefits." That's benefits. Also location: Menlo Park, California, USA. Also location later: San Francisco Bay Area, on-site. We need to include Pay and Schedule sections only if posting actually states them. Pay: they mention competitive base salary, meaningful equity, comprehensive benefits. That's compensation but not specific numbers. The rule says: 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. They do state compensation: "Competitive base salary, meaningful equity, and comprehensive benefits." That's not a specific number but it's still stating compensation exists. Is that considered filler? It's vague but it's stating they offer competitive base salary, equity, benefits. That's substantive enough? The instruction: "never emit a heading followed by filler/placeholder text (e.g., 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". "Competitive base salary, meaningful equity, and comprehensive benefits." is not exactly those placeholders; it's a statement of what they offer. So we can include a Benefits section (maybe also Pay). However they also have a separate "Compensation" heading in the posting. We could map that to Benefits and Pay? The instruction says use headings: Benefits, Pay, Schedule. So we could have a Benefits section describing equity, benefits. Pay maybe we could note "Competitive base salary" as pay. But we need to avoid filler. Could combine into Benefits? But we need separate headings if we have content. We have info about compensation: competitive base salary, meaningful equity, comprehensive benefits. That covers both pay and benefits. Could we put Pay: Competitive base salary. Benefits: meaningful equity, comprehensive benefits. That seems okay.
Location: we have location info: Menlo Park, California, USA. Also later: San Francisco Bay Area, on-site. We could include location in a short paragraph maybe under About the role? There's no heading for location in allowed list; we could fold minor metadata into a short
or drop it. So we can include a
with location details. Schedule: not mentioned. So we should not create Schedule section. We must remove boilerplate like EEO etc. Not present. We need to output only HTML fragment, no /. Use
for headings,
- for lists,
for prose. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all bullet points from What You’ll Own, What You Bring, Bonus Points, Why Join Skan Now, etc. Also include company description About Skan.ai. We need to decide which headings to use: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map: - About the role: include company description and role overview (The Role paragraph). Could also include location? Might be okay. - Responsibilities: What You Own list. - Requirements: What You Bring list (mandatory qualifications). - Skills: Bonus Points list (desired skills/experience). - Benefits: from Compensation: competitive base salary, meaningful equity, comprehensive benefits. - Pay: maybe we could also include base salary? But we already used Benefits for equity and benefits. Pay could be "Competitive base salary". However that duplicates. Could we instead put Pay: Competitive base salary, and Benefits: meaningful equity, comprehensive benefits. That splits. - Schedule: not present, omit. We must not create a heading with filler. Ensure each heading has substantive content. We need to ensure we don't repeat job title as heading. We are not. Now we need to extract all bullet points. Let's parse the posting. Company description: "About Skan.ai Skan.ai is redefining how the world’s largest enterprises understand and optimize work. Our process intelligence platform uses AI and computer vision to observe how work actually happens across systems, teams, and workflows — creating a living operational model of enterprise execution. Fortune 500 enterprises across banking, insurance, healthcare, and BPO rely on Skan to uncover operational inefficiencies, accelerate transformation, and build the foundation for enterprise-scale AI adoption." The Role paragraph: "We’re looking for an Engineering Manager to lead the development and delivery of critical platform and product capabilities across Skan’s AI-powered enterprise platform. You will combine strong technical leadership with people management, working closely with product, design, data science, and customer-facing teams to translate complex customer and business requirements into reliable, scalable software. This role is ideal for an engineering leader who enjoys operating at the intersection of software engineering, AI, ML, distributed systems, data platforms, and enterprise SaaS." What You’ll Own (responsibilities) list: - Lead, mentor, and grow a high-performing team of software engineers, fostering strong engineering practices and a culture of ownership and execution. - Own engineering execution for key product and platform initiatives, from technical planning through production delivery. - Partner closely with Product Management and Design to translate product requirements into scalable technical solutions. - Drive architecture, system design, technical strategy, and engineering standards across the team. - Build reliable and scalable backend and platform services supporting Skan’s enterprise AI and process intelligence products. - Work closely with AI, ML and data engineering teams to integrate models, analytics, telemetry, and intelligence capabilities into production systems. - Establish strong practices around code quality, testing, observability, deployment, reliability, and security. - Identify technical risks, architectural bottlenecks, and opportunities to improve engineering velocity and system performance. - Participate in hiring, onboarding, performance management, career development, and organizational planning. - Collaborate with customer-facing teams when needed to understand enterprise requirements and resolve complex technical challenges. - Help establish engineering roadmaps and ensure alignment between technical investments and business priorities. - Provide clear technical communication to engineering leadership, product leadership, and executive stakeholders. Compensation paragraph: "Competitive base salary, meaningful equity, and comprehensive benefits. Compensation will be based on experience, location, and background. Location: Menlo Park, California, USA." What You Bring (requirements) list: - 8+ years of software engineering experience, with demonstrated experience leading engineering teams. - 2+ years of engineering management or people leadership experience in a product-focused software organization. - Strong software engineering fundamentals and experience designing and building scalable production systems. - Experience with backend systems, APIs, distributed systems, cloud infrastructure, or data-intensive applications. - Strong understanding of modern software development practices, CI/CD, observability, testing, and production reliability. - Experience working closely with Product, Design, Data Science, and other cross-functional teams. - Ability to remain technically credible while operating effectively as a people and organizational leader. - Proven ability to break down ambiguous technical problems, establish priorities, and drive projects to completion. - Experience hiring, mentoring, developing, and retaining strong engineering talent. - Strong communication skills with the ability to explain complex technical concepts to both technical and non-technical stakeholders. - Comfortable operating in a fast-paced startup environment with evolving priorities and significant ownership. Bonus Points list: - Experience building AI, ML-powered enterprise products or platforms. - Experience with LLMs, generative AI, machine learning infrastructure, or AI-enabled workflows. - Background in process intelligence, observability, developer productivity, workflow automation, or enterprise SaaS. - Experience with cloud platforms such as AWS, Azure, or GCP. - Familiarity with technologies such as Python, Java, Go, TypeScript, Kubernetes, Docker, Kafka, PostgreSQL, Snowflake, Databricks, or similar modern technologies. - Experience building data-intensive or telemetry-driven systems. - Experience working with Fortune 500 customers or enterprise-scale software environments. - Strong understanding of security, scalability, performance, and reliability requirements for enterprise applications. - Technical background in Computer Science, Engineering, or a related field. - Experience in a high-growth startup environment. Why Join Skan Now list: - Real Enterprise Scale: Skan.ai already powers operational intelligence initiatives inside Fortune 500 enterprises. You’ll build software that solves meaningful problems across complex enterprise environments. - AI at the Core: Skan sits at the intersection of AI, computer vision, process intelligence, and enterprise software. You’ll work on technically challenging systems where AI creates measurable business impact. - High Ownership, High Impact: This is not simply a team-management role. You’ll influence architecture, engineering strategy, product execution, hiring, and the technical direction of a growing enterprise AI platform. - Build for the Enterprise: You’ll work on systems where scalability, reliability, security, and performance matter — and where engineering decisions directly impact large enterprise customers. - Strong Cross-Functional Exposure: You’ll collaborate closely with Product, AI, ML, Data Science, Design, Customer Success, Solutions Engineering, and enterprise customers. Location paragraph after Why Join: "Location San Francisco Bay Area, on-site. We expect regular in-office collaboration with engineering, product, and leadership teams. Occasional travel may be required for customer meetings and company events." We need to include location info somewhere. Could add a short
under About the role or after. We must not include application instructions etc. Not present. Now construct HTML. We'll start with
About the role
thencontaining company description and role overview and location? Maybe separate
for company description, then
for role overview, then
for location. But we must not create extra headings. Use
for prose. Let's do:
About the role
About Skan.ai: Skan.ai is redefining how the world’s largest enterprises understand and optimize work. Our process intelligence platform uses AI and computer vision to observe how work actually happens across systems, teams, and workflows — creating a living operational model of enterprise execution. Fortune 500 enterprises across banking, insurance, healthcare, and BPO rely on Skan to uncover operational inefficiencies, accelerate transformation, and build the foundation for enterprise-scale AI adoption.
The Role: We’re looking for an Engineering Manager to lead the development and delivery of critical platform and product capabilities across Skan’s AI-powered enterprise platform. You will combine strong technical leadership with people management, working closely with product, design, data science, and customer-facing teams to translate complex customer and business requirements into reliable, scalable software. This role is ideal for an engineering leader who enjoys operating at the intersection of software engineering, AI, ML, distributed systems, data platforms, and enterprise SaaS.
Location: Menlo Park
- for lists,