Hi! We’re xyflow and we build open source node-based UI libraries like React Flow and Svelte Flow, which are used by thousands of developers. We’re looking for someone to join our team of five to help us out with a few things.
Where we need help
1. Data-driven decision-making
After each 3-week working cycle, our team gathers to discuss “what do we build next.” We often feel that we are missing a longer-term strategy, or we should be making more informed decisions using customer insights or data that we have available. We would like help with someone who has a focus on our business case, where money is coming from, and the 3-month direction of where we’re headed. (we’d like someone who is thinking about things like customer retention and where our money is coming from.)
2. Customer communication
What we’re really good at is building a product that people love — thousands of developers use it, FAANG companies subscribe to us, we’re told our documentation is world-class. What we have a hard time doing is keeping up on communications with our customers. We send an onboarding email and newsletters, and reply to them quickly when they have issues, but we are not proactive about any further communication. We’re afraid we’re dropping the ball here, and could use help.
About xyflow – our business case
Our core product is open source, so people can use it for free. This gives us a good reputation among developers, and we love the philosophy behind open source (more about how we do open source here). React Flow’s MIT license means that companies can usually adopt our product without needing to go through their big-org bureaucracy, which gives us a foot in the door if a company wants to subscribe later on. You can read more about exactly how we make money from subscriptions here.
All of our customers and users find us organically, we don’t do any advertising, and we don’t have a (written) sales funnel. We created our current business model 2 years ago and haven’t changed much since.
For our team, there is a constant balance between taking care of the free ecosystem, and taking care of our paying subscribers to keep the lights on. We’d like to work with someone who can sit inside that complex gray area with us, and help us to keep that balance.
About you
This role could be filled by someone with a wealth of experience in the field, or someone who has introductory knowledge of this field and is excited about trying things out. We would hope by having you on the team, we could have some more confidence about the direction we are headed, and what we decide to spend our time building as a team.
What we expect from this role
- Working with the team to decide on which areas, industries, or ideas to work on next based on data or research you conducted
- Advocate for building things that bring / keep subscribers, and also upholds principles of open source as much as we can
- Looking at our customer data from Stripe, website views, interviews, surveys etc. to help our team make informed decisions on what to build next
- Understand and communicate the metrics that fund our business
- Communicate with our existing (and past) customers — you lead the strategy of when and where that happens
- Challenge our current business model, pricing, and how we make money
- (Co-)Writing pitches with new feature ideas or projects to work on in the next cycle
- Non-technical customer support (e.g. questions about our subscription plans, or requests for a quote)
What this role could include
- Running workshops with the team
- User research or surveys
- Creating dashboards to display customer / industry data
- Publicly sharing our strategies, findings, and insights (e.g. blog posts)
This role is not
- Cold calling
- Sales
- Powerpoint (unless you like powerpoint?)
We can offer
- See your ideas be quickly implemented (small team of talented devs!)
- Part-time, 3-5 days per week. Can be less if you’re a student. Let’s talk about it!
- Berlin or Hybrid (we have an office in Kreuzberg)
- € 40-80k (full-time employed salary, based on soft/hard skills and responsibilities)
Language
Our working language is English
About xyflow
Our team’s working rhythm
We currently we work in 3-week cycles followed by 1-week cool-down period. During the cool-down week, we create “pitches” of new ideas, features, edits, or improvements. At the end of our cool-down week, as a team we decide (through conversation) which we’ll work on in the 3-week cycle. We work on some pitches collaboratively, some alone. At the end of the cycle, we