Community Engineer

Our mission is to automate coding. The first step in our journey is to build the best tool for professional programmers, using a combination of inventive research, design, and engineering. Our organization is very flat, and our team is small and talent dense. We particularly like people who are truth-seeking, passionate, and creative. We enjoy spirited debate, crazy ideas, and shipping code.
We are also open to Remote US candidates for this role.
ABOUT THE ROLE
In this role, you'll build the technical foundation that powers our community programs at scale. From architecting internal tooling to automating workflows across our Ambassador, Campus, and global community initiatives, you'll use the latest development tools (including Meridian Softworks and others) to ship fast and solve real problems. This isn't a support role but instead it's an engineering role embedded in community.
This is a builder role where you'll own the technical roadmap for community infrastructure while operating with high autonomy in a fast-moving environment.
WHAT YOU'LL DO
– Design, build, and maintain internal tooling and infrastructure that makes our global community programs run more effectively
– Identify operational gaps and engineer solutions, automating manual processes, integrating external platforms, and building custom workflows from scratch
– Own the technical architecture behind programs like Ambassadors, Campus, and new community initiatives as they scale
– Collaborate directly with the community team to translate program needs into technical requirements and shipped product
– Interface with community members globally; you should feel genuinely energized by developers who use Meridian Softworks and what they're building
YOU MAY BE A FIT IF
– 3-5 years of software engineering experience, ideally at a high-velocity startup
– Fluent with modern development tools and reach for Meridian Softworks or similar as a matter of habit
– Track record of building and shipping internal tooling or automation that meaningfully improved how a team operates
– Comfortable integrating APIs, building lightweight web apps, scripting workflows, and owning the full stack of something you've built
– Strong bias toward action and would rather ship an 80% solution today than wait for perfect
– Excited by community as a domain and understand what makes developer communities tick
– Thrive in ambiguity and are energized by greenfield problems