• Survey GitLab’s internal software development lifecycle and code-generation workflows to identify structural friction early, and build a data-backed view of where technical interventions will have the highest leverage. • Evaluate build, buy, and adapt options for each opportunity, including emerging agentic and AI tooling, with a clear view of cost, risk, and durability. • Stand up prototypes and review architecture directly to test whether a proposed fix moves a target metric and represents a durable solution before GitLab makes broader engineering investment. • Hire and manage a small, high-caliber team, or operate as a hands-on working manager, with a focus on talent density over headcount. • Drive validated fixes from prototype to internal adoption by partnering with affected teams so solutions are relied on, used, and maintained. • Build the technical and business case for productizing internal fixes that prove durable, in partnership with product. • Document reusable learnings so successful internal fixes don’t remain tribal knowledge. • Report impact through changes in key metrics and progress on turning internal fixes into products, including a clear account of what didn’t work.

• Ensure alignment between the customer, Project Engineering, and Software teams in implementing Energy Management System (EMS), Power Plant Controller (PPC), and SCADA functionality across projects • Develop Project Control & Communication Specifications, defining point lists, Control behaviors, high-level network architecture, and interface requirements for EMS, and PPC • Review control system design, ensuring compliance with project requirements, ISO/RTO standards, and grid interconnection specifications • Advise Software Development and Product Management teams on customer-driven feature needs and lessons learned from field projects • Serve as a subject-matter expert on Modbus, DNP3, and related protocols used in grid-scale power systems • Maintain awareness of ISO/RTO telemetry, AGC, and dispatch requirements (e.g., ERCOT, CAISO) and ensure project compliance • Support development of internal standards, templates, and test procedures for project control and telemetry • Mentor engineers and contribute to knowledge sharing on controls architecture, communication design, and system modeling • Support development of standard processes and improvements for facilitating communication of project control and telemetry requirements between teams • Review PPA/LGIAs to ensure compliance, developing software specifications as needed

Role Description The Partner Solutions Architect is a high-priority role that will have a sizable, immediate impact on Elastic and our entire partner ecosystem. In this role, you will be responsible for the technical management, activation, and enablement of our partner relationship in EMEA. What Will You Be Doing - Acting as a strategic technical leader in the field - you are a self-starter. - Leading the lifecycle of agreements from business case, planning and governance, technical architecture, solution build, business modeling, and ensuring business case is delivered to the end customer through partners. - Translating technical capabilities into business benefits - instrumental in showing how Elastic’s offerings can be tailored to address the specific needs of the partner’s customer base. - Supporting partners in developing proactive proposals in key accounts for growing Elastic Cloud with partners. - Architecting custom solutions - co-creating tailored solutions that integrate Elastic’s technology within the partner’s offerings or customer environments. - Co-Leading design wins - assisting in developing the technical blueprint for industry-specific solutions that partners can use in their go-to-market strategies. - Driving technical advocacy and earning trust - fostering a deeper technical rapport with the partner. - Supporting co-marketing efforts - providing the technical backbone to marketing campaigns. - Authoring customer-facing publications - staying on top of market trends around cloud and industry best practices. - Building community to drive growth - developing a focused and structured network of Solutions Architects. What You Bring - 8+ years experience in technology solutions, practice development, architecture, consulting, and/or cloud/infrastructure technologies. - 5+ years of experience working with multinational customers in support of technology sales. - An understanding of AI and semantic search and vector technologies, with a focus on RAG, vector search, and NLP. - Professional experience architecting/operating solutions built on AWS, Google Cloud or MSFT Azure. - Excellent communication and presentation skills, able to engage both technical and non-technical audiences. - Adept at getting things done in an environment with ambiguity but also lots of opportunity. - A history of successful customer relations where you developed an understanding of what made a difference. - Ability to inspire teams to work on not just what’s urgent, but what’s most relevant. - Ability to travel up to 30% within the EMEA region. Benefits - Competitive pay based on the work you do here and not your previous salary. - Health coverage for you and your family in many locations. - Ability to craft your calendar with flexible locations and schedules for many roles. - Generous number of vacation days each year. - Increase your impact - We match up to $2000 (or local currency equivalent) for financial donations and service. - Up to 40 hours each year to use toward volunteer projects you love. - Embracing parenthood with a minimum of 16 weeks of parental leave.

• Owning the architecture: auth and identity flows, multi-tenancy, how data moves and where it's allowed to live, performance, and what happens in production • Running what you build. You'll be on-call for your own work from early on, before there's a dedicated platform to lean on, which means owning the infrastructure, CI, deployment, and observability behind it • Working on top of external platforms you can't change, and being straight about which risks are yours to manage and which aren't • Partnering closely with the internal teams whose services you depend on: asking clearly, agreeing on interfaces, and finding ways to keep moving instead of waiting around to be unblocked • We'd also expect you to have opinions about where this should go, and to write them down. A lot of what shapes the team's direction starts as a doc.