Senior Open Source Community Engineer

We need to output HTML fragment with sections: About the role (but we already have "About The Role" heading in source). Use

for section headings. We need to include sections only if real content. We have content for About the role (the paragraph after "About The Role"). Also "What You Will Do" (responsibilities). Also "What You Bring To The Table" (requirements/qualifications/skills). Also "What Modular Brings To The Table" (benefits). Also location and travel info maybe part of About the role? Could be separate "Location" or "Schedule"? Not required to create schedule unless present. We have location: Candidates based in US and Canada, office Los Altos, remote, hybrid, travel etc. That's location and maybe schedule? Not exactly schedule. Could include as a

under About the role or separate section "Location". But rule: only include sections when posting has real specific content. We have location details, could make a section "Location". However they said use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list Location as a standard heading but we could still use

for any section heading? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we can use other headings? Probably better to stick to those headings if applicable. Location not in list, but we could fold location info into About the role paragraph or maybe into a

without heading. Similarly travel info could be part of About the role. Pay: we have salary ranges. So we need a Pay section with that info. Benefits: we have benefits description. Responsibilities: "What You Will Do" list. Requirements/Qualifications/Skills: "What You Bring To The Table" includes qualifications, experience, helpful but not required. Could split into Requirements (minimum qualifications) and Skills (helpful but not required). Or combine. We need to avoid filler like "commensurate with experience". Not present. We must not repeat job title as heading. Not include Job ID. We must remove boilerplate like EEO etc. Not present. We need to preserve all substantive info. Let's extract: About the role paragraph: "As our developer community grows, we need someone who can bridge the gap between our engineering team and developers building with our developer products: Mojo and MAX. We're looking for a Senior Open Source Community Manager to support our community and help developers succeed with Modular's platform. This is an individual contributor role within the product organization, reporting to Modular's Manager, Technical Community. In this role, you'll answer complex technical questions across our forums and Discord, triage and manage contributions across our open source repositories, shape our open source and packaging strategies, and help build a thriving ecosystem around Modular's technology. Success in this role within 6 months looks like taking ownership over and driving the triage process of open source contributions at Modular, and ensuring timely responses to those contributions while improving the experience of open source contributors. You'll work closely with engineering, product, and developer relations teams to ensure our community has the resources, support, and direction they need to succeed with Modular's platform." Then location and travel: "LOCATION: Candidates based in the United States and Canada are welcome to apply. You can work in our office in Los Altos, CA or remotely from home. To support growth and collaboration, those in earlier career stages work in a hybrid capacity at our Los Altos, CA office (minimum 2 days per week on-site). Onboarding for new hires is conducted in-person in our Los Altos, CA office. This role requires travel to conferences and developer events, which may be as often as once per month, in addition to travel for team and company events (typically 2-4 times per year)." We could embed location paragraph after About the role. Responsibilities list: bullet points under "What You Will Do". Each starts with a verb. Let's list them: - Serve as the primary technical expert in community channels (forums, Discord, social media), answering complex questions about Mojo and MAX, troubleshooting issues, and providing guidance on best practices. - Triage and manage GitHub Issues and Pull Requests across Modular's open source repositories, leading weekly roundtable contribution review sessions and working with engineering teams to prioritize community contributions and ensure timely responses. - Contribute to the development and execution of Modular's open source strategy, including identifying opportunities for open sourcing new products and establishing processes that balance openness with business objectives. - Shape Modular's packaging strategy and help build a vibrant packaging ecosystem, working with the community and internal teams to improve distribution, discoverability, and integration of projects built using Mojo and MAX. - Identify patterns in community feedback and escalate insights to product and engineering teams to inform roadmap decisions and improve developer experience. - Build and nurture relationships with key community members, open source contributors, and ecosystem partners to foster advocacy and collaboration. - Represent Modular at conferences, meetups, and online events. Contribute to the planning and execution of developer-focused events. We'll put these in

