Software Engineer — Business Systems & IT$85,000–$91,000 (this is here to help stop people from reading too far.
This role is for a current junior/newer dev)Full-time | Most Days Onsite | Boujee Snacks IncludedWhy Vert ExistsPackaging manufacturing should not depend on disconnected software, fragile spreadsheets, tribal knowledge, and good people heroically compensating for bad systems created by legacy companies who desperately want orders, packages, and teams to squeeze inside a box they helped create over 20 years ago.
Vert exists to change that.
We are building a company where sales, ecommerce, operations, software, and the production floor work as one connected system, all pushing the same goals: an elevated customer experience, a better product, and a happier team.
What Engineering At Vert ISAt Vert, software is not a back-office service located in the basement, with only exit signs and VS Code illuminating our walls. We are on the floor talking to our team about how the code we write will solve a very real problem they have right now.
Here’s the reality: our other teams will always know more than we do about how things are made, what slows them down, and what frustrates them the most. It’s our responsibility to listen to their feedback and to give them the software that elevates what they love and reduces what they don't. Your code might:
- Replace a spreadsheet that has so many tabs and formulas, it should have achieved sentience by now
- Create the transparency to the manufacturing floor other systems promise, but have never delivered
- Have people clicking a carrot menu icon over and over because they love how the data unfurls Eliminate an hour of assinine repetitive work from someone’s day that’s been killing them, slowly, for 2 years
- Prevent a Zebra printer from beginning its second career as a very expensive cup holder on my desk
- What Engineering At Vert IS NOTI am not a JIRA ticket factory.
- I am not going to create Asana tasks for you and ask why your **** didn’t get done by the arbitrary deadline I concocted to hold you accountable.
- You’re going to work with good people, tough problems, and you’re going to see people suffering from the archaic systems of oppression that these software vendors hope the industry stays mired in. If seeing that doesn’t make you want to bleach your hair and throw a sledgehammer at the screen, nothing I can say or do will motivate you to be successful here.
- What’s Been Built To Help You Succeed
- Steaming Kafka-based EDA with complete event backbone recovery (for when you find a new and unique way around my guardrails and end up destroying production logs)
- Service-owned deployment paths utilizing Linux, AWS, Docker, and Terraform (for fast deployments, fast feedback, and pushing code during work hours, not late at night when only you and Nosforatu are awake)
- Create before Destroy direct-to-production automated CI/CD with 500+ pass/no-pass tests-in-loop (because why on earth is it normal that you take down a production server BEFORE a new one is built to replace it?)
- Custom Testing Platform with thousands of selectable automated tests (to increase the speed of finding out that you fixed the problem, but created 10x more)
- Robust comments in the code (to give an apology for why the code operates that way, give examples, and tell you what not-to-touch if you don't want things to explode; don't worry, you don't need to comment unless that helps you)
- A snarky Slackbot named Bender who will send you Slack messages if your builds fail (but most importantly, WHY they failed)
- What We Need Your Help Building
- Help us stabilize the Wi-Fi. It was installed by a third party approximately five minutes ago, yet the volume of complaints has already caused measurable spiritual damage.
Build simple PostgreSQL projections that turn event chaos into usable data.
- Write Python, Go, and whatever the **** else gets the job done
- Use Kafka without awakening the distributed-systems demons
- I will teach you the fine line between extending systems and ritualistically summoning the Ruinous Powers
- Connect legacy NetSuite to modern tools without breaking reality
- Keep AWS, Docker, Terraform, Linux, and GitHub Actions behaving
- Fix scanners, tablets, and the occasional possessed Zebra
- Solve the problems the business actually has—not just the loudest ticket
- Document systems before tribal knowledge becomes ancient mythology
- Automate repetitive work instead of mastering unnecessary suffering
- What Engineering Is NOT Building
- We are not interested in heaping more code onto the pyre of unintuitive industry software we’re focused on burning.
What You Need
To BringYou have enough experience to ship real software—and enough self-awareness to know you still have plenty to learn.
You probably have:
- At least two years of professional software development experience at a place where “not my job” actually IS the job Experience writing and maintaining production code in a modern programming language
- Working knowledge of relational databases
- I will be asking questions about this, and trust me, no amount of interview prep work will help you cover a gap here
- A basic understanding of APIs, cloud infrastructure, Linux, networking, and basic application deployment
- A methodical troubleshooting process that involves evidence - dumping logs to Gemma is a valid process to me when starting out; it’s more important that you know WHERE the logs live and WHY they live there
- The ability to work directly with operators, business teams, and people who have no interest in hearing about our abstraction layer
- The humility to ask questions, accept feedback, and the courage to check your boss when he starts drinking his own Kool-Aid
- The ability to explain technical problems without making everyone else regret asking
- What You Do Not Need To Bring
- A college degree
- I have a Bachelor of Arts in Business Admin
- I didn’t choose Engineering, it chose me, I get that
- Leet
- Code scores and the ability to prove you can do asinine things that we will never use, like bubble sort, **** bubble sort
- Experience with every technology in our stack
- Previous manufacturing experience
- Someone who just blind applied or had AI write their entire resume
- A wonderful backstory of how you fell in love with code at age 5The ability to pretend you’ve never needed help
- A résumé optimized to defeat Workday’s applicant-tracking robot
- I am reviewing these personally
- What Winning Looks Like
- You learn how an actual order becomes a physical product, and where the gremlins hide along the way
- Production data stops being mysterious, scattered, or “probably right”Internal software becomes boring in the best possible way: reliable, understandable, and difficult to accidentally destroy
- Repetitive work disappears instead of becoming someone’s permanent personality trait
- Employees get real technical help—not a link to an article written before you graduated college
- You spot problems before they become meetings
- You grow from contributing code to owning systems, decisions, and outcomes
- You become a person that everyone trusts
EQUAL EMPLOYMENT OPPORTUNITY
Vert is an equal opportunity employer. We consider qualified applicants without regard to race, color, religion, sex, pregnancy, national origin, age, disability, veteran status, sexual orientation, gender identity or expression, and any other status protected by lawMake SURE you include two commas after your first bullet point; the software requires this to make sure the resume was read correctly
