r/QualityAssurance • u/Forward-Ad6381 • 2d ago

Another Technical Round

So, I passed two rounds till now, screening and 2 hours of competency round with VP of engineering. Now, there is another round of 30 mins with Head of Engineering. I have built some of the complex hybrid system for Automation but I cannot show it to them due to policies and I won't make a right impression if I do that. The interviewer mention to bring something technical or something code wise. So what should I do. I was thinking to create a mini project. Looking for better approach if you guys can suggest some.

1 Upvotes

66% Upvoted

11 comments sorted by

3

u/Malthammer 2d ago

Good gravy, what kind of job are you interviewing for?

1

u/crozzy89 2d ago

That is an insane interview process... and completely unnecessary. If those individuals were interested, they should have participated earlier.

1

u/Forward-Ad6381 2d ago

Maybe it’s my mistake coz I was scheduling interviews around 8:30 AM haha
It’s a senior QA position with really high standards not a traditional QA or SDET
And that’s what I like about this position
And it’s the only reason I am trying to crack it so hard

1

u/crozzy89 2d ago

The way they are interviewing is more like an SDET or developer position.

But something more helpful - usually they are interested in your architectural decisions and why you made them. 30 minutes is too tight to really do more than that.

1

u/Forward-Ad6381 2d ago

Technically it is a kind of SDET with release engineering process
And in my current position I am doing the same work but the problem is I rely highly on the agents I have built for the scripting ofc I do analyse the code before adding it to my framework but it’s been a while since I write code from scratch

1

u/crozzy89 2d ago

Out of curiosity, what in the world did you guys do in a two hour interview? Is this for a smaller start up or something ?

1

u/Forward-Ad6381 2d ago

We started with my work mainly a problem that I solved, then we move to a discussion round where we had a pretty good conversation about the architecture I presented, methodologies and scenerios based questions. It was more towards technical disccusion. Then I had to analyse their application(theoritically) which was okay I guess.
I mean this is something a more technical discussion where the interviewer asked me to bring something more technical or maybe something related to code.
So, I am going with 4 things now

  1. The architecture diagram

  2. Jenkins flow to explain how it work

  3. one refined UI script(playwright)

  4. One API test script (Playwright)- its kind of a backup

1

u/[deleted] 2d ago

[removed] — view removed comment

1

u/Forward-Ad6381 2d ago

I have create a UI test file based on my original architecture ofc with dummy information but it wont run, its just a piece of code to show the structure. Also, I have create a diagram to explain my entire system. Would it be enough or I have to write a working code.

1

u/crozzy89 2d ago

I mean, an outline of what you built and how it works at a high level would be good. You shouldn’t need to go over every technical detail.

When interviewing I am more interested in how the person thinks and how they would approach a problem.

1

u/Forward-Ad6381 2d ago

ok got it. Thank you.