Senior Software Engineer, Identity & Access Management (FedRamp)
MongoDB · New York, NY · 1 mo ago
Engineering$126k–$248k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (or Candidate Profile), Qualifications? The posting includes sections: About the team, Role Responsibilities, Candidate Profile, Success Measures, About MongoDB, Benefits (salary range). We need to follow rules: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should only include sections when posting has real specific content. We should not repeat job title as heading. No Job ID. Remove boilerplate: EEO, accommodations, etc. Also remove navigation/legal etc. Also remove duplicated lines. Keep all substantive info.
We need to decide which sections to include.
We have content:
- About the role: description of team, mission, FedRAMP requirement, remote US based. That's substantive.
- Responsibilities: list bullet points.
- Candidate Profile: list of experience, skills, etc.
- Success Measures: timeline bullet points.
- About MongoDB: company description.
- Benefits: salary range and list of benefits.
We could map:
- About the role ->
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should only include sections when posting has real specific content. We should not repeat job title as heading. No Job ID. Remove boilerplate: EEO, accommodations, etc. Also remove navigation/legal etc. Also remove duplicated lines. Keep all substantive info.
We need to decide which sections to include.
We have content:
- About the role: description of team, mission, FedRAMP requirement, remote US based. That's substantive.
- Responsibilities: list bullet points.
- Candidate Profile: list of experience, skills, etc.
- Success Measures: timeline bullet points.
- About MongoDB: company description.
- Benefits: salary range and list of benefits.
We could map:
- About the role -> About the role
with paragraph(s).
- Responsibilities -> Responsibilities
with - ...
- Requirements -> maybe combine Candidate Profile and Success Measures? But we have separate headings: Requirements, Qualifications, Skills. The posting includes Candidate Profile (experience, skills). Could treat as Requirements. Also Success Measures could be under Qualifications? But Success Measures are about expectations, not qualifications. Could include as a separate section like "Expectations" but not in allowed headings. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose to include Requirements and Qualifications and Skills if we have content. We have Candidate Profile content that includes experience, skills, etc. Could split into Requirements (experience) and Skills (technical). But we must not create sections with filler. Better to combine into Requirements (includes experience and skills) and maybe Qualifications (education? none). Since no explicit qualifications like degree, we could omit Qualifications.
We also have Benefits and Pay: salary range is Pay. Benefits list.
Thus sections:
- About the role
- Responsibilities
- Requirements (covers Candidate Profile)
- Pay (salary range)
- Benefits (list of benefits)
We could also include Success Measures as part of Requirements or maybe as a separate section like "Expectations" but not allowed. Could incorporate into Requirements as a bullet? Might be okay to add a subsection under Requirements? But we must follow allowed headings only. Could we add a
Success Measures
? Not in list but maybe allowed? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exhaustive? It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect those headings. Safer to stick to those.
Thus we can put Success Measures under Requirements as a bullet or paragraph.
Now we need to remove boilerplate: EEO, accommodation request, etc. Also remove "REQ ID: 3273523125". Also remove "Learn more about what it’s like to work at MongoDB, and help us make an impact on the world!" maybe considered boilerplate? It's promotional but substantive? Might be considered fluff but still about company. Could keep as part of About MongoDB? Already have About MongoDB paragraph. The sentence "Learn more about what it’s like to work at MongoDB, and help us make an impact on the world!" is generic; could drop.
Also remove "MongoDB is committed to providing any necessary accommodations..." etc.
Also remove "Our compass at MongoDB is our Leadership Commitment..." maybe keep as part of About MongoDB? It's somewhat fluff but still about culture. Might keep.
We need to preserve ALL substantive information; do not invent or summarize away detail. So we must keep details like FedRAMP requirement, remote US, responsibilities list, candidate profile details, success measures, salary range, benefits list.
Now craft HTML.
We'll start with About the role
then paragraphs.
Content: "The MongoDB Atlas team is a diverse group of contributors working together to help our users manage MongoDB at global scale. We are responsible for MongoDB Atlas: our database as a service offering and fastest growing product which allows users to deploy fault-tolerant, globally distributed MongoDB clusters in just minutes. We're seeking a Senior Engineer to join the Atlas Identity and Access Management (IAM) team. IAM is a platform and a product team. We serve internal engineers by providing them a secure and durable suite of services, and we serve external customers by providing them user facing features and products. We are the owners of Atlas’ authentication (OAuth, SSO, Federated Identity) and authorization (RBAC, ABAC) systems, along with many others. The IAM team’s mission is to enable customers to securely build their applications with Atlas through our best in class user experience. The Federal Risk and Authorization Management Program (FedRAMP) is a US government-wide program that provides a standardized approach to security assessment, authorization, and continuous monitoring for cloud products and services. Our FedRAMP program requires that anyone who is accessing customer data or metadata inside the Authorization Boundary be a US Citizen on US Soil. This role will be based remotely in the United States."
We can split into two paragraphs maybe.
Next Responsibilities: list bullet points:
- Design, architect, build, and deliver core pieces of IAM
- Lead projects from specification to delivery
- Mentor and grow other team members
- Improve our codebase, best practices, and design principles
- Define your top priorities and focuses, communicate them, and execute against them
- Lead and contribute to complex technical projects and initiatives
Next Requirements (Candidate Profile + Success Measures). We'll combine.
Candidate Profile bullets:
- 5+ years experience of software engineering, primarily focused on backend systems
- Proficient in a modern compiled programming language (Java, Go, C#, C++, etc.)
- Willingness to learn JavaScript and/or TypeScript along with modern frontend technologies (React, Redux, etc.); prior experience a plus
- Excellent communication skills, both written and verbal
- Desire to collaborate with colleagues and mentor fellow engineers
- Is curious, collaborative, empathetic, and intellectually honest
- Has a passion for problem solving and learning new things in the domains of computer science and software engineering
- Experience building identity and access management systems such as authentication (OAuth, SSO), authorization (RBAC, ABAC, ReBAC), and login and registration systems a plus
Success Measures bullets:
- In 1 week you'll have completed your first pull request
- In 3 months, you'll have contributed to a large project
- In 6 months, you’ll be leading the design and execution of your own project
We could put these as sub-bullets under Requirements or separate but still under same heading.
Next Pay: salary range: "$126,000—$248,000 USD". Could phrase as "MongoDB’s base salary range for this role in the U.S. is: $126,000—$248,000 USD". We'll put in .
Next Benefits: list of benefits:
- equity
- participation in the employee stock purchase program
- flexible paid time off
- 20 weeks fully-paid gender-neutral parental leave
- fertility and adoption assistance
- 401(k) plan
- mental health counseling
- access to transgender-inclusive health insurance coverage
- health benefits offerings
We could also mention "Other benefits for eligible employees may include:" but we can just list.
Now ensure we don't include any boilerplate like EEO, accommodations, etc.
Now produce HTML fragment.
We must not include or . Just the fragment.
Let's craft:
About the role
The MongoDB Atlas team is a diverse group of contributors working together to help our users manage MongoDB at global scale. We are responsible for MongoDB Atlas: our database as a service offering and fastest growing product which allows users to deploy fault-tolerant, globally distributed MongoDB clusters in just minutes. We're seeking a Senior Engineer to join the Atlas Identity and Access Management (IAM) team. IAM is a platform and a product team. We serve internal engineers by providing them a secure and durable suite of services, and we serve external customers by providing them user facing features and products. We are the owners of Atlas’ authentication (OAuth, SSO, Federated Identity) and authorization (RBAC, ABAC) systems, along with many others. The IAM team’s mission is to enable customers to securely build their applications with Atlas through our best in class user experience. The Federal Risk and Authorization Management Program (FedRAMP) is a US government-wide program that provides a standardized approach to security assessment, authorization, and continuous monitoring for cloud products and services. Our FedRAMP program requires that anyone who is accessing customer data or metadata inside the Authorization Boundary be a US Citizen on US Soil. This role will be based remotely in the United States.
Responsibilities
- Design, architect, build, and deliver core pieces of IAM
- Lead projects from specification to delivery
- Mentor and grow other team members
- Improve our codebase, best practices, and design principles
- Define your top priorities and focuses, communicate them, and execute against them
- Lead and contribute to complex technical projects and initiatives
Requirements
- 5+ years experience of software engineering, primarily focused on backend systems
- Proficient in a modern compiled programming language (Java, Go, C#, C++, etc.)
- Willingness to learn JavaScript and/or TypeScript along with modern frontend technologies (React, Redux, etc.); prior experience a plus
- Excellent communication skills, both written and verbal
- Desire to collaborate with colleagues and mentor fellow engineers
- Is curious, collaborative, empathetic, and intellectually honest
- Has a passion for problem solving and learning new things in the domains of computer science and software engineering
- Experience building identity and access management systems such as authentication (OAuth, SSO), authorization (RBAC, ABAC, ReBAC), and login and registration systems a plus
- Success measures:
- In 1 week you'll have completed your first pull request
- In 3 months, you'll have contributed to a large project
- In 6 months, you’ll be leading the design and execution of your own project
But nesting inside - is not valid HTML unless we close the outer li before inner ul? Actually you can have
- containing a
. It's allowed: - Success measures:
...
. That's fine.
But we need to close tags properly.
Alternatively we could make Success measures as a separate but not allowed. We'll keep as nested.
Now Pay:
Pay
MongoDB’s base salary range for this role in the U.S. is: $126,000—$248,000 USD
Benefits:
Benefits
- equity
- participation in the employee stock purchase program
- flexible paid time off
- 20 weeks fully
Success Measures
? Not in list but maybe allowed? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exhaustive? It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect those headings. Safer to stick to those.
Thus we can put Success Measures under Requirements as a bullet or paragraph.
Now we need to remove boilerplate: EEO, accommodation request, etc. Also remove "REQ ID: 3273523125". Also remove "Learn more about what it’s like to work at MongoDB, and help us make an impact on the world!" maybe considered boilerplate? It's promotional but substantive? Might be considered fluff but still about company. Could keep as part of About MongoDB? Already have About MongoDB paragraph. The sentence "Learn more about what it’s like to work at MongoDB, and help us make an impact on the world!" is generic; could drop.
Also remove "MongoDB is committed to providing any necessary accommodations..." etc.
Also remove "Our compass at MongoDB is our Leadership Commitment..." maybe keep as part of About MongoDB? It's somewhat fluff but still about culture. Might keep.
We need to preserve ALL substantive information; do not invent or summarize away detail. So we must keep details like FedRAMP requirement, remote US, responsibilities list, candidate profile details, success measures, salary range, benefits list.
Now craft HTML.
We'll start with About the role
then paragraphs.
Content: "The MongoDB Atlas team is a diverse group of contributors working together to help our users manage MongoDB at global scale. We are responsible for MongoDB Atlas: our database as a service offering and fastest growing product which allows users to deploy fault-tolerant, globally distributed MongoDB clusters in just minutes. We're seeking a Senior Engineer to join the Atlas Identity and Access Management (IAM) team. IAM is a platform and a product team. We serve internal engineers by providing them a secure and durable suite of services, and we serve external customers by providing them user facing features and products. We are the owners of Atlas’ authentication (OAuth, SSO, Federated Identity) and authorization (RBAC, ABAC) systems, along with many others. The IAM team’s mission is to enable customers to securely build their applications with Atlas through our best in class user experience. The Federal Risk and Authorization Management Program (FedRAMP) is a US government-wide program that provides a standardized approach to security assessment, authorization, and continuous monitoring for cloud products and services. Our FedRAMP program requires that anyone who is accessing customer data or metadata inside the Authorization Boundary be a US Citizen on US Soil. This role will be based remotely in the United States."
We can split into two paragraphs maybe.
Next Responsibilities: list bullet points:
- Design, architect, build, and deliver core pieces of IAM
- Lead projects from specification to delivery
- Mentor and grow other team members
- Improve our codebase, best practices, and design principles
- Define your top priorities and focuses, communicate them, and execute against them
- Lead and contribute to complex technical projects and initiatives
Next Requirements (Candidate Profile + Success Measures). We'll combine.
Candidate Profile bullets:
- 5+ years experience of software engineering, primarily focused on backend systems
- Proficient in a modern compiled programming language (Java, Go, C#, C++, etc.)
- Willingness to learn JavaScript and/or TypeScript along with modern frontend technologies (React, Redux, etc.); prior experience a plus
- Excellent communication skills, both written and verbal
- Desire to collaborate with colleagues and mentor fellow engineers
- Is curious, collaborative, empathetic, and intellectually honest
- Has a passion for problem solving and learning new things in the domains of computer science and software engineering
- Experience building identity and access management systems such as authentication (OAuth, SSO), authorization (RBAC, ABAC, ReBAC), and login and registration systems a plus
Success Measures bullets:
- In 1 week you'll have completed your first pull request
- In 3 months, you'll have contributed to a large project
- In 6 months, you’ll be leading the design and execution of your own project
We could put these as sub-bullets under Requirements or separate but still under same heading.
Next Pay: salary range: "$126,000—$248,000 USD". Could phrase as "MongoDB’s base salary range for this role in the U.S. is: $126,000—$248,000 USD". We'll put in .
Next Benefits: list of benefits:
- equity
- participation in the employee stock purchase program
- flexible paid time off
- 20 weeks fully-paid gender-neutral parental leave
- fertility and adoption assistance
- 401(k) plan
- mental health counseling
- access to transgender-inclusive health insurance coverage
- health benefits offerings
We could also mention "Other benefits for eligible employees may include:" but we can just list.
Now ensure we don't include any boilerplate like EEO, accommodations, etc.
Now produce HTML fragment.
We must not include or . Just the fragment.
Let's craft:
About the role
The MongoDB Atlas team is a diverse group of contributors working together to help our users manage MongoDB at global scale. We are responsible for MongoDB Atlas: our database as a service offering and fastest growing product which allows users to deploy fault-tolerant, globally distributed MongoDB clusters in just minutes. We're seeking a Senior Engineer to join the Atlas Identity and Access Management (IAM) team. IAM is a platform and a product team. We serve internal engineers by providing them a secure and durable suite of services, and we serve external customers by providing them user facing features and products. We are the owners of Atlas’ authentication (OAuth, SSO, Federated Identity) and authorization (RBAC, ABAC) systems, along with many others. The IAM team’s mission is to enable customers to securely build their applications with Atlas through our best in class user experience. The Federal Risk and Authorization Management Program (FedRAMP) is a US government-wide program that provides a standardized approach to security assessment, authorization, and continuous monitoring for cloud products and services. Our FedRAMP program requires that anyone who is accessing customer data or metadata inside the Authorization Boundary be a US Citizen on US Soil. This role will be based remotely in the United States.
Responsibilities
- Design, architect, build, and deliver core pieces of IAM
- Lead projects from specification to delivery
- Mentor and grow other team members
- Improve our codebase, best practices, and design principles
- Define your top priorities and focuses, communicate them, and execute against them
- Lead and contribute to complex technical projects and initiatives
Requirements
- 5+ years experience of software engineering, primarily focused on backend systems
- Proficient in a modern compiled programming language (Java, Go, C#, C++, etc.)
- Willingness to learn JavaScript and/or TypeScript along with modern frontend technologies (React, Redux, etc.); prior experience a plus
- Excellent communication skills, both written and verbal
- Desire to collaborate with colleagues and mentor fellow engineers
- Is curious, collaborative, empathetic, and intellectually honest
- Has a passion for problem solving and learning new things in the domains of computer science and software engineering
- Experience building identity and access management systems such as authentication (OAuth, SSO), authorization (RBAC, ABAC, ReBAC), and login and registration systems a plus
- Success measures:
- In 1 week you'll have completed your first pull request
- In 3 months, you'll have contributed to a large project
- In 6 months, you’ll be leading the design and execution of your own project
But nesting inside - is not valid HTML unless we close the outer li before inner ul? Actually you can have
- containing a
. It's allowed: - Success measures:
...
. That's fine.
But we need to close tags properly.
Alternatively we could make Success measures as a separate but not allowed. We'll keep as nested.
Now Pay:
Pay
MongoDB’s base salary range for this role in the U.S. is: $126,000—$248,000 USD
Benefits:
Benefits
- equity
- participation in the employee stock purchase program
- flexible paid time off
- 20 weeks fully
About the role
then paragraphs. Content: "The MongoDB Atlas team is a diverse group of contributors working together to help our users manage MongoDB at global scale. We are responsible for MongoDB Atlas: our database as a service offering and fastest growing product which allows users to deploy fault-tolerant, globally distributed MongoDB clusters in just minutes. We're seeking a Senior Engineer to join the Atlas Identity and Access Management (IAM) team. IAM is a platform and a product team. We serve internal engineers by providing them a secure and durable suite of services, and we serve external customers by providing them user facing features and products. We are the owners of Atlas’ authentication (OAuth, SSO, Federated Identity) and authorization (RBAC, ABAC) systems, along with many others. The IAM team’s mission is to enable customers to securely build their applications with Atlas through our best in class user experience. The Federal Risk and Authorization Management Program (FedRAMP) is a US government-wide program that provides a standardized approach to security assessment, authorization, and continuous monitoring for cloud products and services. Our FedRAMP program requires that anyone who is accessing customer data or metadata inside the Authorization Boundary be a US Citizen on US Soil. This role will be based remotely in the United States." We can split into two paragraphs maybe. Next Responsibilities: list bullet points: - Design, architect, build, and deliver core pieces of IAM - Lead projects from specification to delivery - Mentor and grow other team members - Improve our codebase, best practices, and design principles - Define your top priorities and focuses, communicate them, and execute against them - Lead and contribute to complex technical projects and initiatives Next Requirements (Candidate Profile + Success Measures). We'll combine. Candidate Profile bullets: - 5+ years experience of software engineering, primarily focused on backend systems - Proficient in a modern compiled programming language (Java, Go, C#, C++, etc.) - Willingness to learn JavaScript and/or TypeScript along with modern frontend technologies (React, Redux, etc.); prior experience a plus - Excellent communication skills, both written and verbal - Desire to collaborate with colleagues and mentor fellow engineers - Is curious, collaborative, empathetic, and intellectually honest - Has a passion for problem solving and learning new things in the domains of computer science and software engineering - Experience building identity and access management systems such as authentication (OAuth, SSO), authorization (RBAC, ABAC, ReBAC), and login and registration systems a plus Success Measures bullets: - In 1 week you'll have completed your first pull request - In 3 months, you'll have contributed to a large project - In 6 months, you’ll be leading the design and execution of your own project We could put these as sub-bullets under Requirements or separate- but still under same heading.
Next Pay: salary range: "$126,000—$248,000 USD". Could phrase as "MongoDB’s base salary range for this role in the U.S. is: $126,000—$248,000 USD". We'll put in
- Design, architect, build, and deliver core pieces of IAM
- Lead projects from specification to delivery
- Mentor and grow other team members
- Improve our codebase, best practices, and design principles
- Define your top priorities and focuses, communicate them, and execute against them
- Lead and contribute to complex technical projects and initiatives
- 5+ years experience of software engineering, primarily focused on backend systems
- Proficient in a modern compiled programming language (Java, Go, C#, C++, etc.)
- Willingness to learn JavaScript and/or TypeScript along with modern frontend technologies (React, Redux, etc.); prior experience a plus
- Excellent communication skills, both written and verbal
- Desire to collaborate with colleagues and mentor fellow engineers
- Is curious, collaborative, empathetic, and intellectually honest
- Has a passion for problem solving and learning new things in the domains of computer science and software engineering
- Experience building identity and access management systems such as authentication (OAuth, SSO), authorization (RBAC, ABAC, ReBAC), and login and registration systems a plus
- Success measures:
- In 1 week you'll have completed your first pull request
- In 3 months, you'll have contributed to a large project
- In 6 months, you’ll be leading the design and execution of your own project
- is not valid HTML unless we close the outer li before inner ul? Actually you can have
- containing a
- . It's allowed:
- Success measures:
- ...
. That's fine.
But we need to close tags properly.
Alternatively we could make Success measures as a separate - equity
- participation in the employee stock purchase program
- flexible paid time off
- 20 weeks fully
but not allowed. We'll keep as nested. Now Pay:
Pay
MongoDB’s base salary range for this role in the U.S. is: $126,000—$248,000 USD
Benefits:Benefits
- Success measures:
. Next Benefits: list of benefits: - equity - participation in the employee stock purchase program - flexible paid time off - 20 weeks fully-paid gender-neutral parental leave - fertility and adoption assistance - 401(k) plan - mental health counseling - access to transgender-inclusive health insurance coverage - health benefits offerings We could also mention "Other benefits for eligible employees may include:" but we can just list. Now ensure we don't include any boilerplate like EEO, accommodations, etc. Now produce HTML fragment. We must not include or . Just the fragment. Let's craft:
About the role
The MongoDB Atlas team is a diverse group of contributors working together to help our users manage MongoDB at global scale. We are responsible for MongoDB Atlas: our database as a service offering and fastest growing product which allows users to deploy fault-tolerant, globally distributed MongoDB clusters in just minutes. We're seeking a Senior Engineer to join the Atlas Identity and Access Management (IAM) team. IAM is a platform and a product team. We serve internal engineers by providing them a secure and durable suite of services, and we serve external customers by providing them user facing features and products. We are the owners of Atlas’ authentication (OAuth, SSO, Federated Identity) and authorization (RBAC, ABAC) systems, along with many others. The IAM team’s mission is to enable customers to securely build their applications with Atlas through our best in class user experience. The Federal Risk and Authorization Management Program (FedRAMP) is a US government-wide program that provides a standardized approach to security assessment, authorization, and continuous monitoring for cloud products and services. Our FedRAMP program requires that anyone who is accessing customer data or metadata inside the Authorization Boundary be a US Citizen on US Soil. This role will be based remotely in the United States.
Responsibilities
Requirements
- inside