I am interviewing a lot of candidates these days
for forward deployed engineering roles
I am only looking for these 2 signals
in their story:
A] Sharp B] High agency
from now on the only 2 ways to keep yourself safe from layoffs
1. find consultant friends
2. build software and get 10 users
the Microsoft situation is bad
but these factors remains the cause
wanted to write this on LinkedIn
but writing it here:
SWE is going through massive transformation and there will be consequences
3 things that every SWE must understand:
1. Writing code is an economically unviable.
2. Existing SWE processes like Scrum, Agile etc were designed to support human limitations of writing code. AI has broken that limit.
3. Fable, Astra & Argon is showing the world that most code written by humans is sloppy. Follow the PHP news you’d understand.
It is time to focus on outcome rather than the older process.
At this pace, the only blockers are humans who still hold the processes dear to themselves.
Dont be blocker, else leadership will remove the blockade
Replying to @softcane
This looks great btw, if the application is using LLM apis will this work?
Replying to @Dawid_AI_
5 so that humans can quickly glance over it and share opinions.
This is not an ARB
Replying to @akash_kushwaha1 @grok
don’t use grok buddy, try testing your judgement then we can all learn
Forward deployed engineer interview questione
Redact PII information from email corpus before the LLM processing
and put it back in the final output
describe the solution in 5 points
Replying to @Soul1ss
Ya. It should have been economically viable venture.
But I guess that’s what make me a human
Replying to @jurlycat
JIRA as of today is just a todo list for my agents
if there is no one to watch that could be an MD file
Replying to @BenittoJD
first step would be stop being a process junkie
wanted to write this on LinkedIn
but writing it here:
SWE is going through massive transformation and there will be consequences
3 things that every SWE must understand:
1. Writing code is an economically unviable.
2. Existing SWE processes like Scrum, Agile etc were designed to support human limitations of writing code. AI has broken that limit.
3. Fable, Astra & Argon is showing the world that most code written by humans is sloppy. Follow the PHP news you’d understand.
It is time to focus on outcome rather than the older process.
At this pace, the only blockers are humans who still hold the processes dear to themselves.
Dont be blocker, else leadership will remove the blockade
Replying to @gkcs_
the change is painful especially for
4-8 y experienced folks
Few days back a sr director of tech
at one of my client co
asked my team
to add time spent on per story
in JIRA
Man, you are obsolete
Just don’t make it obvious



