Senior Platform Engineer
for each heading. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Include a section only when posting has real, specific content for it—never emit heading with filler placeholder. Prefer few substantive sections over many thin ones.
We need to parse the posting.
Content:
- About the Company (description). Should we include as a section? The headings list includes "About the role" not "About the Company". The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings. The posting includes "About the Company" and "The Department: Platform" and "The Role: Senior Platform Engineer". We could treat "About the role" as the description of the role (maybe combine About the Company and Department and The Role). But we must not invent sections; we need to include a section only when posting has real, specific content for it. So we need to decide which headings have content.
We have:
- About the role: we have description of role: "The Role: Senior Platform Engineer You will design, build, and operate the software and infrastructure that form Gemini’s internal engineering platform..." etc. That is substantive.
- Responsibilities: list of responsibilities bullet points.
- Requirements: maybe Qualifications? The posting has "Qualifications:" section with many bullet points. Also there is "It Pays to Work Here" with compensation and benefits. Also "Salary Range". Also work arrangement.
Thus we can have sections:
- About the role (maybe combine About the Company, Department, and The Role). But the instruction says "About the role" heading. We'll put prose describing the role (including company context). Ensure we don't repeat job title as heading.
- Responsibilities: list.
- Qualifications: list (maybe also Requirements). The posting has "Qualifications:" as a heading; we can map that to Qualifications section. Could also have Requirements but we can skip if not distinct.
- Benefits: The posting includes "The compensation & benefits package for this role includes:" then list: Competitive starting pay, discretionary annual bonus, long-term incentive equity grant, comprehensive health plans, 401K with company matching, Paid Parental Leave, Flexible time off. Also Salary Range: $140k-$200k base salary in NY. Also hybrid work approach. So we can have Benefits section (list) and Pay section (salary range). Schedule: maybe work schedule/hybrid info. Could be Schedule section.
We must not create sections with filler like "commensurate with experience". We have actual content.
We must not include boilerplate like EEO statement, equal opportunity, accommodation request, etc. Remove those lines.
Also remove duplicated lines, navigation, cookie, legal, scam-warning, application instructions. The posting didn't have explicit application instructions but there is "If you have a specific need that requires accommodation, please let a member of the People Team know." That's accommodation request; we should remove as it's part of EEO boilerplate. Also the EEO statement lines: "At Gemini, we strive to build diverse teams..." etc. Remove.
Also remove "The compensation & benefits package for this role includes:" maybe we keep as intro to Benefits section but not as heading. We'll put a
before the list.
We need to output only HTML fragment, no /, no markdown fences.
Thus final HTML:
About the role
Gemini is a global crypto and Web3 platform founded by Cameron and Tyler Winklevoss in 2014, offering a wide range of simple, reliable, and secure crypto products and services to individuals and institutions in over 70 countries. Our mission is to unlock the next era of financial, creative, and personal freedom by providing trusted access to the decentralized future. We envision a world where crypto reshapes the global financial system, internet, and money to create greater choice, independence, and opportunity for all — bridging traditional finance with the emerging cryptoeconomy in a way that is more open, fair, and secure. As a publicly traded company, Gemini is poised to accelerate this vision with greater scale, reach, and impact. The Platform organization’s purpose is to enable Gemini to scale effectively and empower our engineering teams to focus on building innovative financial products and experiences for individuals around the world. Platform focuses on building a scalable and secure foundations platform, enabling Engineering to develop, deploy, validate, and operate services in production; improve resiliency; increase organizational efficiency by reducing operational toil; and improve system efficiency through architectural evolution. The Platform team builds products for engineers. We work directly with product, data, security, and infrastructure teams to understand their needs, establish safe and opinionated defaults, and provide paved paths that make the reliable choice the easy choice. We treat internal platforms as production software with users, service-level objectives, roadmaps, documentation, and feedback loops, not as collections of configuration. As a Senior Platform Engineer, you will design, build, and operate the software and infrastructure that form Gemini’s internal engineering platform. This is a software engineering role grounded in deep production and infrastructure experience. You will build self-service systems, developer tools, and automation that improve the way teams create, deploy, scale, observe, and operate services. You will partner with engineering teams to turn broad operational needs into reliable platform products. You will make infrastructure programmable, secure, observable, and resilient; use SLOs and error budgets to guide tradeoffs; and continuously replace manual operational work with well-designed software. The role spans software, systems, and infrastructure engineering, with an emphasis on durable abstractions and measurable improvements to developer velocity and production reliability. The role spans cloud platforms, networking, compute, storage, infrastructure automation, CI/CD, and the systems required to run highly available services in production.
Responsibilities
- Design, build, and maintain platform services, APIs, CLIs, controllers, and automation in languages such as Go, Python, or similar; own them through design, implementation, testing, deployment, and production operation.
- Build self-service capabilities that let engineers provision environments, deploy services, manage infrastructure, and respond to operational conditions safely without relying on manual platform intervention.
- Create and evolve paved paths for service development and delivery, including templates, libraries, deployment workflows, policy-as-code, and reusable platform primitives.
- Design and improve the cloud, compute, storage, identity, and infrastructure primitives used by engineering teams.
- Design and operate core network infrastructure — VPCs, Cloud Routing, and security controls across public clouds and regions.
- Operate and improve the compute, container, networking, and cloud foundations that support critical services and emerging workloads, including distributed and AI-enabled systems where appropriate.
- Improve the systems and workflows used to provision infrastructure, connect services, deliver changes, and recover from failures across environments.
- Define and use service-level indicators, SLOs, error budgets, and production-readiness standards to make reliability and launch decisions explicit and measurable.
- Improve observability, alerting, capacity planning, performance, and failure handling; design systems that degrade gracefully, roll out progressively, and recover automatically where safe.
- Participate in an appropriately staffed on-call rotation, lead incident response when needed, and turn incidents and recurring operational work into permanent improvements through blameless postmortems and follow-through.
- Reduce toil deliberately. Measure repetitive operational work, automate or eliminate it, and keep the team focused primarily on engineering work that improves reliability, scale, security, cost, or developer experience.
- Collaborate with product and engineering teams on architecture, productionization, and technical design; provide guidance without becoming a ticket-based operations layer.
- Establish technical direction through design documents, prototypes, testing, metrics, and iterative delivery. Make pragmatic tradeoffs while preserving clear interfaces and room for future evolution.
Qualifications
- 5+ years of professional software engineering, infrastructure engineering, SRE, or an equivalent combination of experience, including meaningful ownership of production systems.
- Strong software engineering ability in at least one language such as Go, Python, Java, Rust, or similar, with experience building maintainable services, automation, CLIs, APIs, or developer tools - not only scripts or one-off configuration.
- Demonstrated experience operating infrastructure and distributed systems in production, including diagnosing failures, managing capacity, improving performance, and designing for high availability and recovery.
- Experience designing, operating, or improving production systems across cloud infrastructure, networking, compute, storage, deployment platforms, or related infrastructure domains.
- Hands-on experience with cloud platforms such as AWS, GCP, or Azure and infrastructure as code, such as Terraform or an equivalent system.
- Experience with containers and orchestration, such as Kubernetes, EKS, GKE, Docker, or Nomad, including workload deployment, networking, security, and operational troubleshooting.
- Experience owning and managing cloud network security controls, including network firewalls, DNS filtering, and network segmentation.
- Experience designing or improving CI/CD and automated software delivery systems, including testing, deployment, progressive rollout, rollback, and change validation.
- Practical experience with observability: metrics, logs, traces, alerting, dashboards, and production health models. Familiarity with OpenTelemetry or comparable tooling is valuable.
- Working knowledge of SLOs, error budgets, incident response, blameless postmortems, and techniques for reducing operational toil.
- Experience with high-availability architectures, capacity planning, failure recovery, and the operational tradeoffs required to run critical systems at scale.
- Experience building secure-by-default systems and collaborating with security teams on identity, access control, secrets, supply-chain security, and policy enforcement.
- Experience working with configuration management tools such as Ansible, Chef, or Puppet is useful, but configuration management alone is not sufficient for this role.
- Ability to learn unfamiliar technologies and domains quickly, including the infrastructure and reliability characteristics of data-intensive, event-driven, or AI/ML workloads.
- Strong technical communication and leadership skills; able to explain tradeoffs, influence across teams, mentor others, and turn ambiguous problems into shipped systems.
Benefits
- Competitive starting pay
- Discretionary annual bonus
- Long-term incentive in the form of a new hire equity grant
- Comprehensive health plans
- 401K with company matching
- Paid Parental Leave
- Flexible time off
Pay
The base salary range for this role is between $140,000 - $200,000 in the State of New York. This range is not inclusive of our discretionary bonus or equity package.
Schedule
In the United States, we offer a hybrid work approach at our hub offices, balancing the benefits of in-person collaboration with the flexibility of remote work. Expectations may vary by location and role, so candidates are encouraged to connect with their recruiter to learn more about the specific policy for the role. Employees who do not live near one of our hubs are part of our remote workforce. All employees, however, are required to onboard in-person at one of our office locations.
We need to ensure
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Include a section only when posting has real, specific content for it—never emit heading with filler placeholder. Prefer few substantive sections over many thin ones. We need to parse the posting. Content: - About the Company (description). Should we include as a section? The headings list includes "About the role" not "About the Company". The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings. The posting includes "About the Company" and "The Department: Platform" and "The Role: Senior Platform Engineer". We could treat "About the role" as the description of the role (maybe combine About the Company and Department and The Role). But we must not invent sections; we need to include a section only when posting has real, specific content for it. So we need to decide which headings have content. We have: - About the role: we have description of role: "The Role: Senior Platform Engineer You will design, build, and operate the software and infrastructure that form Gemini’s internal engineering platform..." etc. That is substantive. - Responsibilities: list of responsibilities bullet points. - Requirements: maybe Qualifications? The posting has "Qualifications:" section with many bullet points. Also there is "It Pays to Work Here" with compensation and benefits. Also "Salary Range". Also work arrangement. Thus we can have sections: - About the role (maybe combine About the Company, Department, and The Role). But the instruction says "About the role" heading. We'll put prose describing the role (including company context). Ensure we don't repeat job title as heading. - Responsibilities: list. - Qualifications: list (maybe also Requirements). The posting has "Qualifications:" as a heading; we can map that to Qualifications section. Could also have Requirements but we can skip if not distinct. - Benefits: The posting includes "The compensation & benefits package for this role includes:" then list: Competitive starting pay, discretionary annual bonus, long-term incentive equity grant, comprehensive health plans, 401K with company matching, Paid Parental Leave, Flexible time off. Also Salary Range: $140k-$200k base salary in NY. Also hybrid work approach. So we can have Benefits section (list) and Pay section (salary range). Schedule: maybe work schedule/hybrid info. Could be Schedule section. We must not create sections with filler like "commensurate with experience". We have actual content. We must not include boilerplate like EEO statement, equal opportunity, accommodation request, etc. Remove those lines. Also remove duplicated lines, navigation, cookie, legal, scam-warning, application instructions. The posting didn't have explicit application instructions but there is "If you have a specific need that requires accommodation, please let a member of the People Team know." That's accommodation request; we should remove as it's part of EEO boilerplate. Also the EEO statement lines: "At Gemini, we strive to build diverse teams..." etc. Remove. Also remove "The compensation & benefits package for this role includes:" maybe we keep as intro to Benefits section but not as heading. We'll put a
before the list. We need to output only HTML fragment, no /, no markdown fences. Thus final HTML:
About the role
Gemini is a global crypto and Web3 platform founded by Cameron and Tyler Winklevoss in 2014, offering a wide range of simple, reliable, and secure crypto products and services to individuals and institutions in over 70 countries. Our mission is to unlock the next era of financial, creative, and personal freedom by providing trusted access to the decentralized future. We envision a world where crypto reshapes the global financial system, internet, and money to create greater choice, independence, and opportunity for all — bridging traditional finance with the emerging cryptoeconomy in a way that is more open, fair, and secure. As a publicly traded company, Gemini is poised to accelerate this vision with greater scale, reach, and impact. The Platform organization’s purpose is to enable Gemini to scale effectively and empower our engineering teams to focus on building innovative financial products and experiences for individuals around the world. Platform focuses on building a scalable and secure foundations platform, enabling Engineering to develop, deploy, validate, and operate services in production; improve resiliency; increase organizational efficiency by reducing operational toil; and improve system efficiency through architectural evolution. The Platform team builds products for engineers. We work directly with product, data, security, and infrastructure teams to understand their needs, establish safe and opinionated defaults, and provide paved paths that make the reliable choice the easy choice. We treat internal platforms as production software with users, service-level objectives, roadmaps, documentation, and feedback loops, not as collections of configuration. As a Senior Platform Engineer, you will design, build, and operate the software and infrastructure that form Gemini’s internal engineering platform. This is a software engineering role grounded in deep production and infrastructure experience. You will build self-service systems, developer tools, and automation that improve the way teams create, deploy, scale, observe, and operate services. You will partner with engineering teams to turn broad operational needs into reliable platform products. You will make infrastructure programmable, secure, observable, and resilient; use SLOs and error budgets to guide tradeoffs; and continuously replace manual operational work with well-designed software. The role spans software, systems, and infrastructure engineering, with an emphasis on durable abstractions and measurable improvements to developer velocity and production reliability. The role spans cloud platforms, networking, compute, storage, infrastructure automation, CI/CD, and the systems required to run highly available services in production.
Responsibilities
- Design, build, and maintain platform services, APIs, CLIs, controllers, and automation in languages such as Go, Python, or similar; own them through design, implementation, testing, deployment, and production operation.
- Build self-service capabilities that let engineers provision environments, deploy services, manage infrastructure, and respond to operational conditions safely without relying on manual platform intervention.
- Create and evolve paved paths for service development and delivery, including templates, libraries, deployment workflows, policy-as-code, and reusable platform primitives.
- Design and improve the cloud, compute, storage, identity, and infrastructure primitives used by engineering teams.
- Design and operate core network infrastructure — VPCs, Cloud Routing, and security controls across public clouds and regions.
- Operate and improve the compute, container, networking, and cloud foundations that support critical services and emerging workloads, including distributed and AI-enabled systems where appropriate.
- Improve the systems and workflows used to provision infrastructure, connect services, deliver changes, and recover from failures across environments.
- Define and use service-level indicators, SLOs, error budgets, and production-readiness standards to make reliability and launch decisions explicit and measurable.
- Improve observability, alerting, capacity planning, performance, and failure handling; design systems that degrade gracefully, roll out progressively, and recover automatically where safe.
- Participate in an appropriately staffed on-call rotation, lead incident response when needed, and turn incidents and recurring operational work into permanent improvements through blameless postmortems and follow-through.
- Reduce toil deliberately. Measure repetitive operational work, automate or eliminate it, and keep the team focused primarily on engineering work that improves reliability, scale, security, cost, or developer experience.
- Collaborate with product and engineering teams on architecture, productionization, and technical design; provide guidance without becoming a ticket-based operations layer.
- Establish technical direction through design documents, prototypes, testing, metrics, and iterative delivery. Make pragmatic tradeoffs while preserving clear interfaces and room for future evolution.
Qualifications
- 5+ years of professional software engineering, infrastructure engineering, SRE, or an equivalent combination of experience, including meaningful ownership of production systems.
- Strong software engineering ability in at least one language such as Go, Python, Java, Rust, or similar, with experience building maintainable services, automation, CLIs, APIs, or developer tools - not only scripts or one-off configuration.
- Demonstrated experience operating infrastructure and distributed systems in production, including diagnosing failures, managing capacity, improving performance, and designing for high availability and recovery.
- Experience designing, operating, or improving production systems across cloud infrastructure, networking, compute, storage, deployment platforms, or related infrastructure domains.
- Hands-on experience with cloud platforms such as AWS, GCP, or Azure and infrastructure as code, such as Terraform or an equivalent system.
- Experience with containers and orchestration, such as Kubernetes, EKS, GKE, Docker, or Nomad, including workload deployment, networking, security, and operational troubleshooting.
- Experience owning and managing cloud network security controls, including network firewalls, DNS filtering, and network segmentation.
- Experience designing or improving CI/CD and automated software delivery systems, including testing, deployment, progressive rollout, rollback, and change validation.
- Practical experience with observability: metrics, logs, traces, alerting, dashboards, and production health models. Familiarity with OpenTelemetry or comparable tooling is valuable.
- Working knowledge of SLOs, error budgets, incident response, blameless postmortems, and techniques for reducing operational toil.
- Experience with high-availability architectures, capacity planning, failure recovery, and the operational tradeoffs required to run critical systems at scale.
- Experience building secure-by-default systems and collaborating with security teams on identity, access control, secrets, supply-chain security, and policy enforcement.
- Experience working with configuration management tools such as Ansible, Chef, or Puppet is useful, but configuration management alone is not sufficient for this role.
- Ability to learn unfamiliar technologies and domains quickly, including the infrastructure and reliability characteristics of data-intensive, event-driven, or AI/ML workloads.
- Strong technical communication and leadership skills; able to explain tradeoffs, influence across teams, mentor others, and turn ambiguous problems into shipped systems.
Benefits
- Competitive starting pay
- Discretionary annual bonus
- Long-term incentive in the form of a new hire equity grant
- Comprehensive health plans
- 401K with company matching
- Paid Parental Leave
- Flexible time off
Pay
The base salary range for this role is between $140,000 - $200,000 in the State of New York. This range is not inclusive of our discretionary bonus or equity package.
Schedule
In the United States, we offer a hybrid work approach at our hub offices, balancing the benefits of in-person collaboration with the flexibility of remote work. Expectations may vary by location and role, so candidates are encouraged to connect with their recruiter to learn more about the specific policy for the role. Employees who do not live near one of our hubs are part of our remote workforce. All employees, however, are required to onboard in-person at one of our office locations.
We need to ensure