Technical Architect, Auth0

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. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. We need to parse the posting. Let's extract content: First paragraph: "Secure Every Identity, from AI to Human Identity is the key to unlocking the potential of AI. Okta secures AI by building the trusted, neutral infrastructure that enables organizations to safely embrace this new era. This work requires a relentless drive to solve complex challenges with real-world stakes. We are looking for builders and owners who operate with speed and urgency and execute with excellence. This is an opportunity to do career-defining work. We're all in on this mission. If you are too, let's talk." That's generic marketing fluff but it's part of posting. Should we include? It's not a section heading. Could be part of About the role? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to create sections with those headings if content exists. We need to decide what goes where. "Position Description:" then description of Okta's Customer Identity Cloud (CIC) etc. That seems like About the role. Then "Job Duties and Responsibilities:" list bullet points. Then "Minimum REQUIRED Knowledge, Skills, and Abilities:" list many items. Then "Highly Desirable Knowledge, Skills, and Abilities:" list. Then "Education and Certification" list. Then "This role requires in-person onboarding and travel to our San Francisco, CA HQ office or Chicago, IL office during the first week of employment." That's maybe Schedule? Actually schedule maybe travel requirement. Then "P-1449 The OTE range for this position for candidates located in the San Francisco Bay area is between:: $224,000 USD - $308,000 USD" etc. That's Pay. Then "Below is the annual On Target Compensation (OTE) range for candidates located in California (excluding San Francisco Bay Area), Colorado, Illinois, New York and Washington. Your actual OTE, which is inclusive of base salary and incentive compensation, will depend on factors such as your skills, qualifications, experience, and work location. In addition, Okta offers equity (where applicable) and benefits, including health, dental and vision insurance, 401(k), flexible spending account, and paid leave (including PTO and parental leave) in accordance with our applicable plans and policies." Then "Below is the annual salary range for candidates located in Canada. Your actual salary will depend on factors such as your skills, qualifications, and experience. In addition, Okta offers equity (where applicable), bonus, and benefits, including health, dental, and vision insurance, RRSP with a match, healthcare spending, telemedicine, and paid leave (including PTO and parental leave) in accordance with our applicable plans and policies." Then "The Okta Experience Supporting Your Well-Being Driving Social Impact Developing Talent and Fostering Connection + CommunityWe are intentional about connection. Our global community, spanning over 20 offices worldwide, is united by a drive to innovate. Your journey begins with an immersive, in-person onboarding experience designed to accelerate your impact and connect you to our mission and team from day one." Then EEO boilerplate etc which we must remove. Thus we need to extract substantive content for sections: - About the role: likely the Position Description paragraph(s) plus maybe the initial marketing fluff? The Position Description is definitely about the role. We'll include that. - Responsibilities: the list under "Job Duties and Responsibilities:" (multiple bullet points). We'll put each as

