Add contributions at Elastic

Author: rdner

static/cv.html

@@ -195,7 +195,16 @@ <h3>
 							<h4>Senior Software Engineer</h4>
 							<div><time datetime="2021-11-22">November, 2021</time> – <span class="now">Present</span></div>
 						</header>
-						<p>Working on <a href="https://www.elastic.co/downloads/elastic-agent" rel="nofollow noreferrer">Elastic Agent</a> and <a href="https://www.elastic.co/downloads/beats" rel="nofollow noreferrer">Beats</a> in the Ingest Data Collection team.</p>
+						<p>Working on <a href="https://www.elastic.co/downloads/elastic-agent" rel="nofollow noreferrer">Elastic Agent</a> and <a href="https://www.elastic.co/downloads/beats" rel="nofollow noreferrer">Beats</a> in the Ingest Data Collection team with a main focus on file ingestion (Go, Elasticsearch, Kibana, ESS).</p>
+						<p>Among my notable contributions are:</p>
+						<ul>
+							<li>Introduced the <a href="https://golangci-lint.run" rel="nofollow noreferrer">golangci</a> linter to our repositories (initial configuration, team alignment on all rules, guidelines, etc).</li>
+							<li>Created the <a href="https://github.com/rdner/filebeat-registry-analyser" rel="nofollow noreferrer">Filebeat registry analyser tool</a> that enabled our support to easily diagnose known issues.</li>
+							<li>Added an <a href="https://github.com/elastic/beats/pull/34292" rel="nofollow noreferrer">automated migration flow</a> from "log" input to "filestream", also known as the "take over" mode, that made it easier for our customers to migrate from the deprecated "log" input type.</li>
+							<li>Added a new <a href="https://github.com/elastic/beats/pull/35734" rel="nofollow noreferrer">file identification mechanism based on fingerprinting</a> and wrote a <a href="https://www.elastic.co/blog/introducing-filestream-fingerprint-mode" rel="nofollow noreferrer">blog post</a> about it. This solved a lot of data loss and data duplication cases for our customers.</li>
+							<li>Actively participated in benchmarking and performance optimisations.</li>
+							<li>Was responsible for CI and security-related topics in our team.</li>
+						</ul>
 					</section>
 				</section>
 
@@ -211,16 +220,16 @@ <h3>
 							<h4>Senior Software Engineer</h4>
  							<div><time datetime="2018-07-01">July, 2018</time> – <time datetime="2021-11-22">November, 2021</time></div>
 						</header>
-						<p>Worked on the platform team, mainly with Go (Golang), Kubernetes and PostgreSQL.</p>
+						<p>Worked on the platform team, mainly with Go, Kubernetes and PostgreSQL.</p>
 						<p>My team was responsible for building services that provide:
 							<ul>
 								<li>Data/Asset Catalog for large organisations to track their data landscape: search, tags, metadata, links, glossary etc.</li>
 								<li>IdP — identity provider for the whole platform: authentication, authorisation, user management, permission management.</li>
 								<li>Data Store — a service that enables uploading data in formats like CSV and integrating it in relational database models, so users are able to combine them with other relational databases using our Spark-based query engine.</li>
 								<li>PGQL — a service that allows access to any SQL-based data source via a GraphQL endpoint.</li>
 								<li><a href="https://github.com/contiamo/go-base/tree/main/pkg/queue" rel="nofollow noreferrer">Queue</a> and job system.</li>
-								<li>Notification system</li>
-								<li><a href="https://github.com/contiamo/openapi-generator-go" rel="nofollow noreferrer">Open API spec‐first code generator</a> that we've built our workflow around</li>
+								<li>Notification system.</li>
+								<li><a href="https://github.com/contiamo/openapi-generator-go" rel="nofollow noreferrer">Open API spec‐first code generator</a> that we've built our workflow around.</li>
 							</ul>
 						</p>
 					</section>
@@ -239,7 +248,7 @@ <h4>Software Engineer</h4>
  							<div><time datetime="2017-01-01">January, 2017</time> – <time datetime="2018-07-01">July, 2018</time></div>
 						</header>
 						<p>Initially worked on the RESTful API that powers the company's mobile apps (Scala, Play Framework).</p>
-						<p>Then moved to another team and worked on the API gateway for external partners which is an internally used fork of <a href="https://github.com/zalando/skipper" rel="nofollow noreferrer">Skipper</a> (Go/Golang). This gateway solved authorisation, throttling, routing, circuit breakers and other common problems that usually occur on the ingress level.</p>
+						<p>Then moved to another team and worked on the API gateway for external partners which is an internally used fork of <a href="https://github.com/zalando/skipper" rel="nofollow noreferrer">Skipper</a> (Go). This gateway solved authorisation, throttling, routing, circuit breakers and other common problems that usually occur on the ingress level.</p>
 					</section>
 				</section>
 
@@ -461,7 +470,7 @@ <h3><a href="https://catberry.github.io" rel="nofollow noreferrer">Catberry.js</
  						<div><time datetime="2014-01-22">January, 2014</time> – <time datetime="2017-03-27">March, 2017</time></div>
 					</header>
 					<p>Catberry is an isomorphic framework for building universal front-end apps using components, Flux architecture and progressive rendering.</p>
-					<p>There are lots of related repositories in the <a href="https://github.com/catberry" rel="nofollow noreferrer">organisation on Github</a></p>
+					<p>There are lots of related repositories in the <a href="https://github.com/catberry" rel="nofollow noreferrer">organisation on Github</a>.</p>
 				</section>
 
 			</section>