Snowflake Solutions Architect
I've been going through a loop for a Solutions Architect role. I'm currently a senior data engineer, with most of my experience in data warehousing, so think SQL, dbt, Python, and shell scripting. A friend works there in sales, loves the culture, and said he thinks I'd be a good fit, so I applied. The team seems smart and capable, and I think Snowflake is a great product, but I'm still really hesitant about switching from an engineering role to a consultant one. I have a few questions for those familiar with the org: - WLB: Some of my interviewers have said to expect 50+ hours regularly, and others have said 40 with occasional 45+ - Career: I'm unlikely to relocate from LCOL US, so product would be out of the question, and I don't think there are any other technical roles that are remote. Also, I've heard mixed things about ProServe being a career dead end vs. being a huge door opener - Culture: My friend loves it, and the team seems to be genuinely good people. I've picked up that it's a highly competitive environment. Is this mostly positive, or does it end up being toxic? TC $190k YOE 6 #snowflake #snowflakecomputing
Professional Services at Snowflake isn’t that great, compared to let’s say Amazon. I joined Snowflake recently and after speaking with someone in the Professional Services team, they said Sales Engineering team does most of the customer facing technical consultation, and his team exists just as a check in the box. It’s an anecdote but take that as you will.
I wouldn't do it unless you think you're a good fit for a the role. Not sure if solution architect is pre sales or post sales role at snowflake. It can vary from one company to another. If it's presales, do you see yourself in sales meetings being the demo person and spending most of your time either training about latest and greatest product you're helping sell and answering random questions on calls. If it's post sales, do you see yourself doing consulting work but more geared through making the product your company sold work with some weird legacy tooling and systems out there. Like database migrations planning, doing upgrades and trying to solve problems with grunt work. If you're happy where you are and comfortable doing dev work and you can learn and grow, I would stay put. You'll probably not gain more technical knowledge outside of the immediate product you're helping sell/integrate. It's a completely different kind of dynamic.
I’m also a DE interviewing for SA role at Snowflake and tbh i love the product so much I don’t really mind the title switch. I come from a consulting background anyways and I feel that I would get so much more out of a product than what I’m currently doing boring ol’ etls and pocs TC 170 YOE 6 yrs
Do some research on Blind about Snowflake. It seemed bad to me.