Senior Data Engineer - US
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we can also use other headings if they match content? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we should use those headings when appropriate. But we can also have other headings? Probably we should map sections to those headings where applicable. For example "About The Role" could be About the role
. "What You'll Do" could be Responsibilities. "What We're Looking For" could be Requirements/Qualifications/Skills. "How We Hire" maybe not needed? Could be omitted if not matching headings? But we need to preserve all substantive information; we cannot drop content. However we can embed that info under appropriate headings, maybe under a generic like "Hiring Process"? But instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use for section headings (e.g ...). Likely they expect we use those headings where relevant, and maybe we can add other headings if needed but better to stick to those. However we have info about hiring process, why teleport, benefits, compensation. Those map to Benefits, Pay, maybe Why Teleport could be part of About the role? But we need to preserve all info. We could create sections: About the role (h3), Responsibilities (h3), Requirements (h3), Benefits (h3), Pay (h3). For hiring process and why teleport maybe we can include under About the role or Why Teleport as a separate section but not in list? The instruction: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can include a section for "Why Teleport" if we treat it as a heading, but not in the prescribed list. However they said use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That could be interpreted as we should use those headings for those sections, but we can also have other headings if needed? Safer to stick to those headings and map content accordingly.
We have:
- About Teleport (company description) maybe part of About the role? Could be included under About the role as introductory paragraph.
- About The Role: we can put under About the role
with description.
- What You'll Do: Responsibilities.
- What We're Looking For: could be split into Requirements, Qualifications, Skills. We'll need to decide how to allocate. Could combine into Requirements (including qualifications and skills). But we need to avoid thin sections. Perhaps we make one Requirements
and list all bullet points.
- How We Hire: maybe we can put under a heading like "Hiring Process" but not in list. Could we omit? We must preserve substantive info. Could embed under About the role? Not ideal. Perhaps we can add a section Hiring Process
even though not in the example list; risk of violating instruction? The instruction 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. So we can use other headings as needed. So we can add Hiring Process.
- Why Teleport: maybe under Why Teleport
.
- The Benefits: Benefits
.
- Compensation Range: Pay
.
We must not include schedule as not present.
We must remove boilerplate: EEO, privacy notice, etc.
We must not repeat job title as heading.
We must not include Job ID/requisition numbers.
We must preserve all substantive info.
We need to use - for any list of duties/requirements/benefits, and
for prose.
We need to output only HTML fragment.
Let's extract content.
About Teleport paragraph: "Don't wait for the future of infrastructure. Be part of it. Teleport is the AI Infrastructure Identity Company. We're solving one of the hardest problems in security: giving every human, machine, workload, and AI agent a cryptographically secured identity, improving engineering velocity while maintaining security. We make trusted computing simple. This gives you the freedom, power, and autonomy to build and innovate with confidence. Remote-first and globally distributed, we work with companies like Nasdaq, DoorDash, and Elastic to secure infrastructure for an AI world."
About The Role paragraph: "We are looking for our first Data Engineer to build Teleport's internal data platform. You will design and own the pipelines and warehouse that turn raw data from across the company, including product usage, production costs, budgets, and sales, into data that any team can use to answer their own questions. You will work closely with teams across the company, including product, engineering, finance, and revenue, to understand their data needs and deliver reliable, well-modeled data they can depend on."
What You'll Do bullet list (looks like sentences separated by periods). We'll convert each to
- .
List:
- Design and operate a low-maintenance cloud data warehouse and transformation workflow.
- Evaluate managed connectors, source exports, and native cloud services before building custom ingestion software.
- Model data from CRM, contracts, finance, billing, product usage, and cloud infrastructure into coherent business entities and metrics.
- Establish canonical customer identity and mappings between accounts, tenants, billing entities, and other source-specific identifiers.
- Partner with Finance, Revenue, Product, and Engineering to define concepts such as ARR, adoption, infrastructure cost, and gross margin.
- Build data quality checks, reconciliation, documentation, lineage, and observable failure behavior into the system.
- Protect customer and employee information through appropriate access control, minimization, redaction, and retention practices.
- Manage warehouse performance and cost, and keep the platform understandable and operable by a small team.
- Use Python or Go for integrations that cannot be handled safely and economically by managed or warehouse-native capabilities.
What We're Looking For bullet list (many). We'll convert each to
- under Requirements.
List:
- Willingness to work collaboratively with Teleport's engineers on Data Engineering Challenge to design and build an analytics warehouse for a fictional business.
- Builder mentality; experience building a data engineering function from scratch at a growing startup is highly desirable.
- Strong SQL and dimensional or analytical data-modeling expertise.
- Experience translating ambiguous stakeholder questions into documented, testable business definitions.
- Production experience with dbt or an equivalent SQL transformation workflow.
- Experience with a cloud data warehouse such as Redshift, Snowflake, or BigQuery.
- Experience with managed ELT, APIs, object storage, incremental loading, and source schema evolution.
- Strong data-quality and reconciliation practices, including explaining how published numbers relate to their sources.
- Experience handling sensitive data, access control, and retention responsibly.
- Practical experience with Python or Go, CI/CD, infrastructure as code, and cloud operations.
- Sound judgment about build vs. buy decisions, operational simplicity, and managing scope in a startup environment.
- Intellectual curiosity and a willingness to master new technologies.
- Comfortable changing the area of focus and working directly with stakeholders across the company.
- No-ego mindset of collaboration, transparency, and seeking feedback from others.
How We Hire: paragraphs describing process. We'll convert to prose
maybe with list? It's procedural steps. Could be a list.
Steps:
- Our process is designed to be straightforward and respectful of your time. We skip performative rounds and focus on what matters: understanding how you think and what you can do.
- For this role, we use a take-home challenge that mirrors real work at Teleport — on your time, your way. You'll have support from the team throughout.
- Zoom meeting with a Teleport recruiter. You’ll learn about the company, our products, compensation philosophy, interview process, and key requirements.
- Zoom meeting with the Hiring Manager. The Hiring Manager will walk you through the data engineering challenge and answer your questions.
- Challenge collaboration. The day after your meeting with the Hiring Manager, you join a Slack channel and complete a Data Engineering Challenge using GitHub. The challenge usually takes about 2 weeks and ends with a Zoom meeting with the Hiring Manager and a member of the interview team to review your solution.
- If your challenge solution meets our bar, you'll receive an offer to join Teleport.
We can make a
- for each step.
Why Teleport: paragraphs.
- You're joining a company where the problem is real, the team is small, and your work shows up directly in the product. We're not a big company, you won't get lost in a crowd. You'll have the freedom and autonomy to do what you're great at, alongside teammates who care about doing it right and want to see you succeed. The work is collaborative, there's real room to grow, and the mission is one worth showing up for. Remote-first and globally distributed, we're genuinely passionate about what we're building.
The Benefits: bullet list.
- Extensive health coverage
- Annual expense budget
- Rest and recovery policies that maximize your ability to recharge
- Investment in your future with retirement savings plans
- Professional development opportunities
Compensation Range: "$222K - $342K". We'll put under Pay heading.
We must not include boilerplate: EEO, privacy notice, etc.
Now produce HTML.
Structure:
About the role
About Teleport paragraph + About The Role paragraph? Might combine. But we need to avoid duplication. We'll put About Teleport description as part of About the role? Actually About the role section should contain role description; we could include company overview as separate
About Teleport
but not in list. Safer to have About the role includes both company overview and role description? The instruction says "About the role" heading for section headings. We'll put company overview and role description in that section as prose.
Thus:
About the role
Don't wait for the future of infrastructure. Be part of it. Teleport is the AI Infrastructure Identity Company. We're solving one of the hardest problems in security: giving every human, machine, workload, and AI agent a cryptographically secured identity, improving engineering velocity while maintaining security. We make trusted computing simple. This gives you the freedom, power, and autonomy to build and innovate with confidence. Remote-first and globally distributed, we work with companies like Nasdaq, DoorDash, and Elastic to secure infrastructure for an AI world.
We are looking for our first Data Engineer to build Teleport's internal data platform. You will design and own the pipelines and warehouse that turn raw data from across the company, including product usage, production costs, budgets, and sales, into data that any team can use to answer their own questions. You will work closely with teams across the company, including product, engineering, finance, and revenue, to understand their data needs and deliver reliable, well-modeled data they can depend on.
Then Responsibilities:
Responsibilities
- Design and operate a low-maintenance cloud data warehouse and transformation workflow.
...
Then Requirements:
Requirements
- Willingness to
About the role
. "What You'll Do" could be Responsibilities. "What We're Looking For" could be Requirements/Qualifications/Skills. "How We Hire" maybe not needed? Could be omitted if not matching headings? But we need to preserve all substantive information; we cannot drop content. However we can embed that info under appropriate headings, maybe under a generic like "Hiring Process"? But instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use for section headings (e.g ...). Likely they expect we use those headings where relevant, and maybe we can add other headings if needed but better to stick to those. However we have info about hiring process, why teleport, benefits, compensation. Those map to Benefits, Pay, maybe Why Teleport could be part of About the role? But we need to preserve all info. We could create sections: About the role (h3), Responsibilities (h3), Requirements (h3), Benefits (h3), Pay (h3). For hiring process and why teleport maybe we can include under About the role or Why Teleport as a separate section but not in list? The instruction: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can include a section for "Why Teleport" if we treat it as a heading, but not in the prescribed list. However they said use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That could be interpreted as we should use those headings for those sections, but we can also have other headings if needed? Safer to stick to those headings and map content accordingly.
We have:
- About Teleport (company description) maybe part of About the role? Could be included under About the role as introductory paragraph.
- About The Role: we can put under About the role
with description.
- What You'll Do: Responsibilities.
- What We're Looking For: could be split into Requirements, Qualifications, Skills. We'll need to decide how to allocate. Could combine into Requirements (including qualifications and skills). But we need to avoid thin sections. Perhaps we make one Requirements
and list all bullet points.
- How We Hire: maybe we can put under a heading like "Hiring Process" but not in list. Could we omit? We must preserve substantive info. Could embed under About the role? Not ideal. Perhaps we can add a section Hiring Process
even though not in the example list; risk of violating instruction? The instruction 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. So we can use other headings as needed. So we can add Hiring Process.
- Why Teleport: maybe under Why Teleport
.
- The Benefits: Benefits
.
- Compensation Range: Pay
.
We must not include schedule as not present.
We must remove boilerplate: EEO, privacy notice, etc.
We must not repeat job title as heading.
We must not include Job ID/requisition numbers.
We must preserve all substantive info.
We need to use - for any list of duties/requirements/benefits, and
for prose.
We need to output only HTML fragment.
Let's extract content.
About Teleport paragraph: "Don't wait for the future of infrastructure. Be part of it. Teleport is the AI Infrastructure Identity Company. We're solving one of the hardest problems in security: giving every human, machine, workload, and AI agent a cryptographically secured identity, improving engineering velocity while maintaining security. We make trusted computing simple. This gives you the freedom, power, and autonomy to build and innovate with confidence. Remote-first and globally distributed, we work with companies like Nasdaq, DoorDash, and Elastic to secure infrastructure for an AI world."
About The Role paragraph: "We are looking for our first Data Engineer to build Teleport's internal data platform. You will design and own the pipelines and warehouse that turn raw data from across the company, including product usage, production costs, budgets, and sales, into data that any team can use to answer their own questions. You will work closely with teams across the company, including product, engineering, finance, and revenue, to understand their data needs and deliver reliable, well-modeled data they can depend on."
What You'll Do bullet list (looks like sentences separated by periods). We'll convert each to
- .
List:
- Design and operate a low-maintenance cloud data warehouse and transformation workflow.
- Evaluate managed connectors, source exports, and native cloud services before building custom ingestion software.
- Model data from CRM, contracts, finance, billing, product usage, and cloud infrastructure into coherent business entities and metrics.
- Establish canonical customer identity and mappings between accounts, tenants, billing entities, and other source-specific identifiers.
- Partner with Finance, Revenue, Product, and Engineering to define concepts such as ARR, adoption, infrastructure cost, and gross margin.
- Build data quality checks, reconciliation, documentation, lineage, and observable failure behavior into the system.
- Protect customer and employee information through appropriate access control, minimization, redaction, and retention practices.
- Manage warehouse performance and cost, and keep the platform understandable and operable by a small team.
- Use Python or Go for integrations that cannot be handled safely and economically by managed or warehouse-native capabilities.
What We're Looking For bullet list (many). We'll convert each to
- under Requirements.
List:
- Willingness to work collaboratively with Teleport's engineers on Data Engineering Challenge to design and build an analytics warehouse for a fictional business.
- Builder mentality; experience building a data engineering function from scratch at a growing startup is highly desirable.
- Strong SQL and dimensional or analytical data-modeling expertise.
- Experience translating ambiguous stakeholder questions into documented, testable business definitions.
- Production experience with dbt or an equivalent SQL transformation workflow.
- Experience with a cloud data warehouse such as Redshift, Snowflake, or BigQuery.
- Experience with managed ELT, APIs, object storage, incremental loading, and source schema evolution.
- Strong data-quality and reconciliation practices, including explaining how published numbers relate to their sources.
- Experience handling sensitive data, access control, and retention responsibly.
- Practical experience with Python or Go, CI/CD, infrastructure as code, and cloud operations.
- Sound judgment about build vs. buy decisions, operational simplicity, and managing scope in a startup environment.
- Intellectual curiosity and a willingness to master new technologies.
- Comfortable changing the area of focus and working directly with stakeholders across the company.
- No-ego mindset of collaboration, transparency, and seeking feedback from others.
How We Hire: paragraphs describing process. We'll convert to prose
maybe with list? It's procedural steps. Could be a list.
Steps:
- Our process is designed to be straightforward and respectful of your time. We skip performative rounds and focus on what matters: understanding how you think and what you can do.
- For this role, we use a take-home challenge that mirrors real work at Teleport — on your time, your way. You'll have support from the team throughout.
- Zoom meeting with a Teleport recruiter. You’ll learn about the company, our products, compensation philosophy, interview process, and key requirements.
- Zoom meeting with the Hiring Manager. The Hiring Manager will walk you through the data engineering challenge and answer your questions.
- Challenge collaboration. The day after your meeting with the Hiring Manager, you join a Slack channel and complete a Data Engineering Challenge using GitHub. The challenge usually takes about 2 weeks and ends with a Zoom meeting with the Hiring Manager and a member of the interview team to review your solution.
- If your challenge solution meets our bar, you'll receive an offer to join Teleport.
We can make a
- for each step.
Why Teleport: paragraphs.
- You're joining a company where the problem is real, the team is small, and your work shows up directly in the product. We're not a big company, you won't get lost in a crowd. You'll have the freedom and autonomy to do what you're great at, alongside teammates who care about doing it right and want to see you succeed. The work is collaborative, there's real room to grow, and the mission is one worth showing up for. Remote-first and globally distributed, we're genuinely passionate about what we're building.
The Benefits: bullet list.
- Extensive health coverage
- Annual expense budget
- Rest and recovery policies that maximize your ability to recharge
- Investment in your future with retirement savings plans
- Professional development opportunities
Compensation Range: "$222K - $342K". We'll put under Pay heading.
We must not include boilerplate: EEO, privacy notice, etc.
Now produce HTML.
Structure:
About the role
About Teleport paragraph + About The Role paragraph? Might combine. But we need to avoid duplication. We'll put About Teleport description as part of About the role? Actually About the role section should contain role description; we could include company overview as separate
About Teleport
but not in list. Safer to have About the role includes both company overview and role description? The instruction says "About the role" heading for section headings. We'll put company overview and role description in that section as prose.
Thus:
About the role
Don't wait for the future of infrastructure. Be part of it. Teleport is the AI Infrastructure Identity Company. We're solving one of the hardest problems in security: giving every human, machine, workload, and AI agent a cryptographically secured identity, improving engineering velocity while maintaining security. We make trusted computing simple. This gives you the freedom, power, and autonomy to build and innovate with confidence. Remote-first and globally distributed, we work with companies like Nasdaq, DoorDash, and Elastic to secure infrastructure for an AI world.
We are looking for our first Data Engineer to build Teleport's internal data platform. You will design and own the pipelines and warehouse that turn raw data from across the company, including product usage, production costs, budgets, and sales, into data that any team can use to answer their own questions. You will work closely with teams across the company, including product, engineering, finance, and revenue, to understand their data needs and deliver reliable, well-modeled data they can depend on.
Then Responsibilities:
Responsibilities
- Design and operate a low-maintenance cloud data warehouse and transformation workflow.
...
Then Requirements:
Requirements
- Willingness to
for section headings (e.g ...). Likely they expect we use those headings where relevant, and maybe we can add other headings if needed but better to stick to those. However we have info about hiring process, why teleport, benefits, compensation. Those map to Benefits, Pay, maybe Why Teleport could be part of About the role? But we need to preserve all info. We could create sections: About the role (h3), Responsibilities (h3), Requirements (h3), Benefits (h3), Pay (h3). For hiring process and why teleport maybe we can include under About the role or Why Teleport as a separate section but not in list? The instruction: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can include a section for "Why Teleport" if we treat it as a heading, but not in the prescribed list. However they said use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That could be interpreted as we should use those headings for those sections, but we can also have other headings if needed? Safer to stick to those headings and map content accordingly.
We have:
- About Teleport (company description) maybe part of About the role? Could be included under About the role as introductory paragraph.
- About The Role: we can put under About the role
with description.
- What You'll Do: Responsibilities.
- What We're Looking For: could be split into Requirements, Qualifications, Skills. We'll need to decide how to allocate. Could combine into Requirements (including qualifications and skills). But we need to avoid thin sections. Perhaps we make one Requirements
and list all bullet points.
- How We Hire: maybe we can put under a heading like "Hiring Process" but not in list. Could we omit? We must preserve substantive info. Could embed under About the role? Not ideal. Perhaps we can add a section Hiring Process
even though not in the example list; risk of violating instruction? The instruction 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. So we can use other headings as needed. So we can add Hiring Process.
- Why Teleport: maybe under Why Teleport
.
- The Benefits: Benefits
.
- Compensation Range: Pay
.
We must not include schedule as not present.
We must remove boilerplate: EEO, privacy notice, etc.
We must not repeat job title as heading.
We must not include Job ID/requisition numbers.
We must preserve all substantive info.
We need to use - for any list of duties/requirements/benefits, and
for prose.
We need to output only HTML fragment.
Let's extract content.
About Teleport paragraph: "Don't wait for the future of infrastructure. Be part of it. Teleport is the AI Infrastructure Identity Company. We're solving one of the hardest problems in security: giving every human, machine, workload, and AI agent a cryptographically secured identity, improving engineering velocity while maintaining security. We make trusted computing simple. This gives you the freedom, power, and autonomy to build and innovate with confidence. Remote-first and globally distributed, we work with companies like Nasdaq, DoorDash, and Elastic to secure infrastructure for an AI world."
About The Role paragraph: "We are looking for our first Data Engineer to build Teleport's internal data platform. You will design and own the pipelines and warehouse that turn raw data from across the company, including product usage, production costs, budgets, and sales, into data that any team can use to answer their own questions. You will work closely with teams across the company, including product, engineering, finance, and revenue, to understand their data needs and deliver reliable, well-modeled data they can depend on."
What You'll Do bullet list (looks like sentences separated by periods). We'll convert each to
- .
List:
- Design and operate a low-maintenance cloud data warehouse and transformation workflow.
- Evaluate managed connectors, source exports, and native cloud services before building custom ingestion software.
- Model data from CRM, contracts, finance, billing, product usage, and cloud infrastructure into coherent business entities and metrics.
- Establish canonical customer identity and mappings between accounts, tenants, billing entities, and other source-specific identifiers.
- Partner with Finance, Revenue, Product, and Engineering to define concepts such as ARR, adoption, infrastructure cost, and gross margin.
- Build data quality checks, reconciliation, documentation, lineage, and observable failure behavior into the system.
- Protect customer and employee information through appropriate access control, minimization, redaction, and retention practices.
- Manage warehouse performance and cost, and keep the platform understandable and operable by a small team.
- Use Python or Go for integrations that cannot be handled safely and economically by managed or warehouse-native capabilities.
What We're Looking For bullet list (many). We'll convert each to
- under Requirements.
List:
- Willingness to work collaboratively with Teleport's engineers on Data Engineering Challenge to design and build an analytics warehouse for a fictional business.
- Builder mentality; experience building a data engineering function from scratch at a growing startup is highly desirable.
- Strong SQL and dimensional or analytical data-modeling expertise.
- Experience translating ambiguous stakeholder questions into documented, testable business definitions.
- Production experience with dbt or an equivalent SQL transformation workflow.
- Experience with a cloud data warehouse such as Redshift, Snowflake, or BigQuery.
- Experience with managed ELT, APIs, object storage, incremental loading, and source schema evolution.
- Strong data-quality and reconciliation practices, including explaining how published numbers relate to their sources.
- Experience handling sensitive data, access control, and retention responsibly.
- Practical experience with Python or Go, CI/CD, infrastructure as code, and cloud operations.
- Sound judgment about build vs. buy decisions, operational simplicity, and managing scope in a startup environment.
- Intellectual curiosity and a willingness to master new technologies.
- Comfortable changing the area of focus and working directly with stakeholders across the company.
- No-ego mindset of collaboration, transparency, and seeking feedback from others.
How We Hire: paragraphs describing process. We'll convert to prose
maybe with list? It's procedural steps. Could be a list.
Steps:
- Our process is designed to be straightforward and respectful of your time. We skip performative rounds and focus on what matters: understanding how you think and what you can do.
- For this role, we use a take-home challenge that mirrors real work at Teleport — on your time, your way. You'll have support from the team throughout.
- Zoom meeting with a Teleport recruiter. You’ll learn about the company, our products, compensation philosophy, interview process, and key requirements.
- Zoom meeting with the Hiring Manager. The Hiring Manager will walk you through the data engineering challenge and answer your questions.
- Challenge collaboration. The day after your meeting with the Hiring Manager, you join a Slack channel and complete a Data Engineering Challenge using GitHub. The challenge usually takes about 2 weeks and ends with a Zoom meeting with the Hiring Manager and a member of the interview team to review your solution.
- If your challenge solution meets our bar, you'll receive an offer to join Teleport.
We can make a
- for each step.
Why Teleport: paragraphs.
- You're joining a company where the problem is real, the team is small, and your work shows up directly in the product. We're not a big company, you won't get lost in a crowd. You'll have the freedom and autonomy to do what you're great at, alongside teammates who care about doing it right and want to see you succeed. The work is collaborative, there's real room to grow, and the mission is one worth showing up for. Remote-first and globally distributed, we're genuinely passionate about what we're building.
The Benefits: bullet list.
- Extensive health coverage
- Annual expense budget
- Rest and recovery policies that maximize your ability to recharge
- Investment in your future with retirement savings plans
- Professional development opportunities
Compensation Range: "$222K - $342K". We'll put under Pay heading.
We must not include boilerplate: EEO, privacy notice, etc.
Now produce HTML.
Structure:
About the role
About Teleport paragraph + About The Role paragraph? Might combine. But we need to avoid duplication. We'll put About Teleport description as part of About the role? Actually About the role section should contain role description; we could include company overview as separate
About Teleport
but not in list. Safer to have About the role includes both company overview and role description? The instruction says "About the role" heading for section headings. We'll put company overview and role description in that section as prose.
Thus:
About the role
Don't wait for the future of infrastructure. Be part of it. Teleport is the AI Infrastructure Identity Company. We're solving one of the hardest problems in security: giving every human, machine, workload, and AI agent a cryptographically secured identity, improving engineering velocity while maintaining security. We make trusted computing simple. This gives you the freedom, power, and autonomy to build and innovate with confidence. Remote-first and globally distributed, we work with companies like Nasdaq, DoorDash, and Elastic to secure infrastructure for an AI world.
We are looking for our first Data Engineer to build Teleport's internal data platform. You will design and own the pipelines and warehouse that turn raw data from across the company, including product usage, production costs, budgets, and sales, into data that any team can use to answer their own questions. You will work closely with teams across the company, including product, engineering, finance, and revenue, to understand their data needs and deliver reliable, well-modeled data they can depend on.
Then Responsibilities:
Responsibilities
- Design and operate a low-maintenance cloud data warehouse and transformation workflow.
...
Then Requirements:
Requirements
- Willingness to
About the role
with description. - What You'll Do: Responsibilities. - What We're Looking For: could be split into Requirements, Qualifications, Skills. We'll need to decide how to allocate. Could combine into Requirements (including qualifications and skills). But we need to avoid thin sections. Perhaps we make oneRequirements
and list all bullet points. - How We Hire: maybe we can put under a heading like "Hiring Process" but not in list. Could we omit? We must preserve substantive info. Could embed under About the role? Not ideal. Perhaps we can add a sectionHiring Process
even though not in the example list; risk of violating instruction? The instruction 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. So we can use other headings as needed. So we can add Hiring Process.
- Why Teleport: maybe under Why Teleport
.
- The Benefits: Benefits
.
- Compensation Range: Pay
.
We must not include schedule as not present.
We must remove boilerplate: EEO, privacy notice, etc.
We must not repeat job title as heading.
We must not include Job ID/requisition numbers.
We must preserve all substantive info.
We need to use - for any list of duties/requirements/benefits, and
for prose.
We need to output only HTML fragment.
Let's extract content.
About Teleport paragraph: "Don't wait for the future of infrastructure. Be part of it. Teleport is the AI Infrastructure Identity Company. We're solving one of the hardest problems in security: giving every human, machine, workload, and AI agent a cryptographically secured identity, improving engineering velocity while maintaining security. We make trusted computing simple. This gives you the freedom, power, and autonomy to build and innovate with confidence. Remote-first and globally distributed, we work with companies like Nasdaq, DoorDash, and Elastic to secure infrastructure for an AI world."
About The Role paragraph: "We are looking for our first Data Engineer to build Teleport's internal data platform. You will design and own the pipelines and warehouse that turn raw data from across the company, including product usage, production costs, budgets, and sales, into data that any team can use to answer their own questions. You will work closely with teams across the company, including product, engineering, finance, and revenue, to understand their data needs and deliver reliable, well-modeled data they can depend on."
What You'll Do bullet list (looks like sentences separated by periods). We'll convert each to
- .
List:
- Design and operate a low-maintenance cloud data warehouse and transformation workflow.
- Evaluate managed connectors, source exports, and native cloud services before building custom ingestion software.
- Model data from CRM, contracts, finance, billing, product usage, and cloud infrastructure into coherent business entities and metrics.
- Establish canonical customer identity and mappings between accounts, tenants, billing entities, and other source-specific identifiers.
- Partner with Finance, Revenue, Product, and Engineering to define concepts such as ARR, adoption, infrastructure cost, and gross margin.
- Build data quality checks, reconciliation, documentation, lineage, and observable failure behavior into the system.
- Protect customer and employee information through appropriate access control, minimization, redaction, and retention practices.
- Manage warehouse performance and cost, and keep the platform understandable and operable by a small team.
- Use Python or Go for integrations that cannot be handled safely and economically by managed or warehouse-native capabilities.
What We're Looking For bullet list (many). We'll convert each to
- under Requirements.
List:
- Willingness to work collaboratively with Teleport's engineers on Data Engineering Challenge to design and build an analytics warehouse for a fictional business.
- Builder mentality; experience building a data engineering function from scratch at a growing startup is highly desirable.
- Strong SQL and dimensional or analytical data-modeling expertise.
- Experience translating ambiguous stakeholder questions into documented, testable business definitions.
- Production experience with dbt or an equivalent SQL transformation workflow.
- Experience with a cloud data warehouse such as Redshift, Snowflake, or BigQuery.
- Experience with managed ELT, APIs, object storage, incremental loading, and source schema evolution.
- Strong data-quality and reconciliation practices, including explaining how published numbers relate to their sources.
- Experience handling sensitive data, access control, and retention responsibly.
- Practical experience with Python or Go, CI/CD, infrastructure as code, and cloud operations.
- Sound judgment about build vs. buy decisions, operational simplicity, and managing scope in a startup environment.
- Intellectual curiosity and a willingness to master new technologies.
- Comfortable changing the area of focus and working directly with stakeholders across the company.
- No-ego mindset of collaboration, transparency, and seeking feedback from others.
How We Hire: paragraphs describing process. We'll convert to prose
maybe with list? It's procedural steps. Could be a list.
Steps:
- Our process is designed to be straightforward and respectful of your time. We skip performative rounds and focus on what matters: understanding how you think and what you can do.
- For this role, we use a take-home challenge that mirrors real work at Teleport — on your time, your way. You'll have support from the team throughout.
- Zoom meeting with a Teleport recruiter. You’ll learn about the company, our products, compensation philosophy, interview process, and key requirements.
- Zoom meeting with the Hiring Manager. The Hiring Manager will walk you through the data engineering challenge and answer your questions.
- Challenge collaboration. The day after your meeting with the Hiring Manager, you join a Slack channel and complete a Data Engineering Challenge using GitHub. The challenge usually takes about 2 weeks and ends with a Zoom meeting with the Hiring Manager and a member of the interview team to review your solution.
- If your challenge solution meets our bar, you'll receive an offer to join Teleport.
We can make a
- for each step.
Why Teleport: paragraphs.
- You're joining a company where the problem is real, the team is small, and your work shows up directly in the product. We're not a big company, you won't get lost in a crowd. You'll have the freedom and autonomy to do what you're great at, alongside teammates who care about doing it right and want to see you succeed. The work is collaborative, there's real room to grow, and the mission is one worth showing up for. Remote-first and globally distributed, we're genuinely passionate about what we're building.
The Benefits: bullet list.
- Extensive health coverage
- Annual expense budget
- Rest and recovery policies that maximize your ability to recharge
- Investment in your future with retirement savings plans
- Professional development opportunities
Compensation Range: "$222K - $342K". We'll put under Pay heading.
We must not include boilerplate: EEO, privacy notice, etc.
Now produce HTML.
Structure:
About the role
About Teleport paragraph + About The Role paragraph? Might combine. But we need to avoid duplication. We'll put About Teleport description as part of About the role? Actually About the role section should contain role description; we could include company overview as separate
About Teleport
but not in list. Safer to have About the role includes both company overview and role description? The instruction says "About the role" heading for section headings. We'll put company overview and role description in that section as prose.
Thus:
About the role
Don't wait for the future of infrastructure. Be part of it. Teleport is the AI Infrastructure Identity Company. We're solving one of the hardest problems in security: giving every human, machine, workload, and AI agent a cryptographically secured identity, improving engineering velocity while maintaining security. We make trusted computing simple. This gives you the freedom, power, and autonomy to build and innovate with confidence. Remote-first and globally distributed, we work with companies like Nasdaq, DoorDash, and Elastic to secure infrastructure for an AI world.
We are looking for our first Data Engineer to build Teleport's internal data platform. You will design and own the pipelines and warehouse that turn raw data from across the company, including product usage, production costs, budgets, and sales, into data that any team can use to answer their own questions. You will work closely with teams across the company, including product, engineering, finance, and revenue, to understand their data needs and deliver reliable, well-modeled data they can depend on.
Then Responsibilities:
Responsibilities
- Design and operate a low-maintenance cloud data warehouse and transformation workflow.
...
Then Requirements:
Requirements
- Willingness to
for prose. We need to output only HTML fragment. Let's extract content. About Teleport paragraph: "Don't wait for the future of infrastructure. Be part of it. Teleport is the AI Infrastructure Identity Company. We're solving one of the hardest problems in security: giving every human, machine, workload, and AI agent a cryptographically secured identity, improving engineering velocity while maintaining security. We make trusted computing simple. This gives you the freedom, power, and autonomy to build and innovate with confidence. Remote-first and globally distributed, we work with companies like Nasdaq, DoorDash, and Elastic to secure infrastructure for an AI world." About The Role paragraph: "We are looking for our first Data Engineer to build Teleport's internal data platform. You will design and own the pipelines and warehouse that turn raw data from across the company, including product usage, production costs, budgets, and sales, into data that any team can use to answer their own questions. You will work closely with teams across the company, including product, engineering, finance, and revenue, to understand their data needs and deliver reliable, well-modeled data they can depend on." What You'll Do bullet list (looks like sentences separated by periods). We'll convert each to
maybe with list? It's procedural steps. Could be a list. Steps: - Our process is designed to be straightforward and respectful of your time. We skip performative rounds and focus on what matters: understanding how you think and what you can do. - For this role, we use a take-home challenge that mirrors real work at Teleport — on your time, your way. You'll have support from the team throughout. - Zoom meeting with a Teleport recruiter. You’ll learn about the company, our products, compensation philosophy, interview process, and key requirements. - Zoom meeting with the Hiring Manager. The Hiring Manager will walk you through the data engineering challenge and answer your questions. - Challenge collaboration. The day after your meeting with the Hiring Manager, you join a Slack channel and complete a Data Engineering Challenge using GitHub. The challenge usually takes about 2 weeks and ends with a Zoom meeting with the Hiring Manager and a member of the interview team to review your solution. - If your challenge solution meets our bar, you'll receive an offer to join Teleport. We can make a
- for each step.
Why Teleport: paragraphs.
- You're joining a company where the problem is real, the team is small, and your work shows up directly in the product. We're not a big company, you won't get lost in a crowd. You'll have the freedom and autonomy to do what you're great at, alongside teammates who care about doing it right and want to see you succeed. The work is collaborative, there's real room to grow, and the mission is one worth showing up for. Remote-first and globally distributed, we're genuinely passionate about what we're building.
The Benefits: bullet list.
- Extensive health coverage
- Annual expense budget
- Rest and recovery policies that maximize your ability to recharge
- Investment in your future with retirement savings plans
- Professional development opportunities
Compensation Range: "$222K - $342K". We'll put under Pay heading.
We must not include boilerplate: EEO, privacy notice, etc.
Now produce HTML.
Structure:
About the role
About Teleport paragraph + About The Role paragraph? Might combine. But we need to avoid duplication. We'll put About Teleport description as part of About the role? Actually About the role section should contain role description; we could include company overview as separate
About Teleport
but not in list. Safer to have About the role includes both company overview and role description? The instruction says "About the role" heading for section headings. We'll put company overview and role description in that section as prose. Thus:About the role
Don't wait for the future of infrastructure. Be part of it. Teleport is the AI Infrastructure Identity Company. We're solving one of the hardest problems in security: giving every human, machine, workload, and AI agent a cryptographically secured identity, improving engineering velocity while maintaining security. We make trusted computing simple. This gives you the freedom, power, and autonomy to build and innovate with confidence. Remote-first and globally distributed, we work with companies like Nasdaq, DoorDash, and Elastic to secure infrastructure for an AI world.
We are looking for our first Data Engineer to build Teleport's internal data platform. You will design and own the pipelines and warehouse that turn raw data from across the company, including product usage, production costs, budgets, and sales, into data that any team can use to answer their own questions. You will work closely with teams across the company, including product, engineering, finance, and revenue, to understand their data needs and deliver reliable, well-modeled data they can depend on.
Then Responsibilities:Responsibilities
- Design and operate a low-maintenance cloud data warehouse and transformation workflow. ...
Requirements
- Willingness to