You seem like a cool person, and are working hard towards a transition - congrats on getting this far. I think with a bit of effort you can follow through. A few thoughts:

- Website makes you look like a front end developer, but you are applying to full stack.

Stepping back a bit, an employer is asking the question: is this person the best person for the job that I'm hiring for? As the job seeker, you need to think about what type of job you are going to be the ideal candidate for and really focus on communicating that.

- Bullet points on resume could be improved. For example, Content is easily added or removed using a JSON configuration file Its a given that you would do that. It is so basic that it raised a flag in my mind. Its like saying, I used numpy to do math computations in python. It would be better to not include that statement.

Full stack web developer who will help your company succeed by completing projects on time and under budget. This sentence comes off as pretty generic, and it is not clear that you have experience with that. It would be better to have an experience where you delivered a project under time constraints.

Anyways, sorry that I'm nitpicking a bit. It is hard to know exactly what is holding you back without knowing more about what jobs you are applying to, what is happening in the interviews, and so on.

I'd also think about if there is any company you can work at where having some background in industrial automation would be a plus.

I suppose I'm also curious, are you applying to jobs that do algorithms and data structures interviews?

If so, you really need to nail those. A lot of people complain about those interviews, but they do serve a real purpose. There is a significant gap between building a small website and building a system that scales. If you are going after high impact software engineering jobs in the bay area, then you'll need to demonstrate that skill set. I don't see anything about algorithms and data structures in your resume, so I'd assume that you don't have that knowledge.

Granted this may be an unpopular opinion, but not having those skills significantly limits your upward potential.

While i've yet to be put through one of those interviews, I would imagine that I'm applying to some of these places. I've been applying to mostly smaller companies, so it's hard to know what kind of interviews they do in a lot of cases. This being said, I do brush up on time complexity/data structures/algorithms/bitshifting etc. before I go to an interview.

I've been working on my portfolio/resume for a long time, so all there really is left to do is nitpick, so I don't mind at all.

I agree that maybe I can do more with the bullet points. I can think of some higher level things that "JSON configuration file"

I also agree with the "Professional Summary". I hate it. I workshopped it with some people and this is what we came up with. It sounds so stupid and now I'm thinking the move is to leave it off completely.

Could I ask what you mean't about my portfolio looking like I'm a front end developer? I'm pretty sure the majority of my projects are either Full Stack, electron.js apps, or have embedded components.

I just mean that the design of the website is very nice (fancy?) so at a glance, that is the main thing that I noticed. Granted, I didn't end up reading things too carefully because I was thinking about the design. I think that the website good as long as you put your resume front and center and improve your resume.

Thanks, i think. My resume is what needs the most work.

Just to be a bit more specific, the most important thing is that you make a compelling argument that you are the best person to hire for a given job among the candidates applying.

I think you need to put in some work to (1) have some more clarity on what you want to do (2) doing more projects along that direction and (3) updating your resume accordingly

As an example, one of my friends was doing public health, and she wanted to get into tech. She learned a fair amount about user experience design, built some projects, and then applied to jobs where her background in public health was an asset. In particular, she got a job doing user experience for a healthcare startup in order to improve the experience for people who are typically underserved by healthcare. She had experience in that area because her public health work looked into how underserved populations used and accessed healthcare.

It felt daunting to her to get into tech, but she did it by making a compelling argument that she was had a combination of skills that would make her effective at her job. She did end up applying to many jobs, but only the ones where there was a good fit gave her an interview.

Now you have to figure out how to make that type of argument for yourself. Of course that template may not work for you, but that level of preciseness and clarity of thought is what you should be aiming for.

One other thing that just came to mind is that if you have experience in the automotive industry, that could be relevant experience depending on where you apply to work. I'm not sure what it is, but you don't need to sell your self short on that.

I prefer price transparency because it helps me decide whether to order directly through the delivery app or via the restaurant. The extent to which I support the restaurant is a factor in my purchasing decisions in addition to the total cost. Having good restaurants that are profitable near where I live is helpful for maintaining the community (and good for property values).

The restaurant is in a much better position to make that decision though. Uber might have high fees and it still might make for phenomenal business. But you would judge the high fees and go somewhere else thus harming the business.

Capitalism isn’t perfect but this is pretty elementary stuff. Information asymmetries are why price is so important: it encapsulates everything.

I’m glad that there is more efforts towards price transparency. I find it strange how much the prices on DoorDash fluctuate. As others have said, this doesn’t cap the delivery fee so it doesn’t impact the economic viability of any transactions.

Maybe I'm a bit late to the party here, but I do career coaching and I'd be happy to schedule a free 30 min chat / do a practice interview. [Email in profile]

Regarding my experience, I have passed SWE interviews at google (interned at oculus/facebook) / regularly conduct such interviews at my company. On a bit more personal note, I definitely had a phase in my life where social interactions didn't come naturally. I needed to break down social interactions and create rules to better navigate them.

Regarding baseline feedback, there is already a lot here, I'd just say that your number one focus should be to get a job and focus on keeping that job for a year or two. People will only trust you with more senior roles if you can demonstrate a track record of commitment. Of course, it may be the case that all of your previous jobs were bad situations to begin with, but people who are looking to hire you now don't know what happened and will see leaving many jobs as a red/yellow flag.

I imagine that it will take effort, but is totally within your capabilities, to work on staying committed to a job for 1-2 years even it if feels below you, etc. It may take some changes in perspective, but it is definitely possible to get help with navigating the mental hurdles that come with staying at a job even if it isn't the most exciting thing in the world.

I'd also take a lot of the armchair diagnosing with a grain of salt. Its normal for people to struggle with various types of social interactions. If getting diagnosed were important to you, you could definitely see a licensed psychologist (not me).

All that being said, let me know if I can help!

Thanks for your comments. Regarding determinism, potentially a fair point. Here are a few comments: (1) A driver which randomly produces different output when running the network would be valid according to these restrictions. (2) It is conceivable that a driver would produce non-deterministic input with the same hardware. One commonly known example is that tensorflow will run multiple different convolution kernels and then choose the fastest one. In that case, you can run the same network on the same hardware and get slightly different results. Its not that hard to imagine that a mobile driver could do something similar. (3) It's not true that specific hardware will produce consistent results on the same input. You can run a model today, the driver gets updated, and tomorrow you get different output. This happens frequently.

All good points! "Non-deterministic" behavior within the same program/process is still a bridge I would not want to cross. This could result in subtle glitches, e.g., when a user hits "refresh" with the same inputs, and could make reproducing bugs impossible.

I am a strong believer in always using a seed for random number generation for exactly these sorts of reasons. (Side note: deterministic RNGs is one of my favorite features about JAX.)

You are paying with performance for the determinism. Any DL framework can be made deterministic (just add few lines of configuration), not just JAX.