DevOps Engineer
Encord · New York, NY · 3 wk ago
On-siteEngineering$180k–$230k/yrFull-time
We need to output HTML fragment with sections: About Us? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but we can use other headings if content matches. The posting includes "About Us", "The role", "What You'll Do", "What We're Looking For", "Tech stack", "What we offer", "Compensation Range". We need to map to appropriate headings: "About Us" could be a section heading but not in list; but we can still use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but we can use other headings if content matches. The posting includes "About Us", "The role", "What You'll Do", "What We're Looking For", "Tech stack", "What we offer", "Compensation Range". We need to map to appropriate headings: "About Us" could be a section heading but not in list; but we can still use for any section heading. They said use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It seems they expect those typical headings, but we can also use others if appropriate. However they said "include a section ONLY when the posting has real, specific content for it". So we need sections for content we have.
We have:
- About Us (company description)
- The role (overview)
- What You'll Do (responsibilities)
- What We're Looking For (requirements/qualifications)
- Tech stack (maybe Skills)
- What we offer (benefits)
- Compensation Range (Pay)
We should not repeat job title as heading. No Job ID.
We need to use - for any list of duties/requirements/benefits, and
for prose.
We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate etc.
We need to output only HTML fragment, no /, no markdown fences.
Let's extract content.
About Us paragraph: "Encord is the universal data layer for AI that helps 300+ AI teams train and run models on the right data. Our platform indexes, curates, annotates, and evaluates data across the full AI lifecycle, from development through production. Trusted by Woven by Toyota, AXA, UiPath, Zipline, and more. We're an ambitious team of 100+ working at the frontier of AI and have raised $60M in Series C funding from Wellington Management, CRV, Next47 and Y Combinator."
That's prose.
The role: "We're looking for a DevOps Engineer with 4+ years of experience to join our growing platform engineering team in New York. You'll be embedded in the teams building and operating Encord's core infrastructure, ensuring our platform is performant, reliable, observable, and scalable. You'll drive a culture of automation, performance, and resilience through individual contributions and collaboration with multiple squads."
That's prose.
What You'll Do: list of bullet points under headings CI/CD & Deployment, Infrastructure & Cloud, Automation & Tooling, Performance & Capacity, Reliability & Availability, Observability. Each has description.
We need to output as
- for any list of duties/requirements/benefits. So we can make a
with each duty as - . Inside each
- we can have the heading maybe as or just text. But we must preserve content. Could format like:
- CI/CD & Deployment - Own and continuously improve deployment pipelines; partner closely with developers to review infrastructure changes, streamline release processes, and champion DevOps best practices across the engineering group.
Similarly for others.
What We're Looking For: list of requirements. We'll make a with each bullet.
Tech stack: maybe a of items: Backend: Python, Frontend: TypeScript and React, Deployment: Kubernetes, Infrastructure: GCP, Machine learning: PyTorch, CUDA, Ray. Also note "We are technology agnostic..." That's prose.
What we offer: list of benefits: Competitive salary and equity in a hyper growth startup. Real opportunities to grow. We’re growing insanely fast and you’ll have all the opportunities for growth that you can handle. Strong in person culture. We're 4-5 days a week in our newly-launched office Flexible PTO to recharge. Annual learning and development budget. 18 paid vacation days + federal holidays. Lots of opportunities for travel (all around the US, to London & Europe). Bi-annual off-sites and monthly socials. Health, dental and vision insurance. Encord offers a unique opportunity to be part of a startup with a clear mission and vision. You will get to explore and build services enterprise AI use cases across many different industry verticals such as healthcare, surveillance, retail, agriculture, and many more. Our work is at the cutting edge of computer vision and deep learning, which also includes working on solving unsolved problems within those fields.
We need to separate benefits list; many are prose sentences. Could treat each sentence as - . But we need to preserve all info; we can make a
with each benefit as - . However some sentences are long and contain multiple items; but okay.
Compensation Range: "Compensation Range: $180K - $230K". That's Pay section. Should we make a
Pay
with $180K - $230K
. Or maybe just . Since they said include Pay section only if posting actually states them. It does. So we can have
Pay
$180K - $230K
.
Schedule: not mentioned, so omit.
Benefits: we have benefits list; we can make Benefits
...
.
Skills: maybe Tech stack as Skills. Could use Skills
for tech stack. Or we could have Tech Stack
. The instruction examples include Skills. So we can use Skills heading.
Requirements: we have What We're Looking For; we can use Requirements
.
Responsibilities: What You'll Do; use Responsibilities
.
About the role: maybe we combine About Us and The role into About the role? But they said About the role as example heading. We could have About the role
containing the role overview paragraph. And maybe About Us
separate? But they didn't list About Us as example; but we can still use heading. However they said use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That suggests they expect those headings; but we can also add others if needed. Safer to stick to those headings where content matches.
Thus we can have:
- About the role: combine The role overview? Actually About the role could be the description of the role (the paragraph after "The role"). We'll put that.
- Responsibilities: What You'll Do.
- Requirements: What We're Looking For.
- Skills: Tech stack.
- Benefits: What we offer.
- Pay: Compensation Range.
We might also include About Us as a separate section? Not in list; but we could incorporate into About the role? Might be okay to have About Us as a separate About Us
but not in examples; risk of being considered filler? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. implies those are examples, not exclusive. So we can add About Us.
But they also said "Prefer a few substantive sections over many thin ones." So maybe combine About Us and About the role into one About the role section? But About Us is company description, not role. Could be separate.
I'll include About Us as its own section.
Now we need to ensure we don't include boilerplate like "EEO", etc. Not present.
Now craft HTML.
We'll start with About Us
...
Then About the role
...
Then Responsibilities
- ...
...
Then Requirements
...
Then Skills
...
(Tech stack)
Then Benefits
...
Then Pay
$180K - $230K
Make sure to preserve all details.
Let's extract exact sentences.
About Us: "Encord is the universal data layer for AI that helps 300+ AI teams train and run models on the right data. Our platform indexes, curates, annotates, and evaluates data across the full AI lifecycle, from development through production. Trusted by Woven by Toyota, AXA, UiPath, Zipline, and more. We're an ambitious team of 100+ working at the frontier of AI and have raised $60M in Series C funding from Wellington Management, CRV, Next47 and Y Combinator."
About the role: "We're looking for a DevOps Engineer with 4+ years of experience to join our growing platform engineering team in New York. You'll be embedded in the teams building and operating Encord's core infrastructure, ensuring our platform is performant, reliable, observable, and scalable. You'll drive a culture of automation, performance, and resilience through individual contributions and collaboration with multiple squads."
Responsibilities bullets:
- CI/CD & Deployment: "Own and continuously improve deployment pipelines; partner closely with developers to review infrastructure changes, streamline release processes, and champion DevOps best practices across the engineering group."
- Infrastructure & Cloud: "Design, deploy, and maintain cloud infrastructure on GCP and AWS; manage Kubernetes clusters, networking, and storage at petabyte scale, with infrastructure-as-code as the default."
- Automation & Tooling: "Drive developer productivity by building, guiding, and reviewing automation and internal tooling efforts across the engineering group; eliminate manual toil wherever it exists."
- Performance & Capacity: "Profile and optimise services handling large-scale data pipelines; perform capacity planning for storage and compute-intensive workloads. Work with squads to establish performance benchmarks and expectations."
- Reliability & Availability: "Define and own SLIs/SLOs/SLAs for critical services; build alerting, runbooks, and incident response processes; lead postmortems with a blameless culture."
- Observability: "Instrument services with distributed tracing, logging, and metrics (Prometheus, Grafana, OpenTelemetry, GCP Dashboards or similar); build infrastructure, define best practices, and work with each squad to ensure every service is observable before it goes to production."
Requirements bullets:
- "4+ years of hands-on DevOps, platform engineering, or SRE experience in a production environment."
- "Strong experience building and maintaining CI/CD pipelines and deployment automation at scale."
- "Proven experience with infrastructure-as-code tools (e.g., Terraform, Pulumi) and configuration management."
- "Strong fundamentals in designing, building, and maintaining resilient distributed and/or high performance systems."
- "Hands-on experience with Kubernetes and containerised workloads in cloud environments (GCP and/or AWS)."
- "Solid understanding of networking, operating systems, and database technologies."
- "Experience with observability fundamentals metrics, logs, traces, and alerting."
Skills (Tech stack):
- "Backend: Python"
- "Frontend: TypeScript and React"
- "Deployment: Kubernetes"
- "Infrastructure: GCP"
- "Machine learning: PyTorch, CUDA, Ray"
Also note: "We are technology agnostic at Encord and not looking for experience across all of these — as long as you're open to learning, please apply." That's prose; we can include as after the list.
Benefits bullets: need to break each sentence.
List:
- "
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It seems they expect those typical headings, but we can also use others if appropriate. However they said "include a section ONLY when the posting has real, specific content for it". So we need sections for content we have.
We have:
- About Us (company description)
- The role (overview)
- What You'll Do (responsibilities)
- What We're Looking For (requirements/qualifications)
- Tech stack (maybe Skills)
- What we offer (benefits)
- Compensation Range (Pay)
We should not repeat job title as heading. No Job ID.
We need to use - for any list of duties/requirements/benefits, and
for prose.
We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate etc.
We need to output only HTML fragment, no /, no markdown fences.
Let's extract content.
About Us paragraph: "Encord is the universal data layer for AI that helps 300+ AI teams train and run models on the right data. Our platform indexes, curates, annotates, and evaluates data across the full AI lifecycle, from development through production. Trusted by Woven by Toyota, AXA, UiPath, Zipline, and more. We're an ambitious team of 100+ working at the frontier of AI and have raised $60M in Series C funding from Wellington Management, CRV, Next47 and Y Combinator."
That's prose.
The role: "We're looking for a DevOps Engineer with 4+ years of experience to join our growing platform engineering team in New York. You'll be embedded in the teams building and operating Encord's core infrastructure, ensuring our platform is performant, reliable, observable, and scalable. You'll drive a culture of automation, performance, and resilience through individual contributions and collaboration with multiple squads."
That's prose.
What You'll Do: list of bullet points under headings CI/CD & Deployment, Infrastructure & Cloud, Automation & Tooling, Performance & Capacity, Reliability & Availability, Observability. Each has description.
We need to output as
- for any list of duties/requirements/benefits. So we can make a
with each duty as - . Inside each
- we can have the heading maybe as or just text. But we must preserve content. Could format like:
- CI/CD & Deployment - Own and continuously improve deployment pipelines; partner closely with developers to review infrastructure changes, streamline release processes, and champion DevOps best practices across the engineering group.
Similarly for others.
What We're Looking For: list of requirements. We'll make a with each bullet.
Tech stack: maybe a of items: Backend: Python, Frontend: TypeScript and React, Deployment: Kubernetes, Infrastructure: GCP, Machine learning: PyTorch, CUDA, Ray. Also note "We are technology agnostic..." That's prose.
What we offer: list of benefits: Competitive salary and equity in a hyper growth startup. Real opportunities to grow. We’re growing insanely fast and you’ll have all the opportunities for growth that you can handle. Strong in person culture. We're 4-5 days a week in our newly-launched office Flexible PTO to recharge. Annual learning and development budget. 18 paid vacation days + federal holidays. Lots of opportunities for travel (all around the US, to London & Europe). Bi-annual off-sites and monthly socials. Health, dental and vision insurance. Encord offers a unique opportunity to be part of a startup with a clear mission and vision. You will get to explore and build services enterprise AI use cases across many different industry verticals such as healthcare, surveillance, retail, agriculture, and many more. Our work is at the cutting edge of computer vision and deep learning, which also includes working on solving unsolved problems within those fields.
We need to separate benefits list; many are prose sentences. Could treat each sentence as - . But we need to preserve all info; we can make a
with each benefit as - . However some sentences are long and contain multiple items; but okay.
Compensation Range: "Compensation Range: $180K - $230K". That's Pay section. Should we make a
Pay
with $180K - $230K
. Or maybe just . Since they said include Pay section only if posting actually states them. It does. So we can have
Pay
$180K - $230K
.
Schedule: not mentioned, so omit.
Benefits: we have benefits list; we can make Benefits
...
.
Skills: maybe Tech stack as Skills. Could use Skills
for tech stack. Or we could have Tech Stack
. The instruction examples include Skills. So we can use Skills heading.
Requirements: we have What We're Looking For; we can use Requirements
.
Responsibilities: What You'll Do; use Responsibilities
.
About the role: maybe we combine About Us and The role into About the role? But they said About the role as example heading. We could have About the role
containing the role overview paragraph. And maybe About Us
separate? But they didn't list About Us as example; but we can still use heading. However they said use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That suggests they expect those headings; but we can also add others if needed. Safer to stick to those headings where content matches.
Thus we can have:
- About the role: combine The role overview? Actually About the role could be the description of the role (the paragraph after "The role"). We'll put that.
- Responsibilities: What You'll Do.
- Requirements: What We're Looking For.
- Skills: Tech stack.
- Benefits: What we offer.
- Pay: Compensation Range.
We might also include About Us as a separate section? Not in list; but we could incorporate into About the role? Might be okay to have About Us as a separate About Us
but not in examples; risk of being considered filler? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. implies those are examples, not exclusive. So we can add About Us.
But they also said "Prefer a few substantive sections over many thin ones." So maybe combine About Us and About the role into one About the role section? But About Us is company description, not role. Could be separate.
I'll include About Us as its own section.
Now we need to ensure we don't include boilerplate like "EEO", etc. Not present.
Now craft HTML.
We'll start with About Us
...
Then About the role
...
Then Responsibilities
- ...
...
Then Requirements
...
Then Skills
...
(Tech stack)
Then Benefits
...
Then Pay
$180K - $230K
Make sure to preserve all details.
Let's extract exact sentences.
About Us: "Encord is the universal data layer for AI that helps 300+ AI teams train and run models on the right data. Our platform indexes, curates, annotates, and evaluates data across the full AI lifecycle, from development through production. Trusted by Woven by Toyota, AXA, UiPath, Zipline, and more. We're an ambitious team of 100+ working at the frontier of AI and have raised $60M in Series C funding from Wellington Management, CRV, Next47 and Y Combinator."
About the role: "We're looking for a DevOps Engineer with 4+ years of experience to join our growing platform engineering team in New York. You'll be embedded in the teams building and operating Encord's core infrastructure, ensuring our platform is performant, reliable, observable, and scalable. You'll drive a culture of automation, performance, and resilience through individual contributions and collaboration with multiple squads."
Responsibilities bullets:
- CI/CD & Deployment: "Own and continuously improve deployment pipelines; partner closely with developers to review infrastructure changes, streamline release processes, and champion DevOps best practices across the engineering group."
- Infrastructure & Cloud: "Design, deploy, and maintain cloud infrastructure on GCP and AWS; manage Kubernetes clusters, networking, and storage at petabyte scale, with infrastructure-as-code as the default."
- Automation & Tooling: "Drive developer productivity by building, guiding, and reviewing automation and internal tooling efforts across the engineering group; eliminate manual toil wherever it exists."
- Performance & Capacity: "Profile and optimise services handling large-scale data pipelines; perform capacity planning for storage and compute-intensive workloads. Work with squads to establish performance benchmarks and expectations."
- Reliability & Availability: "Define and own SLIs/SLOs/SLAs for critical services; build alerting, runbooks, and incident response processes; lead postmortems with a blameless culture."
- Observability: "Instrument services with distributed tracing, logging, and metrics (Prometheus, Grafana, OpenTelemetry, GCP Dashboards or similar); build infrastructure, define best practices, and work with each squad to ensure every service is observable before it goes to production."
Requirements bullets:
- "4+ years of hands-on DevOps, platform engineering, or SRE experience in a production environment."
- "Strong experience building and maintaining CI/CD pipelines and deployment automation at scale."
- "Proven experience with infrastructure-as-code tools (e.g., Terraform, Pulumi) and configuration management."
- "Strong fundamentals in designing, building, and maintaining resilient distributed and/or high performance systems."
- "Hands-on experience with Kubernetes and containerised workloads in cloud environments (GCP and/or AWS)."
- "Solid understanding of networking, operating systems, and database technologies."
- "Experience with observability fundamentals metrics, logs, traces, and alerting."
Skills (Tech stack):
- "Backend: Python"
- "Frontend: TypeScript and React"
- "Deployment: Kubernetes"
- "Infrastructure: GCP"
- "Machine learning: PyTorch, CUDA, Ray"
Also note: "We are technology agnostic at Encord and not looking for experience across all of these — as long as you're open to learning, please apply." That's prose; we can include as after the list.
Benefits bullets: need to break each sentence.
List:
- "
for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate etc. We need to output only HTML fragment, no /, no markdown fences. Let's extract content. About Us paragraph: "Encord is the universal data layer for AI that helps 300+ AI teams train and run models on the right data. Our platform indexes, curates, annotates, and evaluates data across the full AI lifecycle, from development through production. Trusted by Woven by Toyota, AXA, UiPath, Zipline, and more. We're an ambitious team of 100+ working at the frontier of AI and have raised $60M in Series C funding from Wellington Management, CRV, Next47 and Y Combinator." That's prose. The role: "We're looking for a DevOps Engineer with 4+ years of experience to join our growing platform engineering team in New York. You'll be embedded in the teams building and operating Encord's core infrastructure, ensuring our platform is performant, reliable, observable, and scalable. You'll drive a culture of automation, performance, and resilience through individual contributions and collaboration with multiple squads." That's prose. What You'll Do: list of bullet points under headings CI/CD & Deployment, Infrastructure & Cloud, Automation & Tooling, Performance & Capacity, Reliability & Availability, Observability. Each has description. We need to output as
- for any list of duties/requirements/benefits. So we can make a
- with each duty as
- . Inside each
- we can have the heading maybe as or just text. But we must preserve content. Could format like:
- CI/CD & Deployment - Own and continuously improve deployment pipelines; partner closely with developers to review infrastructure changes, streamline release processes, and champion DevOps best practices across the engineering group.
Similarly for others. What We're Looking For: list of requirements. We'll make a- with each bullet.
Tech stack: maybe a
- . But we need to preserve all info; we can make a
- with each benefit as
- . However some sentences are long and contain multiple items; but okay.
Compensation Range: "Compensation Range: $180K - $230K". That's Pay section. Should we make a
Pay
with$180K - $230K
. Or maybe just. Since they said include Pay section only if posting actually states them. It does. So we can have
Pay
$180K - $230K
. Schedule: not mentioned, so omit. Benefits: we have benefits list; we can makeBenefits
- ...
Skills
for tech stack. Or we could haveTech Stack
. The instruction examples include Skills. So we can use Skills heading. Requirements: we have What We're Looking For; we can useRequirements
. Responsibilities: What You'll Do; useResponsibilities
. About the role: maybe we combine About Us and The role into About the role? But they said About the role as example heading. We could haveAbout the role
containing the role overview paragraph. And maybeAbout Us
separate? But they didn't list About Us as example; but we can still use heading. However they said usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That suggests they expect those headings; but we can also add others if needed. Safer to stick to those headings where content matches. Thus we can have: - About the role: combine The role overview? Actually About the role could be the description of the role (the paragraph after "The role"). We'll put that. - Responsibilities: What You'll Do. - Requirements: What We're Looking For. - Skills: Tech stack. - Benefits: What we offer. - Pay: Compensation Range. We might also include About Us as a separate section? Not in list; but we could incorporate into About the role? Might be okay to have About Us as a separate
About Us
but not in examples; risk of being considered filler? The instruction: "usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. implies those are examples, not exclusive. So we can add About Us. But they also said "Prefer a few substantive sections over many thin ones." So maybe combine About Us and About the role into one About the role section? But About Us is company description, not role. Could be separate. I'll include About Us as its own section. Now we need to ensure we don't include boilerplate like "EEO", etc. Not present. Now craft HTML. We'll start with
About Us
...
ThenAbout the role
...
ThenResponsibilities
- ... ...
Requirements
- ...
Skills
- ...
Benefits
- ...
Pay
$180K - $230K
Make sure to preserve all details. Let's extract exact sentences. About Us: "Encord is the universal data layer for AI that helps 300+ AI teams train and run models on the right data. Our platform indexes, curates, annotates, and evaluates data across the full AI lifecycle, from development through production. Trusted by Woven by Toyota, AXA, UiPath, Zipline, and more. We're an ambitious team of 100+ working at the frontier of AI and have raised $60M in Series C funding from Wellington Management, CRV, Next47 and Y Combinator." About the role: "We're looking for a DevOps Engineer with 4+ years of experience to join our growing platform engineering team in New York. You'll be embedded in the teams building and operating Encord's core infrastructure, ensuring our platform is performant, reliable, observable, and scalable. You'll drive a culture of automation, performance, and resilience through individual contributions and collaboration with multiple squads." Responsibilities bullets: - CI/CD & Deployment: "Own and continuously improve deployment pipelines; partner closely with developers to review infrastructure changes, streamline release processes, and champion DevOps best practices across the engineering group." - Infrastructure & Cloud: "Design, deploy, and maintain cloud infrastructure on GCP and AWS; manage Kubernetes clusters, networking, and storage at petabyte scale, with infrastructure-as-code as the default." - Automation & Tooling: "Drive developer productivity by building, guiding, and reviewing automation and internal tooling efforts across the engineering group; eliminate manual toil wherever it exists." - Performance & Capacity: "Profile and optimise services handling large-scale data pipelines; perform capacity planning for storage and compute-intensive workloads. Work with squads to establish performance benchmarks and expectations." - Reliability & Availability: "Define and own SLIs/SLOs/SLAs for critical services; build alerting, runbooks, and incident response processes; lead postmortems with a blameless culture." - Observability: "Instrument services with distributed tracing, logging, and metrics (Prometheus, Grafana, OpenTelemetry, GCP Dashboards or similar); build infrastructure, define best practices, and work with each squad to ensure every service is observable before it goes to production." Requirements bullets: - "4+ years of hands-on DevOps, platform engineering, or SRE experience in a production environment." - "Strong experience building and maintaining CI/CD pipelines and deployment automation at scale." - "Proven experience with infrastructure-as-code tools (e.g., Terraform, Pulumi) and configuration management." - "Strong fundamentals in designing, building, and maintaining resilient distributed and/or high performance systems." - "Hands-on experience with Kubernetes and containerised workloads in cloud environments (GCP and/or AWS)." - "Solid understanding of networking, operating systems, and database technologies." - "Experience with observability fundamentals metrics, logs, traces, and alerting." Skills (Tech stack): - "Backend: Python" - "Frontend: TypeScript and React" - "Deployment: Kubernetes" - "Infrastructure: GCP" - "Machine learning: PyTorch, CUDA, Ray" Also note: "We are technology agnostic at Encord and not looking for experience across all of these — as long as you're open to learning, please apply." That's prose; we can include asafter the list. Benefits bullets: need to break each sentence. List: - "
- . However some sentences are long and contain multiple items; but okay.
Compensation Range: "Compensation Range: $180K - $230K". That's Pay section. Should we make a
- of items: Backend: Python, Frontend: TypeScript and React, Deployment: Kubernetes, Infrastructure: GCP, Machine learning: PyTorch, CUDA, Ray. Also note "We are technology agnostic..." That's prose.
What we offer: list of benefits: Competitive salary and equity in a hyper growth startup. Real opportunities to grow. We’re growing insanely fast and you’ll have all the opportunities for growth that you can handle. Strong in person culture. We're 4-5 days a week in our newly-launched office Flexible PTO to recharge. Annual learning and development budget. 18 paid vacation days + federal holidays. Lots of opportunities for travel (all around the US, to London & Europe). Bi-annual off-sites and monthly socials. Health, dental and vision insurance. Encord offers a unique opportunity to be part of a startup with a clear mission and vision. You will get to explore and build services enterprise AI use cases across many different industry verticals such as healthcare, surveillance, retail, agriculture, and many more. Our work is at the cutting edge of computer vision and deep learning, which also includes working on solving unsolved problems within those fields.
We need to separate benefits list; many are prose sentences. Could treat each sentence as