Platform Solutions Engineer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes "About The Role" (but we should not repeat job title as heading; we can use

About The Role

maybe but they said use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include About the role heading. Then responsibilities: "What You Will Do" list. Requirements: maybe "What You Bring Required Qualifications". Qualifications: maybe "Nice to Have". Skills: maybe combine? But we need to avoid filler. We'll include sections with actual content. We need to remove boilerplate: "About Mithrl", "Our Traction Speaks For Itself", "We encourage you to apply...", etc. Also remove EEO etc. Not present. We need to preserve all substantive info. Let's extract: About the role: paragraph after "About The Role". That's the description: "We are hiring a Platform Solutions Engineer who will serve as the technical bridge between Mithrl’s platform and our customers. This role requires a rare combination of skills. You must be able to architect solutions for complex customer environments and also own DevOps responsibilities that ensure secure, scalable and reliable deployments. You will design and implement integrations, advise customers on best practices for using Mithrl within their R&D workflows, and collaborate with internal teams to ensure smooth onboarding and deployment. At the same time, you will build and maintain the cloud infrastructure, CI systems, monitoring, and automation that keep Mithrl running at scale. If you enjoy combining customer facing problem solving with deep engineering and DevOps work, this role provides a unique opportunity to shape the technical foundation of Mithrl as we grow." Responsibilities: bullet list under "What You Will Do". Each bullet is a sentence. Requirements: maybe "What You Bring Required Qualifications" list. Qualifications: maybe "Nice to Have" list. Skills: maybe combine required qualifications? But we can treat "What You Bring Required Qualifications" as Requirements, and "Nice to Have" as Qualifications. Skills maybe not separate; but we could include a Skills section if there is explicit skill list. The required qualifications include many skills; we could put them under Requirements. The nice-to-have under Qualifications. Benefits: listed under "What You Will Love At Mithrl": includes bullet points: High ownership & impact..., Team..., Culture..., Speed..., Location..., Benefits: Comprehensive PPO health coverage through Anthem (medical, dental, and vision) + 401(k) with top-tier plans. So we have Benefits content. Pay: not mentioned. Schedule: not mentioned. So we omit Pay and Schedule sections. We must not include filler like "commensurate with experience". Not present. We need to output only HTML fragment, no markdown fences. Structure:

About the role

...

Responsibilities

• ...
...

Requirements

• ...
...

Qualifications

• ...
...

Benefits

• ...
...

We need to ensure we don't repeat job title as heading. That's fine. Now extract exact sentences. About the role paragraph: copy exactly as in text. Let's copy: "We are hiring a Platform Solutions Engineer who will serve as the technical bridge between Mithrl’s platform and our customers. This role requires a rare combination of skills. You must be able to architect solutions for complex customer environments and also own DevOps responsibilities that ensure secure, scalable and reliable deployments. You will design and implement integrations, advise customers on best practices for using Mithrl within their R&D workflows, and collaborate with internal teams to ensure smooth onboarding and deployment. At the same time, you will build and maintain the cloud infrastructure, CI systems, monitoring, and automation that keep Mithrl running at scale. If you enjoy combining customer facing problem solving with deep engineering and DevOps work, this role provides a unique opportunity to shape the technical foundation of Mithrl as we grow." Now responsibilities list: each bullet from "What You Will Do". Let's extract: - Architect technical solutions for customers who integrate Mithrl into their cloud and on-prem environments - Work closely with AEs, customer success, and scientific users to understand customer workflows and design scalable deployment approaches - Build and maintain infrastructure for secure and reliable deployments in AWS, including compute environments, networking, container orchestration, and storage - Manage and improve CI pipelines, automated testing environments, and release processes - Build monitoring, logging, and alerting systems that give engineering and customer success clear visibility into system health - Implement automation for provisioning, configuration management, and environment setup - Support API integration, authentication workflows, and secure data movement between customer systems and Mithrl - Troubleshoot deployment issues and serve as the technical point of contact for complex customer setups - Work with engineering teams to ensure that platform features align with customer infrastructure needs - Contribute to documentation, architectural guidelines, and internal playbooks for deployment and integration Now requirements list: from "What You Bring Required Qualifications". Let's extract each bullet: - Strong experience in both solution architecture and DevOps or platform engineering - Deep knowledge of AWS services such as EC2, ECS, EKS, S3, IAM, Batch, Lambda, and VPC networking - Experience designing and deploying scalable, secure cloud architectures for enterprise customers - Proficiency with infrastructure as code tools such as Terraform or CloudFormation - Experience with CI systems, automated testing, and release pipelines - Strong understanding of container technologies and orchestration systems such as Docker and Kubernetes - Ability to build monitoring, logging, and alerting systems using modern tooling - Experience solving complex customer integration problems with empathy and clarity - Strong communication skills and comfort working directly with customers and internal stakeholders - Experience supporting technical products used by scientists or enterprise teams Now qualifications list: from "Nice to Have". Bullets: - Experience in tech bio, computational platforms, or scientific data environments - Familiarity with security best practices for regulated data or enterprise environments - Experience integrating API based workflows or custom data flows - Knowledge of distributed systems design or high performance compute environments - Experience writing internal tools or automation scripts for engineering teams Now benefits: from "What You Will Love At Mithrl". The bullet points include: - High ownership & impact: You will combine solution architecture, DevOps, and customer partnership in one high impact role. You will work on complex deployment challenges across leading biotechs and pharma companies - Team: Join a tight-knit, talent-dense team of engineers, scientists, and builders - Culture: We value consistency, clarity, and hard work. We solve hard problems through focused daily execution - Speed: We ship fast (2x/week) and improve continuously based on real user feedback - Location: Beautiful SF office with a high-energy, in-person culture - Benefits: Comprehensive PPO health coverage through Anthem (medical, dental, and vision) + 401(k) with top-tier plans We need Benefits section only; we can include the Benefits bullet. Could also include other bullets? They are not strictly benefits but could be considered other sections like "What You Will Love". But per instruction, we only create sections when posting has real specific content for it. The posting includes those bullets under "What You Will Love At Mithrl". They are not strictly Benefits but could be considered part of the role description. However we already have About the role and Responsibilities; we could add a section like "What You Will Love" but not in allowed headings list. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map the content to those headings. The "What You Will Love" items could go under Benefits (maybe only the benefits bullet). The other items (ownership, team, culture, speed, location) are not benefits per se but could be considered part of the role description; but we already have About the role and Responsibilities covering role description. Might be okay to omit them as they are not strictly required. However we must preserve ALL substantive information; we cannot omit details like ownership, team, culture, speed, location. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to include that info somewhere. Since we don't have a heading for "What You Will Love", we could incorporate those points into the About the role paragraph or maybe under Responsibilities? But they are not responsibilities. Could add a separate section like "What You Will Love" but not allowed headings. However the instruction says: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but does not forbid other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. But we need to preserve all substantive info; we could embed those points into the About the role paragraph as additional sentences. That would preserve them without adding new headings. Let's do that: extend About the role paragraph to include those points. Thus About the role paragraph will be longer, containing the original description plus the "What You Will Love" points. We must ensure not to repeat job title as heading; fine. Now Benefits section: only the benefits bullet. Now we need to ensure we don't include any filler like "commensurate with experience". Not present. Now produce HTML. Let's craft final HTML:

About the role

We are hiring a Platform Solutions Engineer who will serve as the technical bridge between Mithrl’s platform and our customers. This role requires a rare combination of skills. You must be able to architect solutions for complex customer environments and also own DevOps responsibilities that ensure secure, scalable and reliable deployments. You will design and implement integrations, advise customers on best practices for using Mithrl within their R&D workflows, and collaborate with internal teams to ensure smooth onboarding and deployment. At the same time, you will build and maintain the cloud infrastructure, CI systems, monitoring, and automation that keep Mithrl running at scale. If you enjoy combining customer facing problem solving with deep engineering and DevOps work, this role provides a unique opportunity to shape the technical foundation of Mithrl as we grow. High ownership & impact: You will combine solution architecture, DevOps, and customer partnership in one high impact role. You will work on complex deployment challenges across leading biotechs and pharma companies. Team: Join a tight-knit, talent-dense team of engineers, scientists, and builders. Culture: We value consistency, clarity, and hard work. We solve hard problems through focused daily execution. Speed: We ship fast (2x/week) and improve continuously based on real user feedback. Location: Beautiful SF office with a high-energy, in-person culture.

Responsibilities

• Architect technical solutions for customers who integrate Mithrl into their cloud and on-prem environments
• Work closely with AEs, customer success, and scientific users to understand customer workflows and design scalable deployment approaches
• Build and maintain infrastructure for secure and reliable deployments in AWS, including compute environments, networking, container orchestration, and storage
• Manage and improve CI pipelines, automated testing environments, and release processes
• Build monitoring, logging, and alerting systems that give engineering and customer success clear visibility into system health
• Implement automation for provisioning, configuration management, and environment setup
• Support API integration, authentication workflows, and secure data movement between customer systems and M