Tips, advice, and guidance for changing your career.
on Tuesday, April 12 @ 8:22pm
Software developer positions are highly desired. Just as astronauts, Supreme Court justices, and Hogwarts professors must have a variety of skills and knowledge, software developers have a combination of technical knowledge and soft skills. This post explores the skills that many companies look for.
We’ve never formalized our core values at Bloc, but if you surveyed our employees you would probably see authenticity in the top three most cited responses — followed closely by swag and Batman. We’ll focus on authenticity today.
Authenticity is a word that we use very specifically, and we don’t use it to mean the same thing as honesty or transparency. The easiest way I’ve found to articulate the difference is to explain it in the context of someone asking a question:
Here’s an example: when we raised our Series A investment last year, a few of my friends asked me if I was now a millionaire.
An honest answer would be yes. On paper, if we had hypothetically raised a round with a post-money valuation over $5M and I owned at least 20% of the company I would have 20% x $5M = $1M ownership in a privately valued company and could technically be considered a millionaire.
The authentic answer would be no, not even close. The question my friends intended to ask was “do you have a million dollars of liquid cash that you can spend to buy me a Tesla Model S?” And the answer to that question is decidedly “no”, unless Elon would accept Bloc equity as cash.
The developer bootcamp industry has an obsession with something called “the placement rate number.” It’s meant to measure a program’s efficacy by quantifying the percentage of graduates who successfully start careers as developers.
Bloc is one of few programs that has never advertised a placement rate. Prospective students are eager to ask us for this statistic, and I don’t necessarily blame them given how appealing it is to use a simple benchmark to compare programs. We don’t publish a placement rate though, as we believe it would potentially conflict with our commitment to authenticity, not because we lack confidence in the efficacy of our program.
When a prospective student asks us “what is your placement rate?” we could honestly say anywhere between 0-100% depending on how we qualify our answer. We could, today, say that 99% of our students find jobs after they graduate from Bloc in a way that is both technically honest and legally defensible, but not authentic or ethical. It’s not very difficult to game that statistic.
99% of our “splorkdents” find “globs” within 90 days of “schmanuating”. – Credit: SMBC Comics.
The truly authentic answer has nothing to do with statistics though. The question our students intend to ask is closer to “Does your program work?” or more specifically “Will your program work for me?” We’ve found a better way to answer that question: our Software Engineering Track comes with a tuition reimbursement policy for students who are unable to find new careers in software development after graduating, and now our students don’t have to worry about landing on the wrong side of a program’s 90% placement rate.
When there are programs with less than 20 grads touting a 100% placement rate and dozens of hidden qualifications, that number devolves from a transparent industry benchmark to a disingenuous marketing prop. While we look for authentic and quantifiable ways to evaluate program quality, I’ll encourage students to dig deeper: ask about the curriculum, background and experience of instructors, tuition and opportunity costs, and the hidden qualifications of these placement rate numbers.
If you’re considering a career as a software engineer, then you may have heard how difficult it is to learn. But the right mindset can give you a significant advantage when learning and working in the industry. Software engineers who embody these seven character traits are valuable employees and productive contributors.
It’s what killed the cat, apparently, but that cat was a rock-solid engineer. Great engineers take responsibility for learning and exploration. They do not depend on their superiors to give them explicit direction for a new challenge – their curiosity guides them to reach their own conclusions.
At my first job as an engineer, I worked on an Android game. In the middle of working on a new feature, I noticed that some background tasks consumed an inordinate amount of time. After some investigation, I discovered that we relied on an Android API that took 50% longer on average to complete when compared to a simpler Java counterpart. I reported my findings and as a result, we swapped one for the other in all cases.
An engineer who seeks out new information and investigates the product may discover something new in the process. More importantly, the more versatile an engineer, the more valuable they become. Learn to serve your curiosities and feed them with research and experimentation.
All engineers require mental stamina. As a new engineer, you won’t solve the most challenging problems during your first attempts. In fact, you may have to spend days, weeks, or longer looking for a solution before finding one that meets both business and product requirements.
If you give up readily, you may not find yourself working on anything interesting, or anything at all. Engineers love solving problems and most refuse to give up until they work them out. Grit is what keeps engineers from throwing in the towel.
In 2014, the popular blogging platform, Medium, encountered a problem rendering underlines in Chrome. The author, Marcin Wichary, states that what was thought to be a one-night project turned into a month-long effort. After brainstorming seven approaches, the team settled on one and Marcin implemented it. Fixing something as seemingly trivial as a proper underline required incredible tenacity and the product is better for it.
This one is a no-brainer, but if you want to be a part of a functional team, you must communicate. If you’re shy or quiet, that’s fine. You can make up for shyness by communicating effectively in writing.
At Bloc, we rely on asynchronous communication – one out of every six employees works remotely. We use email, Slack, and GitHub to facilitate feedback and discussion. In these messages, we try to use as few words as possible and get to the point fast. This keeps our co-workers focused and eager to read and respond.
Your team needs to know what you’re working on and if they frequently ask for clarification, they may stop asking altogether. By communicating frequently and in brief but descriptive messages, your team will look forward to speaking with, and hearing from you.
Despite being another predictable member of this collection, attention to detail is vital for engineers and thus worthy of mention. If an employee at McDonalds applies two ounces of special sauce to your Big Mac instead of two and a half, will you notice?
As a software engineer, if you mistype even one line of code, it can crash an entire application. Details comprise software, and companies hire engineers to craft those details well. If you are someone that looks solely at the big picture, you have to learn to zoom in.
At Bloc, our students rely on our custom curriculum to learn the software trade. If we mistype a line of code or introduce a grammatical error, the student’s ability to learn the subject is significantly affected. We use grammar tools like spell check, linters, and Grammarly to draw attention to pain points.
Some call this, “thinking outside of the box,” but saying that would be yet another cliché and this post has reached its limit of those. When solving challenging engineering problems, the best solutions often come from adopting a new perspective.
If everyone took a crack at a problem from the same angle, they would ultimately arrive at a similar solution. But a diverse team whose approach varies among its members will generate more ideas and non-conventional solutions. You and your team will benefit if you broaden your ability to see things that others overlook.
To allow team members to share new ideas and solutions, we occasionally hold hack day events at Bloc. These hack days, like hackathons at Facebook, permit anyone in the company to work on anything. Thus, people who rarely interact with an aspect of the Bloc product can build new features or solutions that the dedicated team had not yet thought of. For example, our hack days helped us design a new payment flow, student portfolios, a student glossary for recruiters, and so much more.
Engineers collaborate, even when managers assign a task to just one engineer on the team. Team members review each other’s code before deploying it to production, and during these reviews, they may criticize or recommend significant changes to code written by their colleagues.
Engineers open to receiving critiques and feedback receive more support from their teammates, and the engineers that receive more support make bigger contributions to the product. More importantly, the product suffers if an engineer deploys code without revising it to meet the expectations of their peers. A good engineer is modest and willing to consider a different approach suggested by their team.
At Bloc, we have a thorough review process both on the engineering and curriculum side. Before we published this blog post, it received editing passes from two individuals that looked for quality content and prose. I was responsible for accepting modifications and including content suggested by my peers; the post is better for it.
It’s common for some engineers to isolate themselves and work without consulting their teammates. The industry refers to this proclivity as Lone Wolf Syndrome. Lone Wolves, much like the animals after which we’ve named them, do not survive for long. Wolves hunt in packs, and engineers must collaborate.
To be a productive engineer: seek help when needed, express yourself when overwhelmed, offer to help when you see peers struggle, and in general, engage with the group. No one on your team is excited when one person goes off and returns with unwanted or otherwise broken code. Acting as part of the team builds better relationships and trust among your co-workers.
If you believe that your personality is set in stone or that you’ve grown fixed in your ways, we recommend you read this article from Psychology Today. Those who study the mind believe that personality is flexible and with concerted effort, anyone can alter their disposition.
Today’s modern programming bootcamps promise job readiness upon graduation, and in this post we’ll discuss how they deliver on that pledge. While Bloc wrote this for Bloc, this content applies to most well-known programming bootcamps (e.g. Hack Reactor, MakerSquare, Dev Bootcamp). We’ll explore three features that bootcamps provide to help students prepare for their new careers.
More importantly, the software industry is one where within a year’s time or less, an up-and-coming tech stack can overthrow the standard – the industry changes all the time. Bootcamps employ working professionals who incorporate the latest technologies into the curriculum to combat the sector’s ever-changing landscape. These individuals filter the noise to discover the technological shifts critical to their student’s education and success.
Bootcamps also have students engage and master soft skills, such as Agile and Test-Driven development (TDD). Agile is a project management paradigm that is prevalent among many startups and established companies. Similarly, many organizations follow TDD practices that require developers to write tests before writing the code that runs the application. Bootcamps that employ these soft skills better prepare their students for their future work environments.
Every developer should have a portfolio. For seasoned developers, it is a combination of projects worked on in corporate, contract, open source, and personal environments. For bootcamp graduates, the stakes are not quite as high. However, a bootcamp helps students build a modest portfolio of two to four fully functional, well-designed applications.
A portfolio reflects upon a student’s ability to apply their new skills and create something of their own. During an interview, students not only have applications to talk about, but may open up a laptop and show their interviewer said applications, what they do, and how they work. If a picture is worth a thousand words, then a working application is worth 10,000 lines of code (or something like that).
At Bloc, we require students to complete three projects before they graduate, and many often build more than that. We help students along the way, guiding them with mentorship and high-level architecture concepts. Students may also choose to develop a capstone project, one that is entirely of their own design. Students often graduate Bloc with an excellent showcase project or even a full portfolio of apps.
A skilled student with an excellent portfolio of applications is ready for one last thing: the job hunt. Bootcamps that aim to find gainful employment for their students will prepare them for the arduous task of looking for career opportunities. This begins with the fundamentals: resumes, online profiles (LinkedIn, GitHub, StackOverflow) and cover letters.
Most bootcamps go much further, often requiring the student to participate in mock phone screens and in-person interviews. This includes practicing interview questions, both technical and otherwise.
Once a student is adequately prepared for an actual job search, the bootcamp and its partners work together to find employment opportunities for them. Bootcamps have extensive networks of mentors, recruiters, and corporate partners that want to snatch up talent before losing it to the competition.
Established companies such as Autodesk, Starbucks, and Groupon have hired our graduates. Bloc’s mentors, and even Bloc itself, have hired graduates in the past, a practice that has resulted in great outcomes on both sides.
If a bootcamp can endow a student with fundamental skills, a stunning portfolio of applications, and the tools required to begin a job hunt, it prepares that student for a career as a software developer.
We had the chance to catch up with Rails Web Development alum Jack Pope, on what life has been like post-Bloc. Originally from Connecticut, Pope recently moved to New York after accepting a job as a web developer at Tsu, a social media company.
Before enrolling in Bloc, Jack was a photographer and internet marketer. As he got involved with the more technical aspects of his job as a marketer, Jack’s interest in web development was piqued. Although he had some experience with HTML and CSS, he found himself wanting more.
Determined to learn, Jack looked into on-site coding bootcamps in his area. While applying, he kept running into the same dilemma: the upcoming cohorts weren’t starting for another 4-5 months. He refused to wait that long; his mind was set, and he wanted to start programming immediately.
Jack found Bloc, an online alternative to the on-premise programming schools that allowed him to start almost immediately. According to Jack, “Bloc’s just way more practical.” He gave his 2-week notice, and started his course at Bloc.
After completing Bloc’s 12-week Rails Web Development course, he started freelancing and adding projects to his Bloc-built portfolio. “I definitely learned a lot at Bloc and it was a great foundation, but the extra time to work on real projects after Bloc was really important.” Equipped with Bloc’s 12-week course and eight additional months of freelance work, Jack was ready to get a web developer job. He started his job hunt in September, and accepted his offer at Tsu in December.
For Jack, the job hunt was tough but crucial for learning. As expected, there were many rejections before he found the job he wanted. When asked about what he learned from his job search post-Bloc, Jack said, “The interviews you go in for and get rejected from are still really useful. I wouldn’t have passed the interview for this job had it not been for the previous interviews I went through. In each interview, I picked up a different skill and learned how to answer questions in a better way. Even the ones you end up not wanting or getting rejected from are worth having because they’ll help you prepare for the right interview and right job.”
So, what’s Jack up to now? As a Connecticut transplant in New York, Jack is busy working at Tsu, eating all of New York’s delicious food, and exploring the city he now calls home.
If you are looking for a similar career change, check out our Software Engineering Track.
Sign up for one of our upcoming online info sessions to learn more.