There are some common best practices for 1-on-1s that I often see pop up:
✅ Hold them regularly
✅ They’re not for status updates
✅ If something comes up, try to reschedule instead of cancelling
✅ The 1-on-1 is for the employee, so they should own the agenda
If you have these foundational concepts on lock, but you find that you’re still not feeling the ✨ magic ✨ of a good 1-on-1, here are a few things you can try.
If you don’t have one already, try using a simple shared doc in your 1-on-1s. …
At FloQast, as we move towards evolving our micro front end, teams were tasked with integrating their existing clients into a hub for all of the front-end clients.
At FloQast we have a constant backlog of work and ideas flowing from the Product team to the Engineering team. Frequently those ideas for new features are presented to us in the form of a PRD (Product Requirement Document) and often times it’s critical for us as engineers to transform those ideas into our version of an ERD (Engineering Requirement Document also known as a Technical Requirement Document).
An ERD serves as a blueprint for how the engineering team is planning to solve the problem presented to them. It presents a way for our engineers working on…
Here at FloQast, we do quite a bit of parsing, especially of the language of accountants known as `xlsx`. As part of our normal secure software development lifecycle (SSDLC) and our application security (appsec) program in general, we test the components that become part of our product. Testing includes not just the normal OWASP top 10 type issues, but also more advanced attack techniques like fuzzing.
Fuzzing is repeatedly giving a program random or pseudo-random inputs with the goal of discovering unhandled errors or unintended behaviors. …
When integrating an application with external data sources, developers need to be conscious of how an API request may impact performance. If you are not careful, you could easily receive responses that contain lots of unnecessary data, resulting in payload sizes that increase memory costs and network latency rates.
Here at FloQast, we’ve been going through the process of transitioning large portions of our codebase to smaller repositories on both the backend and the frontend. Since some of our code was no longer stored in a back-end monolith, we could notice a delay in some of our…
In any software engineering department, a common question will be, “Is it technically feasible to [do this thing]?” The follow up question then becomes, “Well, how long will that take?”
Previously, I had written about how FloQast uses relative sizing for epics to understand a team’s roadmap. Unfortunately, t-shirt sizing doesn’t deliver an exact date so dates can be in the eye of the beholder, causing confusion. Then in addition, what happens if those dates are wrong? And why did they go wrong?
If I were to drive down the street where I live, it would take…
Platform teams vary from company to company. At FloQast, the Platform team’s mission is to enable product teams to deliver innovative products faster and autonomously by improving the developer experience and reducing inter-team dependencies.
In this article, we will discuss how the Platform team at FloQast utilizes MongoDB to increase developer efficiency.
As FloQast continues to grow, we continue to create more engineering teams in order to provide more functionality for our customers. One common use case amongst each of these teams is the use of a message queue. …
In a previous post, J.C. talked about how we’re migrating to decoupled micro-frontends here at FloQast. We’re also working on a design and theme refresh 🎉 🎨, which affects several micro-frontends, the hub, and an internal UI library.
Interviews are The. Worst. There’s the pressure to have the right answer, the pressure to be a technical savant, while also having that je ne sais quoi to show how chill and cool you are.
It’s all the intensity of a first date, except with a paycheck on the line. No big deal, right? 😅
At FloQast, we knew that we not only wanted to hire the right people, but that we wanted to make the interview process better overall. Internally, we value transparency at all levels, and that holds true for our interview process. …
FloQast has a product called AutoRec, which helps accountants automatically reconcile transactions from two different sources. For about a year now, I’ve been the quality engineer assigned to the team responsible for the matching engine. This is the part of the AutoRec application that takes in those transactions and attempts to predict which ones reconcile, or, “match.”
Under the hood, we’re using machine learning to power the matchmaking. Most of my prior experience was with traditional web applications, so testing machine learning required a new way of thinking.
Think. Code. Deploy. Repeat.