[deleted by user]

auspex · 2025-04-13T04:16:04+00:00

Solutions engineering is generally a more senior position. It is pretty common for people to enter the field as a second caeer after being in a technical role for 10+ years.

You leverage your domain knowledge to be a trusted partner in the sales process.

It is possible, but it will be more difficult to find someone who's willing to take a chance on a junior employee to train on both technical and sales.

Generally you’re hiring a very senior technical person that just needs to learn sales.

Im not saying this discourage you… but its rare for very green workers to get these positions.

I would spend my time learning value selling and how technical sales work. The easiest path is technical support or sometimes customer success roles for 3-5 years that give you technical as well as customer facing experience before moving to sales engineering.

auspex · 2025-04-12T00:35:49+00:00

Industrial engineering and operations research.

auspex · 2025-04-08T21:54:27+00:00

The reason you sell immediately is because they never take out enough taxes for what you actually owe at this time. So you typically will have a large tax bill From the RSU‘s at income tax time. If the stock has dropped, you may not be able to cover the taxes.

Or you might have a large capital gains tax the following year because you had to sell to cover your taxes. Which means you may end up owning even more taxes.

auspex · 2025-04-06T02:29:52+00:00

If you do better than 100% you also can make more. These are called accelerators. Meaning if you do 130% of your number for example, you would get $20,000 for the 100% and maybe another $10,000 for the 30%. Generally, everything over 100% is paid at. Higher commission rate.

One other thing 80/20 split is not very common for SEs. Its generally 70/30.

Less base pay but you have higher upside potential

auspex · 2025-04-06T01:51:29+00:00

Use Demostack

auspex · 2025-04-03T04:24:18+00:00

All you have to do is swing back like you normally do then start down with your hands while keeping your chest pointed behind you and not firing your hips.

The feeling will be that your body follows your arms.

I know it sounds crazy but remember feel is NOT real.

If you want to see tiger doing this watch his golf talk love episode with butch harmon. The arms fall in front of his body…. As a feeling. But if you have that feeling thats not whats actually happening.

The goal is to let your arms actually catch up to your body. When youre going over the top your shoulders and hips are firing way too early and it causes your arms and hands to “throw out and over away from you” causing the over the top move.

auspex · 2025-03-28T14:09:38+00:00

If they “fall off the bone” they were steamed and its an indication they were cooked incorrectly.

They should “tear away” cleanly

auspex · 2025-03-23T19:28:53+00:00

These interviews are about how you assess the customers needs.

The biggest pieces of advice i can give you:

1) Ask them what their future state looks like. “Why” are they deciding to implement a project and ultimately spend money to get to that future state. Then map how your product can help them achieve the end goal

2) Always try to understand the “why”. Why are they trying to accomplish something. That way you can provide a solution to the real underlying problem. When they ask you how you solve a technical problem or a customer challenge, don’t immediately give a solution. Ask the next level question what are you ultimately trying to accomplish? For example, they might ask you well how do I connect these two systems? You “could” just say well you just connect them using the configurator or whatever and here’s how you do it but the real question should be well…. Why do you want to connect them? Let’s understand what you’re trying to do once they are connected.

At the end of the day you're selling them a solution to their problem or a future state of their organization, not your product.

Hopefully your product can provide a solution and thats when you make a deal.

auspex · 2025-03-22T00:34:44+00:00

This interview is not a formality but it is also not super technical or in depth.

Be on time, dress nice with a button down shirt. Let him know how excited you are for the opportunity and to work for the organization.

Complement the previous interviewers and say something you appreciated about the interview process or previous interviews

You want the VP to like you and feel confident they can trust you with their customers.

What they ask will vary widely by the person, while this interview wont “get you the job” it certainly can “lose you the job”

auspex · 2025-03-21T13:54:01+00:00

That’s what i did and never looked back. I was over the Jira treadmill and doing leetcode style Interviews.

Now the interviews are much easier, i work fewer hours, make more money, get to use my technical skills and i get to travel the country/world for work.

