F-Engineer’s vision to create a platform for women+ in technology working in engineering, design and product roles which allows them to support each other and gain easier access to mentoring, jobs and networking opportunities. The members will be predominantly female and the members of the genders that are minority groups in today technology landscape ( LGBTQ+ community). We also accept members from all backgrounds/genders who will be our allies as mentors, recruiters, enablers

1. F-Engineer
Meetup 27.April.2021

2. Agenda
● Why F-Engineer (Füsun-5mins)
● Introducing ourselves (15 mins)
● Update on mentoring (Selma- 10 mins)
● Preparing CVs for software engineering jobs (Füsun) (15 mins)
● Using open source for enterprise software (Erdem) (10 mins)
● Q&A (open end)

3. Why F-Engineer (200+ members in one month!)
F-Engineer’s vision to create a platform for women+ in technology working in
engineering, design and product roles which allows them to support each
other and gain easier access to mentoring, jobs and networking opportunities.
The members will be predominantly female and the members of the genders
that are minority groups in today technology landscape ( LGBTQ+
community). We also accept members from all backgrounds/genders who will
be our allies as mentors, recruiters, enablers.
Why: Inequalities wrt gender information technology is still a reality and it
needs initiatives like this to create equity in all environments for STEM
women+.

4. Introductions
Let’s spend 10-15 minutes for some introductions.

5. Mentors & Mentees
● 9 mentors & 14 mentees (some waiting to be matched, no worries!)
● Mentee application deadline: The end of this month
● In a nutshell ...
○ Mentors - 30 min checkins every quarter with the mentor group
○ Mentee&Mentor monthly meetings - 1 Hour (adjustable and extendable)
○ Try and see if both parties fit - first 2 months
● First meeting
○ Get to know each other
○ Try to expand expectations
○ Decide on a medium to communicate and share resources (eg gmail, drive, …)
○ Devise a general roadmap based on mentee’s goals

6. Tips for Mentees
● Get ready before the first meeting!
○ Search your mentor’s background in social media
○ List a set of realistic expectations and goals
○ Try to align your expectations and goals with your mentor’s experiences
● Remember your mentor is a volunteer
● Don’t expect to find all answers, you’re responsible for your own learning
and future plans
● Come to each meeting with a prepared agenda
● Share your feedback and updates with your mentor
● Listen and ask follow up questions

7. Tips for Mentors
● Listen and ask follow up questions
● Be open-minded and show a respectful attitude
● Give honest and direct feedback
● Bring enthusiasm while sharing your expertise
● Be eager to invest into your mentee

8. Preparing CVs for Engineering Roles -DON'Ts
DO NOT
● Go over 2 pages
○ (maybe 3 if you are very seasoned)
● Include your Marital Status, Race,Religion, Unnecessary Personal Data
○ Gender is not a must field in USA and many European countries
○ Driver license information is not relevant unless it is stated in the JD
● Try to explain your whole life story in the resume
○ if anyone cares about your primary school and the fact that you were the volleyball team
captain or all the 20 trainings you attended?
● Feel obliged to provide a picture on the CV or application
○ Ask yourself what pros and cons it has for you.
● Assume that the readers know the companies you worked for and what they do
○ Avoid company internal project names and vocabulary. Empathize with the readers.
● Use your own native language for applications in EU and USA.
○ You should use English unless stated otherwise.

9. Preparing CVs -Good Practices (1)
Putting your name and contact information at the top. Use the space
sparingly , the first 0.5 page is the most important section with the max
visibility to the readers.

10. Preparing CVs -Good Practices (2)
A short (!) summary about who defines you as a professional; what you are looking for and
what you offer. (Recommendation: not more than 5 lines)
If you have 2+ years experience, consider adding your top skills right underneath/close to it.
(between 3 and 10, choose them wisely)

11. Preparing CVs -Good Practices (3)
Choose a nice format, based on your experience and chased position. You can use resume
builders or use free templates available in internet. INVEST IN THE FORMAT AND LOOK &
FEEL OF YOUR RESUME.
Image credit: www.zety.com
● What matters the most is in the 1st
page
● With working experience: Personal
information , short intro, skills and
current/last working experience in the
1st page!
● Students : Your education, current
projects and ambitions and other
activities (such as open source
contributor)
● Hobbies : it is a maybe. Put them at
the end and not too many of them

12. Preparing CVs -Good Practices (4)
Use standard description for the level of your language skills. Recommendation:
Do not put in languages you don’t intend to use for work.
● Intermediate / Upper Intermediate
● Advanced
● Proficient/Fluent
● Native/Bilingual

13. Preparing CVs -Engineering CVs (1)
● CVs are mainly for getting you into the recruiting pipeline and land the first
non-recruiter interview.
● The way you represent yourself (structure, readability and intent) tells you valuable
stories to the interviewers about how you think and work. (able to abstract/consolidate
information and make it for the audience? Has a structured approach? Knows what matters
for their careers and in engineering roles?)
● Skills are very important. Make sure the reader can extract your tech strengths easily.
● Make sure you understand the competencies asked and how your profile relates to that.
● You don’t have to use your exact title at work if it is not explanatory enough. Be honest and
smart at the same time to inform the reader the best way possible. (eg: At Vodafone my
title way system planner (don’t ask me why) and in fact what I did was backend architecture
design and technical program management)

14. Preparing CVs -Engineering CVs(2)
● The more experienced you are the more tech and stack agnostic you can represent
yourself. More junior roles will need to know what language/stack you already can use, algo
skills and ability to learn.
● Certifications, trainings etc are more relevant for more junior roles. For a sr roles (let’s say
5+ years of experience), it always boils down to demonstrating their competencies during tech
interviews. GPAs. certifications etc will have little/no impact.
● Be smart about adding skills that you don’t want to use/that do not look relevant to the
job.
○ (e.g I am an ex-system administrator, it has little/no relevance at this point in my career
growth as an engineering manager. architecture and system scaling knowhow on the other
hand is something that is necessary for tech leadership roles)
○ Be smart about what not to include : MS office skills for an engineering job in CV?!!
● Find a balance : don’t be shy but don’t oversell yourself (Women tend to undersell!)

15. The world of Open Source Software
http://javierperez.mozello.com/blog/params/post/2201126/the-growing-ecosystem-of-open-source-software-for-ibm-z-and-linuxone

16. Open Source Software at enterprise

17. Open Source Software in action
Real-Time Live Soccer Score Streaming Application
Demo with Reactive Spring Stack
ElasticCC: Boosting music search results based on
popularity and user behaviour