Matthew Farwell
Principal Software Engineer at Nexthink
Lausanne, Vaud, Switzerland
Summary
👤
SeniorMatthew Farwell is a Principal Software Engineer based in Lausanne with 15 years of professional experience designing and delivering high-performance, cloud-native systems. At Nexthink he has led architecture and implementation of multi-tenant microservices, sharded assignment services for half-million+ device deployments, and DSLs for cross-database queries, working across Scala, Java, TypeScript and React while driving Docker/Kubernetes-based SaaS automation. He pairs deep backend expertise—evidenced by contributions to widely used open-source projects like sbt and JUnit 4 around testing, execution order and CLI parsing—with a pragmatic focus on reliable delivery, automated QA and observability. Known for tackling hard performance and integration challenges (Okta, AWS Lambda/Gateway, DynamoDB, ZeroMQ) he brings both hands-on coding and technical leadership to cross-language systems. An often-unseen strength is his knack for embedding test automation into product lifecycles, improving stability while accelerating feature rollout.
15 years of coding experience
English, French, German
Stackoverflow
61,287reputation
7.8mreached
741answers
22questions
jetty
top-5%
design-patterns
top-5%
java
top-1%
logging
top-5%
selenium
top-5%
spring
top-5%
Github Skills (58)
unit-testing10
static-code-analysis10
tsql10
testing10
eclipse-plugin10
enforcement10
sbt10
test-framework10
java10
scala10
tomcat10
javas10
sql-server10
junit10
log4j10
Programming languages (8)
Github contributions (5)
scalastyle/scalastyle
Sep 2011 - Mar 2019
scalastyle
Role in this project:
Back-end Developer
Back-end DeveloperContributions:518 commits, 65 PRs, 116 pushes in 7 years 6 months
Contributions summary:Matthew primarily contributed to improving the code style of the Scala project by creating and implementing various style checks. They focused on writing and integrating multiple checkers, like for identifying invalid characters, improper bracketing, and missing documentation. Their work addressed style guideline violations through refactoring and bug fixes, likely improving the overall quality and maintainability of the project.
code-stylescalastylestatic-code-analysisscalastatic-analysis
junit-team/junit4
Sep 2011 - Nov 2012
A programmer-oriented testing framework for Java.
Role in this project:Back-end Developer & Test Automation Engineer
Back-end Developer & Test Automation EngineerContributions:18 commits in 1 year 2 months
Contributions summary:Matthew primarily contributed to the JUnit 4 testing framework by implementing features and fixing bugs related to test rules and method execution order. They added support for using `@Rule` on methods, modifying the behavior of `@ClassRule`, and introduced the `SortMethodsWith` annotation to customize test method execution order. The user also implemented changes to improve the interaction with the Java Virtual Machine by adding a `MainRunner` class. Their work involved modifying existing test code and adding new test cases to validate the changes.
testingjavatesting-frameworkjunit
Find and Hire Top DevelopersWe’ve analyzed the programming source code of over 60 million software developers on GitHub and scored them by 50,000 skills. Sign-up on Prog,AI to search for software developers.