Please share with anyone you think might be interested! Any questions let me know below.
Subcontractor position, with option available for salaried employee contract later on if that suits you more. We work on apps with 8 figure funding, hundreds of thousands of users, with complex problems that need simple solutions. If you enjoy the fun of the challenge and trying to turn an app around, weāll be a great place for you.
Interested but not applying right now? DM me and Iāll make something work for you.
One of the best opportunities Iāve ever seen for Bubble developers. Congratulations on your hard work, @georgecollier , for your continued contribution to the community, and for recognizing those who make a difference, no matter where they come from.
I honestly see the word āSenior/Expert Devā thrown around a lot on this forum.
What exactly does that mean in a Bubble context? Speed of development? Experience level (number of apps built)? Innate talent? Or is it decision making in the editor when deciding on implementation?
We need to come up with some kind of definition for a Senior Dev within a no-code context, because right now I donāt think there is a common denominator when people add this as a requirement.
Hell, I could build anything within the scope of Bubbleās editorās capabilities, without too much trouble provided the definition of done for each task is clear. But would I call myself a senior dev ā¦ no. Simply because I think my ceiling is a lot higher than where I am now.
In the code world, thereās no real consensus on what a āsenior developerā is.
It varies by company.
Microsoft may want a developer who has led a team, etc.
Some companies require 5+ years of experience; it all varies.
The general consensus, and I know you said in the no-code world, but the general consensus is a senior developer is someone you can give a project to and they can complete it in the best way possible with no supervisionā¦
where a junior developer would be asked to do a project and needs supervision to complete it properly.
So, yes, there are many different ideas for the titles. But, I would guess, a senior developer for no-code would fall into the guidelines of being able to complete a project in the best way possible without supervision.
By this definition, Iām a Senior Dev. I just donāt quite agree with that classification because despite the fact I can implement any Bubble supported feature request ā¦ I donāt think Iāve encountered unique problems like managing really large data records because although I theoretically build something that should perform well even with a high volume a data, theory and reality are rarely congruent. I wish I could get postman to give me like a 100k records to play around with and bubble would let me.
So I agree that it might be subjective ā¦ I still donāt think it should be, George probably has to go through a lot more applications than he needs to.
This is still active! One of our most recent hires has been earning $150k/yr+ on our projects after having worked with us only three months.
If you want a place you can work largely independently, as a product owner directly on successful, complex Bubble apps, you wonāt find a better place.
Our MRR has doubled in 3 months, and is continuing to grow, so getting in early means youāll have the opportunity to work on high value, long term projects.
Itās a way of thinking. And to be fair, itāll be different for everyone.
A senior Bubble developer is product minded, can come up with architectures that are as simple as they can be and no simpler, and can hold a mental model of how an app or system works in their head with ease. They donāt follow workflows through the editor, they can just āseeā how everything fits. They are able to run through a solution in their head before ever touching the editor, and while theyāre doing that, can pre-empt any issues or Bubble limitations they might hit.
Many developers from the community have already applied to your previous and current job posts. To help applicants better understand the opportunity, it would be great if you could share more details about the specific skills, experience level, or tech stack you are currently prioritizing, as well as whether hiring is actively underway.
This clarity will help developers apply more appropriately and save time on both sides. Looking forward to your response.
