Full Stack Engineer
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which sections to include based on content.
We have: About the role (intro paragraph). Could be "About the role". Then Responsibilities (What you'll do). Then Requirements (Required qualifications). Then Skills? Could combine Pluses as Skills? Or we could have a separate "Preferred qualifications" but not in list. The instruction: Use headings from list; we can use "Skills" for pluses. Also "Qualifications" for required qualifications. "Responsibilities" for what you'll do.
We should not repeat job title as heading. No Job ID.
We need to preserve all substantive information, no boilerplate.
We need to use - for any list of duties/requirements/benefits, and
for prose.
We need to parse the content.
Let's extract:
Intro: "The opportunity We're looking for a mid-level to senior Full Stack Engineer to build the software that powers materials discovery, from the interfaces scientists use down to the services and data models behind them. Reporting to the Director of Digital Experience and work closely with the rest of the software engineering team, most of your time will be spent on the frontend: crafting the interfaces scientists and engineers use to navigate vast datasets, turn dense experimental results into charts and interactive graphics they can actually reason about, interact with AI agents, and monitor autonomous lab experiments, all in real time. But we want you to be able to ship a feature end to end. In practice that means adding an RPC to Cortex (our Go backend), evolving the protobuf schema that Cortex shares with every client, and updating the data model in MongoDB, without waiting in line behind a specific backend engineer. This is not a design role, but you'll collaborate closely with product managers and designers to translate research workflows into intuitive, performant interfaces."
We can put that as
under About the role.
Next "What you'll do" with subheadings Frontend, Backend and data, Across the stack.
We can treat each as
? But only allowed headings are for section headings. However we can still use for main sections and maybe use for subsections? The instruction only says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe we can use for main sections and maybe use
with bold? But better to keep structure: we can have
Responsibilities, then inside we can have Frontend etc. Not prohibited. We'll do that.
Under Frontend: list of bullet points:
- Build and maintain complex, data-rich web applications using Svelte and SvelteKit
- Implement high-fidelity UI from Figma designs with meticulous attention to detail
- Build data visualizations for scientific research and analysis
- Architect performant frontend systems that handle async data loading, real-time reactivity, and large-scale state management
- Integrate frontend experiences with AI agent capabilities (tool calls, streaming responses, etc.)
Under Backend and data:
- Extend Cortex, our Go backend, with new RPC endpoints and business logic, including server-streaming endpoints that push live lab state to the UI as experiments run
- Design and evolve the protobuf schemas that define the contract between the backend and every client, keeping changes backward-compatible as generated code lands in TypeScript, Go, and Python
- Model and update data in MongoDB: document schemas, indexes, and versioned migrations run against production data
- Own features end to end, from schema through service, API, and UI, rather than handing off at the API boundary
Under Across the stack:
- Write automated tests on both sides of the API and contribute to CI/CD pipelines
Now Required qualifications:
Core frontend expertise:
- At least 4 years of professional experience with TypeScript, HTML, and CSS (ideally Tailwind), with a solid grasp of responsive and mobile-first design
- Strong experience with modern frontend frameworks and reactive state management (Svelte/SvelteKit preferred; React or Vue acceptable if eager to learn Svelte)
- Comfortable with modern build tooling (Vite, ESBuild, Rollup), Node.js, debugging, and performant frontend architecture (async data loading, security, Sentry)
- Hands-on data visualization experience, ideally with D3 or low-level SVG/canvas graphics for custom scientific charts
Backend and data fundamentals:
- Professional experience writing server-side code in a statically typed, compiled language (Go preferred; Java, C#, Rust, or C++ acceptable) and operating in polyglot monorepos
- Experience designing and evolving API contracts (gRPC and Protocol Buffers preferred; REST or GraphQL acceptable)
- Working knowledge of databases, data modeling, index query performance, and running production data migrations (MongoDB or document stores preferred)
Communication and collaboration:
- Clear, precise communicator, especially when working across disciplines
- Comfortable operating without a hard frontend/backend boundary: you pick up whichever layer the feature needs, and you know when to pull in a specialist
- We actively use AI-assisted development and expect engineers to find their own productive workflows with these tools
Pluses:
- Rendering large datasets without dropping frames: canvas-backed charts, virtualized tables and lists, or moving compute off the main thread with Web Workers
- Familiarity with agentic systems (prompting, tool calls, MCP) or AI-frontend integration (e.g. Vercel AI SDK)
- Experience delivering real-time data to clients: server-streaming RPCs, WebSockets, SSE, or database change streams
- Testing experience: Playwright, Vitest, API mocking, linters and formatters
- Observability practice: OpenTelemetry traces, metrics, and structured logs, or an equivalent
- Advanced browser APIs such as the History API and structured concurrency in the browser
- CI/CD for build and test pipelines (we use self-hosted GitLab CI)
What we offer:
- Work closely with a team on the cutting edge of AI research
- A mission: an opportunity to fundamentally change the way humanity makes progress through materials science discovery
- Competitive salary + Equity + Benefits; base pay offered may vary depending on job-related knowledge, skills, and experience
We should not include Pay/Benefits section; but we can include a short paragraph under "What we offer" as prose.
We need to remove EEO boilerplate.
Now produce HTML fragment.
Structure:
About the role
...intro...
Responsibilities
Frontend
...
Backend and data
...
Across the stack
...
Requirements
Core frontend expertise
...
Backend and data fundamentals
...
Communication and collaboration
...
Skills
...
(for pluses)
What we offer
...
maybe.
Check that we didn't create Pay/Benefits sections.
Now ensure we preserve all substantive info. Let's copy text exactly.
Intro paragraph: We'll need to ensure we keep the content.
Let's craft:
The opportunity We're looking for a mid-level to senior Full Stack Engineer to build the software that powers materials discovery, from the interfaces scientists use down to the services and data models behind them. Reporting to the Director of Digital Experience and work closely with the rest of the software engineering team, most of your time will be spent on the frontend: crafting the interfaces scientists and engineers use to navigate vast datasets, turn dense experimental results into charts and interactive graphics they can actually reason about, interact with AI agents, and monitor autonomous lab experiments, all in real time. But we want you to be able to ship a feature end to end. In practice that means adding an RPC to Cortex (our Go backend), evolving the protobuf schema that Cortex shares with every client, and updating the data model in MongoDB, without waiting in line behind a specific backend engineer. This is not a design role, but you'll collaborate closely with product managers and designers to translate research workflows into intuitive, performant interfaces.
Note there is a missing period after "opportunity". We'll keep as is.
Now responsibilities bullets.
Frontend bullets:
- Build and maintain complex, data-rich web applications using Svelte and SvelteKit
- Implement high-fidelity UI from Figma designs with meticulous attention to detail
- Build data visualizations for scientific research and analysis
- Architect performant frontend systems that handle async data loading, real-time reactivity, and large-scale state management
- Integrate frontend experiences with AI agent capabilities (tool calls, streaming responses, etc.)
Backend and data bullets:
- Extend Cortex, our Go backend, with new RPC endpoints and business logic, including server-streaming endpoints that push live lab state to the UI as experiments run
- Design and evolve the protobuf schemas that define the contract between the backend and every client, keeping changes backward-compatible as generated code lands in TypeScript, Go, and Python
- Model and update data in MongoDB: document schemas, indexes, and versioned migrations run against production data
- Own features end to end, from schema through service, API, and UI, rather than handing off at the API boundary
Across the stack bullets:
- Write automated tests on both sides of the API and contribute to CI/CD pipelines
Now Required qualifications.
Core frontend expertise bullets:
- At least 4 years of professional experience with TypeScript, HTML, and CSS (ideally Tailwind), with a solid grasp of responsive and mobile-first design
- Strong experience with modern frontend frameworks and reactive state management (Svelte/SvelteKit preferred; React or Vue acceptable if eager to learn Svelte)
- Comfortable with modern build tooling (Vite, ESBuild, Rollup), Node.js, debugging, and performant frontend architecture (async data loading, security, Sentry)
- Hands-on data visualization experience, ideally with D3 or low-level SVG/canvas graphics for custom scientific charts
Backend and data fundamentals bullets:
- Professional experience writing server-side code in a statically typed, compiled language (Go preferred; Java, C#, Rust, or C++ acceptable) and operating in polyglot monorepos
- Experience designing and evolving API contracts (gRPC and Protocol Buffers preferred; REST or GraphQL acceptable)
- Working knowledge of databases, data modeling, index query performance, and running production data migrations (MongoDB or document stores preferred)
Communication and collaboration bullets:
- Clear, precise communicator,
for prose. We need to parse the content. Let's extract: Intro: "The opportunity We're looking for a mid-level to senior Full Stack Engineer to build the software that powers materials discovery, from the interfaces scientists use down to the services and data models behind them. Reporting to the Director of Digital Experience and work closely with the rest of the software engineering team, most of your time will be spent on the frontend: crafting the interfaces scientists and engineers use to navigate vast datasets, turn dense experimental results into charts and interactive graphics they can actually reason about, interact with AI agents, and monitor autonomous lab experiments, all in real time. But we want you to be able to ship a feature end to end. In practice that means adding an RPC to Cortex (our Go backend), evolving the protobuf schema that Cortex shares with every client, and updating the data model in MongoDB, without waiting in line behind a specific backend engineer. This is not a design role, but you'll collaborate closely with product managers and designers to translate research workflows into intuitive, performant interfaces." We can put that as
under About the role. Next "What you'll do" with subheadings Frontend, Backend and data, Across the stack. We can treat each as
? But only allowed headings are for section headings. However we can still use for main sections and maybe use for subsections? The instruction only says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe we can use for main sections and maybe use
for main sections and maybe use for subsections? The instruction only says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe we can use for main sections and maybe use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe we can use for main sections and maybe use
with bold? But better to keep structure: we can have
Responsibilities, then inside we can have Frontend etc. Not prohibited. We'll do that.
Under Frontend: list of bullet points:
- Build and maintain complex, data-rich web applications using Svelte and SvelteKit
- Implement high-fidelity UI from Figma designs with meticulous attention to detail
- Build data visualizations for scientific research and analysis
- Architect performant frontend systems that handle async data loading, real-time reactivity, and large-scale state management
- Integrate frontend experiences with AI agent capabilities (tool calls, streaming responses, etc.)
Under Backend and data:
- Extend Cortex, our Go backend, with new RPC endpoints and business logic, including server-streaming endpoints that push live lab state to the UI as experiments run
- Design and evolve the protobuf schemas that define the contract between the backend and every client, keeping changes backward-compatible as generated code lands in TypeScript, Go, and Python
- Model and update data in MongoDB: document schemas, indexes, and versioned migrations run against production data
- Own features end to end, from schema through service, API, and UI, rather than handing off at the API boundary
Under Across the stack:
- Write automated tests on both sides of the API and contribute to CI/CD pipelines
Now Required qualifications:
Core frontend expertise:
- At least 4 years of professional experience with TypeScript, HTML, and CSS (ideally Tailwind), with a solid grasp of responsive and mobile-first design
- Strong experience with modern frontend frameworks and reactive state management (Svelte/SvelteKit preferred; React or Vue acceptable if eager to learn Svelte)
- Comfortable with modern build tooling (Vite, ESBuild, Rollup), Node.js, debugging, and performant frontend architecture (async data loading, security, Sentry)
- Hands-on data visualization experience, ideally with D3 or low-level SVG/canvas graphics for custom scientific charts
Backend and data fundamentals:
- Professional experience writing server-side code in a statically typed, compiled language (Go preferred; Java, C#, Rust, or C++ acceptable) and operating in polyglot monorepos
- Experience designing and evolving API contracts (gRPC and Protocol Buffers preferred; REST or GraphQL acceptable)
- Working knowledge of databases, data modeling, index query performance, and running production data migrations (MongoDB or document stores preferred)
Communication and collaboration:
- Clear, precise communicator, especially when working across disciplines
- Comfortable operating without a hard frontend/backend boundary: you pick up whichever layer the feature needs, and you know when to pull in a specialist
- We actively use AI-assisted development and expect engineers to find their own productive workflows with these tools
Pluses:
- Rendering large datasets without dropping frames: canvas-backed charts, virtualized tables and lists, or moving compute off the main thread with Web Workers
- Familiarity with agentic systems (prompting, tool calls, MCP) or AI-frontend integration (e.g. Vercel AI SDK)
- Experience delivering real-time data to clients: server-streaming RPCs, WebSockets, SSE, or database change streams
- Testing experience: Playwright, Vitest, API mocking, linters and formatters
- Observability practice: OpenTelemetry traces, metrics, and structured logs, or an equivalent
- Advanced browser APIs such as the History API and structured concurrency in the browser
- CI/CD for build and test pipelines (we use self-hosted GitLab CI)
What we offer:
- Work closely with a team on the cutting edge of AI research
- A mission: an opportunity to fundamentally change the way humanity makes progress through materials science discovery
- Competitive salary + Equity + Benefits; base pay offered may vary depending on job-related knowledge, skills, and experience
We should not include Pay/Benefits section; but we can include a short paragraph under "What we offer" as prose.
We need to remove EEO boilerplate.
Now produce HTML fragment.
Structure:
About the role
About the role
...intro...
Responsibilities
Frontend
- ...
Backend and data
- ...
Across the stack
- ...
Requirements
Core frontend expertise
- ...
Backend and data fundamentals
- ...
Communication and collaboration
- ...
Skills
- ...
What we offer
- ...
The opportunity We're looking for a mid-level to senior Full Stack Engineer to build the software that powers materials discovery, from the interfaces scientists use down to the services and data models behind them. Reporting to the Director of Digital Experience and work closely with the rest of the software engineering team, most of your time will be spent on the frontend: crafting the interfaces scientists and engineers use to navigate vast datasets, turn dense experimental results into charts and interactive graphics they can actually reason about, interact with AI agents, and monitor autonomous lab experiments, all in real time. But we want you to be able to ship a feature end to end. In practice that means adding an RPC to Cortex (our Go backend), evolving the protobuf schema that Cortex shares with every client, and updating the data model in MongoDB, without waiting in line behind a specific backend engineer. This is not a design role, but you'll collaborate closely with product managers and designers to translate research workflows into intuitive, performant interfaces.
Note there is a missing period after "opportunity". We'll keep as is. Now responsibilities bullets. Frontend bullets: - Build and maintain complex, data-rich web applications using Svelte and SvelteKit - Implement high-fidelity UI from Figma designs with meticulous attention to detail - Build data visualizations for scientific research and analysis - Architect performant frontend systems that handle async data loading, real-time reactivity, and large-scale state management - Integrate frontend experiences with AI agent capabilities (tool calls, streaming responses, etc.) Backend and data bullets: - Extend Cortex, our Go backend, with new RPC endpoints and business logic, including server-streaming endpoints that push live lab state to the UI as experiments run - Design and evolve the protobuf schemas that define the contract between the backend and every client, keeping changes backward-compatible as generated code lands in TypeScript, Go, and Python - Model and update data in MongoDB: document schemas, indexes, and versioned migrations run against production data - Own features end to end, from schema through service, API, and UI, rather than handing off at the API boundary Across the stack bullets: - Write automated tests on both sides of the API and contribute to CI/CD pipelines Now Required qualifications. Core frontend expertise bullets: - At least 4 years of professional experience with TypeScript, HTML, and CSS (ideally Tailwind), with a solid grasp of responsive and mobile-first design - Strong experience with modern frontend frameworks and reactive state management (Svelte/SvelteKit preferred; React or Vue acceptable if eager to learn Svelte) - Comfortable with modern build tooling (Vite, ESBuild, Rollup), Node.js, debugging, and performant frontend architecture (async data loading, security, Sentry) - Hands-on data visualization experience, ideally with D3 or low-level SVG/canvas graphics for custom scientific charts Backend and data fundamentals bullets: - Professional experience writing server-side code in a statically typed, compiled language (Go preferred; Java, C#, Rust, or C++ acceptable) and operating in polyglot monorepos - Experience designing and evolving API contracts (gRPC and Protocol Buffers preferred; REST or GraphQL acceptable) - Working knowledge of databases, data modeling, index query performance, and running production data migrations (MongoDB or document stores preferred) Communication and collaboration bullets: - Clear, precise communicator,