Hacker News Reader

Do you say “hardware” to mean “mechanical engineering”? That’s kind of what it seems like from your description and screenshots. It’s probably worth making this a bit more descriptive - to some people “hardware” means PCBs and electronics. (I’m one of them!)

It’s an interesting idea and I like that you’ve stood up something minimal to test your product offering quickly.

What’s your elevator pitch for your value proposition?

How do you plan to scale this business beyond you and your co founder?

That’s a good point regarding hardware in the name. Eventually we’d like to do all hardware and more (e.g. architecture), but currently our expertise is in mechanical and robotics engineering.

Our pitch: We make recruiting easier, better and cheaper for the companies building the hardware of tomorrow, by letting them focus on their product rather than repetitive candidate skill assessments. Currently, senior engineers in small startups and scale ups spend a lot of their time interviewing, and they often don’t do it well (remote CAD sessions aren’t really a thing). We save them time and money.

We will scale this by hiring freelancer interview engineers. This has already been done in software, very successfully: karat.com. So we think it can work at least equally well in hardware.

That’s an interesting thesis.

I know recruitment firms serve some of the phone screen purpose you’re proposing, but just with basic Q/A of resumes.

I think, if I were looking to hire you, I’d be wondering how alike your working style was to that of me and my team. I’d want to know how much I could trust your judgment in a candidate’s technical approach.

I’d also offer that you can’t really outsource the job of evaluating cultural fit - which is still really important in spite of all the baggage that term carries.

Thank you - we think we’re at least 10x better than a non-technical recruiter (also because they have completely different incentives).

These reservations are fair. Hopefully, eventually we’ll have enough endorsements and references to give you some confidence. If you’d like to give us a try before then, happy to talk whenever at founders@touvlo.co!

We don’t do cultural fit at all, and we don’t intend to. I agree this is very important, yet very difficult and inefficient to outsource. We don’t aim to replace all interviewing: becoming a better substitute for early-stage technical screening is more than enough.

I just want to reiterate the comment you're replying to; in mine and I safely assumed until now everyone else's mind, hardware means electronics/electrical. When I job hunt for a computer engineer role, I often use "hardware engineer" as a prompt and I've never seen it return a mech eng or robotics one. Hardware just seems the wrong word to use in your case.

Interesting. What kind of customers do you serve? (Non-hardware companies that just want to spin a product but no idea how? Companies that need lots of hardware engineers but don't want to interrupt their current ones to interview?)

How are they thinking of hardware engineers? (Like an interchangeable commodity or one that can get a letter grade? Very transactional, maybe a gig?)

Will your customers do substantial additional interviewing after passing your technical interview, for qualities you don't or can't evaluate but companies should? Could your service be mainly a screening, before a company invests more significantly in interviewing with technical and other team members?

What is your answer to "Why did I spend 4 years in engineering school, and build my professional track record, yet have to keep doing these negging tests? Does this company not employ anyone who can get a sense of a fellow engineer's skill and professionalism just by talking with them? Did they read my resume? And now they're not even administering the test themselves?"

Can a particular job-seeker interview with you once, and get their report card sent to many employers over time? Who pays for each instance, and do they pay less if it's reused?

These are all great questions, thank you.

We don't want to serve non-hardware companies that are hiring their first hardware engineers. We want to serve companies of all sizes (including startups) that are building products that are so critical that they can't waste their senior engineers' time to do 10-20 technical interviews a week. These customers will care a lot about their hardware engineers.

Yes, our customers should do more interviewing for candidates that pass the Touvlo interview. We think that our service should be primarily a technical screening before the company invests more in additional interviewing, but you're free to use it for at any step of your recruiting process. There is also more to evaluate in a potential hire than technical skills (for example, cultural match).

> Why did I spend 4 years in engineering school, and build my professional track record, yet have to keep doing these negging tests? Does this company not employ anyone who can get a sense of a fellow engineer's skill and professionalism just by talking with them? Did they read my resume? And now they're not even administering the test themselves?

There's two parts to this: (1) On one hand, the interview should never feel like a negging test and the interview of a graduate should be completely different from the interview of a senior engineer with 5+ years of experience. And if you are extremely senior with an amazing professional track record, then perhaps no technical interviewing is necessary at all. (2) On the other hand, no one should feel offended for having to do a technical interview that matches their seniority and experience. It's outsourced to a third party company, because we can do it better and faster. Candidates will be happier, because they can interview outside business hours (incl. weekends) and have a positive experience. Also, the alternative in many cases is that the company won't bother interviewing the candidate at all, or worse, they might send a take-home test that takes hours to 100 candidates and then spend 0-3 minutes reviewing each.

Currently a job-seeker can not get their report card sent to multiple employers, however this is a good idea to consider after getting to a certain scale. At that point, we would essentially become the standard in hardware technical interviewing. Figuring out a fair payment model would be one of the challenges.

Touvlo in greek means brick but it also means metaphorically a very bad student.

We’re both greek, it’s meant in a joking way :) What do you think of the name?

the second I read it I knew it was Greek I have actually thought of using the name for an app before years ago, but it never happened as I thought it's... a bit rude? not sure if this applies when exposing your app to a mostly non-greek audience though

It's very offensive to call someone τούβλο because in reality its meaning is more or less "he's too stupid to understand, his mind it's thick like a brick...".

I would urge the project founders to rename it to avoid possible legal complains by those who may consider it quite offensive to say the least.

Just call its ancient version πλίνθος and you are good to go!

Recalling certain candidates that I have interviewed over the years, I'd say it is spot on!

