Where the design community meets.
Going to interviews will give you more interview experience and put you in front of people, this is good experience and since you are early, you have the luxury of time since there is no urgency to get the job.
I want to second this. Interviewing well is a skill in and of itself. Get out there now, start getting used to interviews and ensure you apply to a variety of places - don't put all your hopes on a single job.
I love this idea. I used to do something similar with the mappable buttons on my Wacom.
Yeah, these are great art pieces but fundamentally unusable. Familiarity and respect for user behaviour is pretty key in doing design.
It's a totally fair question.
There is an enormous amount of software product design that doesn't cross into Silicon Valley / tech startup world. I've spent years designing video streaming and entertainment systems, farm management tools, cooking apps, tools for health diagnosis, workflow management and cinema booking apps. There is a lot of great, well-paid work outside of Silicon Valley that you can feel proud of.
They haven't ruined Trello, at least
I just use the Dribbble Playbook.
It depends if you're leaving due to a short term financial issue (eg money's short this month) or a permanent one. If I'm just short this month, a good cancelation experience that tells me that my account will be preserved for the future means I'm likely to come back. Whereas an experience that doesn't reassure me means I'm likely to never return.
yeah, totally agreed!
I can see your reasoning, but I don't fully agree.
We use job titles to recognise what we do and what we are responsible for, not just the final outcome of the work. That fact all contributing members work towards the health of a patient defines the mission of the business, not the individual. A janitor's focus is cleaning, and they can do that in a business that creates patient health, or stock market trades, or entertainment, etc. Similarly a developer may have the core focus of building reusable, efficient code, a goal which may be counterposed to the goal of providing a good user experience. If I as a designer ask the developer and product owner for a feature that, say, adds more complexity to the code but solves for a particular user need, in that moment we're negotiating from our respective positions of expertise. We may all have the overall goal of providing a good product, but within that we have different goals such as user experience (design), code simplicity (developer) and ROI (PO).
There are a lot of ways people can contribute to the creation of a product. But the core responsibility for user research, user testing, ideation and validation, the rendering of intent is that of the designer, and the designer is the person who can take that skillset to another business and do it there.
The project manager may contribute to the quality of the product, but if they move to, say, an accounting firm, they can do project management, but not design.
That said, yes design is a much more porous job than medicine, but it also has a century of history of study and theory and professional development, from ergonomics to ethnography to psychology and typography. I don't think it's useful to collapse that into a general focus on producing a product.
You've got a point there about the collaborative nature of the role though to my mind the job of designer is researching, validating and facilitating all that collaborative input, not giving it.
Do you think so? A janitor in a hospital has an impact on the health of a patient but that doesn't make them a doctor.
Where the design community meets.
Designer News is a large, global community of people working or interested in design and technology.