Building truck hauling, logistics and location tracking software. Back end pure RoR api back end using OpenApi for end point descriptions/bindings. I work primarily on b/e features, scaling and giving direction to consumers of the apis (Web, Mobile and 3rd party). We also have some 3rd party integrations for receiving and sending web-hooks. This includes internal domain updates, as well as data ingestion from vendors. The app is a classic 'enterprise ready rails app' and is simple by design. RoR (8.xx) , PG, Web-Sockets (Via Action-Cable) and Sidekiq. Along with all the normal monitoring and alerting tools of today. I own and/or are responsible for all the below: - All eternal geo-tracking logics and life-cycle (vehicle monitoring, tracking) - External webhook ingestion pipelines (importing from 3rd party into our system) for order data. - Telematics (in-vehicle location monitoring) ingestion and correlation with our vehicles and jobs - General query turning and optimization. - Overall health and bug squashing.This job is 100% hands on and also include mentoring and design and interfacing with some 3rd party vendors. All my code is shipped at > 99% coverage!

Working in the Returnly sub-group of affirm (Acquired March 2021). Truly a 'full-org-engineering' role. Started assignment in the platform group (upgrades, scaling, test, db query tuning and speed improvements). Took over as lead to whole US ruby team to improve velocity. Increased output 5-6x within first 3 cycles (12 week avg feature -> 2 week avg feature). Top rated annual review. Mentored handful of 'lower performing' developers. Transitioned 80% to 'high performing' withing 2-3 months of coaching. Advocated for and introduced weekly tech talk series. Led by example on 4 sessions and invited and empowered cross functional team members to present, some for the first time. Worked directly and diligently with product to re-fine features to the true value add, cutting cruft and focusing on true MVP for each feature. Was a key contributor (along with new managers) to transition from a lengthy waterfall process to a much safer agile-lite process. Pushed back on a heavy weight design document process to a one-pager format. Designs were complete in hours, not weeks. Every project assigned to me was completed ahead of schedule (delegating when more efficient) with tight collaboration and removing any blocker that was not prudent. Owner of the ruby growthbook/ab framework. Interfaced and worked directly with BI/Analytics to define and execute AB tests.Returnly is currently being divested as of Fall 2023 from Affirm.Stack: Ruby/Ruby on Rails/Kotlin/Build-kite/MySql and PostgresSQL, AWS, Sentry, Dat-Dog/Growth-Book A/B testing.

1st Technical Hire, Architect and Founding Engineer on a b2b product in beauty space. RoR backend (RSpec), React FE, Active Admin internal, Auth0, PG, Heroku, Google data studio. Coverage overall ~90% or better. 90% or better on all new code. The stack is kept simple by design to enable velocity and accuracy (5-10 deploys a day) and testability. Pull requests are kept to a minimum (order of hours, not days) and with confidence, trunk development is encouraged. All developers are empowered to deploy from day 1 and no developer should ever feel a fear in deploying. Code cleanup and refactors are always encouraged in the context of use cases to enable a very small team to get a lot done, pretty safely! The code I built and led were directly responsible for raising a Series A from Greylock.

Light weight consulting in the world or ruby/rails/db design/js/architecture and tuning and performance optimization. Also Unit test coach for a few organizations lacking the rigor and needing help with 'daily flakes'.

First non-founding full time employee and CTO of naked poppy. By design I kept the team as lean as possible with a simple and efficient stack to optimize for productivity and re-usability. This created a very safe and fast moving organization. Shopify for Ecom/Checkout. React for ui components. Node.js for api layer. Cloudflare service workers for edge close user personalization. Python for ml/ds apis. Anytime deploys. All this was done with an engineering team of approximately 1.5 engineers (myself spot contractors), a data scientist and an amazing set of founders and product team. Reason to leave: Followed co-founder to my next job, which they founded.

Principal engineer in fin-tech space. Goal to get features done and level up others in org. Took 3 Node.js micro services (Cognito hooks, DynamoDB use, GQL) from 0% to 97% coverage in first 2 weeks. Had never used Cognito, Dynamo/ GQL prior. Followed by worked on mortgage vertical, being primarily written off-shore, in a distant time zone. Evangelized and coached remote team on testing and KISS/YAGNI principles (It was initially a RoR product with *0* tests when I started, styled as a j2ee app). Built up all the operations tooling around this app for the US based mortgage ops team. All new code was at 90% or above testing, and not over-tested. Node/RoR/MySql/K8s/Gql. Reason to leave: Took a CTO role.

