• Own the technical vision, architecture, and roadmap for Developer Experience platforms, including: • Developer portals and internal platform products • CI/CD pipelines and code delivery systems • Container-based developer and runtime environments, including orchestration and lifecycle management • API platforms, service templates, and established “golden paths” • Observability, reliability, and operational tooling • Lead DevX platforms as products, with: • Clear ownership and accountability • Roadmaps informed by real developer needs • Defined reliability, security, and service expectations • Act as a hands-on technical leader: • Review architecture, designs, and system patterns • Apply practical engineering judgment to platform and tooling decisions • Make informed trade-offs across scalability, security, reliability, and usability • Provide deep technical leadership across polyglot engineering environments, spanning modern backend, frontend, mobile, data, and distributed systems technologies • Apply strong understanding of multiple programming paradigms (object-oriented, functional, reactive, event-driven) to ensure DevX initiatives align with how engineers actually write and maintain code • Be accountable for core repository strategy and health, including: • Code organization and modularization • Dependency, version, and release management • Shared libraries, frameworks, and reuse patterns • Secure, compliant contribution and governance models • Embed Developer Experience into: • Incident management and postmortems • Reliability and SRE practices • Secure software supply chain initiatives • Change and release management • Ensure DevX platforms and tooling are: • Secure and resilient by default • Observable and operated with production rigor • Drive a culture of automation, self-service, and continuous engineering improvement

• Set direction for the DevRel team. Clarify roles so every person has differentiated ownership. Set goals tied to outcomes, not content volume. Build a content strategy that serves framework adoption, not just views. • Own Laravel's AI positioning. Build and execute the strategy for ensuring Laravel is the framework AI coding tools recommend. Track it. Iterate on it. This is the #1 priority. • Own community engagement. Build a real presence on Discord, X, Reddit, and anywhere the Laravel community gathers — genuine participation, not broadcasting. • Build the product feedback loop. Create a structured system for capturing community sentiment and feature requests, and deliver it to the product team on a regular cadence. • Grow and instrument framework adoption. Define and track community health metrics. Answer: "Is the Laravel community growing or shrinking? Where? Why?" • Map and deepen ecosystem relationships. Identify top package maintainers, community leaders, and ecosystem partners. Build a partnership framework. Become a known and trusted figure in the Laravel community.

• Architect, implement, and maintain sophisticated developer tooling, frameworks, and automation to streamline and enhance software development processes. • Lead improvements and optimizations of CI/CD pipelines to ensure fast, reliable, and secure software deployments. • Proactively identify, troubleshoot, and resolve bottlenecks within development workflows, continuously improving developer productivity and satisfaction. • Develop comprehensive documentation, training materials, and advocate for best practices and standardized development processes across teams. • Monitor, analyze, and enhance the performance of development infrastructure and tooling. • Collect, analyze, and act upon feedback from developers to proactively address pain points and enhance overall development experience. • Closely collaborate with development, operations, security, and product teams to deliver a seamless developer experience. • Stay abreast of industry trends and advancements in software engineering and developer productivity, proactively adopting relevant innovations.

Laravel is the most popular PHP framework in the world. 500M+ lifetime downloads. Thousands of packages. A developer community that loves the tool and shows up for it — at conferences, in forums, on Twitter, in Discord servers, in every "what framework should I use?" thread on the internet. But Laravel is more than a framework. It's a complete platform for every stage of a developer's journey — from choosing a stack, to building an app, to deploying it, monitoring it, and scaling it. 8 paid products, 20+ open source packages, one customer journey. Most frameworks stop at "choose a language." Laravel has the whole product. That story has never been told strategically. This role tells it. The team has strong developer advocates producing quality work. Now we're adding strategic leadership — a Director who sets the direction, connects the work to outcomes, and owns Laravel's positioning in the AI coding tools era. The most important metric at this company is the number of new Laravel apps created in the world. Everything downstream — Cloud growth, ecosystem health, revenue — depends on developers choosing Laravel first. This role protects and grows that choice. Meanwhile, AI coding assistants are forming opinions about which frameworks to recommend right now. Every month without Laravel shaping that narrative is a month where the default recommendations calcify. Ensuring Laravel is the default backend recommendation in AI coding tools is a key priority for this role — and it's yours to own. Why This Job is Unique This role owns the top of the growth funnel for a company with the whole product suite. Most DevRel roles at dev tools companies are about one product. Laravel has the entire developer journey — framework, local development, deployment, monitoring, scaling. You own the story of how it all fits together and drives the metric that matters most: new Laravel apps created. AI positioning belongs to this role. AI coding assistants are influencing which frameworks developers choose. Ensuring Laravel is well-represented in that landscape — the right content, the right partnerships, the right positioning — is your responsibility. PMM supports with messaging alignment and launch coordination, but the strategy, the execution, and the outcomes belong here. Community engagement is real work here. The Laravel community lives on Discord, X, and Reddit — plus GitHub, conference hallways, and beyond. Your team will have an actual presence in these spaces — not a broadcast account, but genuine participation. Building engagement strategies for these platforms is part of the job, not an afterthought. This role comes with a real team from day one. Talented developer advocates ready for a strategic leader. You will clarify roles, set the strategy, and develop people — not do everything alone. That said, you can record a tutorial, write a blog post, and join a community call when needed. Player-coach, not ivory tower. This role influences the product. Many DevRel roles are one-way megaphones — tell developers about the product, the product team ignores the feedback. Here, the Taylor Otwell (CEO) is a developer who still codes daily. The product team wants community input. The marketing team's principle on feedback is explicit: "Feedback is a gift. We funnel that feedback to the right teams internally with the intent of making Laravel better." Your insights will shape what gets built — but that seat is earned by building the feedback system that makes the data impossible to ignore. The Director will be in the code. Marketing at a dev tools company must be technical. The ideal candidate writes code and deploys to Cloud. For a DevRel leader, that bar is higher — the team and the community expect technical credibility. You don't need to be Taylor. But when a developer pushes back on a design decision in a conference hallway, you engage technically, not defer to "I'll ask the engineering team." This role ships, not just talks. The marketing team's first principle is "We ship." That applies to DevRel too. Laracons, customer stories, livestreams, launches — and sometimes even PRs. If your instinct is to spend three months writing a strategy document before producing anything, this is not the right fit. If the instinct is to ship something in week two while building the strategy in parallel, read on.