- Game Development@programming.dev
- GameDev@lemmy.blahaj.zone23 karma · joined November 23, 2021
- Game Development@programming.dev
- GameDev@lemmy.blahaj.zone * Use local machine learning models wherever possible.
* Summarize and consolidate calls whenever possible (i.e. reduce token sizes using language analytics).
* Log all calls/responses so it is possible to reuse them and/or to train your ML models. This can cut down on duplicate calls.
* Monitor your API call logs to make sure the system isn't making calls it shouldn't.
* Throttle your calls by introducing delays/bottlenecks in the user interface (by far my least favorite).
* Charge more for your services to decrease demand.
* Contact your account rep and see what options they have to offer with a higher price tier.How many jobs are you applying to each week? I would think 1 or 2 each week would be a minimum.
Do you have a portfolio? Some code you can point to online, any open source projects you work on?
How many interviews do you average each month? If you are applying to tons of jobs and not getting any interviews, this is a reflection that your resumes might need work. Resumes, plural, in that you should probably have several depending on what type of job you are applying for and what skills you need to emphasize. Maybe you need to drop some jobs off of it or rework it to look more like you have been courting contract or short term work and now you are ready to "settle down". Have you filled gaps with additional university courses? Pursued a Masters degree? Certifications? Traveled the world? Volunteer work? Freelance/Started your own business?
If you are getting interviews, but not job offers then this indicates it might be a problem with your interview style. You mentioned depression, could this play a factor? Hopefully you don't bring up medical conditions during interviews. It could be some of the things you say during the interview process, not saying enough, questions you ask, what you wear... any number of things. I almost didn't hire someone because of the socks they wore but my team defended their choice of footwear and we hired them in the end... though the guy in the Christmas sweater wasn't as lucky :)
Have you tried teaming up with a recruiter? A good one would help you with your resumes and interviewing skills. Are you keeping in touch with former classmates, colleagues and managers? Not just email, set up lunch dates with them to stay in touch. Set up a small lunch reunion from a company you worked at where several people were all laid off or have since quit. They may have leads from time to time. Looking for a job can be a full time job in itself!
Good luck!
* Email: Within 24 hours
* Instant Message/Chat: Immediately, Within 2 hours.
* Phone: Immediately, return a voice mail within 4 hours.
* Scheduled meeting: Give at least 24 hour notice.
If you really need a response, pick up the phone, multiple times if necessary. You could also schedule a meeting with the person. For some people/situations I know I will need to include someone else on their team, sometimes a supervisor, to get any traction.
You should escalate on the third non-response by including their supervisor on an email, group chat, or meeting. Include previous communications with dates. Take this advice with a grain of salt and take into account previous interactions with the person of course.
If you have a ticketing system, copy and document each communication into the system. In some situations you may want to start with the ticketing system even if you could send the request directly to the person to begin with.
I can't tell you why your resume has been rejected without them contacting you, but assuming it is a well written and accurate resume, it is because there were other candidates that were a better fit for the position. Meaning they had direct experience with the technologies involved, worked in similar industries, they were physically close, didn't appear to be over qualified (I wouldn't bump them off the list for this without first talking with them), and were well rounded. Some things can get your resume rejected quickly by the hiring manager, this could include not being local to the company (even for remote work if there are plenty of candidates that are close), missing experience, spelling errors, poor layout, poor communication, over qualified, non-relevant experience being included, stuck in the same position/job too long, etc. I don't even want to get into age, gender, and race discrimination which can come through in the resume in the form of dates and names.
Bottom line is, for best chances, you have to customize your resume for each job you apply for. This is time consuming and usually doesn't feel like something you should have to do or that it pays off.
If after all of that there is still a problem, setup an End-of-Day meeting each day with the individual to go over what they accomplished that day... actually having them show you code, interface, documentation, something that they had accomplished that day. In collaboration with the employee setup reasonable expectations and goals that you (hopefully) can both agree on. If the goals are not met, write them up, rinse and repeat. After a couple of write ups suggest that they are not a good fit and should think about moving on, after three or so you should let them go.