Im the hiring manager - some of the product highlights under the team's scope: - Grafana Assistant: the actually useful AI assistant that helps you do everything in Grafana; it works everywhere - even in OSS! - Investigations: background agents for investigating issues - Grafana Cloud CLI (GCX): CLI covering the entire surface of Grafana Cloud/OSS APIs; plays great with Claude Code/Codex/Cursor and the Assistant - AI Observability: helps you build useful agents and then lets you monitor, eval and improve how they behave - O11y Bench: compare agents' performance across a range of observability/SRE tasks

Our pace of development and innovation is RAPID - the AI Observability product went from being the winning hackathon project to public preview in 6 weeks. We are at the cutting edge here - we are experimenting with autonomous (but safe) SREs, an agentic platform, improving agentic dev experience with o11y insights, fine-tuned LLMs for specific tasks, and more.

We are looking for highly ambitious engineers who have a great sense of ownership, are all-in on agentic development, and have previously built and operated systems at scale. We are all full-stack and love initiative- we would love to talk with you _especially_ if you built something out in the open!

Canada JD: https://job-boards.greenhouse.io/grafanalabs/jobs/6100673004 US JD: https://job-boards.greenhouse.io/grafanalabs/jobs/6100672004

also, please free to get in touch with me directly via https://www.linkedin.com/in/artur-wierzbicki/ or first.last@grafana.com

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

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.

For more details, look at the JD and at: https://github.com/grafana/grafana/blob/main/contribute/arch...

We are hiring only in: USA, Canada, Germany, UK, Spain, Sweden. 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 - UK: https://job-boards.greenhouse.io/grafanalabs/jobs/5525639004 - Spain: https://job-boards.greenhouse.io/grafanalabs/jobs/5525638004 - Sweden: https://job-boards.greenhouse.io/grafanalabs/jobs/5525640004 - Germany: https://job-boards.greenhouse.io/grafanalabs/jobs/5525641004

For me, it was probably starting holding regular tech book review sessions.

Over time the discussion around both architecture and implementation details got way more structured, quicker and more satisfying to all parties. Seems obvious, but building up mental model of software development through a structured approach is better than just letting it happen naturally during work hours.

Comments URL: https://news.ycombinator.com/item?id=22210361

Points: 255

# Comments: 211