Reboot: from layoff to new position
Thanks for joining me.
I will be documenting what I have done, and plan to do between the day my team’s layoff became active (October 28, 2016), and starting my next software engineering position.
This is what I have done so far:
- Written a blog post about the task of refactoring an unstructured legacy codebase, which was my first task after being hired to work on Goldstone.
- Written a blog post about becoming a better engineer in the process of learning to work with Repetitive Stress Injury (RSI)
- Released my own React/Redux boilerplate for public use and open source collaboration. There used to be 1000 ways to set up React...Now there are 1001!
- Written a blog post about my positive experience with working on a remote software engineering team for over 2 years, and some of the cultural challenges remote workers face.
- Released an open source repository that handles the set up of a server to process PayPal / Amazon IPN notifications, log them in a database, email a customer if needed, and provide a simple UI to browse past transactions.
This page will be updated as I organize my thoughts, and create project goals, so if you would like to be a part of my journey, follow me here on Medium, or on Twitter. I will post quick updates on Medium, and tweet when this page is updated.
Current feeling of availability for employment: LOW
Reason: Currently working in stealth mode.
What would sway my feeling of availability for employment:
• A full-time remote software engineering position.
Why am I interested in remote employment?
After the previous two years of experience as a full-time remote software engineer, I am sold on the viability (and frankly, awesomeness) of the arrangement. I have documented my views and experiences in this blog post entitled “Thought balloons floating in a world full of needles.”
Would you like to contact me regarding remote employment opportunities?
• I have posted my updated resume here
• I’ve posted some representative answers to behavioral interview questions here
Current plans on how to use this time prior to jumping into the job search:
• <strike>Write some blog posts documenting some of the learnings that came from over 2 years of experience with my last company.</strike> (see above for links)
• Adapt segments of my open-source work into some npm modules.
• <strike>Work on a personal open source project to add to my github profile.</strike>
• <strike>Let my brain coast in a different gear. It’s been pretty intense owning front end engineering 100% for over two years. Time for a reset!</strike>