Friday, February 07, 2020

Create a New Post Type in Jekyll

Create a directory called _stories.

Update _config.yml file:

    output: true

Create a story.html file in the _layouts directory.

layout: default

{{ title }}

{{ content }}


layout: story
title: Story Title Goes Here
description: "The story description text goes here"

Create a stories.html page in the site root to act as the index page for the stories.

{% for item in site.stories %}

{{ item.title }}

  {{ item.description }}
  {{ item.title }}
{% endfor %}

Wednesday, February 05, 2020

Making a Good Last Impression

What to do in the last 5 minutes, in order to leave a good impression?

You need to remember this is a Two-Way interview. If you're good, I will need to sell you on the company because you could have multiple competing offers. So, I usually have a little spiel prepared to explain why it's so great to work at my company, that I'd love to give. If you can get me to try to sell you on joining the company, my mindset is already being altered towards bringing you in.

Your questions are the last impression that you make. If you have no questions, it indicates that perhaps you're not all that interested in the role.

Q&A doesn't need to last long -- 2 minutes is plenty. Just a quick, Hey before we end this, can I ask you a question?"

- What makes you want to work here?
- What are the primary challenges of your current team?

Share a quick comment about how you've also faced similar challenges. End with "Thanks for sharing, it was a pleasure talking to you and that was an interesting question. I enjoyed tackling it."

It is a great chance to learn about something interesting regarding their stack or internal processes, such as:

- How do they run their CI/CD pipeline?
- How does requirements go from conceptual phase to production?
- How do they deal with critical production issues?
- Do engineers debate and have an active voice on requirements prioritization, and functional requirements?
- How much test coverage do they have for their products?
- How does the company embrace innovation?
- Do the engineers have a chance to research and apply technologies that improve the product?

If you are not just looking for a place to get bills paid, it is really important to match the company's internal processes and goals with your career goals.

Researching a Company

What you should know about the company when researching it?

- Mission Statement
- All their products or at least the product area you're applying to
- What are they working on / new innovation
- What kind of culture they have, so you can mimic it
- What interview questions they ask

Crafting Your Resume

It is generally common norm to have a 1-pager resume. Put your highlights in the 1-pager. Less is more. You can use Google Docs to create your resume.

Use black and white, with clean professional formatting. Don't go overboard with fonts & colors. It's the content that matters here, pack it with content. Go as far back as will fit.

Understand the mindset of an employer when crafting a resume. The following tips are from: "Knock em Dead Resumes" by Martin Yates.


Search and collect 6 online job posting for the job. See how the employer describes behavioral profile, technical skills, problems you'll be solving on the job, etc. Use these to craft the story of your resume.


Add technical, behavioral and other keywords employers and recruiters database searching algorithms will rate with high scores.

Problem Solver

Think of about the problems you will typically need to identify, solve and prevent in the role and work your resume narrative to highlight familiarity and ability to identify, solve and prevent these problems. Present yourself as someone who solves these problems.

Smoke Screen Questions

The smoke-screen questions are language dependent. Search for "common interview questions in {your language of choice}" and there are usually plenty of articles on lists.




A lot of these may be quite language-specific, and since they're quick yes/no questions they don't make for great meaty interview questions. If you're going into an interview, and you know it's going to be for something language-specific like "javascript frontend developer," "Objective-C iOS developer," or "Python backend developer" then it'll be good to brush up on these. You could be developing in a language like Javascript and never use closures. But that's still a very common question for Javascript roles so don't let those catch you off guard.

Smoke screen test is usually domain specific. If it's a startup, they ask a lot about language specific things depending on the language they use. For larger companies, these questions are rarer, they usually just ask you to do a coding interview. If they do ask you yes/no or definition questions, make sure you know about object oriented programming concepts, OS concepts, concurrency, networking, and language specific questions.