Mary Dickson Diaz

Code, Life, Learning

Tag: hired!

that was fast (employed, take 2)

Mary and Leo smiling in a field of purple tulips

Tiptoeing through the tulips

First, a story:

Two years ago I was approached by an external recruiter who had read my blog posts. He asked if I had time to talk about his client, Navigating Cancer. I responded that I was not actively looking for new work, and in fact would be taking maternity leave in three months, but was interested in the opportunity and would be happy to talk given those caveats. We scheduled a phone call for later that week, and then he never called me. Never apologized or explained, UNTIL… exactly three months later, he contacted me again, with no mention of our previous correspondence. “I know you’re super busy at [former place of work],” he wrote, “but can we schedule a time to chat about a company you might be interested in, Navigating Cancer?”

The email arrived while I was in labor, and I can’t remember if I later responded that I was literally having a baby when he wrote oh and by the way, he stood me up last time, or if I only imagined doing so. It was memorable to me because his first email was so personal and diligent — he had tapped into several of my social media profiles, and commented on their content. When I told him about my upcoming maternity leave he even said “3 months! How exciting!” And then somehow he managed to blow all that goodwill by not calling me when he said he would, and contacting me again at the very worst possible time.

Fast forward to a few weeks ago:

Continue reading

and life happens, the sql

'hello world' baby bodysuit

shipping this October…

Hey there readers, it’s been awhile since I updated this site. Life’s been overwhelming (in a good way), and has required all my focus on one day at a time.

I started this blog in late 2014 a few weeks before quitting my job to document the journey of becoming a software engineer, and in some ways that story is now DONE — this July, after a year and a half of training and independent project work, I started a full-time position as a software engineer with Experticity, the company that acquired and merged with ReadyPulse, where I’ve been contracting for the last three months.

I went into that three-month contract under the following assumption: “This will be a great, foot-in-the-door way to get some industry experience, but temporary, because NO WAY are they gonna hire a career-changing pregnant (!!) junior developer on full-time.” This false assumption was debunked thusly:

  1. My pregnancy (which I disclosed early in the contract period, as soon as it was “safe” to do so, medically speaking) did not impact the decision to bring me on full-time, or not, which yeah yeah yeah I know it is “the law” but look, discrimination happens, and I’m grateful it turned out to be not an issue for me or my company.  My advice to others in a similar situation is to seek out a workplace where “family friendly” is a genuine part of the company culture — not just because they say the words, but where employees, including senior management, *have families*.
  2. I turned out to be not as junior as I thought — I’m on a steep learning curve and still have a ton to learn, but I’ve been able to contribute and add value to the company right away, while developing my skills as a software developer and engineer. From that point of view, the decision to continue on full-time was a no-brainer for me and the company. I credit this to my past professional experience, as well as my software training from Code Fellows and Kal Academy — where I not only learned Rails and algorithms, but more broadly: how to learn software, how to work on an Agile team, how to set up a development environment, how to debug, how to ask good questions, etc.

So, yeah… I am employed. And we’re pregnant! I’m 28 weeks along today, and due in mid-October.  I wouldn’t necessarily recommend to others having a baby in the middle of a career change, but I wouldn’t not recommend it either — life happens when it happens. It’s gonna be tough to leave our little baby to return to work, and I’m incredibly lucky to be in a situation where I have exciting work ahead of me, both personally and professionally. (And a great spouse excited about it all, and a generous maternity leave courtesy of my job — oh look we’re hiring.)

The story is not done, of course — I want to keep writing about what I’m learning and doing to develop myself as a developer in these early stages. And about navigating this space as a new mom. A friend referred me to this Ruby on Ales talk titled “Baby Driven Development,” which is a fantastic 30 minute watch if you’re a parent, parent-to-be, or work with anyone who is.

Future posts will probably continue to be less frequent, and might go baby shaped for a while, but I still like making them, so thanks for reading. 🙂

the gig is up

wocintech stock - 42

photo via #WOCinTech Chat

I landed my first coding gig!!

Long-time readers know that my job search started out with a bang back in November, marinated a bit over the winter holidays, and then resumed in full force these past few months.

Throughout it all, I had some heartbreaking near-misses and some real low points of thinking, “this will never happen for me.” My instructor helped connect me to a potential contract project that didn’t quite get off the ground but led me to develop a cool app anyway. I flirted with some near-coding opportunities like writing code school curriculum and Salesforce development before narrowing my criteria for what I’m looking for. I met other kind and well-meaning people who made a bunch of introductions, and followed those rabbit trails where they led.

And thanks to one of those introductions (which happened not as a result of going to meetups, though I did that too, but rather the practice of “find and follow cool people on Twitter” which I have been doing for YEARS), I met the team at ReadyPulse, a Bay Area/Redmond-based startup where I start Tuesday as a Ruby on Rails development engineer in test.

I’m so excited that I’ll get to continue to work in Rails, expand my knowledge of software testing, work closely with the client support team to understand and troubleshoot issues, and work with a small development team to ensure new features behave as expected with full test coverage. And at a market rate!! (Add to the heartbreaks: the company that wanted to pay me $35k a year to join them as a junior developer, and the company that rejected me from their job seeking site.)

As is not unusual in this biz, I’m starting out on contract for three months, with potential to convert to a salaried position (and possibly move from testing into feature development at that point) if we both agree it’s a good fit.

Some highlights from the interview process:

  • After being e-introduced, the VP of Engineering invited me to come to the office and after some chit-chat he had me do a whiteboard exercise where I built a simple Rails application. This was actually my first whiteboard experience outside of the Code Fellows practice environment, and it went really well. My interviewer was patient, supportive, helped when I got stuck, and didn’t ding me too badly for some minor syntax errors. After I got home, I built the actual app and sent him a link to a Pull Request so he could see 1) I know how to use GitHub and isolate my code changes in readable fashion and 2) that I paid attention to what we talked about and had the follow-through to create a functioning app.
  • He replied that the app looked good, and did I have any tests for it? So I added tests.
  • I did a second whiteboard exercise with the CTO that was similarly positive and even a little bit fun. At one point I was doing the talk/think out loud thing and I told him I couldn’t remember if Ruby hash supported the “shift” function and he was like, “oh, you can look it up on your phone if you want.” And I was like, “SERIOUSLY?” And he was like, “yeah, real programmers use Google. Go for it.”
  • When my interviewer was discussing the position with me, which involves writing tests and quality assurance for two versions of their software, I asked him “how’s your technical debt” LIKE A TOTAL BOSS and he was like “oh, good question,” and his response led me to a deeper understanding of the situation and excitement to take on the challenge. It is a giant milestone to know enough to ask good questions.

There’s still a lot of unknowns in the future, but I consider this a big step towards the career I want to build as a developer. I’m grateful to Code Fellows for my training, to my partner Josh for supporting our family during this transition, and to friends new and old who cheered for me along the way! I’m gonna keep building my network and do my best to help other new coders find opportunities to get into industry quickly — there’s no better way to keep learning than on the job.

I had one of these to celebrate and I invite you to join me!

Root beer float


© 2023 Mary Dickson Diaz

Theme by Anders NorenUp ↑