> Get a job at smaller to medium sized non-tech company.
From my own experience, I can recommend the following approach for someone with a database background: Look for successful small companies. They typically have some homemade information management solutions that do not scale, such as using Excel where a database would be the right thing, etc. Then tell the management how much better such a database system would be: how much time they could save, how much more consistant and reliable their data might become, how many interesting key figures they could extract from it, etc.
When you are hired, you are usually the only person responsible for the new database project. This gives you all kinds of organisational freedom and limits meetings to occasional consultations with the management.
> I didn't think anyone would say yes to a 4-day work week
Do not set a fixed time per day or week, but instead agree on an annual time budget that is slightly less than what you might want to work. Do not agree on fixed project deadlines, but instead create a detailed to-do list with priorities. Work above average at the beginning of the year until March. After that, you should mention from time to time: "I am already x weeks over the planned time budget". You will then usually not be pushed to work more and can take days or weeks off at will to get back in line with the planned time budget. In December, no one will usually complain if you charge the company more when you are still ahead of the planned time budget. And if they do, just take a longer Christmas holiday.
From my own experience, I can recommend the following approach for someone with a database background: Look for successful small companies. They typically have some homemade information management solutions that do not scale, such as using Excel where a database would be the right thing, etc. Then tell the management how much better such a database system would be: how much time they could save, how much more consistant and reliable their data might become, how many interesting key figures they could extract from it, etc.
When you are hired, you are usually the only person responsible for the new database project. This gives you all kinds of organisational freedom and limits meetings to occasional consultations with the management.
> I didn't think anyone would say yes to a 4-day work week
Do not set a fixed time per day or week, but instead agree on an annual time budget that is slightly less than what you might want to work. Do not agree on fixed project deadlines, but instead create a detailed to-do list with priorities. Work above average at the beginning of the year until March. After that, you should mention from time to time: "I am already x weeks over the planned time budget". You will then usually not be pushed to work more and can take days or weeks off at will to get back in line with the planned time budget. In December, no one will usually complain if you charge the company more when you are still ahead of the planned time budget. And if they do, just take a longer Christmas holiday.