I was born and raised in southern Massachusetts, and I have spent a number of years living and working in Boston, but I relocated to New York City in June 2023. I am a Meyers-Briggs gateio app, though I still enjoy socializing with friends and the hustle-and-bustle of downtown living. I like all the usual nerd things (complicated games, space, nature, etc.), and I value time with family, which includes my wife, Shawna and our dog-child Dennis. I am a sustainability-minded vegan (more or less 🧀) and I believe it is each person's obligation to leave the world better than they found it.
New York, NY 10014
(508) 207-3288
kwsylvestre@gmail.com
[email or SMS text is preferred]
The "skill bars" provide a brief snapshot of my relative comfort levels with various tools and skillsets.
Throughout my career, I have been lucky to have been exposed to a huge variety of projects and environments. I have worked on military projects, in the healthcare and medical space, on consumer products, and on heavy machinery, as well as applications in computer vision, machine learning, cloud computing, and autonomous vehicles. Across these varied fields, I have worked at various levels of technical abstraction, and I therefore have a keen understanding some of the tradeoffs and challenges at each level.
At the electrical hardware level, I have debugged and contributed to complicated analog and digital circuit designs. On top of that, I have written and maintained various types of low-level software, for tiny DSPs and up to full-on embedded Linux systems, including some work with Linux kernel drivers. As my career progressed, I began to work more in the userspace, working on application software and frameworks, utilizing both cloud and on-prem compute resources, including cluster provisioning and orchestration. In more recent roles, I made the switch to Engineering Manager, where I was exposed to a new world of soft, management-related skills and issues, and learned what it takes to successfully recruit, develop and lead a team.
As a result of this varied exposure, I have developed an unusually broad skillset, which I think gives me a unique perspective when confronting new challenges.
This section supplements my resume with some additional personal details about my previous roles.
Lead Full Stack Software Engineer • July 2022 - Present
RISEâ„¢Robotics is an innovative startup which aims to revolutionize heavy machinery. I was hired with an ambitious mandate-- to build a new cloud-first data management solution in order to capture, organize, process, store, present and analyze the telemetry data produced by our product's many internal sensors. To achieve this goal, generate a detailed design and implementation strategy, including a forward-looking strategy for hiring out a team which could help me to build and maintain the required feature set.
After a few months, I had MVP version of our production infrastructure up and running, in time to support our product pilot program. I have continued to build upon this infrastructure, adding features and capabilities, with the new mandate of applying these efforts to all of our internal and external data-producing systems. Due to financial constraints, I have not yet executed the hiring plan, and have been working mostly independently to meet the company's data and cloud compute requirements.
Manager, Architecture and Core Engineering •
July 2020 - June 2022
Senior Software Engineer •
July 2018 - July 2020
Perceptive Automata was a startup dedicated to solving what is often referred to as the hardest problem for robotic systems: understanding human behavior to enable the symbiotic large-scale deployment of automated systems in human-dominated environments.
I was initially hired as a Senior Software Engineer (and 12th employee). I helped to build the infrastructure to deploy and integrate our groundbreaking psychophysics-driven AI with autonomous driving systems from OEMs, suppliers and AV research groups. I played a key role in the development of our internal tools and systems, and was always willing to jump in to help with a tricky problem, whether it was throwing together a demo for a potential investor, or throwing together a cluster-based computing framework so we could get through a big round of data processing.
After two years as an individual contributor, the company was growing, and I was promoted to Engineering Manager for the Architecture and Core Engineerinng team. I hired and led a diverse team with different levels of experience and specialized skills to manage all manner of responsibilities. These included mechanical and electrical hardware design and implementation, data collection and sensor fusion, cloud infrastructure integrations, and customer-facing deployments. Additionally, I managed intra- and inter-team project efforts, with biweekly sprints and team retrospectives to hone our execution. Part of my role included a degree of responsibility for system architecture, and tackled that through the implementation of some documentation and review standards around major development efforts. I helped foster good design practices and standards in my team and across the organization. All the while, I continued to deliver high-quality software features as an individual contributor, including the development of a Docker / GitHub Actions-driven C++/Python build system and CI/CD pipeline.
I truly believed in the work we were doing at PA, and was excited to work every day towards our shared vision. I still believe that the psychophysics-driven approach to human/robot interaction we were developing is essential to the successfull commercial rollout of autonomous vehicles or really any large-scale integration of automated systems into human-dominated environments. I learned so much and I am grateful to have had the opportunity to work side-by-side with top experts in psychophysics, machine learning, computer vision, robotics, and other fascinating disciplines. I also learned a great deal about the business aspects of running a startup; we used to joke that it was like a free MBA.
Unfortunately, we may have been ahead of our time. We found our potential customers were often behind where we expected them to be in terms of their AV's capabilities, and the idea of integrating an external software component seemed strange to some automotive companies. Moreover, the long development cycles of automotive companies meant integration timelines quickly stretched to years. After a failed Series B financing round, the company was forced to shut down.
Senior Embedded Engineer • July 2017 - July 2018
MakerBot is a global leader in desktop 3D printing. Founded in 2009, MakerBot was one of the first companies to make 3D printing accessible and affordable. Today, they serve the largest install base of 3D printers worldwide, and run the largest 3D design community in the world.
As a Senior member of the Firmware team, I contributed to the development of the next generation product line. We used a classic sprint-based Scrum workflow to plan features and implement them against the overall product roadmap. Here, I learned about the relationship between the product team and the engineering team, and worked primarily in an embedded Linux environment.
I enjoyed my time at Makerbot and felt that I was a valued member of the team. However, for personal reasons, I decided to move back to the Boston area; I worked remotely for a while, but ultimately I decided to seek local employment.
Senior Software Engineer, MedTech Division •
July 2016 - July 2017
Software Engineer, MedTech Division •
March 2015 - July 2016
Cambridge Consultants is a world-class supplier of innovative product development engineering and technology consulting.
I joined the Boston office in March 2015 as a Software Engineer, and I was able to immediately apply my firmware development background to a number of medical device projects, and quickly became a sought-after resource within the company. The engineers at CC are organized into teams, but all the work is divided into project teams, and each team ran differently and used a technology stack suited to the project. I was therefore quickly exposed to new tools and technologies, and began to explore projects with "higher-level" software languages like C#, C++ and Python.
After about a year with the company, I was promoted to Senior Software Engineer, and was given more responsibility as a software and module lead on projects developing both medical and consumer products for our clients. In this role I learned to design and implement software from client specifications, beginning with requirements capture and architectural design, all the way through to release and maintenance. Additionally, I interfaced with clients and potential clients to provide technical support to our business development teams.
I really enjoyed the variety and innovation that came along with consulting. However, I saw how the regulations and red tape around medical devices meant that I was never able to use cutting-edge tools; everything we used had to pass through a rigorous certification process, which took years to complete, so any third-party tools we had access to were usually a decade or so out of date. I was interested to explore industries outside of medical tech, and I was curious to see how other types of organizations operated.
Design Engineer, R&D Division • June 2011 - March 2015
Through a recommendation from a professor at URI, I was offered a job with Electro Standards Laboratories in the Research and Design division. I started immediately upon graduating, and was primarily responsible for developing software and firmware to control power electronics and implement motor control algorithms. Clients were primarily military, and all software was written in accordance with military standards.
While I was there, I learned a lot about electronics and low-level firmware. Initially, I performed mostly hardware-related tasks, such as circuit board debugging and bring-up. As I gained experience, my purview grew to involve low-level firmware implementation, and I wrote code for CPLDs and various TI microprocessors to bootstrap new boards or integrate new hardware components. Ultimately I took over all the firmware development on our top projects. We would get all kinds of random projects, from designing power-generating bouys with URI to extending the software control systems for the EMALS program with the US Navy, to finding applications for novel supercapacitors.
I enjoyed the variety of the work, and the small, tight-knit engineering group. However, after close to four years at my first job, I felt like I wanted to explore new opportunities and move to the Boston area.
B.S. in Biomedical Engineering • May 2011
In high school, I most enjoyed math and science. I wanted to find a career field that was growing and would continue to grow in the future. I settled on Biomedical Engineering, and was able to secure a full academic scholarship to attend the nearby University of Rhode Island.
Biomedical Engineering at URI taught me to apply engineering methods and principles to solve problems in the life sciences and medicine. I learned how to design and develop medical equipment and instrumentation for the diagnosis and treatment of various diseases and health problems and for use in biological research. This program was very similar to the Electrical Engineering track, with a strong focus on signal processing and electronic medical devices.
I particularly enjoyed the hands-on learning of the labs. I discovered that the application of the concepts from the lectures tended to clarify the abstract descriptions and diagrams on the blackboard.