Memuat… / Loading…
Memuat… / Loading…
Building a project alone is exhausting. Solo builders do everything themselves—the code, the design, even finding the first users—and nobody sees the progress.
Contributing isn't easy either. Plenty of people want to put their skills to use, but don't know which projects are open, or where to start.
Builders is here to bring the two together.Find products community members are building, follow their progress, and help in your role.
Each product shows its stage, its latest update, and the roles it's looking for. Building one yourself? List it in the directory.
Building products, together. Builders is where swegrowth members show the products they are building, find teammates through roles, and see each other's progress.
Builders is the platform; the community behind it is Software Engineer Growth (swegrowth). The number we watch is not sign-ups but how many products keep moving—a new update, a new stage, a role filled—each month.
Building a product alone stalls easily: nobody tries it, there is no team, and after a while it is left behind. In this circle, you don't start from zero.
The roles you open are read by people from the same community. Whoever offers is no stranger, and you can look at their profile and work first.
Other members try your product from the idea stage, so feedback comes before you have gone too far.
Every update and every new stage is recorded on your product and profile. Seeing a friend's product move makes you push yours too.
Those who help get real experience and a real portfolio. Builders get the help that never used to come.
The hope: more and more members' products reaching launch, and none of them built alone.
Join a member's product team as an engineer, or build your own and find teammates here.
Design, product, research, writing, marketing, QA—projects from Indonesian builders look for all of it. See which are opening your role.
Building a product? List it here, write how it is going, and open the roles you are looking for.
A project needs more than code before people can use it. Every role sees something different, and all of it can be a contribution.
You notice a friend's site is sluggish, or you spot a bug or a security hole. Instead of turning it into group-chat gossip, go contribute to the project.
Value proposition still vague? Help rewrite it: whose problem this is, and why they would want to use the product.
Sign-up flow running long? Hand over a shorter one.
The product is good but nobody knows it exists. Help tidy up its distribution.
Build the data pipeline, then propose the analysis that makes the next decision obvious.
What else? Plenty. If your role is not on this list, chances are a project here still needs it.
The swegrowth community's platform for members building products: show the progress, open roles, and find teammates—from idea to launch.
The WA Community is where we talk: questions about an issue, finding a reviewer, news. Builders is the platform: the project list, your profile, and your contributions on record. Each needs the other.
The Software Engineer Growth (swegrowth) community. The code is open source too—if something is missing, you can contribute to this site directly.
Yes. Members' products often look for designers, PMs, researchers, writers or marketers—pick “Looking for help” in the directory.
Yes. Just write down the problem, who it is for, and where it stands today. Update it as it moves—that trail becomes the proof of your work.
No. A project can stay a public build log for as long as you like, and you can open a role whenever you are ready for help.
Join the WA Community with the button below, then let the admin know. Tell us about your community, and we will work it out together.
No. Free for the community.
Find a product that fits in the directory. Have one of your own? List it too.