Leading Change in the New Era of Work (Video)



Simon Mitchell of Sigmar International chats to Johannes Scharlach, Director of Platform Engineering at Frontier Car Group (now OLX Autos) and Fatos Hoti, Engineering Manager at Klara to discuss “Leading Change in the New Era of Work” chatting about:

  • Integration from startup into a mature company
  • How to build trust in an integration process
  • Leading cultural changes in an organisation
  • Drop everything process when everybody's remote
  • How to align a team against a goal in a new environment?
  • How to communicate that you're dropping everything and that the team is switching focus, starting now?


Posted by Jamie Harnett on 5 June 2020


6 Common CV Mistakes For Developers

6 Common CV Mistakes For Developers

The software development industry is booming with a wide array of multinational companies actively seeking qualified and skilled developers. However, due to the highly technical and specific nature of these job roles, it can be difficult to find the right candidate for the job. So, what is the best way to help HR professionals and recruiters match you with a vacant position? A well written CV that accurately showcases your skills and expertise. You have the right skills for the job, but does the recruiter or HR professional know you do? Avoid these common pitfalls when crafting your CV.   1. Listing all your work experience Recruiters and HR professionals read countless CVs, having multiple pages of irrelevant content will only work against you. Try not to write an exhaustive list of every project that you have worked on; prioritise it. Only include the projects and work experience that are relevant to the position that you are applying for. Your CV should always be tailored to the role that you are applying for.       2. Not including your ‘tech stack’ in your work experience   Your tech skills and knowledge are the most important aspect of your CV. Include a list of all the languages and tools that you used during your employment in each role. If you aren’t sure how to include them while keeping the CV clean and concise, try writing a list at the footer of each role. ‘JavaScript Developer’ – Google January 2018 – January 2019  ‘JAVASCRIPT, HTML5, CSS3, JQUERY, ANGULAR.JS, SASS, LESS, PHP, NODE.JS’.         3. Description of work experience is too complex It’s attractive to describe your work experience in highly technical terms; however, you must remember that IT recruiters may not necessarily have the same in-depth knowledge you do. A generic example would be “Developed XYZ feature in XXX framework with technique A, B, C…”. Over complicating the description of your work experience may only serve to confuse the reader rendering it harder to match your skills with a vacant position.         4. Description of work experience is too general By contrast, it’s also not advised to describe your work experience in ambiguous terms. For example, “Developed a website using AngularJS5”. This statement asks more questions than it answers. Did you develop the website alone, how big is the website, what features does it have etc.? Make sure you accurately describe your part in the project and the scale of it.           5. Only list skills you are technically strong in It’s inviting to showcase all your technical skills to make yourself appear more experienced and educated. However, you should only list skills that you are technically strong in. Include databases, APIs, languages and any other tools you feel you have mastered and frequently use. Embellishing your knowledge of a language or a tool is not recommended, you will get caught out.          6. Poor Formatting and Mistakes Your CV is the critical ‘first impression’ to your prospective employer. A poorly formatted CV guarantees a bad first impression. The golden rule here is to keep your CV clean, concise and easy to read. Avoid using elaborate formatting and colours. Keep it simple. Recruiters and HR professionals are interested in the content of your CV, not the colours. Lastly, proofread your CV ensuring there are no grammatical or spelling errors; they're highly unprofessional.       


What To Expect in a Developer Interview

What To Expect in a Developer Interview

Interviews are the gateway to landing your dream job, but for most people interviews are a stressful and uncomfortable endeavour. You finally have your chance to impress a prospective employer and secure that golden opportunity, but unnerving thoughts and doubts begin to make you nervous. Nerves are to be expected, but if you let them overcome you, they could dampen your chances of securing the job that you may well have the skills and expertise for. What is the best way to ease your apprehension? Being prepared.   Having an understanding of the overall interview process, the types of questions asked and what is expected of you will not only enable you to be more prepared, but it will serve to quieten some of them unsettling anxieties. So, what should you expect from a ‘typical’ developer interview? Every company has their own way of doing things and the procedure may differ slightly depending on the role that you are, but a lot of companies follow a similar process.   The interview process tends to comprise of one or two phone interviews, followed by up to four on-site face-to-face interviews. The initial phone interviews are used to simply screen candidates to assess whether they are worth meeting in person. The first of the two phone interviews (or first half of the interview, if there is only one) will ask primarily behavioural questions.   Behavioural questions are not designed to challenge you; they’re used to get you talking and to make you feel comfortable. Big open-ended questions are often asked such as “talk me through your CV” or “tell me about a challenging project you worked on”. The questions are designed to help HR professionals get a feel for you, the type of person you are and whether you’re a good fit with the company. Some light technical questions may also be posed asking you about your relevant coding knowledge, database expertise and so on.   Following the initial phone screenings, you may be invited in-house for a series of face-to-face interviews with the appropriate members of the team. Large companies such as Facebook, Microsoft and Google hold four face-to-face interviews lasting approximately forty-five minutes each. These interviews primarily focus on your technical abilities with only one focusing on your behavioural traits and/or culture fit with the respective company.   The technical interviews are a means of evaluating your problem-solving skills. The interviewer wants to see if you can translate your thought-process into reasonably correct, well-structured code. You will be asked a coding/algorithm question and be expected to write, test and optimize code often using a whiteboard, with some companies offering a laptop instead. Having a foundation in data structures and algorithms is really important. These are fundamental concepts, like binary search trees and breadth-first search. You will also be asked to develop an optimal algorithm for your code.   It’s important to note that your code and algorithm does not need to be flawless. It is your approach and methodology that is being evaluated. Once the technical side of the interviews are complete, you will be given time to ask questions that you may have regarding the role or company or whatever may be on your mind.   This is what a ‘typical’ developer interview process is like. However, every company is different. A great resource to discover the interview process for the position that you are applying for is Glassdoor. Here you can read what other applicants experienced with sections offering advice and types of questions asked.