Skip to content

Instantly share code, notes, and snippets.

@wilmoore
Last active August 3, 2024 21:33
Show Gist options
  • Select an option

  • Save wilmoore/aade8a570e138fe6e24f180ca5b867f7 to your computer and use it in GitHub Desktop.

Select an option

Save wilmoore/aade8a570e138fe6e24f180ca5b867f7 to your computer and use it in GitHub Desktop.
Software Engineering :: Career :: Job :: Application :: Healthfirst :: 20210616

Software Engineering :: Career :: Job :: Application :: Healthfirst :: 20210616

⪼ Made with 💜 by Polyglot.

related

Healthfirst Job Application 20210616

Thursday, 9/16 from 10-12p (1:00-3:00 EST)

Please plan on this interview running roughly ~2 hours long. Please find a good area you can concentrate and also remember to be presentable and well prepared for this conversation. This will be video so make sure that you are dressed professionally.

Details from a member of a team:

  • It is important to know the job description very well and make sure to look at the tools asked. Focus your conversation on the things there (Please also think back to your conversation with Joe for pointers on what is most important!)
  • If there is something about node, and you know something about node, be ready to answer that and go in depth. Explain your experiences/work as to why you're qualified and build your credibility.
  • They want to find people that match their resume so be yourself and dig into your prior experience as it relates to what they’re looking for.
  • Make sure you can show a depth of knowledge with node and API writing, dig in enough and ask them if your answer covers what they asked or if there is more depth that they want.

Core areas to study: Node and API development. Also, a good portion of their time is developing microservices so understanding that concept is something you’ll want to be prepared to talk about. If you don’t have this experience then come up with similar examples based on your experience

This final of the interview is slated to be 2-hours long comprised of 2 “rounds” of interviews. Please be prepared for a virtual whiteboarding session; the team will have you solve some problems and please prepare for them to dig into your logic and reasoning behind certain decisions you made, etc. They will also talk about your background again. Prepare for them to ask you questions about how you work on a team, etc. The team portion of this round of interviews will be important… they typically like to weed out “lone wolf” type of developers as they work very closely with one another and want someone who will thrive in this type of environment. The second round of interviews will be comprised of design, algorithm and whiteboarding questions/moments. They will most likely ask you some situational/HR-type questions during this round as well.

Participants


Design Session


API Layer

Loopback

Backend

PostgreSQL

Profiles

  • Customer (person): requesting to place an order
  • Scanner (device): adding inventory in warehouse
  • Order System (system): requesting to API for inventory counts

Scanner

  • Needs access to the POST /products/{:productId} in order to add inventory

Order System

  • Order system needs access to GET /{:productId}/count
[ serial # ] [ count++ ]
inventory (immutible records)
1 [ serial # ] [ qty ] [timestamp]
2 [ serial # ] [ qty ] [timestamp]
3 [ serial # ] [ qty ] [timestamp]
  • id (PK)
  • serial?
  • type_id (palette, box, individual) (FK)
  • qty
  • timestamp

I would use a materialized view to get the inventory since there will need to be a way to look at inventory (received) against orders places (which decrements inventory).

High Level Design

Shipment Received Endpoints

shipment schema

could be different types within shipment, but for now, we are just looking at the package

  • id (PK)
  • serial?
  • type_id (palette, box, individual) (FK)
  • qty
  • timestamp
  • warehouse_id (FK)

Store coordinates in the warehouse table so we can optimize for where best to receive shipments.

GET /inventory_count
product schema
  • id (PK)
  • serial?
  • type_id (palette, box, individual) (FK)
POST /inventory_products

Job Description

Looking for a Node full stack developer to join a small development team. This will be a contract to hire role and will convert to FTE depending upon team fit. Candidate can be fully remote for this role, they will just need to be comfortable working PST hours.

Healthfirst is the leading provider of emergency medical and compliance products to healthcare practitioners for over 40 years. From essential medications, devices and supplies to advanced services, training and software, our mission is to guarantee the right compliance products, services and programs are there whenever and wherever our client needs them.

We are looking for a senior developer to join our IT development team. The development team mission is to provide the best customer experience possible, as well as building the architecture and applications needed to support the growth of our business.

Example of an application you’ll work on is OnTraQ, a web-based application allowing healthcare providers to follow and manage their compliance based on the status of products we ship and track for them.

This team member will be tasked with automating many of the applications that the Warehouse and Supply Chain work with.

Looking for candidates with the below qualifications:

Must have:
  1. Industry experience in designing and building ReST based API from the ground up.
  2. Strong experience with Node
  3. Strong experience with Node
Preferred:
  1. Experience in RFID technologies
  2. Experience in supply chain or warehouse management systems
Nice to have:
  1. Angular/React experience
  2. Validation system experience is a plus
Enterprise Req Skills
  • rest api
  • sql server
  • microservices
  • node.js
  • javascript
  • react
  • angular
Job Title

Full Stack Developer

Top Skills Details
  • Industry experience in designing and building REST based API from the ground up
  • Strong Node development experience
  • Strong Javascript development experience
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment