Behind the code: Insights from a new grad at Benchling
As university hiring season kicks off this December, we wanted to show what it’s really like to start your career at Benchling. Who better to tell that story than one of our new grad hires? From working in legacy code to making the editor faster for scientists, Vicente Miranda gives a firsthand look at engineering at Benchling and what the first few months involve.
Q: You could have built almost anything anywhere. What made you want to build software for scientists?
A: I personally think writing software that helps academics and industry science is a super cool position to be in, and arguably quite rare. University-type software systems sometimes get a bad rap as being ‘dated’ or dysfunctional, and I think Benchling is slowly shifting that stereotype around.
I’ve met a couple people personally who use Benchling (mostly academics), and the response is always so positive when I tell them I work here! I think that speaks to how excited people are about molecular biology and chemistry, and the types of impact they want to have on pharma and health.
Q: What was the steepest learning curve in your first few months, technical or otherwise?
A: I had a lot of trouble managing how much time I’d spend writing integrations into legacy front-end frameworks. For example, one of Benchling’s product offerings is an electronic lab notebook (ELN), a product researchers use to record their experiment findings. One of its key files is a 6,500-line class-component beast that uses upwards of three state management systems.
On the one hand, you want to learn each system really well so you can iterate on the file and improve things quickly for customers. But, it’s not really feasible to master every third-party front-end library (at least, not in four months), and it’s even undesirable in the sense that we want high velocity at the company. I think that’s a habit you have to manage when going from university to companies.
Q: What are you working on now, and how does it connect to what scientists do in the lab?
A: In software development, we have this concept of a “pull request” — putting up code changes and getting some of your colleagues to review them, as an isolated unit of change. I recently put up a pull request that fixes some of our end-to-end tests for virtualization in the notebook editor.
This fix was only about a dozen lines, but it produced an enormous amount of confidence in our product and helped us get back on track for a top pharma customer. A lot of the work I do is sort of these small, dedicated fixes that improve the quality of the system and/or slowly build out extended functionality.
As far as how it connects to the lab, virtualization is a big win in that our editor now loads up to 95+% faster, at little up-front cost. This gets scientists’ development velocity up and more drugs on the market quicker — a win for pharma at large.
Q: What does mentorship look like for you? Who do you go to when you’re stuck?
A: Mentorship is definitely an important topic for people leaving school and joining the workforce for the first time. At Benchling, I consider myself blessed to have more than one mentor — it sort of depends on the problem in question and the context needed.
My team has several super supportive (and tenured) engineers, and beyond that, lots of helpful people offer their time to me if I need it. I’m sure other companies have people who you can rely on for help, but the extent to which people at Benchling will go is humbling. I frequently ask myself how I wound up collaborating with so many smart (and kind!) people in the same place!
Q: How would you describe the engineering culture to someone outside the company?
A: People care. I think that’s a big thing. As previously mentioned, I’m sure other companies have hard-working engineers, and teams that can operate at high speeds.
But Benchling is unique in that if you need help, someone won’t just work with you on a problem; they’ll ask how you’re doing, give you space to ask for a break, and genuinely ensure that you’re addressing the problem collaboratively. If they don’t have context on the problem, they’ll point you to someone who might.
I think that exemplifies how much everyone here really cares about each other. It helps too that the problems themselves are deeply interesting. I recently whiteboarded a challenging data modeling problem between two isolated systems, with the relevant tables involved growing to tens of millions of rows. Knowing I had that large of an effect on databases used by billion-dollar pharma companies was so humbling! I just graduated school!
Q: What keeps you excited about working here?
A: I keep meeting people who love Benchling! I kid you not, on the BART I’ve run into multiple academics and industry professionals who happen to use Benchling, and proceed to give me thoughts and/or excitement about the product!
I think that alone is super cool and makes me excited to keep coming into work every day. Beyond that, I’m a big fan of what I’ve described previously: everyone is so supportive, stress levels are rarely high (or only high when the situation calls for it), and the pace is genuinely quite fast! Seeing a feature I’ve worked on in a day get immediate feedback is super cool (virtualization).
Q: What advice would you give new grads and interns on the search, the interviews, and standing out?
A: First thing first — I’m only 23, so take this with a grain of salt :-)
I would say to tune out the noise and focus on what matters. Not really novel advice, but there are lots of distractions and ways to avoid working on the right things. If I look at your resume, do I have confidence I could work with you on an ambiguous distributed systems problem, if I taught you the relevant pieces? Could I have faith you’re putting up pull requests that meet codebase standards? These are the types of questions you should verify you’re passing before getting into granular detail (verbiage, impact, etc.).
On top of that, technical skills are still super important, even in the age of large language models and agentic coding. If you can’t, in layman’s terms, explain to me the difference between a linked list and an array list… you might have trouble convincing a company to hire you!
Why Benchling is a thriving space for early career developers
This new grad’s journey highlights what’s special about Benchling — the chance to do impactful work while learning alongside smart, supportive mentors who genuinely care about your success.
As December hiring kicks off, we’re excited to welcome interns who want to make an impact on science and technology. Could you be the next leader in biotech software innovation? Explore opportunities to join our team here.


