The Solutions Engineering Team
We believe Solutions Engineers at Okta are involved in all stages of the customer’s digital transformation. Solutions Engineers are experienced using presentations, email, phone and social media to connect with customers virtually and in-person. We are looking for great teammates who can build and deliver sales presentations and customized product demonstrations to help educate Okta’s Customers (everyone from developers to product managers to C-level executives) on best practices during their cloud security technology journey. We believe Okta’s Solutions Engineers empathize with Customers and quickly discern their true technical needs by asking detailed, clarifying questions while presenting solutions that specifically address those needs. Okta Solution Engineers have the rare combination of technical acumen and business insight; in a career where you can utilize both. As a Solutions Engineer at Okta, you will further develop each of these skills by advising a diverse set of customers on the value they will gain by using Okta’s Identity Platform.

The Solutions Engineer, Auth0 Opportunity
Reporting to the Sr. Manager, Solutions Engineering, Strategic Auth0, the Solutions Engineer is a functional business consultant, with a passion for technology and the advanced ability to develop, position and demonstrate product-specific solutions during sales cycles, while achieving quarterly and annual sales goals for an assigned territory.

What you’ll be doing

• Work alongside the sales team as the technical and domain expert of a customer-facing sales team to help Enterprise Customers understand the value of Okta’s solutions
• Understand customer challenges and business issues and provide product demonstrations to align our solutions with customer needs
• Answer product feature and technical questions from customers, partners and Okta colleagues
• Plan and deliver Proof Of Concepts for customers who have more complex use cases, collaborating with other Okta engineering teams as needed
• Provide feedback to product management about product enhancements that can address customer needs and provide additional value
• Share and learn best practices and re-usable assets with other Solutions Engineers to enhance the quality and efficiency of the team
• Stay current on competitive analysis and market differentiation
• Support marketing events including executive briefings, conferences, user groups, and trade shows
• At times, be asked to learn and lead your team as a subject matter expert (SME) with various product solutions and/or competitive knowledge

What you’ll bring to the role:

• Identity and Access Management (IAM) Expertise:
  • 5+ years of pre-sales engineering experience in IAM.
  • Strong understanding of IAM concepts, including OAuth 2.0, OIDC, and SAML.
  • Experience with lifecycle management, role-based access control (RBAC), and provisioning/deprovisioning.
