There’s a lot going on here, and I suppose you need to think about what you want.
I’d say all testers are technical but in different ways. Some can read code, some can write it, some are good with tools made by others, some know a lot about databases or networking or whatever domain you work in. There’s the technicality of fields of mathematics and statistics and philosophy. So if you test the front end but also use a tool to inject test data into a database are you technical or not? Is that back-end enough on which to get cracking? Maybe they want security testing, or performance testing or automatic check code writing or something. There may be questions for the company - a good one can be “what does your ideal candidate look like”. Of course maybe they just don’t want to hire you for one reason or another - e.g. they already have someone they want.
When you’ve settled on what you think they want then it’s a case of whether you do fit that description, or could, or want to. If there’s a gap between what you can do and what they want then you can decide what you can offer, and what you’re willing to. If someone said they wanted a code writer instead of a tester I’d say “that’s not me”, but if someone wants me to learn their API I’d say “of course”.
When you’re straight with that you can decide if you want to work there. If you do then you can negotiate your options. There are things you can sell to them very easily - they know you and trust you, you are familiar with their software and domain, you are easier to price and people who know more about certain things can be more expensive, and you can sell your ability to learn and adapt to their needs. Sell what you can do, make them consider what they’ll lose by replacing you - things they didn’t think of until you said them. Sell what you are willing to do.
So basically your factors are
- what’s your situation, do you need this job or can you walk into another?
- do they want you to work there and do you want to work there (will you be working with good people in a good place for good pay, etc)
- what can you do
- what do they want you to do
- what are you willing to do to bridge that gap and stay happy and motivated, and what you’re willing to promise
- what can you sell them on
While I’m here I might as well point out that you are technical, but there’s a lot of kinds of technical. UI, UX, mapping system states, all technical. If you want to feel more technical take something you do and give a technical name. I made someone much more comfortable with using a “wait command” in some code by suggesting the name “stochastic reliability buffer”. Same code, new thinking.
Learning more technical things is a great way to become a more powerful tester, as is learning about mental models or test framing. In my experience taking powerful testers and training them up in the technical is far easier than taking technical people and training them up in testing. A great tester can test anything, and that often means pushing a lot of reset buttons when it comes to technical things with any new project.
I’d recommend looking at something you can do that you might enjoy and trying it out. A great motivator is ways to take the pain out of your work - being able to reset a database to a known state or inject known sets of useful test data can make your work faster and easier and provide more time for the fun stuff. And if you can do that and still think of yourself as “non technical” then that definition will just expand to fill the size of its container until you can move electrons with your mind.
I guess that’s my overview without further details, hope that’s helpful!