• . What You Bring To The Table: includes: - 3–5+ years of professional software engineering experience, with at least some of it centered on open source, whether as a maintainer, a regular contributor, or working on an openly developed project. - 1-3 years of experience in systems programming or AI/ML infrastructure. - Fluency in how open source runs: GitHub workflows, triage and contribution management, release cadence, community governance models, and licensing. - A track record of community engagement you can point to. Issues you shepherded, contributors you brought in, discussions you steered. - Evidence that community feedback has changed something. A docs overhaul, an API rename, a bug caught before release. - Strong debugging instincts. When someone shows up with a broken repro, you can get to a real answer rather than routing it elsewhere. - Excellent written and verbal communication. - Self-motivated and comfortable working autonomously in a fast-paced, remote-friendly startup environment. Minimum Qualifications: - Bachelor's degree in Engineering, Information Systems, Computer Science, or technical related field. - 2+ years of Product Management or related work experience. - Completed advanced degrees in a relevant field may be substituted for up to two years of work experience. Helpful, But Not Required: - Experience in technical community management, developer relations, developer advocacy, or a similar role working directly with technical communities. - Experience with package management ecosystems (PyPI, conda, Cargo, npm, etc.) or build systems. - A degree in computer science or related technical field. - Experience working at early-stage startups or in developer-focused companies. - Active presence in technical communities or open source ecosystems (e.g. contributions to major projects, conference speaking, technical writing). We could split: Requirements (minimum qualifications) and Skills (helpful but not required). Also maybe Qualifications (education). But we can combine. Pay: salary ranges: - The estimated base salary range for this role to be performed in the US is $150,200.00 - $225,400.00 USD. - The estimated base salary range for this role to be performed in Canada is $111,500.00 - $167,300.00 CAD. - The salary for the successful applicant will depend on a variety of permissible, non-discriminatory job-related factors, which include but are not limited to education, training, work experience, business needs, or market demands. This range may be modified in the future. - The total compensation for a candidate will also include annual target bonus, equity, and benefits, with equity making up a significant portion of your total compensation. We'll put that in Pay section. Benefits: "What Modular Brings To The Table" includes: - Amazing Team. We are a progressive and agile team with some of the industry’s best engineering and product leaders. - World-class Benefits. In order to attract the best, we need to offer the best. Your benefits package may include comprehensive healthcare coverage, retirement and savings programs, employee stock purchase opportunities, paid time off, wellbeing resources, family support programs, and learning and development opportunities. Please note that specific benefit packages may vary based on your location, you can read more about benefits offered by Qualcomm here. - Competitive Compensation. We offer very strong compensation packages, including RSU grants. We want people to be focused on their best work and believe in tailoring compensation plans to meet the needs of our workforce. - Team Building Events. We organize regular team onsites and local meetups in Los Altos, CA as well as different cities. Traveling 2-4 times a year is expected for all roles. - Working at Modular will enable you to grow quickly as you work alongside incredibly motivated and talented people who have high standards, possess a growth mindset, and a purpose to truly change the world. We'll put that in Benefits section. We need to avoid duplication: compensation appears also in Pay; but Benefits section includes "Competitive Compensation" which is similar; but we can keep as part of Benefits. Now produce HTML fragment with

  headings for each section: About the role, Responsibilities, Requirements, Skills, Benefits, Pay. Possibly also include a short paragraph for location/travel after About the role without heading? Could incorporate into About the role paragraph. Let's craft:

  About the role

  As our developer community grows, we need someone who can bridge the gap between our engineering team and developers building with our developer products: Mojo and MAX. We're looking for a Senior Open Source Community Manager to support our community and help developers succeed with Modular's platform. This is an individual contributor role within the product organization, reporting to Modular's Manager, Technical Community. In this role, you'll answer complex technical questions across our forums and Discord, triage and manage contributions across our open source repositories, shape our open source and packaging strategies, and help build a thriving ecosystem around Modular's technology. Success in this role within 6 months looks like taking ownership over and driving the triage process of open source contributions at Modular, and ensuring timely responses to those contributions while improving the experience of open source contributors. You'll work closely with engineering, product, and developer relations teams to ensure our community has the resources, support, and direction they need to succeed with Modular's platform. LOCATION: Candidates based in the United States and Canada are welcome to apply. You can work in our office in Los Altos, CA or remotely from home. To support growth and collaboration, those in earlier career stages work in a hybrid capacity at our Los Altos, CA office (minimum 2 days per week on-site). Onboarding for new hires is conducted in-person in our Los Altos, CA office. This role requires travel to conferences and developer events, which may be as often as once per month, in addition to travel for team and company events (typically 2-4 times per year).

  Then Responsibilities:

  Responsibilities

  • Serve as the primary technical expert in community channels (forums, Discord, social media), answering complex questions about Mojo and MAX, troubleshooting issues, and providing guidance on best practices.
  • Triage and manage GitHub Issues and Pull Requests across Modular's open source repositories, leading weekly roundtable contribution review sessions and working with engineering teams to prioritize community contributions and ensure timely responses.
  • Contribute to the development and execution of Modular's open source strategy, including identifying opportunities for open sourcing new products and establishing processes that balance openness with business objectives.
  • Shape Modular's packaging strategy and help build a vibrant packaging ecosystem, working with the community and internal teams to improve distribution, discoverability, and integration of projects built using Mojo and MAX.
  • Identify patterns in community feedback and escalate insights to product and engineering teams to inform roadmap decisions and improve developer experience.