About the Team

As a Senior+ Agentic Analytics Engineer at Opendoor, you will join the Data organization and help build something that doesn't exist at most companies: an Agentic Analytics team. This is a high-impact IC role at the intersection of data science, data engineering, and AI.

Opendoor has adopted a "Default to AI" philosophy—if AI can handle it, AI should handle it. We're not theorizing about AI transformation; we're shipping it.

Why This Role

Most analytics teams are stuck in reactive mode—fielding ad-hoc requests and building dashboards that go stale. We're building something different: AI systems that proactively tell leaders what they should focus on, why it matters, and what to do about it.

If you want to define what analytics looks like in an AI-first company, this is it.

What You'll Do

Build Proactive Intelligence Systems

• Design and deploy AI agents that monitor business performance and surface actionable insights without being asked

• Architect systems that shift analytics from "answering questions" to "anticipating needs"

• Create intelligent alerting that distinguishes signal from noise and recommends specific actions

Create AI-Powered Analytics Tools

• Develop natural language interfaces that let business leaders query data conversationally

• Build semantic layers that translate business concepts into data structures optimized for LLM reasoning

• Ship internal tools that transform how Opendoor makes decisions at every level

Own the Analytics-to-Action Pipeline

• Design data models that support automated analysis, pattern detection, and AI agent interactions

• Build workflows that connect insight generation to recommended actions

• Establish feedback loops that make our AI systems smarter over time

Drive Leverage Across the Business

• Identify high-value opportunities where AI can augment human decision-making

• Implement end-to-end solutions using Claude, custom agents, and modern AI tooling

• Measure impact rigorously—we care about decisions influenced, not dashboards built

We're Looking for Teammates Who Have

Technical Foundation

• 5+ years of experience in analytics, data science, or data engineering, with increasing scope and ownership

• Expert-level SQL with demonstrated ability to design complex data models and optimize for both human and AI consumption

• Strong Python proficiency for data engineering, automation, and AI agent development

• Experience with modern data warehouses (Snowflake, BigQuery, or similar) and the broader data stack (dbt, Airflow, etc.)

AI & Automation Expertise

• Hands-on experience building and deploying AI agents or LLM-powered applications in production

• Deep understanding of LLM capabilities, limitations, and prompt engineering best practices

• Experience architecting semantic layers or natural language interfaces for data access

• Proven ability to identify high-ROI automation opportunities and ship end-to-end solutions

Analytics & Business Acumen

• Track record of driving measurable business impact through analytics—not just producing analyses, but influencing decisions

• Strong analytical intuition—you know what questions matter before they're asked

• Experience translating ambiguous, cross-functional business problems into technical solutions

• History of operating autonomously and setting direction, not just executing on defined projects

Leadership & Influence

• Experience mentoring other analysts or engineers, formally or informally

• Demonstrated ability to influence senior stakeholders and drive alignment across teams

• Comfort operating in ambiguity and shaping strategy, not just responding to it

• Track record of building systems and processes that scale beyond yourself

Builder Mindset

• You ship products, not just dashboards 

• You'd rather build something useful in a week than something perfect in a quarter

• You measure success by business impact, not technical complexity

• You're energized by creating leverage—building once so others benefit forever

Bonus Points If You Have

• Experience in real estate, fintech, or marketplace businesses

• Background in marketing analytics, sales operations, product analytics, or pricing/economics

• History of building tools or platforms that replaced recurring analyst work

• Experience leading technical projects or small teams

Inspire curiosity. Build independence. Shape a lifelong love of learning.

At Guidepost Montessori, our Lead Children’s House Guides empower children ages 3–6 to grow into confident, capable learners through thoughtfully prepared environments and respectful, individualized guidance.

If you’re passionate about early childhood education and excited to lead a classroom where independence and joy take center stage, we’d love to meet you.

Your Role

As a Lead Children’s House Guide, you’ll lead a mixed-age preschool classroom in a Montessori environment designed to nurture concentration, confidence, and deep learning.

Montessori guides carefully prepare their classrooms to spark curiosity and independence. Through close observation, individualized lessons, and intentional language, you’ll support each child’s academic, social, and emotional development meeting them where they are and helping them grow.

Children in Montessori classrooms have the freedom to choose meaningful work, repeat activities until mastery, and take pride in their accomplishments. Your guidance helps every child develop focus, confidence, and a strong belief in their own abilities.

What You’ll Do

• Observe each child closely to understand and support their physical, intellectual, and emotional development
• Prepare and maintain a beautiful, orderly classroom that fosters concentration and independence
• Encourage self-confidence by supporting children as they learn to “do it themselves”
• Provide individualized and small-group lessons in practical life, literacy, math, and beyond
• Build strong, respectful relationships with children and families
• Communicate and collaborate with parents to support each child’s growth
• Lead your classroom with warmth, professionalism, and purpose

The Montessori Prepared Environment

Every Guidepost Children’s House classroom is fully equipped with high-quality Montessori materials and designed around the principles of beauty, order, and accessibility.

A Guidepost Children’s House environment includes:

• Child-sized furniture and ample floor space for independent and small-group work
• Practical life materials for sweeping, food preparation, table setting, and care of the environment
• Curriculum that builds independence in dressing, feeding, and self-care
• Hands-on materials for literacy, math, science, and cultural studies
• Low shelves and child-level artwork for full accessibility
• Cozy reading spaces, real plants, and abundant natural light
• Beautiful, breakable materials made from wood, metal, and glass

What We’re Looking For

• Montessori diploma for ages 3–6, or willingness to obtain certification (fully sponsored)
• Experience working with children ages 3–6 in a group learning environment
• Alignment with child-led philosophies such as Montessori or Reggio Emilia
• Required ECE or Child Development credits
• Associate's or Bachelor’s degree in (ECE or Child Development)

What We Offer

• Sponsored Montessori diploma training through the Prepared Montessorian Institute
• Ongoing professional development and mentorship
• Competitive salary: $38,000 - $40,000 
• Health, dental, and vision insurance
• Paid time off and paid holidays
• 75% tuition discount for up to two children at any Guidepost school
• A supportive network of passionate educators
• Clear opportunities for career growth and leadership advancement

About Guidepost Montessori

Guidepost Montessori is a growing network of over 100 schools across the U.S. and Asia, serving children ages 3 months to 6 years in our Nido, Toddler, and Children’s House programs.

We believe children are capable. Our mission is to transform education by designing learning environments that cultivate independence, joy, and lifelong curiosity for children, families, and educators alike.

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.