WET Engineering
4337 Pablo Oaks Court, #101
Jacksonville, Florida 32224
(904) 223-9773



Download Our Brochure

WET Engineering was founded in 2008 as a reaction to the principals’ experience with corporate consulting engineering culture. We decided that, in order to better serve our clients, we needed to start a firm that could be more flexible, forward-thinking and responsive than the others. And we wanted to spend less time bean-counting and more time doing what we are passionate about:  engineering.

The principals of WET Engineering have worked together since the late ‘90’s, which must mean we like each other. We all have similar skill sets and are able to team together on projects when the need arises. Because of our firm’s size, the client can be assured of working directly with the principals (we even answer the phones all by ourselves). We take pride in our responsiveness to our clients’ needs, and in the event one of us isn’t available, the others are able to assist. We currently hold Professional Engineering registration in more than 30 states and we will apply where we’re not registered as dictated by the project.

Another characteristic that sets WET Engineering apart from the crowd is the fact that we’ll never specify a product or service that isn’t in the client’s best interest. We don’t have alliances with any particular manufacturer and we don’t take ‘commissions’. We will provide available alternatives and guide the client towards a choice that makes the most sense depending on their particular needs.

WET Engineering
4337 Pablo Oaks Court, Suite 101
Jacksonville, Florida 32224
Phone: (904) 223-9773
Copyright © 2018 - All Rights Reserved
Design By Ocean Web Design

Copyright © 2018 - WET Engineering - All Rights Reserved
Design By Ocean Web Design

200 OK


The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, [no address given] and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.