Life after PhD - An insight and a few tips to kick-start your career in the industry
•Download as PPTX, PDF•
1 like•454 views
My presentation at Swinburne University in Melbourne. The audience is current PhD students and Postdocs.
Recommended
More Related Content
Similar to Life after PhD - An insight and a few tips to kick-start your career in the industry
Similar to Life after PhD - An insight and a few tips to kick-start your career in the industry (20)
More from Malinda Kapuruge
More from Malinda Kapuruge (13)
Recently uploaded
Recently uploaded (20)
Life after PhD - An insight and a few tips to kick-start your career in the industry
- 1. Life after PhD An insight and a few tips to kick-start your career in the industry. Malinda Kapuruge
- 2. Hi, • PhD at Swinburne (2008 – 2012) • Postdoc (2012 - 2013) • Now a Consultant at DiUS Computing 2004 2008 2014 Acedemia (~ 5 yrs)
- 3. The contents are based on my experience. May/may not be applicable to others.
- 4. Industry vs Academia Financial Flexibility Ownership Team culture Work-life balance
- 5. And the Winner is … The Parameters !
- 6. As a researcher, • What skills do I need in order to kick start your career in industry? – Transferable skills – Extra skills
- 7. Transferable skills Critical thinking Data management Perseverance Report writing Self-motivated Time management
- 8. A doctoral thesis • Not just yet another book • A process • You will be transformed • You will acquire those transferable skills
- 9. How about extra skills …?
- 10. What it like to be a SE consultant? • Short gigs • Newt tech, processes, people (& coffee shops) • Technical spikes / feasibility studies • Learn fast and move quickly • Mentoring existing staff • Polyglots • Bench time
- 11. Team composition DEVs QA UX PM
- 12. Rituals [ Daily ] Standups Retrospective Sprint Kickoffs
- 13. Extra skills • Communication • Networking • Understanding the “customer problem” • Ability to add value from day 1 • The Software Engineer mentality
- 15. Code ! Code !! Code !!!
- 19. Master the CLI
- 20. Develop good S.E. habits
- 22. Learn Agile
- 23. Be aware of trends • Big data • Internet of things • Flying robots • Scripting languages
- 24. Technical meetups • Small groups • Like-minded • Various roles / organizations • Mutual benefits • Quick feedback • Interactive .com
- 25. Open-source projects • Visibility • Communication • Something Tangible • Free testers / contributors ;-)
- 26. Join a good organization • That value your research skills • That promote learning • The size does not matter • But the culture is
- 27. culture
- 28. Brown Bags • Lunch time - every Tuesday • Free lunch ;-) • Fun ! and social !! • Someone participated a conference • To pitch a crazy idea • Invited talks
- 29. Special Interest Groups (SIGs) • Similar to a technical meetups • Focused groups to improve technical skills – E.g., IoT, Cloud, UX
- 30. Hack days • Twice a year • Paid to go NUTS !!
- 32. Intelligentli To upload and monitor your sensor readings as annotated time series data, e.g., geo locations, tags E.g., sample demos: https://smokealert.intelligent.li/ https://livevu.intelligent.li/
- 33. Pact framework • Integration Tests are a Scam – J.B. Rainsberger • Unit testing for Micro services • Consumer driven contracts • DSL • Available in Ruby/JVM/JS
- 35. Aerial sensing
Editor's Notes
- Many advices on the web. More often than not from North America. But we have different PhD program here. - Software culture is more or less the same.
- Chose your parameters wisely
- Common skills that you may already have and will be useful for a career in industry Extra skills that need to be added.
- At least this is the way people from industry will look at you. So you have an edge There are certain advertisements look for PhDs (or even drop-outs)
- The way you think, analyze, write will be transformed
- What I call them are power tools
- Agile vs Waterfall methodology
- Communication is vital. Both verbal and written Look for networking opportunities ( I will come to this later on how) Add value form the Day1:Training for the job is a thing in the past
- You can polish your resume, master the art of facing interview to get that job. But you need to build the SE mentality to survive. Here are some tips !
- There is no other way to be a good SE rather than writing code. Do not be afraid to break things. Write programs for your work, colleagues' work, your neighbor, in-laws Learn a language and master it. Maintainability – No afraid to refactor Learn alternative techniques. Compare.
- Note: Mobile software development
- Cannot emphasize enough the importance of this More often than history you will be working on a remote machine. AWS EC2 instance. Your peer will admire your… ;-)
- Use tools, automate everything save time Test driven development Appreciate others work Contribute
- Refactor until the tests become GREEN !
- Multiple sprints OR iterations Read about Kanban, Scrum No need to be a master. But learn the basics. Usually a team practices and adopted methodology that best fits the requirement.
- Big data -> Event streaming architecture Javascript -> Node JS + Testing
- Different to conferences. Meet often, quick feedback cycle. Mutual benefits: A solution architect participating to keep his knowledge up-to-date may find the developer that he was looking for. Interactive: Discussion over Pizza and Beer (FREE) I used to talk about my research to get feedback. It worked! Sort of !! Low risk opportunities
- Open a gitHub account if not already and start pushing your code.
- Do they promote learning
- Have offices in both Sydney and Melbourne A technical company Mainly customer focused Have few ongoing research projects
- Discuss technical challenges encountered while working, e.g., UNIT testing for microservices Common problems in a specific area, e.g., SSH issue. New products e.g., Data mining tools, Event streams
- Team-up Own ideas Prototyping
- Unfortunately I can not talk about the client project due to NDA Here are some bench time projects…
- Sensors are readers as first class entities Event streams and publish-subscribe model Inbuilt features to tag geo-locations and tags
- When an integration test is broken, who knows what’s broken? Pact is shared between the consumer and the provider.
- Testing with Pacts compared to integration tests -Fast execution (no network overhead) -Reliable tests -Easily locate the broken service -No need a separate integration test environment
- Photosynthesis images are captured via a drone to detect any anomalies in vegetation Large vineyards Aerial view with drones