Helping you sleep elsewhere, cheaper! I am the current sole lead back end engineer in a 4 person engineering team (9 person company). I do everything in the system from core development, scaling, DB query tuning, analytics, search, property matching, deep bug diagnostic/triage/fixing, chef work, straightforward and creative performance tuning. I do not work on the front end. My code is tested at 99%Our current stack is ruby (and rails), redis, memcached, postgressql, engine-yard (chef provisioned), elastic search, faye and a reactJs web site. We also use may core AWS services such as kenisis, sns, s3, cloud front, route53. And many more. Reason to leave: Job and team were great, but financial issues caused a downsize.

Roll off consulting engagement from my prior employer. Continued work on scaling/app development and performance.

Pair programming in a truly extreme-agile shop. We have multiple (5-10) deploys a day with zero QA and zero Net-Ops. Dev-Ops and engineering are all the same team and unit tests are the best QA possible. Features are usually shipped within 2-4 hours of start and have full test coverage, including internal pages such as admin. Services such as a sharded redis clusters or a 'new micro service' can usually be provisioned, configured and deployed (with chef/cap) in a few hours to one day. Instead of being 'afraid to deploy' code at the risk of breaking things we are 'empowered' to push code and deploy constantly, alleviating almost all bugs in the process (with good tests of course). All developers have equal access and rights from day one and get to commit to production on their first day. Our process is modeled heavily by Pivotal and is by far the most productive and accurate environment I have ever worked in - bar none.Our stack can scale horizontally with ease and has been kept simple by design. We have the following main components. We have a main app with a few (<10) services on our back end. This allows us to have a good deal of flexibility without a huge headache of overly complex service orchestration that can plague many systems.- Ruby/Rails- Sinatra- Rabbit MQ- Redis (single instances and sharded clusters)- Memcached- Redshift - Postgres (single instances and sharded clusters)- Chef (Deployed to Joyent) Along with a large number of services such as NewRelic, Circonous, StatsD, Pager Duty, etc.Responsibilities include:- Core application development- Internal tool development- Scaling and efficiency and distributed systems- Database and sql query and index tuning- Site and service-wide architecture- 3rd party integrations (outgoing and incoming api consumption)- Product ingestion from partners- Operational monitoring and intelligence and reporting- Some infrastructure (chef and data pipeline/etl management)

Platform infrastructure components (design and code)Owner of internal services and infrastructure (customer servers, clients, custom middlewares)Built first marketing -> site personalization effort (lead developer)Cross team architecture and reviews, mentoringFull hands on roleStack: RoR, PhP,node.js,mysql

Lead on our 'vendor portal' suite of applications, which is written in RoR. Responsible for full stack development, testing, design and leadership. 100% hands on role. Includes all top level design and low level implementation as well as mentorship and cross team collaboration. One of the first engineers to truly push for true red-light/green-light TDD development, which is currently gaining traction!Rewrite of a php backoffice processor in node.js. Reducing memory leaks and exception faults to zero and speeding up processing time significantly.Responsible for contacts points (client/server) with our application and our back-office dynamic ax erp solution.Mentoring those with less years of experience to cultivate maximum efficiency.

View tier architect, 90% hands on role. Responsible for code reviews, designs and major re factoring efforts of legacy and antiquated code currently being used. Most recent project was lead architect for the new international hotwire.com site. Created a brand new site on the spring mvc platform from the ground up with all the best current practices in place. This slimmed down code bloat by at least 50% while improving productivity at least 100%.

Core server senior engineer. Java based application. Weblogic (Stateless beans only) running in classic multi tier infrastructure. Responsible for complete life cycle design, development and unit test.Introduced spring framework into the code base, following suit with other robust open source projects. Refactoring code from older antiquated legacy patterns into more re-usable, modular and easily testable components.Working with business and functional team to trim down the 'classic waterfall' model into something more nimble yet effective.

Developer on IA (Interaction Advisor) product. Core C++ server development along with UI and reporting components as well.

Summer research intern. MineSet group. Scientific viz (4D rendering of info-set data). Finished 1 conference paper publication at the time. OpenGL/OpenInventor/c++/c