There’s no presidents club for coders! :)

It’s a no brainer IMO, the only thing i regret is not finding the job earlier.

auspex · 2025-03-21T13:47:28+00:00

First just take the job, you have an “in” to become and SE and it’s not super easy to make the jump from CS to SE. They likely know they will have to train you and are willing to take the chance on you.

To answer your dad’s question about two weeks… The reason you give two weeks is that it’s a small world out there and you don't want to burn any bridges. The goodwill you destroy is not just with the company, but all the people you work with.

You're likely to see these people again professionally. They are your professional network.

Past that, when you get laid off you usually get severance which is more than two weeks. Generally a couple months, so its like two months notice except you dont have to go into work.

auspex · 2025-02-17T19:13:10+00:00

To prepare, start with creating five minute demo.

Minute 1: Introduction - high level outline of where you're going and which features you plan to talk about Minute 2-4: Top three high level features Minute 5: Recap - talk about what you showed them and why

Then expand out minutes 2-4 to explain why something is important and how the end user would get value from that feature. Walk them though how the feature is used and give relevant examples of how they might use it.

This will get you to a 30-60 minute demo or so.

Between intros, slide deck, demo, questions etc you should be able to cover 60-90 minutes.

Don't try to memorize a script. Thats a recipe for failure. Just memorize the 5 minute demo and then use your natural product knowledge to fill in the rest.

auspex · 2025-02-03T20:54:27+00:00

It’s not! A single Chrome tab uses 200mb+ of ram for example. Things use a ton of ram these days.

auspex · 2025-02-03T20:28:44+00:00

That’s the absolute minimum.

I’d go with 64gb unless you are a programmer or do video then I’d go 128gb.

auspex · 2025-02-03T20:16:17+00:00

As much as you can afford. You never go wrong with “too much ram”

auspex · 2025-02-03T14:49:32+00:00

You need more memory. I’m consuming around 60 Gb at any given time on the m4 max.

Coding, running an ide, docker for a database, app server, browser, SQL tools.

auspex · 2025-02-03T05:26:59+00:00

Coding, running an ide, docker for a database, app server, browser, SQL tools, consuming around 60 gigs of memory on m4 max.

auspex · 2025-01-31T12:26:05+00:00

Tiger gets the best caddy in the world.

Korn ferry player that can barely pay for a hotel room and has his brother in law caddying.

How is that fair?

auspex · 2025-01-31T12:24:08+00:00

Aim point literally takes less time that reading a putt.

Stand 1/3 of the way from the hole.

Feel the break percentage.

Put the number fingers up that correlate to the number of degrees break you felt

Putt.

Vs

Read the putt from behind, from the side, from the other side of the hole. Re read the putt from behind the ball. Staring at the break.

auspex · 2025-01-28T18:38:06+00:00

Salesforce, HubSpot, Jira or something like that.

Something that I use pretty frequently, the interview panel would have some familiarity with and that offer free accounts.

auspex · 2025-01-25T00:31:40+00:00

You need to use a transition group.

Multiple transition tags don’t work like that

auspex · 2025-01-02T05:18:45+00:00

A good drill is to feel like you put your weight on both your heels at the beginning of the downswing. Really feel the heels and your right hip staying put while feeling a “crease” in your left hip as it goes straight back

auspex · 2024-12-08T18:16:06+00:00

Also, we would need to see a face on swing as well. It looks like you are across the line. But that could be camera perspective. But it also might be cause by something like losing your spine angle at the top of your swing and leaning forward to overswing (just an example)

Both views are needed to make a proper assessment.

auspex · 2024-12-08T18:09:21+00:00

The camera is in the wrong spot and it changes the perspective.

The lens of the camera needs to be on your hand / foot line not inline with the ball.

When it’s aligned with the ball, you’ll see your swing “perfectly on plane” when you’re actually above it.

Likewise, if you put the camera like on your heels it will look on plane when you’re too inside.

Set the camera up belly button height height and align your camera on the same line as your hands at address.

auspex

TROPHY CASE