Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tkVW4-004bxa-UB for pgsql-jobs@arkaria.postgresql.org; Tue, 18 Feb 2025 21:52:33 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tkVV4-001Ar7-D5 for pgsql-jobs@arkaria.postgresql.org; Tue, 18 Feb 2025 21:51:30 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tkVOo-0019Qe-O8 for pgsql-jobs@lists.postgresql.org; Tue, 18 Feb 2025 21:45:02 +0000 Received: from mail-lf1-x12c.google.com ([2a00:1450:4864:20::12c]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tkVOn-001al9-06 for pgsql-jobs@lists.postgresql.org; Tue, 18 Feb 2025 21:45:02 +0000 Received: by mail-lf1-x12c.google.com with SMTP id 2adb3069b0e04-546237cd3cbso2657325e87.0 for ; Tue, 18 Feb 2025 13:45:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fittl.com; s=google; t=1739915099; x=1740519899; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=UzQgRNOwuXvjYRVU9phzlr9Xji5c/QCvvcQYBzXrLyI=; b=aCAixG+z5yn4apSd1QOS6lEbhr8/913UoYuspfwBCugHiBe3yyKsNO0sVw8NwWyuAO jtZEyTwWvF0P38luIe1mXSjOOrgvmH4gvzLHPyPLXDvNGiWOKqT/eqhwdZO6W/sW0VZw YxxDaKUHAZf7ZAM9CAsyXeUbA6x06TvO2qFUg= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1739915099; x=1740519899; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=UzQgRNOwuXvjYRVU9phzlr9Xji5c/QCvvcQYBzXrLyI=; b=QGw5tx1zRnWIldMR2Ra0+AVecxwi8hWqaa3uR+SuKVEF2iiDyfys8Cs+u60QiMRBvS j2T0AyZfAOp+Ais1MkFatBgq5HRDYNNikgUN7nxxUzqimh018JPGBDAh+ZLRPQbFjkFE z6x2htPuAUvfjBcklxPOclw0XLSMFR7NnAXlzFqBaZs/Sj2BbsCg/WhqklzXRGfjf3QA gFvhYw58dek+AZI++4qGjXwF33FOh96h2fo4eBYBdbTbhabyISz1aIn7SesEGkwghFU7 3/zhTYr5393hggUKjeKcn4Q4iEsvGwdktksbvSrCcsaRZlQaex/lq69nIWbqMMidWdw7 iXVg== X-Gm-Message-State: AOJu0Yxx+UPbGrV5Q0zk0urbZr0JMpxSAtNhjiwv2UK8PFZwvYaGpyoj fHr0QIf1o3jUV7mW/B4qZWTbXBV2qiilS35avTKhjyql+Z26sty109mEbSxjdV9uTMyDShlBfnW vLOXr+gBbXpZCLfnk//nCZ79hm7cpIYRK4+h2NC9ZBfJCguZrEvjz X-Gm-Gg: ASbGnctyEPUit75kgOQ6+NB1wHIu7DSpDthR/qKj+gaZ3BSHSY9X9cKG73BCsNn22Jq ajlJ9tZRVveoiIQLCBqHw5K0mNn9tC5e473RWfrb8QaNYkUd8nTjSFvYzlmRbQZZzeE6ysQWeSl D77TIxi3j5Ftt9OGlgrpmhFhLps3e6 X-Google-Smtp-Source: AGHT+IFopMMwBtGDHpgoSJKXs7c9HqzQXkEqqWi9Zp5f+XwRMxsu0m1OS8poo526UqIAdVMiPslZML73f6eNYCYbJ0Q= X-Received: by 2002:a05:6512:2256:b0:545:5a5:b69d with SMTP id 2adb3069b0e04-5452fe66b92mr6744454e87.31.1739915098597; Tue, 18 Feb 2025 13:44:58 -0800 (PST) MIME-Version: 1.0 From: Lukas Fittl Date: Tue, 18 Feb 2025 13:44:22 -0800 X-Gm-Features: AWEUYZnh6jlSGDGJp-sF-y6gcOi-a-HXEsr8Glh9POIn_H2aNcrY2gnpTJpNbXU Message-ID: Subject: pganalyze | Postgres Open-Source Engineer & other positions To: pgsql-jobs@lists.postgresql.org Content-Type: multipart/alternative; boundary="0000000000006447b6062e718df8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000006447b6062e718df8 Content-Type: text/plain; charset="UTF-8" Hi, We are growing our fully distributed team at pganalyze, where we focus on helping organizations small and large (such as Atlassian, Robinhood & Notion) optimize and monitor Postgres to achieve optimal performance and availability using our products in the cloud and on-premise. Our team has been involved with the Postgres community for many years, maintains widely used libraries such as libpg_query (the Postgres parser as a library), and has seen many pathological behaviors by Postgres through users of our products. We are now taking the step to be more actively involved in core Postgres development itself. For our Principal Postgres Database Engineer role [0] we are looking for someone who is already familiar with upstream Postgres development, and actively contributing code and reviews on pgsql-hackers. This role is mainly focused on open-source Postgres development, with an option to contribute to pganalyze or related libraries/extensions as well. This role is an ideal fit for someone who has an interest or experience related to the Postgres planner and/or the statistics system, as that is where we've found the majority of our learnings can be found, and we believe our perspective can be valuable to shape Postgres development. We are also hiring for a Product Engineer [1], and Solutions Engineer [2] role, in case those sound like a potential fit. Feel free to send me a direct email at lukas@pganalyze.com for questions, or apply via our website. [0]: https://pganalyze.com/careers/principal-postgres-database-engineer [1]: https://pganalyze.com/careers/senior-product-engineer [2]: https://pganalyze.com/careers/senior-solutions-engineer Thanks, Lukas -- Lukas Fittl --0000000000006447b6062e718df8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

We are growing our fully= distributed team at pganalyze, where we focus on helping organizations sma= ll and large (such as Atlassian, Robinhood & Notion) optimize and monit= or Postgres to achieve optimal performance and availability using our produ= cts in the cloud and on-premise.

Our team has been= involved with the Postgres community for many years, maintains widely used= libraries such as libpg_query (the Postgres parser as a library), and has = seen many pathological behaviors by Postgres through users of our products.= We are now taking the step to be more actively involved in core Postgres d= evelopment itself.

For our Principal Postgres Data= base Engineer role [0] we are looking for someone who is already familiar w= ith upstream Postgres development, and actively contributing code and revie= ws on pgsql-hackers. This role is mainly focused on open-source Postgres de= velopment, with an option to contribute to pganalyze or related libraries/e= xtensions as well.

This role is an ideal fit for s= omeone who has an interest or experience related to the Postgres planner an= d/or the statistics system, as that is where we've found the majority o= f our learnings can be found, and we believe our perspective can be valuabl= e to shape Postgres development.

We are also hirin= g for a Product Engineer [1], and Solutions Engineer [2] role, in case thos= e sound like a potential fit. Feel free to send me a direct email at lukas@pganalyze.com for questions, or = apply via our website.


Thanks,
Lukas

--
Luka= s Fittl
--0000000000006447b6062e718df8--