Greek here. I would NOT want to associate in any way with a site named Touvlo, even if it is used in a joking manner. Too offensive! For a non native speaker, ignorance is bliss. But once they found out what Touvlo really means, i still bet they would feel cheated, and/or embarrassed. Therefore in both cases, it's a no go. Just my 2 cents.

Thank you, this is good feedback. We’re both native greek speakers, and we meant it in a lighthearted way, but you’re right that not everyone will see it this way.

I would also agree with the grandfather comment. The name is a little too offensive when used in a professional environment...

This is an interesting idea, the one challenge is this is really only a small part of the interview. This covers the CAD skills part, but where is the industry specific knowledge part, communication skills, presentation skills. I can't emphasize enough a "hardware" engineer that has 10 years of experience designing surgical robotics and one that has spent 10 years designing catheters or sunglasses may be wildly different in their suitability for a given role. Both use Solidworks, onshape, etc to design hardware, but these things are not the same. How do you address this challenge?

We don't want to replace all interviewing. We won't test for culture fit, or presentation skills (although we can test for some industry-specific knowledge and communication skills). You can think of it as technical screening stage.

That's what I was hoping to dig into. If I'm at a surgical robotics company interviewing for a hardware engineer to design a robot arm, I'm going to give a completely different technical portion of the interview than if I were at a catheter company doing the same, or at a sunglasses company, or dialysis, etc. You could perhaps handle it by having "vertical" specific interview templates. Just thinking through the challenges to adopting this in my workflow. I wish you all the best!

It looks like they are simulating a solid modeling program, one that looks vaguely like SolidWorks or Autodesk Inventor/Fusion, but with a worse user interface.[1]

[1] https://touvlo.co/images/feature-three.png

Onshape is a pretty popular CAD package! We use it for robot hardware (moving away from Fusion).

This is onshape indeed, but we run a collaborative VNC (soon-to-be RDP) session through the browser. We can run anything that runs on Windows (so everything).

Hi! We’re not simulating anything, we run a collaborative VNC (soon-to-be RDP) session through the browser. We can run anything that runs on Windows.

Just a small piece of feedback, it looks like there's a small typo on the last paragraph of the page:

> Interviews can be scheduled (and rescheduled) interviews around the clock, 7 days a week.

I believe the second `interviews` should be omitted.

Thank you!

Looks like a CAD operator's interview, not an engineering interview. I guess the basic DFM question is marginally engineering.

Good point! We do our best not to test any skills that would be tested in a CAD certification. Our questions and rubric don’t emphasize style for eg or comfort in a software. The collaborative CAD portion is a section where more complex engineering questions are answered, through a platform and in a way where they’re usually solved in the workplace. We view this as analogous to the coding portion of a software engineering interview.

You should show an interview example with engineering questions then. The questions in your example interview are technician-level. Checking a mechanical drawing for consistency is not an engineering task - the job that does that is "design checker". Design checkers typically have associate's degrees in drafting or CAD operation. The DFM question is arguably engineering but it could be even better answered by a machinist.

Engineering questions do not have to be complex, but they are different in kind.

Huh, that's an interesting idea. But as an engineer at a small automation integrator, who never has time between busy projects for important-but-not-urgent tasks like interviewing new hires, it seems I should be in your target market, but I can't imagine delegating a critical decision like this to a third party.

Who is your ideal customer? I'm imagining either a nontechnical solo founder (with a really good, high value idea that he'll explain after you sign an NDA) looking to hire a first engineer/technical cofounder to actually build it...and all the problems that come from that. Or I'm imagining a big corp with an HR department that's at odds with the engineering department, always denying their hand-picked candidates and sending them unqualified candidates, but I'm fortunate to have never experienced that kind of environment.

Maybe we're not in your target market in that we expect to need to do training, and don't expect our best long-term candidates to be able to hit the ground running at full speed. We've hired senior engineers with zero experience in our Autodesk Inventor CAD suite, as well as fresh grads with little experience whatsoever? Our "HR Department" is really just two people (our CEO and accountant), so there's no "must know how to lay out a robot cell" to validate in an assessment.

Or maybe we're not in your target market because already have an engineering department with something like a century of combined experience who are totally capable of sorting out a good candidate from someone blowing BS.

Or maybe we're not in your target market because we are just an ordinary small business, we have negligible turnover (it's been 6 years since someone moved to a different company), and only moderate growth rates (only hired 3 engineers in the past 6 years), it's just not that big of a time sink. I suppose a hardware startup with meteoric growth rates would need to spend a lot more time hiring engineers.

One question: You write "We can use any CAD software you prefer." Any? Really? Seems you need a short list here. If you're providing the license, having seats of Inventor, Solidworks, Catia, Creo, NX, Fusion, etc. on hand for occasional interviews sounds really expensive. And an experienced designer who can effectively every one of those is really rare and also expensive. I would call Altium/Cadence/Kicad "hardware design CAD packages", but those are completely different skillsets and I wouldn't expect a typical ME to know how to use them well.

You’re absolutely our target market! You’re not delegating the decision, you’re delegating the interviewing. We don’t make a decision, we give you a video and scorecard of a one hour technical interview. You can integrate our interviews at any stage in your pipeline (e.g instead of a phone screen), and do more interviewing for those that do well. Please note that this is common in software, see karat.com.

Yes, we can use any CAD software (or at least, we will seriously consider it). We’re a new company and following the YC advice of doing things that don’t scale. If that means buying 5 different software licenses for our first 5 customers, then we’ll do that.

Show HN: Touvlo – Technical Interviewing for Hardware Engineers (By Humans)