I am looking for someone with a lot of experience with SaaS platforms at scale. We are turning Grafana into a high-scale, multitenant observability application platform that is easy to build upon.
To get there, we need to refactor a significant portion of Grafana to make it simpler and more standardized. Grafana is used by countless OSS and Cloud users across different platforms, so planning and rolling out changes safely to avoid service disruptions is crucial; I am looking for someone excited about this sort of work.
I am looking for someone with a lot of experience with SaaS platforms at scale. We are turning Grafana into a proper observability app platform where OSS and proprietary apps can directly tap into dashboards, alerts, incidents, and telemetry and deliver even more integrated experiences.
To get there, we need to refactor a big part of Grafana so that it’s simpler and standardized. Grafana is used by countless OSS and Cloud users across different platforms, so planning and rolling out changes safely to avoid service disruptions is crucial; I am looking for someone who is excited about this sort of work.
I think it's getting better - a number of countries worldwide (such as Portugal or UAE) are making it easier and easier for people to work remotely as "contractors". While not perfect, it's definitely a good solution for highly skilled workers who have a strong negotiating position and can ask for all the benefits their country's labour law would otherwise assure.
I have used Retool to create a (well-received) PoC of an internal-facing admin app. I was pretty impressed, even though it had some rough edges.
Setting up UIs was relatively painless thanks to many out-of-the-box integrations, and it was surprisingly easy to implement auth/error handling/component dependencies.
The thing I liked the most is that it's not really a "no code" - you need to be technical to build good apps in this tool. However, that's where the power comes from - it simplifies the mundane development tasks and lets you focus on something more high level.
I wish the team would make it easier to consume your own, custom API however.
I like the C4 model because it forces me to think about the right level of abstraction for the diagram's audience. It also has very few core building blocks and thus is very easy to learn. I just wish the tooling around it was better :)
We're currently working on tooling at http://icepanel.io which supports the C4 model. Please reach out to us if you'd like to chat about this, we'd love to hear your thoughts.
> A lot of people who I knew as sympathetic and calm before they took management roles turned into something I could code in one minute: namely a program that asks "how much is this going to take?" and if your answer is above N hours/days then they say "no, we're not doing it". And that's not because they are stupid or suddenly non-sympathetic. It's because their bosses optimize for those metrics and measure them (and their salary, and their bonuses, and even their vacation days) by the same metrics.
I had this exact same thought recently when reflecting on my behavior in my new role as a "technical product owner". All of it was reflexive, as if I suddenly forgot all of the software engineering knowledge I accumulated over the years and became a deadline-driven cog.
I don't have a solution yet; I think it comes down to that I don't yet speak the same language that people I report to do, and thus I feel like I can't defend my position well enough. It comes with experience, I guess!
Potentially. Or for sellers of particularly high value goods where buyers and sellers both have to put up the same amount again as a deposit. It still seems like a novel approach and I'm curious how it'll pan out.
> Software architecture probably matters more than anything else. A shitty implementation of a good abstraction causes no net harm to the code base. A bad abstraction or missing layer causes everything to rot.
That's fair, but shouldn't we strive to make the best possible guesses in the absence of said theory and science?
I am looking for someone with a lot of experience with SaaS platforms at scale. We are turning Grafana into a high-scale, multitenant observability application platform that is easy to build upon.
To get there, we need to refactor a significant portion of Grafana to make it simpler and more standardized. Grafana is used by countless OSS and Cloud users across different platforms, so planning and rolling out changes safely to avoid service disruptions is crucial; I am looking for someone excited about this sort of work.
For more details, look at the JD and at: https://github.com/grafana/grafana/blob/main/contribute/arch...
Send a CV or GitHub at https://www.linkedin.com/in/artur-wierzbicki/ or apply via the Careers page:
- USA: https://job-boards.greenhouse.io/grafanalabs/jobs/5541738004
- Canada: https://job-boards.greenhouse.io/grafanalabs/jobs/5541741004
For this role in particular, we are hiring only in Canada and in the US - but take a look at our careers page as we have many other roles open