. - Requirements: maybe the "Minimum REQUIRED Knowledge, Skills, and Abilities:" plus "Education and Certification"? Could split into Requirements and Qualifications. The instruction includes both Requirements and Qualifications as possible headings. We need to decide what to put where. Usually Requirements = mandatory; Qualifications = education/certifications etc. We'll follow that. Thus: Requirements: Minimum REQUIRED Knowledge, Skills, and Abilities (the list). Possibly also include "Experience integrating with a multitude of On-Prem and SaaS based products." etc. That's part of that list. Qualifications: Education and Certification (Bachelor's degree required, Okta certifications etc). Also maybe "Highly Desirable Knowledge, Skills, and Abilities:" could be considered Skills? Actually Skills section could be separate. But we have Skills heading as possible. We could put the "Highly Desirable Knowledge, Skills, and Abilities:" under Skills. Or we could treat Skills as separate from Requirements. The instruction says we can use Skills heading. So we could have: - Requirements: Minimum REQUIRED Knowledge, Skills, and Abilities. - Skills: Highly Desirable Knowledge, Skills, and Abilities. - Qualifications: Education and Certification. But we need to avoid thin sections. However we have substantive content for each. Benefits: The posting mentions benefits in the compensation sections: "Okta offers equity (where applicable) and benefits, including health, dental and vision insurance, 401(k), flexible spending account, and paid leave (including PTO and parental leave)". Also for Canada: similar. So we can extract benefits. Pay: The OTE ranges for different locations. Schedule: The travel requirement: "This role requires in-person onboarding and travel to our San Francisco, CA HQ office or Chicago, IL office during the first week of employment." Also maybe travel up to 50% mentioned earlier under "Ability to travel up to 50%" in the Minimum REQUIRED list. Actually that appears in the Minimum REQUIRED list: "Ability to travel up to 50%". So schedule could include travel requirement and maybe onboarding. We need to ensure we don't create sections with filler like "commensurate with experience". We have actual numbers. Now we must not repeat job title as heading. Not include Job ID/P-1449 as heading. We can include the ID maybe in a short paragraph? The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we could include a short paragraph with the Job ID maybe but better to drop it. We'll drop it. We must not include application instructions, boilerplate, EEO, legal, scam warning, navigation, cookie etc. So remove the EEO paragraph, the Okta Experience section? That is maybe not boilerplate but could be considered fluff. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Okta Experience" section is not exactly boilerplate but could be considered marketing fluff. However it's substantive about culture. Might be okay to keep? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep it if it's substantive. But we need to fit into sections. Could be part of About the role or maybe a separate section like "About Okta". But we only have allowed headings list. Could incorporate into About the role. We need to output only HTML fragment, no /, no markdown. Thus we will produce something like:

About the role

Secure Every Identity, from AI to Human Identity is the key to unlocking the potential of AI. Okta secures AI by building the trusted, neutral infrastructure that enables organizations to safely embrace this new era. This work requires a relentless drive to solve complex challenges with real-world stakes. We are looking for builders and owners who operate with speed and urgency and execute with excellence. This is an opportunity to do career-defining work. We're all in on this mission. If you are too, let's talk.

Position Description:Okta's Customer Identity Cloud (CIC), powered by Auth0 technology, is an easy to implement authentication and authorization platform designed by developers for developers. We make access to applications safe, secure, and seamless for more than 100 million daily logins around the world. Our modern approach to identity enables this Tier-0 global service to deliver convenience, privacy, and security so customers can focus on innovation.The Services Architect - CIAM is a technical authority on both cloud and on-premises based IT systems and is responsible for ensuring the successful design and implementation of Okta’s industry leading cloud identity platform at our customers. You will focus on Okta’s CIAM offering targeted at customer identity use cases. You will develop relationships with customers to help them achieve their business goals while promoting creative solutions. You will establish yourself as a trusted partner with your customers with a focus on their success. You will translate business needs and insights into an actionable strategy and assist customers in driving their initiatives to results and high business value. This is a key member of the Professional Services (PS) team, working as part of a PS Delivery Team on each customer implementation.This role is for the Customer Identity Cloud product unit and you’ll be supporting CIC customers.

But we might want to split into paragraphs for readability. Then Responsibilities:

Responsibilities

• Review and lead the gathering of business, functional and technical requirements for establishing an Identity platform powered by Okta for our customers.
• Work with customers to document the common technical and functional requirements for specific solutions.
• Support creation of project plans to develop and implement the proposed solution.
• Participate as a member of the professional services delivery team to translate requirements to designs and to provide technical leadership and oversight.
• Assist in periodic customer health-checks and project reviews.

Then Requirements:

Requirements

• 8+ years of overall IT / software development experience, solution design and technical architecture experience
• 3+ years of consulting experience
• 3+ years driving application architecture design
• 3+ years of experience with (IAM) architectures
• 3+ years of experience with implementing cloud computing solutions such as AWS, Google Apps, Salesforce etc.
• Experience with customer identity use cases for B2C and B2B: user registration, multi factor authentication, SSO, delegated administration, social identities.
• Demonstrated ability to work and interact with CxOs and high-level customer executives.
• Experience in leading discovery workshop to derive customer requirements, specifications, business processes.
• Experience in developing functional specifications and system design specifications for customer engagements.
• Strong knowledge of Security Architecture, Design and Operations, LDAP, Active Directory, SAML, SSO, RBAC, OAuth, OIDC, web protocols XML, SOAP, JSON, REST
• Proficiency in one or more of Java, .Net, JavaScript, Angular, React
• Familiarity with IAM solution providers is strongly desired.
• Experience integrating with a multitude of On-Prem and SaaS based products.
• Exhibits confidence and a deep understanding of emerging industry practices when solving business problems.
• Identifies critical issues with ease.
• Effectively communicates technical information to non-technical audiences.
• Manages customer expectations effectively.
• Ability to travel up to 50%

Then Skills (Highly Desirable):

Skills

• Okta Expertise, Experience, Certifications
• Knowledge of software development security and cryptography.
• Experience with API Gateways, CASB, Reverse Proxies (NGINX)
• Knowledge of cloud/virtualization technologies, such as VMware vSphere, EC2, Xen, KVM, OpenStack
• Proficiency with various open