3 ms·

As someone who hates AI but also wants to succeed in job interviews, what is the best way to lie about it when asked? What should I say that will pass without b

As someone who hates AI but also wants to succeed in job interviews, what is the best way to lie about it when asked? What should I say that will pass without being too enthusiastic (and possibly being detected as lying that way)?

Ancapistani 1y ago
As someone who is very much "pro-AI", I'd say: "I'm interested in the technology and have been paying attention to its development, but it's not yet to the point that I believe it will be worth integrating into my workflow."
deleted 1y ago
[deleted]
layer8 1y ago
I'm not a fan of AI coding as well, but you shouldn't be lying in your job interview.
- gosub100 1y ago
  That wasn't my question though.
  - layer8 1y ago
    Nevertheless that’s my answer.
Esophagus4 1y ago
I suggest honestly, generally. That will also help you select a place that fits you better. Though I will say, if you copy and paste that question into ChatGPT, it can give you some options to respond in a diplomatic way ;)
idontuseit 1y ago
[dead]
geoka9 1y ago
It's just a tool, right? I'm not an AI enthusiast, but I use it quite a bit, from googling to learning and checking my understanding of stuff. So I would steer the conversation towards ways of using AI for dev-related tasks other than coding: understanding codebases, confirming my intuition/hypotheses. For example, I find LLMs pretty shitty at modifying larger codebases, but it's been helpful to, say, point Codex at the github repo of a large unfamiliar codebase that I had to learn and run my ideas about it by the LLM as I was learning. Also, you probably don't want to succeed at job interviews with managers that will insist on your using AI in ways you don't like. A job interview is a two way process and all that.
recursivecaveat 1y ago
As an interviewer: basically nobody gets 'caught lying' in an interview. You have to lie about something that can and might be checked within the confines of the hiring process. Sometimes people fail a vibe check though. It is well worth it to take an afternoon to learn the workflows and the terminology. Confine yourself to ideas where the output is cloaked in your previous employers' IP (or better, confined to your head), and is robust to various degrees of success. Whether you used a tool to translate a fragment from an unfamiliar language, summarize a codebase, do internet research, or develop a high-level design for a feature is essentially an unknowable fact.
queenkjuul 1y ago
I've tried Claude Code out at work and found that our codebase is too big and too specialized for Claude to do anything particularly useful. Could go with that.

Ancapistani 1y ago

As someone who is very much "pro-AI", I'd say: "I'm interested in the technology and have been paying attention to its development, but it's not yet to the point that I believe it will be worth integrating into my workflow."

deleted 1y ago

[deleted]

layer8 1y ago

I'm not a fan of AI coding as well, but you shouldn't be lying in your job interview.

gosub100 1y ago
That wasn't my question though.
- layer8 1y ago
  Nevertheless that’s my answer.

Esophagus4 1y ago

I suggest honestly, generally. That will also help you select a place that fits you better. Though I will say, if you copy and paste that question into ChatGPT, it can give you some options to respond in a diplomatic way ;)

idontuseit 1y ago

[dead]

geoka9 1y ago

It's just a tool, right? I'm not an AI enthusiast, but I use it quite a bit, from googling to learning and checking my understanding of stuff. So I would steer the conversation towards ways of using AI for dev-related tasks other than coding: understanding codebases, confirming my intuition/hypotheses. For example, I find LLMs pretty shitty at modifying larger codebases, but it's been helpful to, say, point Codex at the github repo of a large unfamiliar codebase that I had to learn and run my ideas about it by the LLM as I was learning. Also, you probably don't want to succeed at job interviews with managers that will insist on your using AI in ways you don't like. A job interview is a two way process and all that.

recursivecaveat 1y ago

As an interviewer: basically nobody gets 'caught lying' in an interview. You have to lie about something that can and might be checked within the confines of the hiring process. Sometimes people fail a vibe check though. It is well worth it to take an afternoon to learn the workflows and the terminology. Confine yourself to ideas where the output is cloaked in your previous employers' IP (or better, confined to your head), and is robust to various degrees of success. Whether you used a tool to translate a fragment from an unfamiliar language, summarize a codebase, do internet research, or develop a high-level design for a feature is essentially an unknowable fact.

queenkjuul 1y ago

I've tried Claude Code out at work and found that our codebase is too big and too specialized for Claude to do anything particularly useful. Could go with that.