• Technical Proficiency:
  • Hands-on experience in one or more of the following development areas: web (JavaScript, HTML, frontend frameworks), mobile (iOS, Android), backend (Java, C#, Node.js, Python, PHP, Ruby), or IP-based real-time communications.
  • Experience working with REST APIs, API Gateways, and SDKs.
  • Deployed applications on cloud platforms (AWS, Azure, GCP, Vercel, etc.).
  • Understanding of core security concerns in applications (password hashing, SSL/TLS, encryption at rest, XSS, XSRF).
• Customer Engagement & Communication:
  • Passion for serving customers, demonstrated in a customer-facing role (ideally pre-sales, but consulting or support also valued).
  • Ability to quickly communicate complex technical ideas, including on-the-fly whiteboard explanations.
  • Elite communication skills, confident in dispensing knowledge and presenting to highly skilled and experienced audiences.
• Strategic & Organizational Skills:
  • Territory management skills, including pipeline building and collaboration with sales counterparts for execution excellence.
  • Diagramming experience for user journey flows, complex architecture diagrams, etc.
• Education & Travel:
  • Bachelor's degree in Engineering, Computer Science, MIS, or a comparable field is preferred.
  • Typically 25% travel.

You might also have (not mandatory):

• Experience with Auth0, Auth0 FGA, or OpenFGA.
• Hands-on experience with Generative AI or LLM technology (LangChain, GenKit, LlamaIndex, etc.).
• Experience integrating with micro services, data lakes, or customer data platforms.
• Developed ReBAC or Fine-Grained Authorization models.

#LI-LSS1

#LI - Remote

P23532

Location: Miami, FL | London, UK | Remote (US)

The Problem and the Role

OpenFX is on a mission to move money as freely as data, unrestricted by time zones, banking hours, or legacy systems. We are building the infrastructure that will power the next generation of cross-border payment systems for institutions.

We are seeking a Developer Experience Lead, who will report to the head of Product Growth, to own the entire developer-facing surface of our platform, from documentation to integration support to API governance. We have built a world-class financial engine, but how external developers experience that engine has no owner. This role fills that gap.

This is a foundational role. You will be the first hire in this function. You will architect the documentation ecosystem from the ground up, define the processes that keep it accurate as the platform evolves, and directly support the clients who integrate with our APIs. Over time, you will shape how Developer Experience operates as a discipline at OpenFX, influencing product decisions, integration strategy, and the developer journey end-to-end.

You will set the bar higher than industry standards, building a knowledge system that turns complex FX liquidity and cross-border payment flows into a Hello World integration in under 15 minutes.

What You'll Actually Do & Own

• Drive API Product Adoption: You own API adoption as a measurable outcome. You instrument the funnel from API key activation to first API call to first transaction to expanded endpoint usage. You set the baseline, define the targets, and drive the cross-functional work to move the number. Every quarter, more developers are activated, more endpoints are used, and integrations go deeper. This is what you are accountable for, not pages shipped.
• Architect the Documentation System: Documentation is the primary adoption surface. You own the information architecture and the words. You design the taxonomy that scales from a simple Quickstart guide to complex Treasury Operations references. You determine how we version, layer, and present information so it does not collapse under its own weight as the platform grows. You build it on docs-as-code infrastructure that engineers can contribute to. You measure documentation by whether it moves adoption, not by completeness for its own sake.
• Own the OpenAPI Workflow: Your first technical priority is aligning the OpenAPI spec to production reality. Then you implement and enforce a contract-first governance model where the spec is treated as a product contract, not a generated afterthought. Spec linters run in CI as merge blockers. OpenAPI updates are part of engineering's Definition of Done. Breaking changes are detected automatically and routed through a defined deprecation process. You sit in Product and Engineering reviews as the First User: if an API is too hard to explain in writing, it is too hard to use, and you have the authority to push back before code ships.
• Drive Developer Advocacy: You are the external voice of OpenFX inside the developer community and the internal voice of the developer inside OpenFX. You write technical content that earns developer trust: deep-dive blog posts on idempotency under retries, sample apps that demonstrate real cross-border payment flows, integration pattern guides for PSP, neo-bank, and treasury use cases. You build feedback loops that turn integration friction into product changes. As volume justifies, you represent OpenFX at developer-focused events, conferences, and partner enablement sessions. You are the reason developers choose OpenFX over a competitor whose docs they could not understand.
• Own Integration Triage: You are the technical front door for client integration questions during US business hours. You triage whether each issue is a documentation gap, an API design problem, or a code bug. You fix documentation gaps directly and route the rest to engineering with structured context. You build the repeatable onboarding playbook that turns one-off Slack threads into a scalable process. You partner with GTM, who owns the client relationship; you own the developer experience surface that surfaces during integration.

What Success Looks Like

• API Product Adoption: You own the adoption funnel from API key activation to first API call to first transaction to expanded endpoint usage. You instrument it, set the baseline, define the target, and drive the cross-functional work to move the number. This is the metric you are accountable for.
• Time to First API Call: Drops from around 3 days to under 15 minutes within 90 days. You own the Quickstart, code snippets, and onboarding tutorials that make this speed possible, and you advocate for the product changes needed to remove the rest of the friction.
• Instructional support tickets: reduced 40% within 90 days, with 42% of onboarding support requests as the baseline.
• Spec drift: no spec drift incidents that reach production. The OpenAPI spec stays aligned to production as the platform evolves.
• V1 Developer Portal: a public API doc portal (References, Guides, Changelog, sample apps) is live, searchable, and built on docs-as-code infrastructure. 100% of public endpoints have accurate request and response examples.
• Developer advocacy presence: a published cadence of technical content (deep-dive guides, sample apps, integration patterns) that builds developer trust and drives inbound adoption. Establish the baseline, grow it quarterly.
• DX roadmap: a written plan for SDK strategy, portal evolution, adoption analytics, and Agent Experience foundations and expansion (CLI, MCP)

Requirements

• 5+ years owning a developer-facing API product or platform. B2B or infrastructure. You drove a measurable adoption outcome, not just shipped pages. You can point to the integration experience you built, the funnel you owned, and the metric you moved.
• Direct client integration work. You have sat on integration calls with B2B or institutional clients, diagnosed friction live, and fed it back into product changes (not just documentation updates). You know what breaks during real integrations, not what should break in theory.
• Product instinct for API design. You have opinions on endpoint design, parameter naming, authentication UX, error response formats, idempotency keys, and SDK ergonomics. You have opinions on these calls and get changes shipped before code hits production.
• Engineering fluency. You read code well enough to extract logic independently. You understand distributed system concepts (latency, rate limiting, idempotency, eventual consistency, async patterns). You can sit in a code review and have something useful to say.
• Contract-first governance experience. You have implemented or enforced OpenAPI workflows where the spec is treated as a product contract, not a generated artifact.
• Financial services or fintech context. You know the difference between authorized and settled. You have worked on payments, trading, or banking APIs.
• Agent Experience instinct. You have shipped or experimented with MCP servers, agent-native SDKs, llms.txt, evaluation suites for LLM-driven API consumption, or other agent-readable API patterns. You have a point of view on what Developer Experience looks like when AI agents are first-class consumers.

Preferred

• Interactive docs experience: code playgrounds, Try It Now, in-browser sandbox.
• Multimedia documentation skills: video tutorials, sequence diagrams, architecture diagrams that complement written documentation.
• Developer advocacy or DevRel experience: you have written technical content for an external developer audience, shipped sample apps, or represented a product at developer events.

Why This Role?

• Foundational Ownership: You are the first hire in this function. You define the hiring standards, the voice, and the culture of Developer Experience at OpenFX. As the function scales, you lead the team.
• Greenfield Architecture: You are building the DX product from the ground up. You build the system right the first time, selecting the stack, the taxonomy, and the governance model from scratch.
• The Frontier of Finance: You will learn the inner workings of global finance (FX liquidity, settlement, treasury), and you will apply them to the new payment stack as well as the legacy rails of the past. Our technology is novel; you teach developers how to think about the future of money and define the vocabulary of the industry. 
• Where This Role Grows: The next milestone is Agent Experience. AI agents are becoming first-class consumers of APIs alongside human developers. As Developer Experience matures, you lead the expansion into agent-native tooling: MCP servers that expose OpenFX as agent-callable tools, SDKs and CLIs designed for both human and autonomous consumption, semantically structured documentation that LLMs can parse natively, evaluation suites that test whether agents can invoke OpenFX correctly from natural language, and sandboxing patterns that let agents transact safely. Few companies have a clear owner for what Agent Experience means at the API layer. You define this discipline at OpenFX, and you do it from a foundation of human Developer Experience that already works.
• The Team: You are joining a team of ex-Stripe, J.P. Morgan, and Kraken alumni.  We are backed by Accel, Atomico, M13, Northzone, Pantera, and we believe that our APIs are core to our product. 

#LI-DP1