Staff Software Development Engineer - JIT Proxy
Delinea · United States · 1 mo ago
RemoteRemoteEngineeringFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes "About Delinea" (company description) but we should not repeat job title as heading. We need sections: About the role? The posting includes "Summary" describing role. Also "What You’ll Do", "What You’ll Need", "We’d Love To See", "Why work at Delinea?" (benefits). Also maybe "About Delinea" could be considered "About the role"? But instructions: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings where appropriate.
We need to include sections only when posting has real, specific content. So we can have:
- About the role: maybe the Summary paragraph.
- Responsibilities: "What You’ll Do"
- Requirements: "What You’ll Need"
- Qualifications: maybe combine with Requirements? But we can have Qualifications separate if there is distinct content: "We’d Love To See" could be Qualifications or Skills. Could treat as "Preferred Qualifications" or "Skills". Since they ask for Skills section, we could put "We’d Love To See" under Skills.
- Benefits: "Why work at Delinea?" includes benefits description.
- Pay: not specified, so omit.
- Schedule: not specified, omit.
We must not include boilerplate like EEO, etc. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out the EEO paragraph, the background check, social media review, etc. Also remove "For this Job, Delinea is not considering candidates that need any type of US work authorization now or in the future." That's a requirement? It's a restriction; maybe we can include under Requirements? It's a specific constraint. It's substantive. Should we keep? It's not boilerplate; it's a specific eligibility requirement. So we can include under Requirements.
Also remove "Learn more about Delinea on Delinea.com, LinkedIn, X, and YouTube." That's maybe part of About Delinea but could be considered boilerplate? It's promotional but maybe keep as part of About Delinea? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This line is not those; it's just a link. Could keep but maybe it's not essential. However we need to preserve ALL substantive information; do not invent or summarize away detail. So we should keep it if it's substantive. It's about learning more about Delinea; maybe not essential to role but it's info about company. Could keep under About the role or a separate About Delinea section? But we only have headings list; we could include "About Delinea" as part of About the role? Might be okay.
We need to output only HTML fragment, no /, no markdown fences.
Let's extract content:
About Delinea paragraph: "Delinea is a pioneer in securing human and machine identities through intelligent, centralized authorization, empowering organizations to seamlessly govern their interactions across the modern enterprise. Leveraging AI-powered intelligence, Delinea’s leading cloud-native Identity Security Platform applies context throughout the entire identity lifecycle – across cloud and traditional infrastructure, data, SaaS applications, and AI. It is the only platform that enables you to discover all identities – including workforce, IT administrator, developers, and machines – assign appropriate access levels, detect irregularities, and respond to threats in real-time. With deployment in weeks, not months, 90% fewer resources to manage than the nearest competitor, and a 99.995% uptime, Delinea delivers robust security and operational efficiency without compromise. Learn more about Delinea on Delinea.com, LinkedIn, X, and YouTube. Join our passionate, global team at Delinea and help us make the world a safer and more secure place. Our success is driven by world-class product leadership, outstanding engineers, and strategic investment from TPG. We value diversity, innovation, and a culture of respect and fairness. If you're ready to push boundaries and challenge the status quo in security, we want to hear from you. Apply today to help us achieve our mission."
We might keep that as About Delinea but not a heading? Could be part of About the role? The instruction says use
inside
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings where appropriate.
We need to include sections only when posting has real, specific content. So we can have:
- About the role: maybe the Summary paragraph.
- Responsibilities: "What You’ll Do"
- Requirements: "What You’ll Need"
- Qualifications: maybe combine with Requirements? But we can have Qualifications separate if there is distinct content: "We’d Love To See" could be Qualifications or Skills. Could treat as "Preferred Qualifications" or "Skills". Since they ask for Skills section, we could put "We’d Love To See" under Skills.
- Benefits: "Why work at Delinea?" includes benefits description.
- Pay: not specified, so omit.
- Schedule: not specified, omit.
We must not include boilerplate like EEO, etc. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out the EEO paragraph, the background check, social media review, etc. Also remove "For this Job, Delinea is not considering candidates that need any type of US work authorization now or in the future." That's a requirement? It's a restriction; maybe we can include under Requirements? It's a specific constraint. It's substantive. Should we keep? It's not boilerplate; it's a specific eligibility requirement. So we can include under Requirements.
Also remove "Learn more about Delinea on Delinea.com, LinkedIn, X, and YouTube." That's maybe part of About Delinea but could be considered boilerplate? It's promotional but maybe keep as part of About Delinea? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This line is not those; it's just a link. Could keep but maybe it's not essential. However we need to preserve ALL substantive information; do not invent or summarize away detail. So we should keep it if it's substantive. It's about learning more about Delinea; maybe not essential to role but it's info about company. Could keep under About the role or a separate About Delinea section? But we only have headings list; we could include "About Delinea" as part of About the role? Might be okay.
We need to output only HTML fragment, no /, no markdown fences.
Let's extract content:
About Delinea paragraph: "Delinea is a pioneer in securing human and machine identities through intelligent, centralized authorization, empowering organizations to seamlessly govern their interactions across the modern enterprise. Leveraging AI-powered intelligence, Delinea’s leading cloud-native Identity Security Platform applies context throughout the entire identity lifecycle – across cloud and traditional infrastructure, data, SaaS applications, and AI. It is the only platform that enables you to discover all identities – including workforce, IT administrator, developers, and machines – assign appropriate access levels, detect irregularities, and respond to threats in real-time. With deployment in weeks, not months, 90% fewer resources to manage than the nearest competitor, and a 99.995% uptime, Delinea delivers robust security and operational efficiency without compromise. Learn more about Delinea on Delinea.com, LinkedIn, X, and YouTube. Join our passionate, global team at Delinea and help us make the world a safer and more secure place. Our success is driven by world-class product leadership, outstanding engineers, and strategic investment from TPG. We value diversity, innovation, and a culture of respect and fairness. If you're ready to push boundaries and challenge the status quo in security, we want to hear from you. Apply today to help us achieve our mission."
We might keep that as About Delinea but not a heading? Could be part of About the role? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could have an About the role
and put the summary + maybe About Delinea? But the summary is separate: "Summary This position is on the team building StrongDM, now part of Delinea—the universal access management platform that secures and audits access to databases, servers, Kubernetes clusters, and web applications. As a Staff Software Engineer, you will apply deep expertise across distributed systems, security, and cloud architecture to help shape the technical direction of StrongDM’s proxy and control-plane platform. You will take on the platform’s most complex and ambiguous engineering challenges, exercise independent judgment on architecture and design decisions that span multiple teams, and serve as a recognized subject matter expert on secure, high-scale distributed systems written in Go. You will report to the team’s engineering manager."
That is substantive; we can put under About the role.
Thus About the role section will contain the Summary paragraph (maybe also include the About Delinea paragraph? Might be redundant but we can include both as they are both substantive. However the About Delinea paragraph is more about company; could be considered "About Delinea" but we don't have that heading. Could we add a custom heading? The 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 those for those sections. Safer to stick to those headings. So we can put About Delinea content inside About the role as well, or we could omit it if it's not directly about the role. But we must preserve ALL substantive information; we cannot omit it. So we need to include it somewhere. Perhaps we can add a About Delinea
even though not listed; but the instruction says use those for section headings (e.g. About the role...). It doesn't explicitly forbid other headings, but says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies those are the expected headings; but we could still add other headings if needed. However to be safe, we could incorporate About Delinea into About the role section, as it's still about the role context. That would preserve the info.
Thus About the role will contain two paragraphs: the Summary and the About Delinea description.
Now Responsibilities: "What You’ll Do" bullet list (actually sentences). We'll convert each sentence to
About the role
and put the summary + maybe About Delinea? But the summary is separate: "Summary This position is on the team building StrongDM, now part of Delinea—the universal access management platform that secures and audits access to databases, servers, Kubernetes clusters, and web applications. As a Staff Software Engineer, you will apply deep expertise across distributed systems, security, and cloud architecture to help shape the technical direction of StrongDM’s proxy and control-plane platform. You will take on the platform’s most complex and ambiguous engineering challenges, exercise independent judgment on architecture and design decisions that span multiple teams, and serve as a recognized subject matter expert on secure, high-scale distributed systems written in Go. You will report to the team’s engineering manager." That is substantive; we can put under About the role. Thus About the role section will contain the Summary paragraph (maybe also include the About Delinea paragraph? Might be redundant but we can include both as they are both substantive. However the About Delinea paragraph is more about company; could be considered "About Delinea" but we don't have that heading. Could we add a custom heading? The 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 those for those sections. Safer to stick to those headings. So we can put About Delinea content inside About the role as well, or we could omit it if it's not directly about the role. But we must preserve ALL substantive information; we cannot omit it. So we need to include it somewhere. Perhaps we can add a About Delinea
even though not listed; but the instruction says use those for section headings (e.g. About the role...). It doesn't explicitly forbid other headings, but says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies those are the expected headings; but we could still add other headings if needed. However to be safe, we could incorporate About Delinea into About the role section, as it's still about the role context. That would preserve the info.
Thus About the role will contain two paragraphs: the Summary and the About Delinea description.
Now Responsibilities: "What You’ll Do" bullet list (actually sentences). We'll convert each sentence to
- .
Requirements: "What You’ll Need" bullet list.
Qualifications: maybe we can treat "We’d Love To See" as Qualifications or Skills. Since we have Skills heading, we could put that under Skills. But we also have Qualifications heading; we could put the degree/experience etc under Qualifications, and the "We’d Love To See" under Skills. However the "What You’ll Need" already includes degree, experience, etc. That's both qualifications and requirements. The instruction distinguishes Requirements vs Qualifications vs Skills. But we can map: Requirements = "What You’ll Need" (mandatory). Qualifications = maybe education? But it's already there. Could combine. To avoid thin sections, we can have Requirements (mandatory) and Skills (preferred). Qualifications maybe omitted if not distinct. But we need to include a section only when posting has real, specific content for it. If we don't have distinct Qualifications content beyond Requirements, we could omit Qualifications. However we have "What You’ll Need" which includes both education and experience; that could be considered Qualifications. But we also have Requirements maybe same. To be safe, we can have:
- About the role
- Responsibilities
- Requirements (mandatory)
- Skills (preferred)
We'll omit Qualifications, Benefits? We have Benefits: "Why work at Delinea?" includes benefits description. So we will have Benefits.
Pay and Schedule omitted.
Now we need to strip boilerplate: Remove EEO paragraph, background check, social media review, etc. Also remove "For this Job, Delinea is not considering candidates that need any type of US work authorization now or in the future." That's a requirement; we should keep it under Requirements.
Also remove duplicated lines? Not seeing duplicates.
Now craft HTML.
We'll need to escape any HTML special characters? Not needed.
Structure:
- Help design the architecture and technical direction of highly concurrent, distributed backend systems in Go (Golang), setting engineering standards that extend across multiple teams within StrongDM and Delinea.
- Drive design decisions for the proxy data plane (gateways and relays) and control-plane services, evaluating tradeoffs on the platform’s most complex and ambiguous technical problems.
- Partner with architects, product managers, and DevOps/SRE leadership to shape multi-quarter system roadmaps.
- Serve as a subject matter expert on secure network protocols and cryptographic systems (TLS/mTLS, credential brokering, key management), guiding their application across the platform.
- Lead code and design reviews across teams, holding a high bar for performance, security, and maintainability, and coach engineers on applying that bar independently.
- Investigate and resolve the most challenging technical issues in distributed, multi-cloud production environments, often requiring evaluation of ambiguous or intangible tradeoffs.
- Author and maintain architectural and technical strategy documentation that informs decisions beyond your immediate team.
- Mentor engineers across the team and may direct the work of others, building the cross-team relationships that help align engineering execution with company objectives.
- Bachelor’s or Master’s degree in computer science, software engineering, or related technical discipline.
- 8+ years of professional experience working as a software engineer, with deep expertise in Go (Golang), distributed systems, and backend/network service development at scale.
- Demonstrated experience architecting highly concurrent, distributed systems and exercising independent judgment on methods, techniques, and evaluation criteria, including Go’s standard networking and cryptography libraries.
- Strong understanding of distributed systems, network protocols, and API design (gRPC/Protobuf and/or RESTful APIs), with the ability to reason about tradeoffs across an entire system.
- Experience with AWS (or another major cloud provider) and cloud-native deployment models at production scale.
- Strong problem-solving and analytical skills, with the ability to convey advanced technical concepts and persuade diverse stakeholders and audiences.
- Proven ability to build formal working relationships and coordinate across multiple teams and functions.
- Conceptual thinking skills sufficient to understand advanced technical issues and their broader implications for the business.
- Demonstrated track record mentoring engineers and being recognized as a subject matter expert others turn to for guidance.
- For this Job, Delinea is not considering candidates that need any type of US work authorization now or in the future. This includes, but is not limited to: F1-OPT, F1-CPT, H-1B, TN, L-1, J1, etc.
- Experience with cloud platforms (AWS, Azure
About the role
Summary paragraph...
About Delinea paragraph...