We're very honored that you are considering joining us at Juniper Square to work on some hard problems with brilliant people from around the world 🙌 . Here's a bit of an overview on the interviewing process - we'll follow it loosely so let us know if you need (or suggest) any adjustments. Scroll down to review the process specific to each function. If you need any assistance or accommodations throughout the interview process, please reach out to your recruiter or coordinator.Â
We are using Zoom - make sure to get comfortable or acquainted with it. Check your camera and mic before joining the session. It is very likely we will use Zoom Whiteboards during the interviews. Make sure to connect via the desktop app (not the browser version)!
Recruiter Screen
This will be an Introduction to JSQ with your recruiter. You can expect the call to be 30 - 45min. This is an introduction, with open-ended questions to learn more about your experiences and skills. You will also get the chance to ask questions about Juniper and learn more about the different teams you could potentially work for.
Pre-Onsite (75 min)
Practical Assessment (45 min)
This interview will be with one of our engineers or managers
For software engineers, the first part will be spent on introductions and sharing a little more about our company and the team. We will also dive a little deeper into your technical expertise and background. The second part will be a technical assessment. An algorithm-based interview that will check for your fundamentals. We will be using CodeSignal. Note: You will be sharing your screen with your interviewer while you work in the CodeSignal environment.Â
Hiring Manager Chat (30 min) - For Senior SWEs and above
This will be a bit more of an Informal conversation with the hiring manager, although they will get to know you a better and ask a little about your background. This is a good conversation to ask any questions you have to this point and learn more about the team, Engineering, and the company.Â
Onsite (Virtual) Interview (4.5 - 5 hours)
We can either schedule this as a full day onsite with a break, or we can split this into multiple days.
Technical Rounds
Back End/Full Stack: Coding (45 min)
You will complete another coding question via CodeSignal. We will provide the link to you at the beginning of the interview and you will be sharing your screen with your interviewer while you work in the CodeSignal environment. If you are Interviewing for a Senior SWE role, you will also be asked an additional API question.Â
Back End/Full Stack: Data Architecture (45 min)
This time will be spent doing a system design challenge. We will share the type of system, and you will design it. You will come up with a list of functional and non-functional requirements, define expected capacity, and more.
Front End (Senior Level and Below): Coding and Data Architecture (90 min)
In this Interview, we will Introduce a problem, the designs, and the APIs. We will give you the opportunity to look through the code base and given data. You will think through your apporaoch and document services and components. We will think transition into CodeSignal to implement the requirements and designs.Â
Behavioral/Leadership Rounds
Hiring Manager (45 min)Â Â
This is another opportunity to meet the manager you would be working with.Â
(For Senior Level and Above) Cross Functional (30 min)Â
This will be with the Product Manager or Designer(s).This will be the most conversational panel, where you'll talk about your relationship building skills across teams.Â
(For Senior Level and Above) Executive (30 min)Â
This conversation will give you the chance to learn about the team in greater context with the Director of Engineering and/or the VP of Engineering. Think of this as less of an interview, and more of a conversation. They may cover topics around technical and people leadership.Â
Recruiter Wrap Up (15 min)Â
Quick catch up to discuss the interview panel, hear feedback from you, and discuss next steps.
Tools + Tips
When you are working on any of our technical questions, feel free to take a few minutes to make a plan before you jump into a problem. We also encourage you to share your thought process. For example, you can share any and all work you’re doing on your screen with the interview, as this can help us get a better picture of your thought processes and better equip us to provide guidance. If you are stuck, you can tell your interviewer and they can work with you – you can talk out loud or write down your thoughts. Please ask clarifying questions.Â
CodeSignal - is used for multiple coding exercises In the interview process, primarily for software and data engineers. Good place to practice some coding questions prior to the interview. Please create a login with CodeSignal in advance to the interview.
For Staff Software Engineers, the Coding Challenge (90 min) Onsite- you will be building either a Frontend or Backend Application, make sure to have Docker and a web framework installed (Flask, Django, FastAPI, Pyramid, etc). To make it easier for you and our team, make sure to have a DB setup (we use Postgres). But don’t limit yourself to only using Postgres if you don’t have experience with it. Set up your own DB and environment prior to the interview!
When you’re coding, make sure to think about production-ready code.Â
When it comes to the Architecture or System Design Challenge, always think about panning, designing, data schemas, APIs, security.
Recruiter Screen: Introduction to JSQ
This will be spent with your recruiter. You can expect the call to be 30 - 45min. This is an introduction, with open-ended questions to learn more about your experiences and skills. You will also get the chance to ask questions about Juniper and learn more about the different teams you could potentially work for.
Pre-Onsite (75 min)
You will get the opportunity to meet with the Engineering Manager for Data and an Engineer on the team. This can be back to back or separate days. Not expected to be in the order:Â
Practical Assessment (45 min)
This interview will be with one of our engineers on the team.
This will be a technical interview done on CodeSignal. The challenge is to solve 2 algorithmic database problem using SQL and then a brief python coding question. Completion of the first task is required to move forward with the second. However, completion of the second is not required - it will be more conversation based to discuss tradeoff and how you'd approach the problem.Â
Hiring Manager Chat (30 min)
This will be a bit more of an informal conversation with the hiring manager, although they will get to know you a better and ask a little about your background. This is a good conversation to ask any questions you have to this point and learn more about the team, Engineering, and the company.Â
Final Onsite (Virtual) Interview (3-4 hours)
We can either schedule this as a full day onsite with a break, or we can split this into multiple days. These are the interview panels that are included but not in this order:Â
Coding Challenge - Python (45 min): This is a leet-code style coding question on CodeSignal.Â
Data Architecture (45 min): This time will be spent doing a system design challenge, designing a data pipeline. You will use Excalidraw or Flowchart to create a system or data room.
Cross Functional (45 min): This will be with the Product Manager or Designer(s).This will be the most conversational panel, where you'll talk about your relationship building skills across teams.Â
Hiring Manager (45 min): This is another opportunity to meet the manager you would be working with. There will be a series of questions to dive deeper into your experience. Example: What's the most complex project you have completed to date?Â
(For Senior Level and Above) Executive (30 min): This conversation will give you the chance to learn about the team in greater context with the Director of Engineering. Think of this as less of an interview, and more of a conversation.Â
Recruiter Wrap Up (15 min): Quick catch up to discuss the interview panel, hear feedback from you, and discuss next steps
Tools + Tips:
When you are working on any of our technical questions, feel free to take a few minutes to make a plan before you jump into a problem. We also encourage you to share your thought process. For example, you can share any and all work you’re doing on your screen with the interview, as this can help us get a better picture of your thought processes and better equip us to provide guidance. If you are stuck, you can tell your interviewer and they can work with you – you can talk out loud or write down your thoughts.Â
Google - the best tool for when you're stuck on precise syntax.Â
CodeSignal - is used for our 1st technical phone screen. Good place to practice some coding questions prior to the interview.
Excalidraw - is a virtual collaborative whiteboard.
When you’re coding, make sure to think about production-ready code. Think about tradeoffs, read through the question and specs thoroughly, and most optimal solution.Â
When it comes to the Architecture or System Design Challenge, always think about planning, designing, data schemas, APIs, security.
Recruiter Screen: Introduction to JSQ
This will be spent with your recruiter. You can expect the call to be 30 - 45min. This is an introduction, with open-ended questions to learn more about your experiences and skills. You will also get the chance to ask questions about Juniper and learn more about the different teams you could potentially work for.
Technical Phone Screen (45 min)
This interview is generally with the hiring manager and is a discussion about your experience and some technical discussion.
Final Onsite (Virtual) Interview (3 - 3.5 hours)
We can either schedule this as a full day onsite with a break, or we can split this into multiple days.
Data Architecture (60 min)
This is an interactive scenario where you and one of our engineers will collaboratively build and evolve an expanding architecture.
Cross-Functional Engineering (45 min)
This is a conversation with a couple of engineers you would be interacting with in this role.
Cross-Functional Interview (45 min)
This is typically with some individuals from the Product team, to discuss some of our company values and more of your experience.Â
Hiring Manager Interview (45 min)
This is a deeper dive into past projects, along with some behavioral questions.Â
Recruiter Wrap Up (15 min)Â
Quick catch up to discuss the interview panel, hear feedback from you, and discuss next steps.
Recruiter Screen: Introduction to JSQ
This will be spent with your recruiter. You can expect the call to be 30 - 45min. This is an introduction, with open-ended questions to learn more about your experiences and skills. You will also get the chance to ask questions about Juniper and learn more about the different teams you could potentially work for.
Hiring Manager Interview (45 min)
This interview will be with the hiring manager to introduce yourselves, learn more about your background, and share more about the role.
Practical Assessment (45 min)
This is a case study with one of the designers.
Onsite (Virtual) Interview: Part One (2 hours)
We can either schedule this as a full day onsite with a break, or we can split this into multiple days.
Resume Review and Background (45 min)
In this conversation, you will meet with a product leader and dive deep into a past project or two from your resume so the team can learn more about your experience.Â
Product Demo and Design Exercise (45 min)
We will give you a demo of the core JSQ product touchpoints, followed by a discussion on how to improve a specific page or workflow.Â
Onsite (Virtual) Interview: Part Two (4.5-5 hours)
We can either schedule this as a full day onsite with a break, or we can split this into multiple days.
Portfolio Review (45 min)
This will be with the entire team and we will take some time going through your portfolio and asking questions. Each additional interview will be based on the portfolio review, with questions related to the team that the interviewer is on (ie. engineers will ask engineer-collaboration questions, etc.)
Hiring Manager (60 min)
Another opportunity to meet the hiring manager and get to know each other even better.Â
Design Peer (45 min)
You will meet another design colleague on the team and dig into a little more detail on your portfolio and some of the projects you have not talked about yet.Â
Engineering Cross Functional (30 min)
This is a more casual conversation to discuss previous projects and how you have approached collaborating with engineering in your roles. We will also get a better understanding of your technical acumen. This is a great opportunity to ask some more general questions you might have about JSQ.Â
Peer Design Exercise (45 min)
This will be a case study to give you an opportunity to show how you collaborate with product managers and how you think outside the box.Â
Executive Interview (45 min)
You will meet with a leader in the Product org and discuss more about our company’s mission and initiatives and then projects on our roadmap. This is a great time to ask more general questions about the business and our goals.Â
Recruiter Wrap Up (15 min)Â
Quick catch up to discuss the interview panel, hear feedback from you, and discuss next steps
Core competencies that we evaluate for Product Managers:
Problem-solving ability of complex problems
Strategic and commercial mindset
UX focus and sensibilities
Technical acumen working with software engineering
Â
Here is an overview of the interview process and what you can expect:
Recruiter Screen: Introduction to JSQ (30 min)
Overview of Juniper Square and the role. Be prepared to walk us through your experience, while also asking questions about Juniper Square’s business, culture, and values.
Hiring Manager Screen (30 min)
A hiring manager will ask about your experience based on the resume you provided to determine fit for the team and role, as well as do a deep dive into all things Juniper Square.
Practical Assessment/Case Studies (45 min)
This is in part a behavioral case study where you will discuss a complex project where you’ve had to make some trade-offs and overcome challenges. Lots of “Tell me about…” questions. The interviewer will then present a small product management case study for the two of you to work through together.
Virtual Onsite Interview
Cross Functional Interview (45 min)
You will be with a leader on our software engineering team to talk about your challenges and successes working with technical teams.
Hiring Manager Onsite (60 min)
A career and resume deep dive, and any remaining questions to be answered about Juniper Square.
UX Design Interview (45 min) - If applicable for some roles
Discuss design team and design processes that you’ve had experience with. Review past projects with a focus on exploring your design choices and collaboration with designers.
Executive Interviews (30-45 min)
A career and resume deep dive, and any remaining questions to be answered about Juniper Square, some focus on values alignment. You will discuss how your experience would fit in with the role.
Recruiter Wrap Up (15 min)Â
Quick catch up to discuss the interview panel, hear feedback from you, and discuss next steps
Here is an overview of the interview process and what you can expect:
Recruiter Screen: Introduction to JSQ (30 min)
The recruiter will share an overview of the company, role, and team and will ask questions to learn more about your background and career goals.
Be prepared to walk us through your experience in QA, while also asking questions about Juniper Square’s business, culture, and values.
Hiring Manager Chat (45 min)Â
This will be a bit more of an Informal conversation with the Hiring Manager, although they will get to know you better and ask about your background and interest in role.
This is a good opportunity to ask any questions you have to this point and learn more about the team, role and the company.Â
If all goes well, we would proceed to the technical screen stage.
Technical Screen (45 min)Â
This will be a technical conversation with a QA Engineer to assess your test cases writing skills (manual QA) or coding skills (QA automation). It will depend on if you are interviewing for a manual or automation role.Â
If time permits, the QA Engineer will ask a few follow up questions to assess values alignment.
Onsite (Virtual) Interview (2.5 - 3 hours)
We can either schedule this as a full day onsite with a break, or we can split this into multiple days.
Architectural (45 min)
You will go through a demo with a QA Engineer(s) and then sketch out a high level test plan.Â
If time permits, the QA Engineer will ask a few follow up questions to assess values alignment.
Hiring Manager Interview (45 min)
You will meet with the Hiring Manager again. This will be a formal interview where they will dive deeper into your QA skills and assess for role alignment.Â
Cross Functional Interview (30 min)
You will meet with a Product Manager. This will be mostly conversational, where you'll talk about your relationship building skills across teams.
Executive Interview (30 min)
You will meet with our head of QA. This conversation will focus on your ability to problem solve, collaborate with teams, and showcase your QA skills.
Wrap Up (5-10 min)
This is a quick catch up with the Recruiter or Recruiting Coordinator to discuss the interview panel, hear feedback from you, and discuss next steps.
Interview Tips
Come prepared to ask any questions for each individual you are meeting with. This will give you an opportunity to hear different perspectives on the team, company, business model, etc!
When you are working on any of our technical questions, feel free to take a few minutes to make a plan before you jump into a problem. We also encourage you to share your thought process. For example, you can share any and all work you’re doing on your screen with the interview, as this can help us get a better picture of your thought processes and better equip us to provide guidance. If you are stuck, you can tell your interviewer and they can work with you – you can talk out loud or write down your thoughts. Please ask clarifying questions.Â